Re: [Mailman-Users] command line tool to list ban_list, discard_these_nonmembers, accept_these_nonmembers, etc
Thanks, Mark. That works perfectly. -- Matthew Needham mneed...@hdfgroup.org 217-531-6110 The HDF Group 1800 South Oak Street, Suite 203 Champaign, IL 61820 -- 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] command line tool to list ban_list, discard_these_nonmembers, accept_these_nonmembers, etc
Mark,
> On Jul 8, 2016, at 17:39 PM, Mark Sapiro <m...@msapiro.net> wrote:
>
> On 7/8/16 10:11 AM, Matthew Needham wrote:
>> Is there a succinct way to list "auxiliary" addresses that are configured in
>> a list? By "auxiliary" I'm referring to addresses other than member, owner,
>> or moderator, since those are easy to find with list_owners and find_members.
>
> Since it was trivial to do, I just created
> <https://www.msapiro.net/scripts/list_etc.py>. Try it.
Thanks! However, I'm seeing "ValueError: zero length field name in format"
whether I run it for all lists or one:
[root@lw4 mailman]# ./bin/withlist -a -r list_etc
Importing list_etc...
Running list_etc.list_etc()...
Loading list hdf5lib_lists.hdfgroup.org (unlocked)
Traceback (most recent call last):
File "./bin/withlist", line 299, in
main()
File "./bin/withlist", line 274, in main
r = [do_list(listname, args, func) for listname in Utils.list_names()]
File "./bin/withlist", line 202, in do_list
return func(m, *args)
File "/usr/local/cpanel/3rdparty/mailman/bin/list_etc.py", line 29, in
list_etc
print('List:{}'.format(mlist.real_name))
ValueError: zero length field name in format
Finalizing
[root@lw4 mailman]# ./bin/withlist -r list_etc hdf-forum_lists.hdfgroup.org
Importing list_etc...
Running list_etc.list_etc()...
Loading list hdf-forum_lists.hdfgroup.org (unlocked)
Traceback (most recent call last):
File "./bin/withlist", line 299, in
main()
File "./bin/withlist", line 277, in main
r = do_list(listname, args, func)
File "./bin/withlist", line 202, in do_list
return func(m, *args)
File "/usr/local/cpanel/3rdparty/mailman/bin/list_etc.py", line 29, in
list_etc
print('List:{}'.format(mlist.real_name))
ValueError: zero length field name in format
Finalizing
Have I missed something?
Thanks again.
--
Matthew Needham
mneed...@hdfgroup.org
217-531-6110
The HDF Group
1800 South Oak Street, Suite 203
Champaign, IL 61820
--
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] command line tool to list ban_list, discard_these_nonmembers, accept_these_nonmembers, etc
Is there a succinct way to list "auxiliary" addresses that are configured in a list? By "auxiliary" I'm referring to addresses other than member, owner, or moderator, since those are easy to find with list_owners and find_members. I'm trying to practice better list hygiene, and remove all relevant address when someone leaves the organization. The best way I've currently found is use a foreach loop to grab each list's config.pck and run dumpdb against it. I then filter out the uninteresting addresses and manually scan the results for relevant addresses. I can't simply grep the output for relevant addresses, because a subscriber john@domain.com may be allowed (or disallowed) to post from jd...@free-email.com. I don't mind the manual scanning, but parsing the output if dumped is time consuming. I'm guessing there's a way to grep for the relevant settings and all relevant following lines, but my regex skills have not been up to the task. I took a look at https://www.msapiro.net/scripts/non_members, but it appears to require that I know the addresses in advance, and not allow me to discover the relevant addresses. It also doesn't support ban_list, which is admittedly a rare occurrence for me, but I don't know if there are other unincluded settings I should be considering. I suppose this raises a question of other possible list hygiene best-practices. Besides removing subscriptions and removing/reassigning administrator or moderator responsibilities, when else should I be doing to clean up when someone leaves? Thanks! -- Matthew Needham mneed...@hdfgroup.org 217-531-6110 The HDF Group 1800 South Oak Street, Suite 203 Champaign, IL 61820 -- 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] View the Private mail lists from UI
On Jun 2, 2015, at 21:53 PM, Mark Sapiro m...@msapiro.net wrote: I suppose there could be an authentication requiring the site password (for various reasons, it couldn't be a list admin password) on the admin and listinfo overview pages to see 'all' lists, but there is not such a feature. Although my Mailman install is is currently part of CPanel, so I don't need such a feature, it does seem like it would be useful. Does this sort of functionality exist in Mailman 3? -- Matthew Needham mneed...@hdfgroup.org 217-531-6110 The HDF Group 1800 South Oak Street, Suite 203 Champaign, IL 61820 -- 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] The right way to reply to a mailing list
On Mar 21, 2015, at 19:52 PM, William Bagwell rb...@tds.net wrote: On Saturday 21 March 2015, Al Black wrote: Although the ideal solution is obviously users changing their behaviour and or MUAs, I've wondered whether an auto-trim function within mailman would make sense (for digest users...) Yes! For every one, not just digest users. And it should default to removing all but one single level of quoted text (regardless of top or bottom posting) and be *user* setable to none removed or all quoted text removed. The email interface for our ticket system attempts to avoid these sorts of problems in comments by automatically stripping all quoted text. It undoubtedly could work better than it does (perhaps a more recent version does), and this situation is certainly different from a mailing list, but it has convinced me that any programmatic trimming of content is bound to cause problems for users. Despite this, due to the preponderance of the very issues discussed in this thread, the feature is still useful and enabled. -- Matthew Needham mneed...@hdfgroup.org 217-531-6110 The HDF Group 1800 South Oak Street, Suite 203 Champaign, IL 61820 -- 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] The right way to reply to a mailing list
On Mar 20, 2015, at 03:23 AM, Peter Shute psh...@nuw.org.au wrote: If you're referring to the problem of getting the selection boundaries in exactly the right spot, I'm well familiar with that. So easy to get them within one or two characters, but requires excessive concentration and effort to get them closer. Don't know why they don't add cursor keys to help with it. NextApp Keyboard does have arrow keys, as well as a key to switch from cursor movement to selection movement and other useful things missing from most soft keyboards. It's not nearly as easy as with a real keyboard, but it does at least provide the functionality. -- Matthew Needham mneed...@hdfgroup.org 217-531-6110 The HDF Group 1800 South Oak Street, Suite 203 Champaign, IL 61820 -- 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] Executive summary of DMARC issues
Around a year ago we started using Exchange Online. In my experience, the undesired responses are correct. On May 16, 2014, at 09:13 AM, mail.ulticom.com g...@ulticom.com wrote: My management wants to replace our in-house email with an Exchange Online (aka MS365) solution. Several high priced consultants have told them that Exchange can do it all. I am trying to prove otherwise. Actually to be fare, two consulting firms have said: 1. Exchange can't do what Mailman can. It has fancy forwards, but besides rudimentary moderation, very little in the way of traditional mailing list features. 2. MS365 can't work with Mailman. I migrated my lists to a dedicated subdomain to work around this, and some of the details surrounding that are documented in the list archives. 3. MS365 will cost more, don't do it. This may or may not be true. It’s a subscription service, so costs will change. It seems like these services are trending to go down in price as competition goes up and more users sign on, but not always. (We qualified for nonprofit pricing, which has gone from $2/user/mo to FREE, which is nice. However, we’ve been told that we no longer qualify for the nonprofit program.) Feel free to contact me directly for more details. -- Matthew Needham mneed...@hdfgroup.org 217-531-6110 The HDF Group 1800 South Oak Street, Suite 203 Champaign, IL 61820 -- 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] Executive summary of DMARC issues
On May 14, 2014, at 22:47 PM, Stephen J. Turnbull step...@xemacs.orgmailto:step...@xemacs.org wrote: If distribution lists are pure forwards, MS365 will be OK. But I find it hard to believe that that level of functionality is popular with users -- there's a reason why all popular MLMs implement subject prefixes, body headers and body footers, and it isn't because it's the Microsoft way. Exchange Online (standalone or as part of Office 365) really does lack most of the basic mailing list functionality. It does have moderation, but no subject tagging, list footer, etc. I believe the main reason distribution groups get used is because of the integration with Outlook and compatibility with Exchange Calendaring (inviting a Mailman list to a meeting is bad). It is limited, but in many cases is “good enough”, and many people don’t know what they’re missing. Here’s a table comparing select features of the two: [cid:2EBFB349-BF05-4E11-BED3-DCE3885C4D60@hdfgroup.uiuc.edu] -- Matthew Needham mneed...@hdfgroup.orgmailto:mneed...@hdfgroup.org 217-531-6110 The HDF Group 1800 South Oak Street, Suite 203 Champaign, IL 61820 -- 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] A word to the wise: spam-checking and RFC conformance
On my server, it was being instead by spamassassin and was then visible in each message handled by Mailman. The “content-preview” in the header is easily removed in /etc/mail/spamassassin/local.cf. Matthew On May 14, 2014, at 02:52 AM, Stephen J. Turnbull step...@xemacs.org wrote: Hi all, I just discovered that the spam-checker for a non-Mailman list I subscribe to (I suspect SpamAssassin but I can't confirm yet, the MLM is ListServ) is introducing 8-bit characters into the header. What appears to be happening is that the original post uses a Content-Transfer-Encoding of 8bit or binary, and contains some 8-bit octets (typically fancy quotes and the occasional accented character in the posts I receive), and the spam checker copies an excerpt from the body into the X-Spam-Report field *verbatim*, including the non-ASCII characters. If your spam-checker doesn't produce an X-Spam-Report field or similar, you don't have the problem. If it does, you might want to check its behavior with respect to body excerpts. Regards, Steve -- 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/mneedham%40hdfgroup.org -- Matthew Needham mneed...@hdfgroup.org 217-531-6110 The HDF Group 1800 South Oak Street, Suite 203 Champaign, IL 61820 -- 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] fixing a reordered archive
On Jun 17, 2013, at 13:01 PM, Mark Sapiro m...@msapiro.net wrote: On 06/17/2013 10:21 AM, Matthew Needham wrote: Older.mbox contains 1512 messages, five of which contain unescaped lines starting with From . What's the best way to escape those lines and preserve archive order? Is it as simple as escaping the line and adding an empty From immediately after the containing message? Yes, that should do it. It did work, but I noticed that cleanarch complained about the new lines. I was a little concerned that a future admin would notice the warnings and fix them in a way that broke the archives, so I inserted lines like this: From nob...@hdfgroup.org Thu May 31 00:00:00 2007 Date: Thu May 31 00:00:00 2007 That placed the five empty messages at the very beginning of the archives where they're least likely to bother anyone. This is better than the previous location at the end of the archives, and much better than the previous problem with missing content after the unescaped From. With these changes, a fixed, reordered, and consolidated mbox, and a readme file to inform any future admins, I hope this problem won't return. Thanks for all your help. -- Matthew Needham The HDF Group 1800 South Oak Street, Suite 203 Champaign, IL 61820 217-531-6110 mneed...@hdfgroup.org -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] fixing a reordered archive
On Jun 12, 2013, at 18:09 PM, Mark Sapiro m...@msapiro.net wrote: On 06/12/2013 12:10 PM, Matthew Needham wrote: As best as I can tell, there's no way for me to determine which messages were in the archive before older.mbox was added. Is there a way? If you still have the old archive (maybe on a backup), the first message in that archive from older.mbox has number nn. Message nn-1 is the last of the messages that were in the archive when older.mbox was added. It took a little while to figure out, but I believe I've gotten everything straightened out. It looks like my complication was the fact that cleararch had been run on my current version of older.mbox, but no when it was originally added to the archives. I found the original file and everything lines up. Thanks for getting me this far. Older.mbox contains 1512 messages, five of which contain unescaped lines starting with From . What's the best way to escape those lines and preserve archive order? Is it as simple as escaping the line and adding an empty From immediately after the containing message? -- Matthew Needham The HDF Group 1800 South Oak Street, Suite 203 Champaign, IL 61820 217-531-6110 mneed...@hdfgroup.org -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] fixing a reordered archive
A couple of weeks ago I moved all of my mailing lists to a new subdomain. So far, everything has worked great, but I've now discovered that the archive message numbering has changed. For example, I'm referring to the numbers 006782 at the end of a URL like http://lists.hdfgroup.org/pipermail/hdf-forum_lists.hdfgroup.org/2013-May/006782.html. I believe that this happened because after the list was first created in mailman (in 2009), older archives were added using arch listname older.mbox. My hypothesis is that if I were able to separate the current mbox into the messages that existed before older.mbox was archived, and those that were added afterwards, I could then rebuild the archive in the original order so that the message numbering would be preserved. As best as I can tell, there's no way for me to determine which messages were in the archive before older.mbox was added. Is there a way? Alternatively, is these a better way to preserve all of the links that are now sitting in Google, various third party archives, sundry word documents, and user mailboxes? Or is this a fool's errand I should abandon posthaste? In case it helps, before migrating the lists I made tarballs of everything, so I still have access to the archives before they were rebuilt. Thanks. -- Matthew Needham The HDF Group 1800 South Oak Street, Suite 203 Champaign, IL 61820 217-531-6110 mneed...@hdfgroup.org -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] moving a mailing list to a new subdomain
On May 17, 2013, at 12:34 PM, Mark Sapiro m...@msapiro.net wrote: On 05/17/2013 08:45 AM, Matthew Needham wrote: An update... On May 16, 2013, at 14:48 PM, Matthew Needham mneed...@hdfgroup.org wrote: 1. For the situation I described, are the instructions on that FAQ (moving the files) the ones I should be following? They are as good as any. 2. Should the arch --wipe command really be fixing the links to the scrubbed attachments? I also tried renaming the list from list1 to list2 without changing the domain, and that didn't help. It seems like it should be easy enough change them manually, but I'd rather use whatever mechanism Mailman provides. The URL in the archives is updated for attachments that were received when scrubbing is OFF. For attachments that were received when scrubbing is ON, the URL is not rewritten and still points to the old list. The issue here is that bin/arch --wipe will fix the links to attachments scrubbed during the archiving process. However, for attachments scrubbed during incoming message processing because scrub_nondigest is Yes, the situation is different. The attachment was saved in the attachments directory and replaced by a link in the actual message body. Thus, the LIST.mbox file contains only the link in the body and the only place the scrubbed attachment exists is in the attachments directory on the old server. The only way to fix this is to move the actual files from the attachments directory on the old server and update the links manually or possibly with some programmatic process. Thanks, I'll make a script to fix these. -- Matthew Needham The HDF Group 1800 South Oak Street, Suite 203 Champaign, IL 61820 217-531-6110 mneed...@hdfgroup.org -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] moving a mailing list to a new subdomain
I have a mailman install under cPanel, and I need to move my lists from listn...@bigdata.org to listn...@lists.bigdata.org. I've read quite a few webpages about how to move lists and rename lists, and I've done a lot of testing. I feel like I'm very close to getting this to work. The only problem that remains is scrubbed attachments. I've followed the directions at http://wiki.list.org/pages/viewpage.action?pageId=4030617, and while it says that links to scrubbed attachments [that] point to the oldlist can be fixed with bin/arch --wipe newlist, this doesn't work for me. the command completes without error, but when I look at an archived message, the I still see URL: http://mail.bigdata.org/mailman/private/listname_bigdata.org/attachments/20130513/5d587194/attachment.obj I have two questions. 1. For the situation I described, are the instructions on that FAQ (moving the files) the ones I should be following? 2. Should the arch --wipe command really be fixing the links to the scrubbed attachments? I also tried renaming the list from list1 to list2 without changing the domain, and that didn't help. It seems like it should be easy enough change them manually, but I'd rather use whatever mechanism Mailman provides. Thanks. -- Matthew Needham The HDF Group 1800 South Oak Street, Suite 203 Champaign, IL 61820 217-531-6110 mneed...@hdfgroup.org -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] moving a mailing list to a new subdomain
An update... On May 16, 2013, at 14:48 PM, Matthew Needham mneed...@hdfgroup.org wrote: I have a mailman install under cPanel, and I need to move my lists from listn...@bigdata.org to listn...@lists.bigdata.org. I've read quite a few webpages about how to move lists and rename lists, and I've done a lot of testing. I feel like I'm very close to getting this to work. The only problem that remains is scrubbed attachments. I've followed the directions at http://wiki.list.org/pages/viewpage.action?pageId=4030617, and while it says that links to scrubbed attachments [that] point to the oldlist can be fixed with bin/arch --wipe newlist, this doesn't work for me. the command completes without error, but when I look at an archived message, the I still see URL: http://mail.bigdata.org/mailman/private/listname_bigdata.org/attachments/20130513/5d587194/attachment.obj I have two questions. 1. For the situation I described, are the instructions on that FAQ (moving the files) the ones I should be following? 2. Should the arch --wipe command really be fixing the links to the scrubbed attachments? I also tried renaming the list from list1 to list2 without changing the domain, and that didn't help. It seems like it should be easy enough change them manually, but I'd rather use whatever mechanism Mailman provides. The URL in the archives is updated for attachments that were received when scrubbing is OFF. For attachments that were received when scrubbing is ON, the URL is not rewritten and still points to the old list. Incidentally, message headers report that this is Mailman 2.1.15. Thanks. -- Matthew Needham The HDF Group 1800 South Oak Street, Suite 203 Champaign, IL 61820 217-531-6110 mneed...@hdfgroup.org -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
