Prev: bounce & local process consumes high CPU usage
Next: Postfix rate control using anvil
From: mouss on 12 Mar 2010 18:33
Gmail-teopro a �crit :
> Yes mouss I commented -o statements because when they are enabled,
> Postfix do not recognize virtual aliases.

you should not disable address rewrite in the whole chain. only when
mail is passed through a filter.

> Following your kind suggestion, I enabled -o statement for main smtp
> service.(I use to listen also on 10025 because some ISP are bloking port
> 25)

this is a different issue. I was assuming that 10025 is the after filter
port. if this is different, please explain.

> The log after sending a message towards a virtual alias
> (virtalias(a)mydomain.tld <mailto:virtalias(a)mydomain.tld>) follows:
>
> Mar 12 07:06:20 one postfix/smtpd[5426]: connect from
> unknown[189.189.189.189]
> Mar 12 07:06:20 one postfix/smtpd[5426]: C3B512944C3:
> client=unknown[189.189.189.189]
> Mar 12 07:06:20 one postfix/cleanup[5433]: C3B512944C3:
> message-id=<8209475102.20100312070704(a)dom.tld>
> Mar 12 07:06:20 one postfix/qmgr[5421]: C3B512944C3:
> from=<sender(a)dom.tld>, size=1732, nrcpt=1 (queue active)
> Mar 12 07:06:20 one postfix/smtpd[5426]: disconnect from
> unknown[189.189.189.189]
> Mar 12 07:06:20 one postfix/pipe[5434]: C3B512944C3:
> to=<virtalias(a)mydomain.tld>, relay=dovecot, delay=0.66,
> delays=0.64/0.01/0/0.01, dsn=5.1.1, status=bounced (user unknown)

there is no evidence that mail was passed through a filter.

>[snip]

From: Gmail-teopro on 13 Mar 2010 13:55
Hello mouss,

Saturday, March 13, 2010, 1:33:44 AM, you wrote:

> Gmail-teopro a écrit :
>> Yes mouss I commented -o statements because when they are enabled,
>> Postfix do not recognize virtual aliases.

> you should not disable address rewrite in the whole chain. only when
> mail is passed through a filter.

I get the point here. I fill things become more clear. The filter is
triggered in main.cf, like this:
.......
smtpd_recipient_restrictions =
check_sender_access hash:/etc/postfix/maps/sender_nrfilter
.......

sender_nrfilter file contains:
mydomain.tld FILTER nrfilter:

If you can suggest a way to disable address rewrite in this point,
you will help me a lot to understand the Postfix mechanism.


>> Following your kind suggestion, I enabled -o statement for main smtp
>> service.(I use to listen also on 10025 because some ISP are bloking port
>> 25)

> this is a different issue. I was assuming that 10025 is the after filter
> port. if this is different, please explain.

No, 10025 is simply a second smptd listener, used for some clients who can't
access Postfix on usual 25 port being cut(filtered) by their ISPs

>> The log after sending a message towards a virtual alias
>> (virtalias(a)mydomain.tld <mailto:virtalias(a)mydomain.tld>) follows:

>> Mar 12 07:06:20 one postfix/smtpd[5426]: connect from
>> unknown[189.189.189.189]
>> Mar 12 07:06:20 one postfix/smtpd[5426]: C3B512944C3:
>> client=unknown[189.189.189.189]
>> Mar 12 07:06:20 one postfix/cleanup[5433]: C3B512944C3:
>> message-id=<8209475102.20100312070704(a)dom.tld>
>> Mar 12 07:06:20 one postfix/qmgr[5421]: C3B512944C3:
>> from=<sender(a)dom.tld>, size=1732, nrcpt=1 (queue active)
>> Mar 12 07:06:20 one postfix/smtpd[5426]: disconnect from
>> unknown[189.189.189.189]
>> Mar 12 07:06:20 one postfix/pipe[5434]: C3B512944C3:
>> to=<virtalias(a)mydomain.tld>, relay=dovecot, delay=0.66,
>> delays=0.64/0.01/0/0.01, dsn=5.1.1, status=bounced (user unknown)

> there is no evidence that mail was passed through a filter.

The filter wasn't triggered because the (virtual)user wasn't recognized.
The filter triggers only for (valid) users belonging to @mydomain.tld
(see above, sender_nrfilter check file)
>>[snip]



--
Best regards,
Gmail-teopro mailto:teopro(a)gmail.com
First  |  Prev  | 
Pages: 1 2
Prev: bounce & local process consumes high CPU usage
Next: Postfix rate control using anvil