Re: postfix bounce access table

2010-12-10 Thread Per Jessen
Victor Duchovni wrote: > On Thu, Dec 09, 2010 at 10:51:18AM +0100, Per Jessen wrote: > >> I guess this is intended behaviour - there is no sender address, >> so the destination hostname is looked up instead, but shouldn't there >> also be a lookup with sender='<>' ? > > No. Just as there is no u

Re: postfix bounce access table

2010-12-09 Thread Victor Duchovni
On Thu, Dec 09, 2010 at 10:51:18AM +0100, Per Jessen wrote: > I guess this is intended behaviour - there is no sender address, > so the destination hostname is looked up instead, but shouldn't there > also be a lookup with sender='<>' ? No. Just as there is no user-specific relayhost for sender

Re: postfix bounce access table

2010-12-09 Thread Per Jessen
Per Jessen wrote: > This produces an ndr, which is also rejected due to lack of authentication, > as '<>' doesn't seem to be found in smtp_sasl_password_maps. Extract from a test with debug enabled: (suitably snipped & obscured) Dec 9 10:40:56 neon postfixo/qmgr[16294]: A77FE33266: from=<>, s

Re: postfix bounce access table

2010-12-08 Thread Per Jessen
Ralf Hildebrandt wrote: > * Per Jessen : >> Is there a way of specifying the bounce/null address in an >> smtp_sasl_password_maps table ? I've tried using '<>', but that >> didn't seem to work. > > Usually the smtpd_null_access_lookup_key should work for that (which > is "<>" by default). > Yes