Mailman 3 July 2014 - Mailman-Users

Editing Mailman's text files
by Pete Bell May 7, 2024

May 7, 2024

Hi. I'm a new member of this group but have been running an email list with Mailman for a long time. I am now setting a list up again and want to give a "look and feel" to the list which has more branding of my user group as a whole, and less of a Mailman-feel. I seem to remember that besides editing the public HTML pages, it is possible to edit the text files which Mailman automatically sends out for certain needs (such as 'approve.txt', 'adminsubscribeack.txt', 'invite.txt', and so on). A. Is this still the case? B. If so, where can I find them? (in case they've changed from the ones I have from long ago). C. Where do they need putting, so that Mailman can use them again? It's important that I should tell you that Mailman on my webhosts servers is a "server-wide" installation, and I don't get to edit anything which other clients to their servers need. This would be only for my own use, and as such I need to know where these files go in my own webspace, and how to get Mailman to use them instead of the default ones. I should also say that I have done this before, so unless the facility to do this has been ditched in recent years, I *should* still be able to do it ! Does Mailman perhaps look for these files somewhere in my webspace (which I have to give a specific name), and if it doesn't find them it goes on to find its default versions of these files? Thanks in advance for your help. Pete Bell, UK

3 3

Running two list with same email prefix
by Andrea Cappelli Feb. 26, 2024

Feb. 26, 2024

Hi all, I'm running a mail server with Debian Lenny, MTA is Postfix and i will use postfix-to-mailma.py script to run list I would set up Mailman for running mailing list with same email prefix on different domains, obvious with different list names For example we have ml.domain1.com and ml.domain2.net, i would like to have LISTADDRESS LISTNAME tech(a)ml.domain1.com tech-ml.domain1.com tech(a)ml.domain.2.net tech-ml.domain2.net In this way i can have the same address on differente domains and Mailman (my version is 2.1.11) can distinguish between lists because the list name is different. The list name will be also used to access web interface, so we have http://ml.domain1.com/mailman/admin/tech-ml.domain1.com http://ml.domain2.net/mailman/admin/tech-ml.domain2.net Is possible to accomplish this task? Any idea?

4 5

Hide list address?
by Ricardo Kleemann Nov. 16, 2023

Nov. 16, 2023

Hi, Is there any way to configure Mailman such that, for an announcement-only type list, when a message is sent to the list, the To: shows the member's address, rather than the list address? Some list software allows the ability to hide the list address itself, so that address is not advertised. I couldn't find any configuration specific to that.

7 6

Add "sender's name/email" to BODY of mail as header?
by Mal Feb. 16, 2021

Feb. 16, 2021

I want all mails sent to the list to come from the list's email address... But, in this case, if the user forgets to sign their name at the bottom of their mail body, effectively the mail to the list is anonymous...! Is there a way to add the user name (or email address) to the top of each mail so that the mails have the name of the sender, while the mail itself comes from the list address? I have looked high and low for an answer, but noone seems to have the solution. Thank you! Mal

9 14

Mailman CGI Error-Group mismatch error
by Wang, Mary Y Sept. 9, 2020

Sept. 9, 2020

Hi, I received the following error this morning. So I rerun configure again with the following command: ./configure --with-cgi-id=apache --prefix=/var/mailman. I'm still getting the same error. Is there any place that I can look for so that I can debug this problem better? Perhaps, looking at the config history file or something. Any other places that I can check the cause of this error? "Mailman CGI error!!! The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog: Group mismatch error. Mailman expected the CGI wrapper script to be executed as group "nobody", but the system's web server executed the CGI script as group "apache". Try tweaking the web server to run the script as group "nobody", or re-run configure, providing the command line option `--with-cgi-gid=apache'." Thanks Mary

3 3

Re: [Mailman-Users] Is there tool convert archived files/directories into a mbox file?
by Mark Sapiro March 2, 2015

March 2, 2015

On 05/10/2013 06:35 AM, Xie, Wei wrote: > > Here we have one customer to request migrating all old archived files of > mailing list ‘kinejapan’ under directory > /usr/local/mailman/archives/private/kinejapan prior to 2009 (as attached > file) to Yale university. Yale university IT guys needs us to create a > mbox file for these old archived file to be easy for them to run > command ‘archdo migration. > > > > I check there is no file kinejapan.mbox under directory > /usr/local/mailman/archives/private/kinejapan.mbox to match these old > archived files as attached. This mailing list was maintained by our > pre-mailman admin, who passed away 2011, so I do not know why the mbox > file was missing. If ARCHIVE_TO_MBOX is set to 0 in mm_cfg.py, Mailman will not create/update LISTNAME.mbox/LISTNAME.mbox files. > Do you know whether there is a tool/method to convert these old archived > files/directories as attached into a mbox file? Lots of information is lost if there is no .mbox file. You can do as well as anything with cat /usr/local/mailman/archives/private/kinejapan/*.txt > kinejapan.mbox -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 9

We're sorry, we hit a bug!
by Roel Wagenaar Jan. 10, 2015

Jan. 10, 2015

L.S. Bug in Mailman version 2.1.15 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. The above message shows up on the web pages, unfortunately the last log written to is qrunner, error is empty, so no info on what it is about. The last thing changed is the adres of the main pages. It looks like the mail-system is not affected, any idea what is going on? Would like to show some logging, but it simply is not there. -- Roel Wagenaar, Linux-User #469851 with the Linux Counter; http://linuxcounter.net/ Antw.: Omdat het de volgorde verstoord waarin mensen tekst lezen. Vraag: Waarom is top-posting een slechte gewoonte? Antw.: Top-posting. Vraag: Wat is het meest ergerlijke in e-mail? Why be difficult, when with a bit of effort, you can be impossible?

3 4

Erratic mail delivery times
by Peter Shute Sept. 4, 2014

Sept. 4, 2014

As a moderator of our list, I know when messages are approved, and I'm seeing very erratic delivery times to my own address, which is on an Exchange server. They used to come through within a minute or so, now they can take 20 minutes or an hour. I subscribed my gmail address for comparison, and am finding that the same list messages come through to it as quickly as ever. >From those observations I would conclude that the Exchange server is having problems receiving external mail, but I've found that test messages sent from my gmail account to my Exchange address come through within seconds. Can I assume this has nothing to do with mailman? Peter Shute Sent from my iPad

10 39

Erroneous results with Find_member
by Kyle Vernon July 29, 2014

July 29, 2014

This probably isn't the forum for questions, and I've submitted a request to join the user mailing list, however, I'm in a bit of a time pinch and would like to know if you guys have seen this before and if so, what might be the cause. When I run the find_members script natively on the mailman box I get this result: root@mbox1:/opt/mailman/bin# ./find_member -w k.vernon(a)ntta.com<mailto:k.vernon@ntta.com> k.vernon(a)ntta.com<mailto:k.vernon@ntta.com> found in: billinglist dbdev2-notice (as owner) it_storage it_storage (as owner) san_notify (as owner) itlist dbdev1-notice (as owner) db1-notice (as owner) ccrb mailman mailman (as owner) nttadallas db2-notice (as owner) peoplesoftlist shap-notice shap-notice (as owner) it_unix it_unix (as owner) hardwaremaint scan_results db3-notice (as owner) it_dns it_dns (as owner) it_server (as owner) ntta-corporate it_backup it_backup (as owner) page_unix (as owner) ilom_alerts ilom_alerts (as owner) zmanda zmanda (as owner) But when I run it from inside a script, I get totally different results: ################################################################## ## NOTE NOTE NOTE NOTE ## ## This part of script produces erroneous ## ## results. Do NOT trust ## ################################################################## #SSH to mbox1 and run /opt/mailman/bin/find_member USERNAME=kyle HOST=mbox1.it.ntta.com SCRIPT="op mailmanscripts /opt/mailman/bin/find_member -w ${2} " ssh -o StrictHostkeyChecking=no -l ${USERNAME} ${HOST} "${SCRIPT}" cas-webomerrors(a)verio.net<mailto:cas-webomerrors@verio.net> found in: webomusers k.vernon(a)ntta.com<mailto:k.vernon@ntta.com> found in: ccrb it_storage mailman ntta-corporate shap-notice it_backup it_unix hardwaremaint billinglist nttadallas peoplesoftlist itlist ilom_alerts scan_results it_dns zmanda Kyle A. Vernon IT Systems and Storage Professional NTT America 1950 N Stemmons Fwy, #2001 Dallas, TX 75207 214-800-7519 office 903-879-1360 cell ________________________________ This email message is intended for the use of the person to whom it has been sent, and may contain information that is confidential or legally protected. If you are not the intended recipient or have received this message in error, you are not authorized to copy, distribute, or otherwise use this message or its attachments. Please notify the sender immediately by return e-mail and permanently delete this message and any attachments. makes no warranty that this email is error or virus free. Thank you. **************************************************** ************ This email message is intended for the use of the person to whom it has been sent, and may contain information that is confidential or legally protected. If you are not the intended recipient or have received this message in error, you are not authorized to copy, distribute, or otherwise use this message or its attachments. Please notify the sender immediately by return e-mail and permanently delete this message and any attachments. NTT America makes no warranty that this email is error or virus free. Thank you. **************************************************** ************

2 1

emails from mailman rejected with error "reject=550 Relaying denied. IP name possibly forged"
by Abdullah Maskari July 29, 2014

July 29, 2014

Hi, I seem to have an issue with my mailhost server randomly rejecting emails from my mailman server whenever they are directed externally. My current setup is I have a mailman server running mailman and sendmail which sends all emails to my mailhost server also running sendmail. Mailhost passes the emails through mailscanner etc. and then relays them either externally or internally based on the target email. Internal relaying works just fine but external relaying seems to sporadically accept some addresses for delivery and reject others. the choice of addresses it chooses to accept or reject is different for every attempt I am so for example for my first attempt it will forward the email to the first and 3rd external email addresses and reject to forward to the rest and on the 2nd attempt it rejects the the 2nd and 3rd and 4th but sends the emails to the 1st and 5th addresses just fine and so on. My mailman server's logs do not show any errors but my mailhost does. this is the extract in question from my mailhost server mail log file: Jul 24 09:08:52 mailhost sm-mta[3296]: s6O88pSr003296: from=<Source-email(a)external-domain.com>, size=2260, class=0, nrcpts=1, msgid=<cq0nx1du5icvm2eubfc8lvdy.1406189339980(a)email.android.com>, proto=ESMTP, daemon=MTA-v4, relay=mail-we0-f174.external-domain.com [74.125.82.174]Jul 24 09:08:52 mailhost sm-mta[3296]: s6O88pSr003296: to=<mailman-list(a)dmz.on.internal-domain.com>, delay=00:00:00, mailer=esmtp, pri=32260, stat=queuedJul 24 09:08:53 mailhost MailScanner[2909]: New Batch: Scanning 1 messages, 2837 bytesJul 24 09:08:53 mailhost MailScanner[2909]: Virus and Content Scanning: StartingJul 24 09:09:07 mailhost MailScanner[2909]: MCP Checks: StartingJul 24 09:09:07 mailhost MailScanner[2909]: Uninfected: Delivered 1 messagesJul 24 09:09:07 mailhost MailScanner[2909]: Deleted 1 messages from processing-databaseJul 24 09:09:08 mailhost sendmail[3307]: s6O88pSr003296: to=<mailman-list(a)dmz.on.internal-domain.com>, delay=00:00:16, xdelay=00:00:01, mailer=esmtp, pri=122260, relay=mailman-server.dmz.on.internal-domain.com. [172.16.0.143], dsn=2.0.0, stat=Sent (s6O893Rm003831 Message accepted for delivery)Jul 24 09:09:16 mailhost sm-mta[3309]: s6O89FAL003309: ruleset=check_rcpt, arg1=<target-address(a)external.domain2.com>, relay=mailhost.server.in-dmz.on.internal-domain.com [mailhost ip address] (may be forged), reject=550 5.7.1 <target-address(a)external.domain2.com>... Relaying denied. IP name possibly forged [mailhost ip address]Jul 24 09:09:16 mailhost sm-mta[3309]: s6O89FAL003309: from=<mailman-list-bounces(a)dmz.on.internal-domain.com>, size=4645, class=0, nrcpts=0, proto=ESMTP, daemon=MTA-v4, relay=mailhost.server.in-dmz.on.internal-domain.com [mailhost ip address] (may be forged)Jul 24 09:09:16 mailhost sm-mta[3309]: s6O89FAN003309: <mailman-list-bounces(a)dmz.on.internal-domain.com>... User unknownJul 24 09:09:16 mailhost sm-mta[3309]: s6O89FAN003309: from=<>, size=0, class=0, nrcpts=0, proto=ESMTP, daemon=MTA-v4, relay=mailhost.server.in-dmz.on.internal-domain.com [mailhost ip address] (may be forged)Jul 24 09:09:16 mailhost sm-mta[3309]: s6O89FAP003309: from=<>, size=2657, class=0, nrcpts=1, msgid=<201407240809.s6O89CZP003837(a)mailman-server.dmz.on.internal-domain.com>, proto=ESMTP, daemon=MTA-v4, relay=mailhost.server.in-dmz.on.internal-domain.com [mailhost ip address] (may be forged)Jul 24 09:09:16 mailhost sm-mta[3309]: s6O89FAP003309: to=<support-email(a)internal-domain.com>, delay=00:00:00, mailer=esmtp, pri=32657, stat=queuedJul 24 09:09:16 mailhost sm-mta[3310]: s6O89FRV003310: from=<mailman-list-bounces(a)dmz.on.internal-domain.com>, size=4640, class=-30, nrcpts=2, msgid=<cq0nx1du5icvm2eubfc8lvdy.1406189339980(a)email.android.com>, proto=ESMTP, daemon=MTA-v4, relay=mailhost.serscis.eu [mailhost ip address]Jul 24 09:09:16 mailhost sm-mta[3310]: s6O89FRV003310: to=<Source-email(a)external-domain.com>, delay=00:00:00, mailer=esmtp, pri=118640, stat=queuedJul 24 09:09:16 mailhost sm-mta[3310]: s6O89FRV003310: to=<target-address(a)external.domain.com>, delay=00:00:00, mailer=esmtp, pri=118640, stat=queuedJul 24 09:09:16 mailhost sm-mta[3311]: s6O89Fll003311: ruleset=check_rcpt, arg1=<target-address(a)external.domain3.com>, relay=mailhost.server.in-dmz.on.internal-domain.com [mailhost ip address] (may be forged), reject=550 5.7.1 <target-address(a)external.domain3.com>... Relaying denied. IP name possibly forged [mailhost ip address]Jul 24 09:09:16 mailhost sm-mta[3311]: s6O89Fll003311: from=<mailman-list-bounces(a)dmz.on.internal-domain.com>, size=4640, class=-30, nrcpts=1, msgid=<cq0nx1du5icvm2eubfc8lvdy.1406189339980(a)email.android.com>, proto=ESMTP, daemon=MTA-v4, relay=mailhost.server.in-dmz.on.internal-domain.com [mailhost ip address] (may be forged)Jul 24 09:09:16 mailhost sm-mta[3311]: s6O89Fll003311: to=<target-address(a)internal-domain.com>, delay=00:00:00, mailer=esmtp, pri=88640, stat=queuedJul 24 09:09:17 mailhost sm-mta[3311]: s6O89Fln003311: <mailman-list-bounces(a)dmz.on.internal-domain.com>... User unknownJul 24 09:09:17 mailhost sm-mta[3311]: s6O89Fln003311: from=<>, size=0, class=0, nrcpts=0, proto=ESMTP, daemon=MTA-v4, relay=mailhost.server.in-dmz.on.internal-domain.com [mailhost ip address] (may be forged)Jul 24 09:09:17 mailhost sm-mta[3311]: s6O89Flp003311: from=<>, size=2657, class=0, nrcpts=1, msgid=<201407240809.s6O89CZP003841(a)mailman-server.dmz.on.internal-domain.com>, proto=ESMTP, daemon=MTA-v4, relay=mailhost.server.in-dmz.on.internal-domain.com [mailhost ip address] (may be forged)Jul 24 09:09:17 mailhost sm-mta[3311]: s6O89Flp003311: to=<support-email(a)internal-domain.com>, delay=00:00:00, mailer=esmtp, pri=32657, stat=queued Any help would be appreciated. ThanksAbZ

4 7