Mark,
In light of your finding about TLS, I suspect the problem is with
mis-configured SMTP servers advertising TLS capability, but then choking when
Courier tries to establish a TLS session with the mis-configured server.
Usually, the problem is that the server is missing its certificate.
I seem to remember that Sam added an option to selectively disable TLS on a
per-domain basis, and perhaps someone else on this list can remember which man
page it's in.
Happy New Year.
William
Mark Robinson wrote:
> On Dec 29, 2006, at 10:02 AM, Mark Robinson wrote:
>
>
>>On Dec 28, 2006, at 9:51 PM, Sam Varshavchik wrote:
>>
>>
>>>Mark Robinson writes:
>>>
>>>
>>>>Hi all,
>>>>I am using courier 0.52.2_1 on freebsd 6.1
>>>>Email to certain mail servers is being delayed (all day so far).
>>>>The info in the maillog is:
>>>>Dec 28 21:08:38 mail courieresmtp: id=00033D1E.4593F09C.
>>>>0000E967,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>:
>>>>Connection unexpectedly closed by remote host.
>>>>Dec 28 21:08:38 mail courieresmtp: id=00033D1E.4593F09C.
>>>>0000E967,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>,status:
>>>>deferred
>>>>Dec 28 21:08:38 mail courieresmtp: id=00033D1E.4593F09C.
>>>>0000E967,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>:
>>>>Connection unexpectedly closed by remote host.
>>>>Dec 28 21:08:38 mail courieresmtp: id=00033D1E.4593F09C.
>>>>0000E967,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>,status:
>>>>deferred
>>>>The same email will make it to other mail servers at different
>>>>clients without any problem.
>>>>I have telnet'd directly into the delayed mail servers and
>>>>received their 220.
>>>>Any ideas?
>>>
>>>Yes. Exactly how did you manage to telnet to noname.net's mail
>>>server, since this domain doesn't have one?
>>>
>>>So, to summarize: you are having problems sending mail to some mail
>>>server. Ok, fine.
>>>
>>>But, rather then give full details, you choose to replace real data
>>>in your logs with random made-up nonsense. Since all the key data
>>>from the logs have been ommited, the only real data that's left are
>>>the exact times when you've had those errors, which really doesn't
>>>mean much.
>>>
>>>So, since you've chosen to omit all the key data, you'll just have
>>>to figure it on your own. You can't really expect much help when
>>>the essence of your question is, essentially "I can't send mail to
>>>some random mail server."
>>>
>>>Telnetting to this mysterious mail server only proves that the
>>>initial connection succeeds. 'Connection unexpectedly closed'
>>>indicates that the remote host closed the connection at some point
>>>later in the process, so you'll need to send the exact sequence of
>>>commands Courier would normally send, when attempting to deliver
>>>mail to this mail server, to find out which specific command the
>>>remote server is barfing on.
>>>
>>
>>Sorry Sam. I replied to you directly instead of replying back to the
>>mailing list.
>>ok below is the text from a telnet session with one of the
>>problematic servers. I again replaced my client info with fake info.
>>If I am leaving out an SMTP command or this isn't the exact way that
>>Courier talks to other mail servers, please let me know and I will
>>retry the telnet session.
>>Thanks
>>
>>su-2.05b# telnet CLIENT1.COM.S8A1.PSMTP.com 25
>>Trying <client1.com ip address>...
>>Connected to CLIENT1.COM.S8A1.PSMTP.com.
>>Escape character is '^]'.
>>220 Postini ESMTP 51 y6_8_7c0 ready. CA Business and Professions
>>Code Section 17538.45 forbids use of this system for unsolicited
>>electronic mail advertisements.
>>MAIL FROM: <[EMAIL PROTECTED]>
>>250 Ok
>>RCPT TO: <[EMAIL PROTECTED]>
>>250 Ok
>>DATA
>>354 Feed me
>>Hi Jeremy. I am having trouble emailing you. Can you respond to this
>>to let me know you received it? Thanks, Mark
>>.
>>250 Thanks
>>quit
>>221 Catch you later
>>Connection closed by foreign host.
>>su-2.05b#
>>
>
>
> please ignore previous response. I sent original message from the
> mail server that was having problems and received WARNING: delayed
> mail from the courier mailing list server. I have since fixed this
> problem by changing ESMTP_USE_STARTTLS=0 in the courierd config file
> and restarting courier.
> heh, after fixing it I flushed the message and the original delayed
> email went through.
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> courier-users mailing list
> [email protected]
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
