> Date: Thu, 4 Dec 2014 20:47:37 -0800
> From: m...@msapiro.net
>
> On 12/04/2014 05:55 PM, Jon 1234 wrote:
>
>>> The get_memb script is specific to our database, but it could basically
>>> be anything, even just a straight MySQL query, that produces the desired
>>> list (In our case, the logic of
On 12/12/2014 06:32 AM, joseph cook wrote:
> This morning all of my subscribers with aol addresses were automatically
> unsubscribed from my list.
>
> Why today? I thought all the DMARC issues had been resolved in the latest
> mailman version, and it's been 8 months now since the changes at AOL.
This should have nothing to do with AOL's DMARC policy, I think. For some
reason AOL has been rejecting all your list's mail, so maybe it's an anti spam
issue. Did you get bounce action notifications for those addresses? What
reasons were given?
How many addresses are involved? And are you sure
On 12/12/2014 6:32 AM, joseph cook wrote:
This morning all of my subscribers with aol addresses were automatically
unsubscribed from my list.
Did you check the bounce log? The scores might have been creeping upwards
for weeks and just hit the threshold.
z!
--
On 12/12/2014 02:37 AM, Hal wrote:
>
> 1. permission fixing for the archive
>
> $ sudo chmod g+w
> /var/lib/mailman/archives/private/my_list_name.mbox/my_list_name.mbox
>
> So this adds write permission to the group ("hal" and "mailman"), right?
> Here's a lis
This morning all of my subscribers with aol addresses were automatically
unsubscribed from my list.
Why today? I thought all the DMARC issues had been resolved in the latest
mailman version, and it's been 8 months now since the changes at AOL.
--Any suggestions?
Joe C
--
On 11/12/2014 19:12, Mark Sapiro wrote:
$ ls
total 808
-rw-r--r-- 1 hal mailman 825894 Nov 8 15:39 my_list_name.mbox
And here's the problem.
sudo chmod g+w
/var/lib/mailman/archives/private/my_list_name.mbox/my_list_name.mbox
will fix it. Then you can run bin/unshunt which will put the shu
