>>> I don't think that using local(8) as a content filter is a good idea,
>>> perhaps you meant to instead use "REDIRECT" or "HOLD".
>>
>> /^X-Spam.*YES/ REDIRECT s...@m0.rg.net
>>
>> did the trick, along with a specific transport
>>
>> s...@m0.rg.net local:/var/mail/spam
>
> You've still not quite internalised my explanation of local(8) nexthops.
> There's no good reason to set the nexthop explicitly here, and the value
> chosen no significance. When the mail is delivered depends only on
> the recipient address, and your aliases(5) file, passwd(5) file,
> .forward file for the user, ... See local(8) for details.
part of my problem is i miss playing `sendmail -bt` adventure to see
what the mta is gonna do and why. e.g. from an exim system
% sendmail -bt s...@m0.rg.net
R: dnslookup for s...@m0.rg.net
s...@m0.rg.net
router = dnslookup, transport = remote_smtp
host m0.rg.net [2001:418:3807::22]
host m0.rg.net [198.180.152.22]
% sendmail -bt randy
R: userforward for ra...@ran.psg.com
ra...@ran.psg.com -> |/usr/bin/procmail
transport = address_pipe
on mx0.rg.net there is a local userid spam. but without that explicit
transport it sends it off to a host where users with 42 j random domains
hide due to the last line in transport
* smtp:[psg.com]
putting it in virtual works i guess
s...@m0.rg.net spam
though i do not have an gut intuition of why to prefer this. isn't the
local transport going to be used to deliver this too?
thanks for your patience.
randy
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
