Hi,
my current setting:
parent_domain_matches_subdomains =
debug_peer_list,fast_flush_domains,mynetworks,permit_mx_backup_networks,qmqpd_authorized_clients,smtpd_access_maps
I'm not using relay_domains, instead it is configured via virtual_maps. It's
not under my control because i'm using a configure tool for customers, which
generates the maps. But how is this linked to that forward problem, which was
the underlying question?
Thanks so far.
----- Original Message ----
From: Wietse Venema <wie...@porcupine.org>
To: Postfix users <postfix-users@postfix.org>
Sent: Fri, February 5, 2010 6:19:30 PM
Subject: Re: Weird forwarding problem, what happened?
Andreas Grimm:
> Hi Wietse,
>
> that's right, it isn't listed. But it was a non exisiting subdomain
> the spamer sent the mail to.
OK, in that case you could set
main.cf:
relay_domains=
If, on the other hand, you really need to have a non-empty
relay_domains setting, you would need to change the
parent_domain_matches_subdomains setting from its lengthy default:
# postconf parent_domain_matches_subdomains >> main.cf
# vi main.cf
and delete relay_domains from the parent_domain_matches_subdomains list.
Wietse
> The mail address was like
> zirkel.in...@nonexistingsub.domain.net So the mail was directly
> delivered to the A record (which is wildcarded). What i don't
> get is, why did postfix forwarded the message to the other host
> without permission? Is this linked to the issue you mentioned?
>
>
> ----- Original Message ----
> The machine is MX host for REMOVED, but you broke Postfix by not
> listing that domain in virtual_alias_domains, mydestination,
> relay_domains, or virtual_mailbox_domains.
>
> Wietse
>
>
>
>
>
>
>
