Mark's fix:
If your Mailman is at
least 2.1.16, all you need to do is set
SUBSCRIBE_FORM_SECRET = 'Some string unique to your site"
in mm_cfg.py, and that attack will no longer work.
Is working fine. But thanks for the alternative suggestions. I've got a
copy of fail2ban ready to install bu
Never mind - it started working. I just had to leave the house and come back.
Mayby the issues at work can be done that way, too. :-)
Allan
Hi,
I have waited almost a year for AOL and Yahoo to admit that they messed up and
to remove their DMARC policy. My AOL and Yahoo subscribers are pretty
On 05/23/2015 02:45 PM, Allan Hansen wrote:
>
> So against my better judgement, I included this hack in Cleanse.py;
>
> 22c22
> < from email.Utils import formataddr, parseaddr
> —
>>from email.Utils import formataddr
>
> 69,74d68
> <
> < # Added to deal with DMARC issuej
> < name, a
Hi,
I have waited almost a year for AOL and Yahoo to admit that they messed up and
to remove their DMARC policy. My AOL and Yahoo subscribers are pretty upset at
me because I won’t let them post. A number now have two subscriptions, one for
posting (from GMail) and another for receiving the mes