[Mailman-Users] Email Address getting Deleted

[ajay babu]

 Hi Team,

Need your kind help.

When ever i add an email-id to mailing list, the email-id is getting
deleted on its own in mailman and the below logs were captured in bounce &
subscribe log files:

May 11 00:59:27 2018 (11937) it-support: new a...@xxx.com ,
admin mass sub

May 11 20:00:51 2018 (27739) it-support: *deleted *a...@xxx.com*; disabled
address*

May 11 20:00:51 2018 (27739) it-support: a...@xxx.com
 auto-unsubscribed
[reason: BYBOUNCE]

May 11 20:00:51 2018 (27739) it-support: a...@xxx.com  bounce
score: 1.0

May 11 20:00:51 2018 (27739) it-support: *a...@xxx.com
 disabling due to bounce score 1.0 >= 1.0*
May 11 20:00:51 2018 (27739) it-support: *a...@xxx.com
 deleted after exhausting notices*

Could you help me to understand what might be the reason for this issue? if
you're not the right point of contact, can you share me the correct details
to whom i can contact in this regards?

Thanks in Advance.

~Regards
AJ
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Encoding issues when importing archives

[Eric Abrahamsen]

I'm recreating some old lists I had in a Mailman 2 installation, and
trying to import the old mboxes into Hyperkitty.

The lists were on Chinese-related subjects, and we've got both messages
that contain Chinese characters, and attachments that have Chinese
filenames and contents.

The import process is blowing up with a UnicodeEncodeError, in
hyperkitty/lib/incoming.py#add_to_list, it looks like when the
attachments are being processed:

content = content.encode(decoding)

UnicodeEncodeError: 'gb2312' codec can't encode character '\ufffd' in position 
3131: illegal multibyte sequence

Apparently the offending attachments are specified as gb2312 (a common
Chinese encoding).

Is there something I can do to somehow preprocess the archive mboxes, or
otherwise re-encode the attachments?

Thanks,
Eric
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman not dispatching Status mail to user list

[ajay babu]

Hi Team,

I have an application which uses mailman for receiving Validation &
Notification mails to my mailing list.
But unfortunately am facing intermittent issues with receiving the
Notification mails to my mailing list, but am getting Validation mails to
my mailing list without any issues.

Any idea what might be the issue? appreciate your help here.

Thanks in Advance.

~Regards
AJ
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Help with mailman instance in broken state

[Kevin Bowen]

My mailman instance (2.1.9) has gotten into a funky broken state where one
of my lists has become inoperable, with a message which should be awaiting
moderation, but the moderator never got notified. The list's config appears
to be corrupt - attempting to load the admin web interface results in a
timeouts (the archive and basic listinfo pages still work, and the admin
interface for all other lists work). When I look in
/var/lib/mailman/lists/,
I can see that mailman is continually rewriting config.pck every few
seconds.

I attempted to fix the issue by restoring the contents of
/var/lib/mailman/lists/ from the previous day's backup, and that
got the config into a working state such that it was possible to load the
web admin interface for the list, but as soon as I started back up the
mailman service, it got right back into the same broken state.

Next I tried deleting the list with rmlist, then recreating it and
importing its config and membership with config_list and sync_members, but
again, as soon as I restart the mailman service, it gets right back into
the same broken state.

Any ideas how to fix this?

Kevin Bowen
UCSD ITS UBPS
ke...@ucsd.edu
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] [Mailman-cabal] GDPR

[Andrew Hodgson]

Grant Taylor wrote:


On 05/14/2018 06:33 AM, Andrew Hodgson wrote:

[...]

>> - Audit logs for data access.  it is not clear who is accessing
>> subscription data for the list as there is just a single owner and
>> moderator account.  Unsure if current logging data in either MM2 or MM3 is
>> "good enough" for this.  MM3 may solve the issue about single accounts.

>I guess I don't understand the problem and / or make invalid assumptions
>about MM.

>I see six modes of access to the data:

>1)  List subscribers
>2)  List owners / administrators

At the moment the list administrator and moderator account is accessed via no 
username and a single password.  If that password is shared, I have no audit 
trail of who logged into the system.  Also the system currently doesn't log 
specific access, for example admin A exported a load of addresses, admin B 
added 100 subscribers to the mailing list etc.

Andrew.
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Encoding issues when importing archives

[Mark Sapiro]

On 5/14/18 2:16 PM, Eric Abrahamsen wrote:
> I'm recreating some old lists I had in a Mailman 2 installation, and
> trying to import the old mboxes into Hyperkitty.


This is not the appropriate list for Mailman 3.
mailman-us...@mailman3.org

or possibly mailman-develop...@python3.org
 are the
appropriate lists.


> The lists were on Chinese-related subjects, and we've got both messages
> that contain Chinese characters, and attachments that have Chinese
> filenames and contents.
> 
> The import process is blowing up with a UnicodeEncodeError, in
> hyperkitty/lib/incoming.py#add_to_list, it looks like when the
> attachments are being processed:
> 
> content = content.encode(decoding)
> 
> UnicodeEncodeError: 'gb2312' codec can't encode character '\ufffd' in 
> position 3131: illegal multibyte sequence
> 
> Apparently the offending attachments are specified as gb2312 (a common
> Chinese encoding).
> 
> Is there something I can do to somehow preprocess the archive mboxes, or
> otherwise re-encode the attachments?


Possibly there is, but this is a bug in the hyperkitty_import process.
It would help if you file an issue at
 with enough
information for us to reproduce it.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Help with mailman instance in broken state

[Mark Sapiro]

On 5/14/18 7:26 PM, Kevin Bowen wrote:
> When I look in
> /var/lib/mailman/lists/,
> I can see that mailman is continually rewriting config.pck every few
> seconds.


I think the "duplicate" post I rejected mentioned a qrunner at 99% cpu.

Which runner? What's in the various mailman/qfiles/* queues.

What's in Mailman's logs?

What's in Mailman's locks directory? See .

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Email Address getting Deleted

[Mark Sapiro]

On 5/14/18 11:59 PM, ajay babu wrote:
> 
> When ever i add an email-id to mailing list, the email-id is getting
> deleted on its own in mailman and the below logs were captured in bounce &
> subscribe log files:
...
> May 11 20:00:51 2018 (27739) it-support: *a...@xxx.com
>  disabling due to bounce score 1.0 >= 1.0*
> May 11 20:00:51 2018 (27739) it-support: *a...@xxx.com
>  deleted after exhausting notices*


Your list's Bounce processing is set with

bounce_score_threshold = 1.0
bounce_you_are_disabled_warnings = 0

So the first bounce removes the user from the list. The list welcome
message to the user bounces and the user is removed. You might consider
different bounce processing settings, but the real question is why is
this message bouncing. Look in Mailman's smtp and smtp-failure logs and
the MTA logs.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman not dispatching Status mail to user list

[Mark Sapiro]

On 5/15/18 12:02 AM, ajay babu wrote:
> 
> I have an application which uses mailman for receiving Validation &
> Notification mails to my mailing list.
> But unfortunately am facing intermittent issues with receiving the
> Notification mails to my mailing list, but am getting Validation mails to
> my mailing list without any issues.
> 
> Any idea what might be the issue? appreciate your help here.


Not without more information. What is different about the Notification
mails that have issues. What are the issues? Are the messages held? If
so, for what reason. What's in Mailman's vette log?

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] [Mailman-cabal] GDPR

[Andrew Hodgson]

Bernd Petrovitsch [be...@petrovitsch.priv.at] wrote:

>On Mon, 2018-05-14 at 12:33 +, Andrew Hodgson wrote:
[...]
>> These are just rough notes:
>>
>> - Archive purge requests. We have discussed the same items as on the
>> list to date.  I am looking at doing a simple grep for the relevant
>> person's details and changing that.  The main reason for doing this
>> is that if we just remove the author's messages they will be in a
>> thread of other messages and our users typically don't remove quoted
>> material.  Current advice from the GDPR people is we may have to
>> delete the whole thread.  Still under discussion, this is also

>While at it, why not delete the entire archive just to be sure? SCNR

That is something we haven't ruled out just yet!

>And to be honest: If person X fullquotes and the email ends in an
>archive, who's fault is it?

The last archive removal request I had a few weeks ago stemmed from one of the 
subscribers posting a private message about an event and it had the original 
poster's mobile number in it as well as contact details for the event.  There 
was a large thread about this event, and everyone used top posting.  The 
original author contacted us after having been informed they found the event 
invitation from our website, and were not happy.  What do I redact or remove in 
this instance?

- The whole thread;
- Personal details about the original poster and the event who had not 
consented to having their email posted to the mailing list;
- Anything else?

In the end I removed the phone numbers, her personal address and the 
Eventbright links from *all* messages, including some messages from other 
people where they had re-echoed the Eventbright links as part of their 
conversation to help other people.  She wasn't very happy, but worse is the 
person who forwarded it to the mailing list refused to understand what they had 
really done and believed they had the right to send the post anywhere as they 
believed it was in the public domain.

Just an example of the type of stuff that I may get asked to remove in future.

Andrew.
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] [Mailman-cabal] GDPR

[Grant Taylor via Mailman-Users]

On 05/15/2018 03:18 AM, Andrew Hodgson wrote:
At the moment the list administrator and moderator account is accessed 
via no username and a single password.  If that password is shared, 
I have no audit trail of who logged into the system.


ACK

I like to run Mailman (et al) administration pages behind htaccess 
protection.  Thus I have the username that authenticated to the web 
server to corroborate who's actually accessing things.


Also the system currently doesn't log specific access, for example admin 
A exported a load of addresses, admin B added 100 subscribers to the 
mailing list etc.


Can you not tell what was done based on the web server logs and the 
requested URLs?  I know that won't catch POST data, but it will give you 
more information than not looking at the web server logs.


Aside:  I personally consider the web server to be part of the 
application framework.  As such, I exercise and use it to (what I think 
is) my advantage.




--
Grant. . . .
unix || die

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Help with mailman instance in broken state

[Kevin Bowen]

So the issue seems to have resolved itself over night - there's no longer a
qrunner process taking 99% cpu, the list's admin interface is accessible,
and it's no longer rewriting its config.pck every few seconds, so I think
that means the list is now fine (although there hasn't yet been any traffic
through it so I'm not 100% sure). Even if resolved, I'd like to figure out
what happened so it doesn't happen again. To answer your questions:

>Which runner?

I remember the process had qrunner in its command line, but since it's gone
now I can't tell you in any more detail.

>What's in the various mailman/qfiles/* queues.

I don't seem to have that directory? I'm running v2.1.9 on RHEL5, do you
know where it would be located?

>What's in Mailman's logs?

The only thing relvant-seeming we were able to find in the logs was a
mention in vette that a message was being held for moderation, and then a
bunch of bounce-processing.

>What's in Mailman's locks directory? See .

Ok, now this is interesting: there are 6 files in /var/lock/mailman named
.lock.announce.ucsd.edu..0 They have timestamps between 3
and 4 in the morning, which is probably around the time the issue cleared
up. Looking in /var/log/mailman/locks I see, starting right around the time
the problem started yesterday, a bunch of stack traces with
".lock lifetime has expired, breaking" and ".lock
unexpected linkcount: -1"

Also, I notice that in /var/lib/mailman/data, there are currently 4 files
called heldmsg--.pck, although the admin interface says
there are currently no messages being held for moderation. Does that mean
anything?

Kevin Bowen
UCSD ITS UBPS
ke...@ucsd.edu

On Tue, May 15, 2018 at 5:59 AM, Mark Sapiro  wrote:

> On 5/14/18 7:26 PM, Kevin Bowen wrote:
> > When I look in
> > /var/lib/mailman/lists/,
> > I can see that mailman is continually rewriting config.pck every few
> > seconds.
>
>
> I think the "duplicate" post I rejected mentioned a qrunner at 99% cpu.
>
> Which runner? What's in the various mailman/qfiles/* queues.
>
> What's in Mailman's logs?
>
> What's in Mailman's locks directory? See  >.
>
> --
> Mark Sapiro The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/
> mailman-users%40python.org/
> Unsubscribe: https://mail.python.org/mailman/options/mailman-users/
> kevin.t.bowen%40gmail.com
>
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Help with mailman instance in broken state

[Mark Sapiro]

On 5/15/18 10:27 AM, Kevin Bowen wrote:
> 
>> What's in the various mailman/qfiles/* queues.
> 
> I don't seem to have that directory? I'm running v2.1.9 on RHEL5, do you
> know where it would be located?


In RHEL, it's /var/spool/mailman/ (see ).



>> What's in Mailman's locks directory? See > .
> 
> Ok, now this is interesting: there are 6 files in /var/lock/mailman named
> .lock.announce.ucsd.edu..0 They have timestamps between 3
> and 4 in the morning, which is probably around the time the issue cleared
> up. Looking in /var/log/mailman/locks I see, starting right around the time
> the problem started yesterday, a bunch of stack traces with
> ".lock lifetime has expired, breaking" and ".lock
> unexpected linkcount: -1"


So the issue was a locked list. See 
for more on locks, but those file names are  if the form
.lock... so what yo call 'digits' is the
pid of the process waiting on the lock. If there is no file named just
.lock, the list isn't locked and all the other
.lock.* files are orphans and their pids are probably gone, so
just remove them.

Actually, when these files are created, they are created with a time
stamp in the future which represents the expiration of the lock lifetime
so that probably is when the list was no longer locked and things
cleared up.

As far as what caused it, that's hard to say, but one strong possibility
is there was an interaction with the list's admin or admindb UI that was
timed out by the web server and left the list locked.


> Also, I notice that in /var/lib/mailman/data, there are currently 4 files
> called heldmsg--.pck, although the admin interface says
> there are currently no messages being held for moderation. Does that mean
> anything?


Those are orphaned held messages, probably orphaned when you deleted and
recreated the list. You can look at them with Mailman's bin/dumpdb and
if you want them, you can reprocess them with the script at



-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] [Mailman-cabal] GDPR

[Grant Taylor via Mailman-Users]

On 05/15/2018 03:08 AM, Andrew Hodgson wrote:

What do I redact or remove in this instance?

- Personal details about the original poster and the event who had not 
consented to having their email posted to the mailing list;


I would likely have (presuming sufficient motivation):

1)  Get mailman into a state that I can safely modify the archive.
2)  Run a script (likely sed) to REDACT the contents.
  sed -i$ticketID 's/phone number/REDACTED/g;s/Eventbright 
Link/REDACTED/g;#etc'

3)  Restarted Mailman and possibly web server serving the archive.
(Or otherwise flushed caches.)

I quite like "REDACTED" as it shows that there was something, and that 
it was removed, but it does not show what that something was.


In the end I removed the phone numbers, her personal address and the 
Eventbright links from all messages, including some messages from other 
people where they had re-echoed the Eventbright links as part of their 
conversation to help other people.


Fair enough.


She wasn't very happy,


I doubt there was much more that you could have done.  She's free to be 
upset.  But she shouldn't be upset with you.  You did her a favor that I 
don't think you were strictly compelled to do.


but worse is the person who forwarded it to the mailing list refused to 
understand what they had really done and believed they had the right to 
send the post anywhere as they believed it was in the public domain.


*sigh*

I don't know what to say there.

I feel like that's between her and the event owner / organizer.

Just an example of the type of stuff that I may get asked to remove 
in future.


IMHO that is not unexpected, if not somewhat typical.



--
Grant. . . .
unix || die

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] [Mailman-cabal] GDPR

[Joly MacFie]

​Following with interest, although my mailmans are on Dreamhost and I don't
have root access only admin.

​
RBTF concerns aside, I am wondering how to do a renewed opt-in, similar to
what I see Mailchimp currently running. Any ideas?

-- 
---
Joly MacFie  218 565 9365 Skype:punkcast
--
-
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] GDPR

[Mark Sapiro]

On 5/15/18 11:51 AM, Grant Taylor via Mailman-Users wrote:
> 
> I would likely have (presuming sufficient motivation):
> 
> 1)  Get mailman into a state that I can safely modify the archive.
> 2)  Run a script (likely sed) to REDACT the contents.
>   sed -i$ticketID 's/phone number/REDACTED/g;s/Eventbright
> Link/REDACTED/g;#etc'
> 3)  Restarted Mailman and possibly web server serving the archive.
>     (Or otherwise flushed caches.)
> 
> I quite like "REDACTED" as it shows that there was something, and that
> it was removed, but it does not show what that something was.


I've been silent in this thread because it doesn't interest me that
much, but I want to point out that redacting a pipermail archive is more
difficult than it would first appear.

You not only have to redact the HTML pages, but also the .txt and
.txt.gz files, and if there is sensitive information in the index pages
(subject and sender info), you also have to redact that in the pipermail
database. See the script at  and
read its docstring for an idea.

Finally, you have to redact the cumulative LIST.mbox/LIST.mbox and maybe
the attachments directory.

Actually, the easiest way is to just redact the cumulative
LIST.mbox/LIST.mbox file and rebuild the archive with 'bin/arch --wipe'
but that can have undesired side effects.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] GDPR

[Grant Taylor via Mailman-Users]

Duly noted.

On 05/15/2018 07:04 PM, Mark Sapiro wrote:
Actually, the easiest way is to just redact the cumulative 
LIST.mbox/LIST.mbox file and rebuild the archive with 'bin/arch --wipe' 
but that can have undesired side effects.


Doesn't that run the risk of renumbering messages, thus breaking 
existing links to messages?  Or at least disassociating them such that 
they link to the wrong message?




--
Grant. . . .
unix || die
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org