Dear Gilles, You are a genius! I have no idea why this did not work out in the last weeks when I tried to get it up and running. Now I ended up with:
action aaa relay host smtp+tls://[email protected] auth <authinfo> action bbb mbox virtual { "@" => buggy } match from any for domain example.com rcpt-to [email protected] action aaa match from any for any action bbb This does exactly what I intend: Take mail from local network and local machine from arbitrary sender to arbitrary recipient, pass it to the local user buggy, modify the recipient to be [email protected], and allow relay for only this recipient. (If recipient is fine in the first place, it does not take the route through the local user.) Excellent! Thank you so much for your help and the trigger to try it again! Regards Stefan > On 2. Dec 2018, at 14:49, Gilles Chehade <[email protected]> wrote: > > On Sun, Dec 02, 2018 at 02:38:46PM +0100, Stefan Bagdohn wrote: >> Hi all, >> >> with the old grammar i used the following config: >> >> accept from any for domain "example.com" recipient "[email protected]" relay >> via tls+auth://[email protected] auth >> accept from any for any virtual { "@" => buggy } deliver to mbox >> >> to do some sort of catchall. >> >> This worked well. Any mail (local from system and remote from lan) was >> basically delivered to the local user buggy which had a .forward that >> contains [email protected]. So it was relayed afterwards by the first rule. >> >> Any hint how this could be done in the new grammar? I have no idea how to >> implement the old-style => catchall. >> > > grammar set aside, it's done the exact same way. > > -- > Gilles Chehade @poolpOrg > > https://www.poolp.org tip me: https://paypal.me/poolpOrg > > -- > You received this mail because you are subscribed to [email protected] > To unsubscribe, send a mail to: [email protected] > -- You received this mail because you are subscribed to [email protected] To unsubscribe, send a mail to: [email protected]
