250-AUTH LOGIN PLAIN not advertised. Why?

2015-11-22 Thread Mufit Eribol
Hello, I have been running postfix at a small company for years without any problem. For some reason, now I cannot get 250-AUTH LOGIN PLAIN when telnetting to port 25. It may be due to a change in the upgraded packages or a misconfiguration by me. Probably, I "fixed" something which is not br

Re: 250-AUTH LOGIN PLAIN not advertised. Why?

2015-11-22 Thread Patrick Ben Koetter
* Mufit Eribol : > Hello, > > I have been running postfix at a small company for years without any > problem. For some reason, now I cannot get 250-AUTH LOGIN PLAIN when > telnetting to port 25. It may be due to a change in the upgraded > packages or a misconfiguration by me. Probably, I "fixed" s

Re: 250-AUTH LOGIN PLAIN not advertised. Why?

2015-11-22 Thread Mufit Eribol
On 22.11.2015 22:44, Patrick Ben Koetter wrote: * Mufit Eribol : Hello, I have been running postfix at a small company for years without any problem. For some reason, now I cannot get 250-AUTH LOGIN PLAIN when telnetting to port 25. It may be due to a change in the upgraded packages or a misc

Re: 250-AUTH LOGIN PLAIN not advertised. Why?

2015-11-22 Thread Viktor Dukhovni
On Sun, Nov 22, 2015 at 09:43:46PM +0200, Mufit Eribol wrote: > I have been running postfix at a small company for years without any > problem. For some reason, now I cannot get 250-AUTH LOGIN PLAIN when > telnetting to port 25. It may be due to a change in the upgraded packages or > a misconfigur

Re: 250-AUTH LOGIN PLAIN not advertised. Why?

2015-11-22 Thread Mufit Eribol
On 23.11.2015 00:10, Mufit Eribol wrote: On 22.11.2015 22:44, Patrick Ben Koetter wrote: * Mufit Eribol : Hello, I have been running postfix at a small company for years without any problem. For some reason, now I cannot get 250-AUTH LOGIN PLAIN when telnetting to port 25. It may be due to

Feature: postqueue JSON output

2015-11-22 Thread Wietse Venema
This weekend I added preliminary support for JSON-formatted queue listings. See below for a fragment from the postqueue manpage. Now, a Postfix queue may contain millions of messages, and each message may contain lots of recipients. A robust application would not read the entire JSON queue listin

LMTP TLS delivery failure with 3.0.3 (regression from 2.11.4)

2015-11-22 Thread Quanah Gibson-Mount
I'm currently testing out migrating to postfix 3.0.3. However, LMTP delivery is failing due to: Nov 22 20:40:56 zre-ldap002 postfix/lmtp[20350]: SSL_connect error to zre-ldap002.eng.zimbra.com[10.137.242.52]:7025: -1 Nov 22 20:40:56 zre-ldap002 postfix/lmtp[20350]: warning: TLS library proble

Re: LMTP TLS delivery failure with 3.0.3 (regression from 2.11.4)

2015-11-22 Thread Quanah Gibson-Mount
--On Sunday, November 22, 2015 6:49 PM -0800 Quanah Gibson-Mount wrote: Setting lmtp_tls_security_level to none allows mail delivery to succeed. Setting lmtp_tls_CApath fixed this (although that wasn't necessary in 2.11.4). Sorry for the noise. :) --Quanah -- Quanah Gibson-Mount Platfo

Re: LMTP TLS delivery failure with 3.0.3 (regression from 2.11.4)

2015-11-22 Thread Viktor Dukhovni
On Sun, Nov 22, 2015 at 06:49:51PM -0800, Quanah Gibson-Mount wrote: > I'm currently testing out migrating to postfix 3.0.3. However, LMTP > delivery is failing due to: Same OpenSSL library??? Seems implausible. > Nov 22 20:40:56 zre-ldap002 postfix/lmtp[20350]: SSL_connect error to > zre-ldap

Re: LMTP TLS delivery failure with 3.0.3 (regression from 2.11.4)

2015-11-22 Thread Viktor Dukhovni
On Sun, Nov 22, 2015 at 06:57:47PM -0800, Quanah Gibson-Mount wrote: > --On Sunday, November 22, 2015 6:49 PM -0800 Quanah Gibson-Mount > wrote: > > >Setting lmtp_tls_security_level to none allows mail delivery to succeed. > > Setting lmtp_tls_CApath fixed this (although that wasn't necessary i

Re: LMTP TLS delivery failure with 3.0.3 (regression from 2.11.4)

2015-11-22 Thread Quanah Gibson-Mount
--On Monday, November 23, 2015 3:13 AM + Viktor Dukhovni wrote: Setting lmtp_tls_CApath fixed this (although that wasn't necessary in 2.11.4). Sorry for the noise. :) I am at a loss to explain what lmtp_tls_CApath has to do with this, most likely you just happened to flush sufficiently

Re: LMTP TLS delivery failure with 3.0.3 (regression from 2.11.4)

2015-11-22 Thread Viktor Dukhovni
On Sun, Nov 22, 2015 at 07:29:56PM -0800, Quanah Gibson-Mount wrote: > --On Monday, November 23, 2015 3:13 AM + Viktor Dukhovni > wrote: > > >>Setting lmtp_tls_CApath fixed this (although that wasn't necessary in > >>2.11.4). Sorry for the noise. :) > > > >I am at a loss to explain what lmt

Re: LMTP TLS delivery failure with 3.0.3 (regression from 2.11.4)

2015-11-22 Thread Quanah Gibson-Mount
--On Monday, November 23, 2015 3:36 AM + Viktor Dukhovni wrote: On Sun, Nov 22, 2015 at 07:29:56PM -0800, Quanah Gibson-Mount wrote: --On Monday, November 23, 2015 3:13 AM + Viktor Dukhovni wrote: >> Setting lmtp_tls_CApath fixed this (although that wasn't necessary in >> 2.11.4).

Re: LMTP TLS delivery failure with 3.0.3 (regression from 2.11.4)

2015-11-22 Thread Viktor Dukhovni
On Sun, Nov 22, 2015 at 07:29:56PM -0800, Quanah Gibson-Mount wrote: > And hm, you're right, it is a different OpenSSL version too (1.0.1p vs > 1.0.1m). If these are not vendor builds that mask the true upstream version then the only plasibly relevant change in the relese notes from 1.0.1m to 1.0

Re: LMTP TLS delivery failure with 3.0.3 (regression from 2.11.4)

2015-11-22 Thread Viktor Dukhovni
On Mon, Nov 23, 2015 at 03:51:24AM +, Viktor Dukhovni wrote: > If these are not vendor builds that mask the true upstream version > then the only plasibly relevant change in the relese notes from > 1.0.1m to 1.0.1p is: > > Changes between 1.0.1m and 1.0.1n [11 Jun 2015] > > *) Rejec

Re: socket: malformed response

2015-11-22 Thread Vicki Brown
How many times do I need to say that /etc/postfix IS postfix. > On Nov 20, 2015, at 04:24, Wietse Venema wrote: > > Viktor Dukhovni: >> On Thu, Nov 19, 2015 at 03:26:27PM -0800, Vicki Brown wrote: >> >>> The only program that uses /usr/local/cutedge/postfix/etc is.. postfix. >> >> Well, the re

Re: socket: malformed response

2015-11-22 Thread Vicki Brown
command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix manpage_directory = /usr/share/man queue_directory = /private/var/spool/postfix readme_directory = /usr/share/doc/postfix sample_directory = /usr/share/doc/postfix/examples This installation has b

Re: socket: malformed response

2015-11-22 Thread Viktor Dukhovni
On Sun, Nov 22, 2015 at 08:45:48PM -0800, Vicki Brown wrote: > How many times do I need to say that /etc/postfix IS postfix. Zero, instead you need to listen. You're here to get help from folks who understand Postfix deeply. You can get help, but only if you start listening, and stop objecting

Re: socket: malformed response

2015-11-22 Thread Viktor Dukhovni
On Sun, Nov 22, 2015 at 08:51:46PM -0800, Vicki Brown wrote: > command_directory = /usr/sbin > config_directory = /etc/postfix > daemon_directory = /usr/libexec/postfix > manpage_directory = /usr/share/man > queue_directory = /private/var/spool/postfix > readme_directory = /usr/share/doc/postfix >

Re: socket: malformed response

2015-11-22 Thread Peter
On 11/23/2015 05:51 PM, Vicki Brown wrote: > Also, from my discussion with him, Bernard Teo does seem to know what he's > doing. I suggest you type "man postfix", scroll down to the bottom and look at the list of authors, then compare that list to the two people who have been trying to help you h

Re: 250-AUTH LOGIN PLAIN not advertised. Why?

2015-11-22 Thread Mufit Eribol
On 23.11.2015 00:16, Viktor Dukhovni wrote: On Sun, Nov 22, 2015 at 09:43:46PM +0200, Mufit Eribol wrote: I have been running postfix at a small company for years without any problem. For some reason, now I cannot get 250-AUTH LOGIN PLAIN when telnetting to port 25. It may be due to a change i