I solved the problem... when i installed clamav i set the following in main.cf that blocked every virtual user in virtual table: receive_override_options =Message 1 of 2 , Dec 1 3:33 AMView SourceI solved the problem...
when i installed clamav i set the following in main.cf that blocked every
virtual user in virtual table:
receive_override_options = no_address_mappings
i don't know why this appens... and i don't know if clamav works even
without that rule.. can you explain to me?
----- Original Message -----
From: "Magnus Bäck" <magnus@...>
Sent: Thursday, December 01, 2005 7:58 AM
Subject: Re: virtual alias table
On Wednesday, November 30, 2005 at 22:59 CET,
Bissio <bissio2000@...> wrote:
> I made last week an upgrade to postfix 2.2 from postfix 1.1 and i set
> my virtual domain and recipient in virtual_alias_maps in main.cf
> instead of virtual_maps (like postfix 1.1), but when i receive any
> message to one of my recipient listed in virtual table
> (/etc/postfix/virtual) i see this error in maillog (even if i set my
> virtual domain and recipient in virtual file):
> postfix/error: CE4A73F723: to=<virtual@...>, relay=none,
> delay=0, status=bounced (User unknown in virtual alias table)
More information is needed. Provide full logs, configuration, and
relevant extracts of the virtual alias table. My guess is that you
have an unqualified address in your virtual address table,
and that myorigin is not a local domain. There was a lengthy thread
about this exact problem just a few days ago.
... so you did this in main.cf? I say so because spaces aroun = aren t valid in master.cf. you should only do that once: either before the filter or afterMessage 1 of 2 , Dec 1 4:10 AMView SourceBissio a écrit :
> I solved the problem...so you did this in main.cf? I say so because spaces aroun '=' aren't
> when i installed clamav i set the following in main.cf that blocked
> every virtual user in virtual table:
> receive_override_options = no_address_mappings
valid in master.cf.
you should only do that once: either before the filter or after the
filter. The idea is to avoid having virtual aliases expanded twice. but
you should not do this globally. otherwise, your virtual aliases aren't
used (thus the error at delivery time).
Typically, you use a different receive_override_options before and after
(1) use -o receive_override_options=no_address_mappings
in the before-the-filter smtpd (the one listening on port 25)
(2) use -o receive_override_options=no_unknown_recipient_checks
in the after-the-filter smtpd (the one listening on port 10025)
you can set one of the options in main.cf, then override it in one of
the listeners, but this is risky.
you can set the options safely in main.cf when you use different
instances of postfix.