I've run into the problem described at
http://courier-mail-server.10983.n7.nabble.com/courieresmtp-quot-No-such-file-or-directory-quot-td11972.html
 and have a couple of questions.  First, whence comes the "No such file or 
directory" response?  This doesn't show up in the DSNs sent to sender.  Is this 
coming from the misconfigured receiving server, or from Courier?

Second, is Courier unique in exciting this particular config bug?
Surely many or most sending SMTP servers attempt to use STARTTLS if the
receiving server advertises support for it, and the mail admins of the
problem receiving Exchange server would doubtless become aware of such a
problem and fix it.

I put an adquate band-aid on the problem by adding the appropriate line
to esmtproutes, as suggested in the above link.  This isn't the first
time I've had to do this, but it's been a while.

-- 
Lindsay Haisley       | "The difference between a duck is because
FMP Computer Services |    one leg is both the same"
512-259-1190          |     - Anonymous
http://www.fmp.com    |


------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to