On Mon, 28 Dec 2020, RW wrote:
On Sun, 27 Dec 2020 10:17:15 -0800 (PST)
John Hardin wrote:
To catch those you'd need to check for the address in a Received:
header, assuming your MTA adds the envelope recipient to the
Received: header it generates.
You might do:
header ABUSED_PLUS
On Sun, 27 Dec 2020 10:17:15 -0800 (PST)
John Hardin wrote:
> To catch those you'd need to check for the address in a Received:
> header, assuming your MTA adds the envelope recipient to the
> Received: header it generates.
> You might do:
>
>header ABUSED_PLUS Received =~ /\bfor
> /i
On Sun, 27 Dec 2020, Kenneth Porter wrote:
--On Saturday, December 26, 2020 11:20 PM -0500 Bill Cole
wrote:
You definitely want to escape that '+' and catch the recipient instead of
sender:
header RULENAME To:addr =~ /\+.+\@/
score RULENAME -1
That looks like what I want. Although
--On Saturday, December 26, 2020 11:20 PM -0500 Bill Cole
wrote:
You definitely want to escape that '+' and catch the recipient instead of
sender:
header RULENAME To:addr =~ /\+.+\@/
score RULENAME -1
That looks like what I want. Although since my server is hacked to accept a
dot
On 26 Dec 2020, at 18:17, Kevin A. McGrail wrote:
Header rulename from:addr =~ /.*+.*\@/
You definitely want to escape that '+' and catch the recipient instead
of sender:
header RULENAME To:addr =~ /\+.+\@/
score RULENAME -1
Another approach:
whitelist_to *+*@example.com
In that
Header rulename from:addr =~ /.*+.*\@/
Should match an email with a plus one the left hand side.
On Sat, Dec 26, 2020, 18:11 Kenneth Porter wrote:
> I usually sign up for a web service using a "plussed" address like
> shiva+vendorn...@sewingwitch.com. (My server also recognizes a dot
> instead
I usually sign up for a web service using a "plussed" address like
shiva+vendorn...@sewingwitch.com. (My server also recognizes a dot instead
of a plus, to deal with broken websites that won't allow me to use a plus
in my email address.) I use procmail rules on my server to filter messages
