著者: Scott Neader 日付: To: David Woodhouse CC: exim-users 題目: Re: [exim] SMTP command timeout on connection - how to troubleshoot
Hi David. First, I wasn't obfuscating the ID, I was just saying "we send
our 250, they ack". Didn't think the actual log messsage and ID would be
important enough to paste into the email...
Anyway... you are right... these messages ARE getting delivered. I was
looking at log messages based on IP, and only seeing the connection, data
and delivery messages, but I did not look at how Exim dealt with the
message... when looking by ID as you have suggested, it shows the messages
are being delivered into the local mailbox.
The mystery still stands as to why I am seeing all these SMTP command
timeouts from just these "EdgeWave" mail servers. If the EdgeWave server
has received our "250 OK" message, and their packet capture shows they have
received it, and they have sent an ACK, then why don't they DISCONNECT?
I have started a ticket with EdgeWave, to see if they have any interest in
figuring this out.
Regarding a packet capture on my side, I have to admit, I have never done
it on command-line Linux before (done many on Windoze via
Ethereal/WireShark), so I will have to research that.
Thanks for the input -- much appreciated!!
- Scott
On Wed, Feb 22, 2012 at 4:42 AM, David Woodhouse <dwmw2@???>wrote:
> On Fri, 2012-02-17 at 16:08 -0600, Scott Neader wrote:
> > I was able to get the remote mail server admin to send me a packet
> capture
> > in .pcap format (if anyone wants to see it, I'd be glad to share, nothing
> > confidential in the cap).
> >
> > What I see is that our Exim server sends the "250 OK id=xxxxxxx" message
> > just fine, and within a few ms, their server sends an ACK packet.
>
> Hm, if the message they see is really 'OK id=xxxxxxx' with a real
> Exim-like queue ID (why the hell do you feel the need to obfuscate a
> local queue ID, anyway?) then it's unlikely to have been generated
> anywhere but your server.
>
> If you search your logs for that specific ID, what do you see?
>
> If you do a capture on *your* end, does it match what they see at their
> end?
>
> --
> dwmw2
>
