Re: [Mailman-Users] Maximum attachment size
On Jun 5, 2019, at 8:13 PM, Mark Sapiro mailto:m...@msapiro.net>> wrote: > > On 6/5/19 2:18 PM, Bryan Blackwell wrote: >> >> I've run into an apparent limit in size - we send newsletters through one of >> our lists, and they can get large. One in particular runs over 20MB, and I >> get an error on the held messages page trying to process it. Currently we >> have version 2.1.20, I know there are updates but not if they address this >> limit or if there's some other fix. > > > Others have answered, but what exactly is the error? > > And if it is the Mailman "we hit a bug" error, what's in Mailman's error > log? > > Also as noted by Grant, you can set the web admin General Options -> > max_message_size to zero to avoid this check. Yep, I get the "Bug in Mailman version 2.1.20" error page. This setup handles other attachments pretty well, just this particular person posts much larger files. Below is the log entry, it looks like an out of memory condition. Perhaps I need to tune python itself? Thanks for any clues. --Bryan Jun 06 08:45:56 2019 admin(3662): admin(3662): [- Mailman Version: 2.1.20 -] admin(3662): [- Traceback --] admin(3662): Traceback (most recent call last): admin(3662): File "/home/mailman/scripts/driver", line 117, in run_main admin(3662): main() admin(3662): File "/home/mailman/Mailman/Cgi/admindb.py", line 203, in main admin(3662): process_form(mlist, doc, cgidata) admin(3662): File "/home/mailman/Mailman/Cgi/admindb.py", line 810, in process_form admin(3662): forward, forwardaddr) admin(3662): File "/home/mailman/Mailman/ListAdmin.py", line 167, in HandleRequest admin(3662): forward, addr) admin(3662): File "/home/mailman/Mailman/ListAdmin.py", line 301, in __handlepost admin(3662): inq.enqueue(msg, _metadata=msgdata) admin(3662): File "/home/mailman/Mailman/Queue/Switchboard.py", line 110, in enqueue admin(3662): msgsave = cPickle.dumps(_msg, protocol) admin(3662): MemoryError: out of memory admin(3662): [- Python Information -] admin(3662): sys.version = 2.7.10 (default, Sep 24 2015, 17:50:09) [GCC 5.1.1 20150618 (Red Hat 5.1.1-4)] admin(3662): sys.executable = /bin/python admin(3662): sys.prefix = /usr admin(3662): sys.exec_prefix = /usr admin(3662): sys.path= ['/home/mailman/pythonlib', '/home/mailman', '/home/mailman/scripts', '/home/mailman', '/usr/lib64/python27.zip', '/usr/lib64/python2.7/', '/usr/lib64/python2.7/plat-linux2', '/usr/lib64/python2.7/lib-tk', '/usr/lib64/python2.7/lib-old', '/usr/lib64/python2.7/lib-dynload', '/usr/lib/python2.7/site-packages'] admin(3662): sys.platform= linux2 admin(3662): [- Environment Variables -] admin(3662):HTTP_REFERER: http://www.vv.corvair.org/mailman/admindb/chapters <http://www.vv.corvair.org/mailman/admindb/chapters> admin(3662):CONTEXT_DOCUMENT_ROOT: /home/mailman/cgi-bin/ admin(3662):SERVER_SOFTWARE: Apache admin(3662):CONTEXT_PREFIX: /mailman/ admin(3662):SERVER_SIGNATURE: admin(3662):REQUEST_METHOD: POST admin(3662):PATH_INFO: /chapters admin(3662):HTTP_ORIGIN: http://www.vv.corvair.org <http://www.vv.corvair.org/> admin(3662):SERVER_PROTOCOL: HTTP/1.1 admin(3662):QUERY_STRING: admin(3662):CONTENT_LENGTH: 168 admin(3662):HTTP_USER_AGENT: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36 admin(3662):HTTP_CONNECTION: Keep-Alive admin(3662):HTTP_COOKIE: chapters+admin=28020069ff0af95c7328003264376435346333636532636563386332323239343634363138353338373665396563336336; __utma=58530232.852040186.1559307710.1559307710.1559307710.1; __utmz=58530232.1559307710.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none) admin(3662):SERVER_NAME: www.vv.corvair.org <http://www.vv.corvair.org/> admin(3662):REMOTE_ADDR: 209.83.109.196 admin(3662):PATH_TRANSLATED: /corsa/vv/chapters admin(3662):SERVER_PORT: 80 admin(3662):SERVER_ADDR: 192.168.1.13 admin(3662):DOCUMENT_ROOT: /corsa/vv admin(3662):PYTHONPATH: /home/mailman admin(3662):SCRIPT_FILENAME: /home/mailman/cgi-bin/admindb admin(3662):SERVER_ADMIN: webmas...@tiger.skiblack.com <mailto:webmas...@tiger.skiblack.com> admin(3662):SCRIPT_URI: http://www.vv.corvair.org/mailman/admindb/chapters <http://www.vv.corvair.org/mailman/admindb/chapters> admin(3662):HTTP_HOST: www.vv.corvair.org <http://www.vv.corvair.org/> admin(3662):SCRIPT_URL: /mailman/admindb/chapters admin(3662):HTTP_UP
[Mailman-Users] Maximum attachment size
Hi folks, I've run into an apparent limit in size - we send newsletters through one of our lists, and they can get large. One in particular runs over 20MB, and I get an error on the held messages page trying to process it. Currently we have version 2.1.20, I know there are updates but not if they address this limit or if there's some other fix. --Bryan -- Bryan Blackwell -- Linux Systems Engineer br...@skiblack.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] Systemctl unit file for MM
On Apr 10, 2019, at 11:44 AM, Mark Sapiro wrote: > > You may want to add > > PIPFile=/home/mailman/data/master-qrunner.pid Ok, thanks, will do. > > However, I don't think that's relevant to your issue. I don't know why > the rm command doesn't work. How do you know it doesn't? I touched a test file in the locks directory and it was still there after starting MM. I found the solution after further searching (on an archived systemd-devel mailing list post, of course): >> ExecStart does not go through a shell, so it won't expand wildcards. >> Try running 'find /dir -mindepth 1 -delete', that also cleans up dotdirs. >> Alternatively 'sh -c "rm .../*" to handle wildcards. Problem solved! --Bryan -- 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] Systemctl unit file for MM
Hi folks, I'm learning how to use systemd on my Fedora box, since I still had MM as a script startup I thought I'd fix that. Below is a unit file, it starts and stops ok but the rm command doesn't work. Comments welcome. [Unit] Description=Mailman, the GNU Mailing List Manager After=local-fs.target postfix.service [Service] Type=forking ExecStartPre=/bin/rm -f /home/mailman/locks/* ExecStart=/usr/bin/python /home/mailman/bin/mailmanctl -s -q start ExecReload=/usr/bin/python /home/mailman/bin/mailmanctl -q restart ExecStop=/usr/bin/python /home/mailman/bin/mailmanctl -q stop [Install] WantedBy=multi-user.target -- Bryan Blackwell -- Unix Systems Engineer br...@skiblack.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] Filtering messages with no subject
On May 29, 2018, at 4:33 PM, Mark Sapiro wrote: > > Use header_filter_rules (on the admin Privacy options... -> Spam filters > page. > > A regexp of > > ^subject:\s*(\(no subject\))?\s*$ > > will match messages with an empty Subject: header or literally '(no > subject)', but it's more complicated than that because the message may > have no Subject: header at all. To account for that you need three > rules. The first of these has the regexp above with an action of > discard. The second has the regexp > > ^subject: > > and an action of accept to accept messages with Subject: headers that > didn't match the first rule, and the third has the regexp > > ^.*$ > > and action discard to discard all messages that got past the first two, > i.e. those with no Subject: header at all. > > If you already have header_filter_rules, these three are added after the > others. Otherwise, they are the only rules. > Excellent, thanks. I put them in with 'hold' instead of 'discard' for now just in case I made a mistake. Right now I have a bunch of lines in the Legacy section, is it ok to leave those in place? --Bryan -- 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] Filtering messages with no subject
Hi folks, I'm having trouble with some spam using spoofed addresses getting through to my lists, they all seem to have no subject. I don't see any obvious way to filter these, am I missing an option? If not, has anyone implemented a filter to block these sorts of messages? Thanks for any help, --Bryan -- Bryan Blackwell -- Unix Systems Engineer br...@skiblack.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] Targeted attack against german universities using mailman
On May 9, 2017, at 8:17 AM, Sebastian Hagedorn wrote: > > The bigger issue is that clearly the admin addresses of all lists were > scraped from the public listinfo pages. This means that the same thing could > happen again anytime. :-( Some years ago I ran into this problem, we turned off all the "Advertise this list" options and instead refer to them from other general info pages for the group. That cut down the spam to the lists, admins, and -owners addresses considerably. --Bryan -- Bryan Blackwell -- Unix Systems Engineer br...@skiblack.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
[Mailman-Users] Friendly name for digest sender
Hi folks, I noticed recently that there's no real name for my digest mail - the -request address is correctly displayed, but there no friendly name. So on my Yahoo mail the pop up display for message shows the sender name as "null". Clearly this isn't a big deal, but I looked and couldn't find a setting, is there an easy way to have a name associated with that address? --Bryan -- Bryan Blackwell -- Unix Systems Engineer br...@skiblack.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
[Mailman-Users] Configure admin mail Return-Path
Greetings, I have a functional Mailman 2.1.20 environment on Fedora 22 (I own and built the box). The native domain is skiblack.com, and I host corvair.org. The config and archives were copied over from the old server and normal list delivery works fine. I've had trouble delivering moderator request e-mail and found this error: Oct 3 08:00:29 tiger postfix/smtp[1851]: B63BC16541: to=, orig_to=, relay=mailin-04.mx.aol.com[152.163.0.100]:25, delay=25, delays=0/0/25/0.39, dsn=5.7.1, status=bounced (host mailin-04.mx.aol.com[152.163.0.100] said: 554 5.7.1 : Sender address rejected: Access denied (in reply to MAIL FROM command)) vv-help is a local alias that points to three separate addresses, we are the admins for the lists. Sending mail directly to the alias works fine. I think the issue is localhost.localdomain in the sender header, can someone tell me where that's configured?I've pasted the headers from a moderator e-mail below. Return-Path: X-Original-To: br...@skiblack.com Delivered-To: br...@skiblack.com Received: from tiger.skiblack.com (localhost [127.0.0.1]) by tiger.skiblack.com (Postfix) with ESMTP id 8EE6B1654B; Mon, 3 Oct 2016 08:00:03 -0400 (EDT) Received: from tiger.skiblack.com (localhost [127.0.0.1]) by tiger.skiblack.com (Postfix) with ESMTP id 8E1A916541; Mon, 3 Oct 2016 08:00:03 -0400 (EDT) X-Original-To: virtualvairs-ow...@corvair.org Delivered-To: virtualvairs-ow...@corvair.org Received: from tiger.skiblack.com (localhost [127.0.0.1]) by tiger.skiblack.com (Postfix) with ESMTP id 2E7E316542 for ; Mon, 3 Oct 2016 08:00:02 -0400 (EDT) Received: from tiger.skiblack.com (localhost [127.0.0.1]) by tiger.skiblack.com (Postfix) with ESMTP id 2D4C812877 for ; Mon, 3 Oct 2016 08:00:02 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: 2 VirtualVairs moderator request(s) waiting From: virtualvairs-boun...@corvair.org To: virtualvairs-ow...@corvair.org Message-ID: Date: Mon, 03 Oct 2016 08:00:01 -0400 Precedence: list X-BeenThere: virtualva...@corvair.org X-Mailman-Version: 2.1.20 List-Id: Corvair discussion X-List-Administrivia: yes X-Virus-Scanned: ClamAV using ClamSMTP Errors-To: mailman-bounces@localhost.localdomain Sender: "VirtualVairs" X-Virus-Scanned: ClamAV using ClamSMTP -- 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] illegible message in moderation approval queue
On Sep 22, 2016, at 9:58 PM, Matt Morgan wrote: > > I have a message in a moderation queue. It's from a member (everyone is > moderated on this list) so I think it's not spam or other junk. But when I > click to review it, it's not legible. This is all I see in the message > excerpt: > > IENvbnNkaXNsaXN0DQoNCrOqwMcgaVBob25lv6G8rSC6uLO/ > > I feel like I've seen other messages that look encoded/illegible in > moderation, though I don't have other examples right now. What can cause > this? > > For what it's worth, the sender is a speaker of a language that uses a > different character set, so if that's possible cause, that might be the > reason here. > Hi Matt, Sometimes it's the encoding. Selecting "Additionally, forward this message" and sending it to yourself for review can be very helpful. Of course, it's also possible it's got a forged address and is spam/malware. --Bryan -- 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] Filtering out Digest replies
> On Jul 6, 2016, at 9:21 AM, Jim Popovitch wrote: > > I've been inspired by something I read somewhere else. > > I have long thought that mailing lists should be > configured to reject messages with a Subject of > "Re: [the subject format for the list's digest messages]". > Maybe a scan of the message content for a copy > of the digest prologue would be a good idea as well. > > and now I want to implement something like this. > > > Will this generic Spam filter work: > > Subject: Re: \[.*\] .* Digest, Vol [0-9]+, Issue [0-9]+ > > > Tia, > > -Jim P. Mine is simpler than that. Name of the list is VirtualVairs, thus: Subject: .*VirtualVairs Digest, Vol.* --Bryan -- 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 owner delivery
On Feb 22, 2016, at 5:40 PM, Mark Sapiro wrote: > > On 02/22/2016 01:51 PM, Bryan Blackwell wrote: >> I found one little thing that >> doesn't. Held message e-mails going to the -owner addresses have a >> strange issue. I have "list-help" aliases for all my lists, and the >> MM list owners are set to those addresses. > > > Do you mean that you have an additional per-list alias like > > LISTNAME-help: "|/path/to/mailman/mail/mailman owner LISTNAME" > > Or do you mean something else? Something else. In the system alias file I have: LISTNAME-help: bryan, den...@foo.com, m...@bar.com The Mailman List Owner points to that. I get the messages, but Dennis and Matt do not. > > >> I've verified that the >> aliases work, and deliver mail to all the folks on the alias if I >> just send a message. However, Mailman -owner mail only comes to me >> (I'm the first address on the list and local to the box). I can find >> no errors in the logs, it all looks like it's working (status=sent). > > > Does the postfix log say for mail to mailman-owner > > status=sent (delivered to command: /path/to/mailman/mail/mailman owner > mailman) > > or something else. If it delivers as above, Mailman should then resend > the mail to all addresses listed as owner or moderator of the mailman > list. Is this not happening? > That's just what I'm getting. No errors, it appears to deliver to the system alias but the alias never gets expanded. The system alias otherwise works as expected, it's something specific to the MM -owner mail. --Bryan -- 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 owner delivery
Hi all, I have a minor mystery. I recently migrated to a new server, hosting a half dozen or so Mailman lists. The old server ran on Fedora 8, but I had upgraded to Mailman 2.1.18. The new server is Fedora 22, running Mailman 2.1.20. Postfix is the MTA on both. Migration was just to copy over ~mailman, install the new software (same paths), install /etc/aliases and ~mailman/aliases. And everything worked! Or so I thought, I found one little thing that doesn't. Held message e-mails going to the -owner addresses have a strange issue. I have "list-help" aliases for all my lists, and the MM list owners are set to those addresses. I've verified that the aliases work, and deliver mail to all the folks on the alias if I just send a message. However, Mailman -owner mail only comes to me (I'm the first address on the list and local to the box). I can find no errors in the logs, it all looks like it's working (status=sent). Any suggestions appreciated. --Bryan -- Bryan Blackwell -- Unix Systems Engineer br...@skiblack.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] Message may contain ... administrivia?
> On Oct 1, 2015, at 1:35 AM, Steve Matzura wrote: > > Well now I've seen everything. Why would Mailman send a return message > to a subscriber to a mailing list that says their message couldn't be > posted to the mailing list because "message may contain > administrivia"? When e-mail lists had no web interface, subscribers would often send admin commands - "unsubscribe", "set digest", etc., to the actual list instead of the admin address. This was pretty common when MJ lists were ported to MM. Those filters are in place to catch those, in part to avoid the follow on "RTFM" posts to the main list. Probably just as well to turn them off, most people use the web interface nowadays and have for some time. --Bryan -- 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] Question about confirming each email for one subscriber
Easy to do - check the "mod" (for "moderate") box next to their name on the member list, and set the list so moderated messages are held for review under Privacy options... > Sender filters > member_moderation_action. --Bryan > On May 28, 2015, at 5:17 PM, Nancy C wrote: > > Hi > > > > We have a member who is very computer / email illiterate & continually sends > emails that should not get through > > to the group as a whole. > > > > Is there a setting that could be made so her emails always come to the > listkeepers first? > > > > Thank you for any help :) > > > > Nancy > > -- > 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/bryan%40skiblack.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] How to hide one list from the page https:///mailman/admin?
On the "Privacy Options" main page (/privacy>) for a given list, set "Advertise this list" to No. --Bryan > On Apr 8, 2015, at 9:25 AM, Xie, Wei wrote: > > I have a quick question - when any user can look at all mailman lists from > our admin page https:///mailman/admin, my boss asks whether we can > hide some VIP lists from all mailman lists. Because recently some spammers > sent subscribers request to all lists of our university and attempted to join > all lists. Some lists were set to "require approval", so the subscriber > requests were pending for approval and notices were sent to owners. My boss > wanted some VIP lists are hidden. > -- 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] No mail received
On Mar 3, 2015, at 8:08 PM, len ward wrote: > > Hi > I manage a list of 60 members. If I send an email it does not get to > anybody, yet it is recorded in archives. Same for most others, although I > know one person gets through and maybe others. How do I fix this? > Regards len I found that DMARC is pervasive enough to cause this behavior. Using "munge from" fixed it for me, be aware you need a very recent version of MM to have the options. --Bryan -- 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] From munging to show user via listname
On Feb 18, 2015, at 6:04 PM, Mark Sapiro wrote: > > If you have command line access, you could try running 'bin/config_list > -o fname listname' on both lists and diff the results. > Never mind, I found it - it's a display issue. Argh. Thanks for the help, I was going a bit bonkers. FWIW, I did find a fix to something else I was looking to take care of while I've been reading the screens. --Bryan -- 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] From munging to show user via listname
On Feb 18, 2015, at 2:19 PM, Mark Sapiro wrote: > > On 02/17/2015 06:21 PM, Bryan Blackwell wrote: >> Greetings, >> >> I dug through the archive but couldn't quite find the answer to this >> question. I have a couple e-mail lists I manage, I thought I had them set >> up identically but I'm stuck getting the From address to appear the way I >> want it. One list's messages comes through as: >> >> From: via >> >> This is what I want. The other is: >> >> From: > > > Is this list set anonymous_list Yes? if not, are both lists on the same > Mailman server? > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan Both lists are on the same host, same domain, and both have anonymous_list set to "No". I forgot to mention, I'm on Mailman version 2.1.18-1. --Bryan -- 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] From munging to show user via listname
Greetings, I dug through the archive but couldn't quite find the answer to this question. I have a couple e-mail lists I manage, I thought I had them set up identically but I'm stuck getting the From address to appear the way I want it. One list's messages comes through as: From: via This is what I want. The other is: From: Which is not what I'm looking for. Other than that, everything works as desired. Thanks for any clues. -- Bryan Blackwell -- Unix Systems Engineer br...@skiblack.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] Permission problems cause postfix postalias error
Did you install Mailman as root, or with the mailman user? That might be it. -- -- Bryan Blackwell -- Unix System Administrator [EMAIL PROTECTED] On Mar 3, 2005, at 3:32 AM, Graham Leggett wrote: - The check_perms script is setting the ownership of the files to "root", when the docs say they should be "mailman". -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] How to transfer Majordomo archive to mailman
On Mar 1, 2005, at 2:51 AM, Martin Mewes wrote: Hi Bryan, no need to send a post to the list _and_ a cc to me as I am reading the list :-) Oops, sorry, I thought I had changed the To address :-( Bryan Blackwell <[EMAIL PROTECTED]> wrote : Majordomo doesn't (by default anyway) store its sent messages in an mbox. My archives are essentially a directory with all the digests. You can see one of the digests here: http://www.corvair.org/chapters/test/v02.n4928.txt As far as I can see you should provide a real mbox where eMails are stored with full headers. If you do not have one, you can only re-post them to the new mailman-list, but I am unsure about that. Nope, no mbox. Re-posting won't work since I don't have the individual posts. Looks like I may end up writing something, it just surprises me that no one else has had this problem and posted a solution - this is the default Majordomo archiving mechanism. I guess all the folks who really wanted web archives had already converted to a real archiver and worked from that. --Bryan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] Moving of the subscribers with their passwords, preferences etc.
I just did exactly this, following the procedure at: http://www.mail-archive.com/mailman-developers@python.org/msg03127.html Worked great. -- -- Bryan Blackwell -- Unix System Administrator [EMAIL PROTECTED] On Feb 28, 2005, at 6:38 PM, Andy wrote: Hi! Is that possible during moving of the lists to a new server to move all users along with their e-mails, names, passwords and preferences they set, so that they would not need to resubscribe (or that list-owner would not need to subscribe them again, what would unfortunately generate new passwords for them)? Which files to move in order to do that? Regards ak -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] How to transfer Majordomo archive to mailman
I've been looking for an answer to migrating archives as well. The only problem with this procedure is this step: On Feb 28, 2005, at 4:51 PM, Martin Mewes wrote: d) Copy the mbox of the majordomo-list to the correct place of the mailman-mbox Majordomo doesn't (by default anyway) store its sent messages in an mbox. My archives are essentially a directory with all the digests. You can see one of the digests here: http://www.corvair.org/chapters/test/v02.n4928.txt I've taken a look at the old digest_arch script, but I don't know python at all to figure out how to make it work (I tried a pass on some test files, but didn't end up with a useful mbox). I've also dug through the FAQ and the Mailman Users list archive, but I haven't found a posted solution. If someone has made this work and can pass a solution or clue, I'd be grateful. I do know perl and shell scripting well enough to adapt someone else's solution, if something like that exists. Thanks for any insight. -- -- Bryan Blackwell -- Unix System Administrator [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
