Le 04/01/2011 17:44, Phil Howard a écrit : > On Tue, Jan 4, 2011 at 11:14, mouss <mo...@ml.netoyen.net> wrote: > >> with amavis, setup a spamassassin rule that matches your bizarre text. >> fopr instance >> >> body FOO_BAR_RULE /SomeExpression/i >> score FOO_BAR_RULE 0.1 >> (0.1 is small enough to not alter spam status). >> >> then "FOO_BAR_RULE" will appear in the X-Spam-Status, which your >> sieve/whatever script can catch. > > At that point it probably won't matter so much what the score is, as I > will be committing it to the spam subfolder. > > >> if you want more, then you can probably create a before_send hook in amavis. > > Hopefully I can keep this simple ... if it smells spammy, it goes into > the spam subfolder. Then the user can look there for missing stuff if > needed, but it won't be making their phones buzz. > > So many people checking their mail by phone now days changes priorities. >
another idea is to use the FILTER action to pass these messages to a specific listener (smtpd) which prepends a header or rewrites the recipient to recipient+s...@example.com (via a specific cleanup).
