Re: [courier-users] Misconfigured Exchange Servers
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 software from source that keeps all the package dependencies, unless the newer Courier version requires a newer library version or something. I'm guessing it's the sort of thing that's a hassle to do once, but not too bad once you get it documented. -- Own the Future-Intelreg; Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Misconfigured Exchange Servers
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 STARTTLS was announced in Courier 0.67.0 http://courier-mail-server.10983.n7.nabble.com/New-releases-of-Courier-packages-tc11544.html -- 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
Re: [courier-users] Misconfigured Exchange Servers
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 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 broken again. So I take it that there isn't actually a missing file or directory, yes? -- Lindsay Haisley | Behold! Our way lies through a FMP Computer Services |dark wood whence in which 512-259-1190 | weirdness may wallow!” http://www.fmp.com| --Beauregard -- 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
Re: [courier-users] Misconfigured Exchange Servers
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. 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 broken again. So I take it that there isn't actually a missing file or directory, yes? Nope. Just a bug in reporting an accurate error message. pgpBl9oWmg6y6.pgp Description: PGP signature -- 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
[courier-users] Misconfigured Exchange Servers
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
Re: [courier-users] Misconfigured Exchange Servers
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 problem receiving Exchange server would doubtless become aware of such a problem and fix it. I don't know much about other servers, but Exim seems to handle this automagically. Exim's documentation has the following to say (http://www.exim.org/exim-html-current/doc/html/spec_html/ch-encrypted_smtp_connections_using_tlsssl.html#SECID185): When the server host is not in hosts_require_tls, Exim may try to deliver the message unencrypted. It always does this if the response to STARTTLS is a 5xx code. For a temporary error code, or for a failure to negotiate a TLS session after a success response code, what happens is controlled by the tls_tempfail_tryclear option of the smtp transport. If it is false, delivery to this host is deferred, and other hosts (if available) are tried. If it is true, Exim attempts to deliver unencrypted after a 4xx response to STARTTLS, and if STARTTLS is accepted, but the subsequent TLS negotiation fails, Exim closes the current connection (because it is in an unknown state), opens a new one to the same host, and then tries the delivery unencrypted. Exim also provides a blacklist for bad hosts, so that you can do the same as Courier does. This seems like a very sane way to handle it, which would explain why we get so few complaints about lost mail to Exchange servers at $workplace, where we use Exim for authenticated outgoing SMTP. Doing it the Courier way ensures that there are fewer tries and retries for a given session to a misconfigured host, but IMHO, Courier developers might want to look into doing it similarly to Exim when there are no particular configuration options set for a given host. -- Jan -- 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
Re: [courier-users] Misconfigured Exchange Servers
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 the DSNs sent to sender. Is this coming from the misconfigured receiving server, or from Courier? 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 broken again. 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. The admins you mention are generally clueless. Nobody looks at their logs. 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. pgpKsaonLDeaX.pgp Description: PGP signature -- 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
Re: [courier-users] Misconfigured Exchange Servers
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 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 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 broken again. I'm running Courier 0.66.1 as distributed with Ubuntu Server 12.04 LTS, which is probably not the latest. I'd hate to have to abandon and freeze the packaged version in favor of building Courier from a more recent source, but it wouldn't be the first time I've had to do that. Bypassing a distribution's package management system always seems to introduce issues. 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. 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 would this be a feature request? -- Lindsay Haisley | The only unchanging certainty FMP Computer Services |is the certainty of change 512-259-1190 | http://www.fmp.com| - Ancient wisdom, all cultures -- 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
Re: [courier-users] Misconfigured Exchange Servers
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 broken again. I'm running Courier 0.66.1 as distributed with Ubuntu Server 12.04 LTS, which is probably not the latest. I'd hate to have to abandon and freeze the packaged version in favor of building Courier from a more recent source, but it wouldn't be the first time I've had to do that. Bypassing a distribution's package management system always seems to introduce issues. Well, if that's your only issue, it's not worth the hassle to go on your own. 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 would this be a feature request? No, Courier cannot be configured to do that. I'm thinking about changing that, but, of course, it would require an upgrade for you, at some point. pgpE6lUdyUwSQ.pgp Description: PGP signature -- 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
Re: [courier-users] Misconfigured Exchange Servers
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 would this be a feature request? No, Courier cannot be configured to do that. I'm thinking about changing that, but, of course, it would require an upgrade for you, at some point. Upgrading Courier from source is entirely doable, and the built version can match the installed version quite well, thanks to courier-config. Most of the issues resulting from stepping outside the package management system are the result of dependencies, either other packages depending on the custom-built one, or on which the custom-built one depends. I don't imagine there's much in Ubuntu Server that depends on Courier, but Courier's dependencies would have to be managed manually. -- Lindsay Haisley | Humor will get you through times of no humor FMP Computer Services | better than no humor will get you through 512-259-1190 | times of humor. http://www.fmp.com|- Butch Hancock -- 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
