Re: unknown user status code changed

2015-04-15 Thread Noel Butler
On 16/04/2015 11:40, wie...@porcupine.org wrote: > Noel Butler: 20120917 > > Feature: RFC 7372 enhanced status code for unknown SMTP > client hostnames. File: smtpd/smtpd_check.c > > Wietse > Thanks, I assume you only introduced this into 3.x? and did not in > 2.11.x? New features don't g

Re: unknown user status code changed

2015-04-15 Thread Wietse Venema
Noel Butler: > > 20120917 > > > > Feature: RFC 7372 enhanced status code for unknown SMTP > > client hostnames. File: smtpd/smtpd_check.c > > > > Wietse > > Thanks, I assume you only introduced this into 3.x? and did not in > 2.11.x? New features don't go into the **STABLE** release. It's cal

Re: unknown user status code changed

2015-04-15 Thread Viktor Dukhovni
On Thu, Apr 16, 2015 at 11:11:12AM +1000, Noel Butler wrote: > > 20120917 > > > > Feature: RFC 7372 enhanced status code for unknown SMTP > > client hostnames. File: smtpd/smtpd_check.c > > > > Wietse > > Thanks, I assume you only introduced this into 3.x? and did not in > 2.11.x? > > Just try

Re: unknown user status code changed

2015-04-15 Thread Noel Butler
On 16/04/2015 10:58, wie...@porcupine.org wrote: > Noel Butler: > >> Did I miss the changes or was it omitted from 3.0 about the code change >> from 5.7.1 to 5.7.25 ? >> >> "550 5.7.25 Client host rejected: cannot find your hostname," >> >> heh, just upgraded one production box and had lo

Re: unknown user status code changed

2015-04-15 Thread Wietse Venema
Noel Butler: > > > Did I miss the changes or was it omitted from 3.0 about the code change > from 5.7.1 to 5.7.25 ? > > "550 5.7.25 Client host rejected: cannot find your hostname," > > heh, just upgraded one production box and had logwatch flood me with a > 19mb file with unmatched entries :

unknown user status code changed

2015-04-15 Thread Noel Butler
Did I miss the changes or was it omitted from 3.0 about the code change from 5.7.1 to 5.7.25 ? "550 5.7.25 Client host rejected: cannot find your hostname," heh, just upgraded one production box and had logwatch flood me with a 19mb file with unmatched entries :) Cheers

Re: [Newbie question] Recursive virtual aliasing

2015-04-15 Thread Michel Blancard
That works ! Thanks to both of you. It may take the risk to irritate some postfix aficionados, but I find that the postfix documentation is very dense and you need to read it from end to end before getting the big picture. The most discouraging is that few relevant information can be found on

Re: [Newbie question] Recursive virtual aliasing

2015-04-15 Thread Wietse Venema
Michel Blancard: > Hi all, > > I've spent a lot of time trying to configure virtual aliases. Command > 'postmap -q "whate...@i.try" /etc/postfix/virtual" always returns the > first result after just one aliasing, even if a second alias is > matching. Here is an example : ... > I think the probl

Re: [Newbie question] Recursive virtual aliasing

2015-04-15 Thread Noel Jones
On 4/15/2015 1:11 PM, Noel Jones wrote: > On 4/15/2015 12:50 PM, Michel Blancard wrote: >> Hi all, >> >> I've spent a lot of time trying to configure virtual aliases. >> Command 'postmap -q "whate...@i.try" /etc/postfix/virtual" always >> returns the first result after just one aliasing, even if a

Re: [Newbie question] Recursive virtual aliasing

2015-04-15 Thread Noel Jones
On 4/15/2015 12:50 PM, Michel Blancard wrote: > Hi all, > > I've spent a lot of time trying to configure virtual aliases. > Command 'postmap -q "whate...@i.try" /etc/postfix/virtual" always > returns the first result after just one aliasing, even if a second > alias is matching. Here is an example

[Newbie question] Recursive virtual aliasing

2015-04-15 Thread Michel Blancard
Hi all, I've spent a lot of time trying to configure virtual aliases. Command 'postmap -q "whate...@i.try" /etc/postfix/virtual" always returns the first result after just one aliasing, even if a second alias is matching. Here is an example : # pwd /etc/postfix # cat virtual a...@virtualdom