Re: [courier-users] Misconfigured Exchange Servers

2013-03-26 Thread Steve Shockley
On 3/21/2013 8:10 PM, Lindsay Haisley wrote: Bypassing a distribution's package management system always seems to introduce issues. Why not just use the OS packaging system for your new version? I don't know much about building for apt, but it seems you should be able to build and package

Re: [courier-users] Misconfigured Exchange Servers

2013-03-22 Thread Alessandro Vesely
On Fri 22/Mar/2013 01:10:35 +0100 Lindsay Haisley wrote: 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 I'm running Courier 0.66.1 as distributed with Ubuntu Server 12.04 LTS, Ignoring

Re: [courier-users] Misconfigured Exchange Servers

2013-03-22 Thread Lindsay Haisley
On Thu, 2013-03-21 at 19:56 -0400, Sam Varshavchik wrote: 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? From Courier. Shouldn't happen in

Re: [courier-users] Misconfigured Exchange Servers

2013-03-22 Thread Sam Varshavchik
Lindsay Haisley writes: On Thu, 2013-03-21 at 19:56 -0400, Sam Varshavchik wrote: 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? From Courier.

[courier-users] Misconfigured Exchange Servers

2013-03-21 Thread Lindsay Haisley
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

Re: [courier-users] Misconfigured Exchange Servers

2013-03-21 Thread Jan Ingvoldstad
On Thu, Mar 21, 2013 at 6:49 PM, Lindsay Haisley fmouse-cour...@fmp.com wrote: 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

Re: [courier-users] Misconfigured Exchange Servers

2013-03-21 Thread Sam Varshavchik
Lindsay Haisley writes: 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

Re: [courier-users] Misconfigured Exchange Servers

2013-03-21 Thread Lindsay Haisley
On Thu, 2013-03-21 at 19:56 -0400, Sam Varshavchik wrote: Lindsay Haisley writes: 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

Re: [courier-users] Misconfigured Exchange Servers

2013-03-21 Thread Sam Varshavchik
Lindsay Haisley writes: On Thu, 2013-03-21 at 19:56 -0400, Sam Varshavchik wrote: Lindsay Haisley writes: From Courier. Shouldn't happen in the current version; there was a bug that was fixed, some time ago, where the wrong error message came out. I'll have to double-check that it's no

Re: [courier-users] Misconfigured Exchange Servers

2013-03-21 Thread Lindsay Haisley
On Thu, 2013-03-21 at 20:32 -0400, Sam Varshavchik wrote: Courier is probably not the only mail server that fails a message if STARTTLS fails. Other mail servers probably ignore it, and proceed to send the message without using encryption. Can Courier be configured to do this? Or