Re: Logging sender and recipient when message size exceeds fixed limit

2016-06-21 Thread Wietse Venema
[google ignoring SIZE in EHLO response] I believe that initially Postfix has done that as well, because the number as announced might not be parseable with system library routines (for example bigger than 4GB, at a time that Postfix typically ran on 32-bit systems). Later, Postfix got its own off

Postfix - SRS - Address rewriting

2016-06-21 Thread Pascal Maes
Hello, We are using the SRS mechanism to avoid problem with the SPF when we forward emails to external servers. We have followed the documentation from postsrsd, in main.cf : sender_canonical_maps = proxy:tcp:127.0.0.1:10001 sender_canonical_classes = envelope_sender recipient_canonical_maps

Re: Logging sender and recipient when message size exceeds fixed limit

2016-06-21 Thread Mick
Hi Bill, Shameful admission : I didn't realise that a sending machine using EHLO could declare the message size in the 'Mail from:'. I have been able to replicate the log behaviour using Telnet using an example in RFC1870. After issuing a EHLO command; >> mail from: SIZE=234567895 << 452 4.

Re: Postfix - SRS - Address rewriting

2016-06-21 Thread Wietse Venema
Pascal Maes: > Hello, > > > We are using the SRS mechanism to avoid problem with the SPF when > we forward emails to external servers. > > We have followed the documentation from postsrsd, in main.cf : Suggestion: 1) Open your preferred search engine. 2) Enter search terms: srs milter.

Re: Different SMTP AUTH options and credentials for different clients

2016-06-21 Thread Rob Maidment
On 31 May 2016 at 17:21, Viktor Dukhovni wrote: > > The Dovecot SASL backend has access to the client's IP address, > but I don't know whether it sees that early enough to supply Postfix > with a client-dependent mechanism list, nor whether Dovecot has the > feature you're looking for. The Cyrus

Re: Different SMTP AUTH options and credentials for different clients

2016-06-21 Thread Wietse Venema
Rob Maidment: > On 31 May 2016 at 17:21, Viktor Dukhovni wrote: > > > > The Dovecot SASL backend has access to the client's IP address, > > but I don't know whether it sees that early enough to supply Postfix > > with a client-dependent mechanism list, nor whether Dovecot has the > > feature you'r

force postifx to look up again for mail exchangers

2016-06-21 Thread Pedro David Marco
Hi! i have many emails in the deferred queue that cannot be sent because the destination resolved IP is no longer available. is there anyway to force Postfix to look up again the list of mail exchangers addresses for the destination host/domain and try to send them again??? Thanks! Pedrete

Re: force postifx to look up again for mail exchangers

2016-06-21 Thread Wietse Venema
Pedro David Marco: > is there anyway to force Postfix to look up again the list of mail > exchangers addresses for the destination host/domain and try to > send them again??? The Postfix SMTP client **always** looks up the current list of MX hosts and IP addresses. If it gets the wrong information

Re: force postifx to look up again for mail exchangers

2016-06-21 Thread Pedro David Marco
Thanks Wietse... does this also happen with connections saved in scache? Pedreter. On Tue, 6/21/16, Wietse Venema wrote: Subject: Re: force postifx to look up again for mail exchangers To: "Postfix users" Date: Tuesday, June 21, 2016, 9:10 PM

Re: force postifx to look up again for mail exchangers

2016-06-21 Thread Wietse Venema
Wietse: > The Postfix SMTP client **always** looks up the current list of > MX hosts and IP addresses. If it gets the wrong information, you > need to update your system configuration. Pedro David Marco: > Thanks Wietse... > does this also happen with connections saved in scache? By default, a