I opened a ticket with EdgeWave, to see if they were aware of any
particular problems talking to Exim. Their response was this:
Per RFC 2821, If your mail server is issuing a 250 response at the end of
> the smtp session then that means that the message was successfully
> delivered. (as far as the sender is concerned).
>
> I am not aware of any general issues with sending mail to exim mail
> servers.
I do agree they have a point... when Exim sends the 250 OK... shouldn't
Exim then deposit the message into the local mailbox or whatever needs to
happen at this point? Doesn't it seem wrong for Exim to send a 250 OK, but
not have actually accepted the message?
- Scott
On Tue, Feb 21, 2012 at 12:00 AM, Scott Neader <scott@???> wrote:
> FYI, I'm seeing a number of timeouts from a mail provider called "
> redcondor.net" and sure enough, when I telnet to port 25:
>
> 220 smtp450.redcondor.net ESMTP EdgeWave mag4000e
>
>
> LOL... http://redcondor.com/ -- owned "by EdgeWave".
>
> I guess the question is... is it something EdgeWave is doing, or is it
> Exim?
>
> We sure don't get along, that is for sure.
>
> - Scott
>
>
> On Mon, Feb 20, 2012 at 11:54 PM, Scott Neader <scott@???> wrote:
>
>>
>> Set your timeout to 4 minutes instead of two minutes and see what, if
>>> anything, changes.
>>>
>>
>> I changed the timeout to 240 seconds, with no change... it just hangs for
>> 240 seconds after I send the 250 OK, and then I disconnect due to timeout.
>>
>> Make sure there are no Cisco PIX or ASA devices with "smtp fixup" or
>>> "inspect smtp" switched on between you and the remote site.
>>
>>
>> I'm told they do not have a PIX or ASA, but they do have a series 7200
>> router... it is capable of "smtp fixup", so I am asking them to ask their
>> router folks if it is enabled.
>>
>> As another data point... I remembered having this problem with another
>> ISP a few months back. I just telnet'd to port 25 on their server and
>> guess what popped up in their initial greeting?:
>>
>>
>>> ESMTP EdgeWave mag4000
>>
>>
>> Yep... so here we have two of these "EdgeWave" mail servers that I can't
>> get mail from (but I can send them mail fine).
>>
>> Anyone out there interested in looking at the package capture .pcap file
>> I have?
>>
>> I will try to look through my logs for "SMTP command timeout" and try to
>> sift out the obvious spam zombie PCs and look for real mail servers, then
>> try to see if there is are more EdgeWave issues out there. Maybe it's
>> something?
>>
>> - Scott
>>
>> On Sat, Feb 18, 2012 at 4:51 AM, W B Hacker <wbh@???> wrote:
>>
>>> 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.
>>>>
>>>> Here's the funny part... 120 seconds later, my Exim server sends a "421
>>>> my.servername.net: SMTP comamnd timeout - closing connection" packet,
>>>> and
>>>> their server sends the ACK for that also, then my server sends the "FIN,
>>>> ACK", and their server sends the ACK, and the connection is closed.
>>>>
>>>> Any ideas what is going on?
>>>>
>>>> - Scott
>>>
>>>
>
