Mailman 3 May 2004 - Mailman-Users

Hide list address?
by Ricardo Kleemann 17 Nov '23

17 Nov '23

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

Membership Management And Other Problems.
by multimedia-fan＠myrealbox.com 22 Mar '06

22 Mar '06

Greetings, I cannot "Set everyone's moderation bit, including those members not currently visible" to on, in the membership management section in any list. I have set OWNERS_CAN_ENABLE_PERSONALIZATION = 1 In /Mailman/mm_cfgy.py But still have the same problem. Also I cannot set or unset digest for all users, any thing I overlooked? This was happening before the changes made in the next issue explained below. In the last couple of days we had to reconfigure reverse mapping in DNS for the server, and now the URLs that Mailman builds in the list admin and info pages are pointing to the old host name, is there a way of correcting this, without re-installing mailman from scratch? Any pointers, clues will be greatly appreciated. Thank you for your assistance.

2 5

[Fwd: Re: [Mailman-Users] .signature to posts]
by Solignani Tiziano 16 Apr '05

16 Apr '05

Charles Sebold said: > On 24 Shevat 5762, Clark Cooper wrote: > >> Is there a way in Mailman to append text to each posts as done with a >> .signature file? > > On the web admin interface, go to page "Regular-member (non-digest) > Options" and change the option labeled "Footer added to mail sent to > regular list members". Is that what you were after? > -- > Charles Sebold 25th of Shevat, BTW how can I add taglines, i.e. random strings picked frpm a text file where they lies every one on a separate line. ALmost every list manager has tag lines administration, but I did not find them in mailman... Cheers, ---- Avv. Tiziano Solignani via Bonesi n. 15 - Vignola (MO) tel. 059 76.19.26 - fax 059 77.04.535 mail: solignani(a)solignani.it web: http://www.solignani.it chat: avv_tiziano_solignani(a)hotmail.com PC Open magazine - www.pcopen.agepe.it "rarest jewel is a true heart" -- ---- Avv. Tiziano Solignani via Bonesi n. 15 - Vignola (MO) tel. 059 76.19.26 - fax 059 77.04.535 mail: solignani(a)solignani.it web: http://www.solignani.it chat: avv_tiziano_solignani(a)hotmail.com PC Open magazine - www.pcopen.agepe.it "rarest jewel is a true heart"

2 1

Where is 'reject' message stored
by Warren Hoffman 25 Jan '05

25 Jan '05

One of my associates set up content filters to reject attachments and other things. He created a custom message to explain this. Now he wants to change the message, but I cannot locate which file in /mailman holds the text (and I did look at all of them). Can somebody tell me how I could find it. I do know text fragments. Thanks!!! --Warren

4 3

Upgrade hell (Debian)
by Deirdre Saoirse Moen 05 Jan '05

05 Jan '05

Upgrade script broke (not the first time). from Mailman import MailList from Mailman.LockFile import TimeOutError from Mailman.i18n import _ I'm getting error: Traceback (most recent call last): File "/usr/lib/mailman/bin/update", line 51, in ? from Mailman.i18n import _ ImportError: No module named i18n It doesn't balk on the line before, so it doesn't seem to be a path issue. When I comment that line out (for grins), it balks on: from Mailman.Queue.Switchboard import Switchboard from Mailman import OldStyleMemberships from Mailman.MemberAdaptor import BYBOUNCE, ENABLED Any clues? -- _Deirdre http://deirdre.net "Cannot run out of time. There is infinite time. You are finite. Zathras is finite. This....is wrong tool." -- Zathras

2 2

Mailman/pipermail/MHonArc integration issue
by Wiley Wimberly 22 Sep '04

22 Sep '04

Hi, I am using the Mailman/pipermail/MHonArc integration patchs found at http://www.openinfo.co.uk/mailman/index.html and have been seeing the following issue. When I run bin/arch --wipe listname it correctly builds the html for each month section unless there is only a single message for the month. The output shows: figuring article archives 2004-May Warning: Could not parse date for message Message-Id: <f7589c774a9bf75f62148a712f1140fd(a)NO-ID-FOUND.mhonarc.org> This only seems to happen if there is just one message for that month. I also see the same error in the error log on all incoming messages that are sent to the archiver. Warning: Could not parse date for message Message-Id: <4173763d54406fe2a588db538ad84586(a)NO-ID-FOUND.mhonarc.org> The message shows up in the html, but the subject and sender are missing from the toc. • [no subject] , Unknown - Sat May 01 14:28:54 2004 Also all of the header lines are missing from the message page. I just get a heading of [no subject]. I am using mailman 2.1.4 with the following patches which all seemed to apply cleanly. modinc-2.1.4-0.1.patch indexing-2.1.4-0.1.patch htdig-2.1.4-0.1.patch mhonarc-2.1.4-0.1.patch Is anyone else seeing this issue? I have been beating on this for a few days and any suggestions will be greatly appreciated. Thanks.

4 5

RE: [Mailman-Users] changing ISP servers
by Jon Carnes 06 Jul '04

06 Jul '04

Even Cpanel should let Mailman dump out the user lists for you. There is a Mailman commandline that specifically does that (list_members). The command to dump out your configuration to text is config_list. Your admin can dump the config out, edit the fields that change (URL and default host names - the list name, if that changes) then simply create a list with the same name and upload the config file using config_list again. It's almost a "no brainer" once you read the help that comes with config_list. Good Luck - Jon Carnes On Mon, 2004-03-08 at 23:16, Pastor Augie wrote: > Jon, > > thanks for your reply. I've passed along your message to my ISP - he's > pretty responsive... we'll see what he says. > > Unfortunately, we *do* use cPanel ... and this is NOT the first problem > we've had... funny you should mention that! Sometimes our messages get > stuck in queue and don't come out for days if at all. > > Anyway, I don't have command line access and am not even sure where the > files for mailman are. They don't appear to be in our user directory. If > you could tell me the name of the file to look for, I could direct the > sysadmin to look for it. > > But just double checking - there is no way to export email addresses and > names? Then it would be a simple matter to re-import them. > > Thanks for all your help! > > Augie. > > > > -----Original Message----- > From: Jon Carnes [mailto:jonc@nc.rr.com] > Sent: Monday, March 08, 2004 7:41 PM > To: pastor(a)SavingGraceLC.org > Cc: mailman-users(a)python.org > Subject: Re: [Mailman-Users] changing ISP servers > > > On Mon, 2004-03-08 at 10:33, Pastor Augie wrote: > > Hello, > > > > I have several mailman lists setup. Because of technical difficulties > > with our ISP's physical server, I am being required to migrate our > > entire website, including lists, to a new server (new IP and new > > name). My ISP contact tells me that when the mailman lists are moved > > to the new server they will need to be RECREATED FROM SCRATCH!! > > > > Is that the case? What is the most desirable way to migrate to a new > > server? Is there a simple export feature or some flat (or db) file I > > can export or something like that so I don't have to recreate the list > > by hand?? > > Thanks in advance for your help. > > > > Augie. > > > > Well, if they are using a straight version of Mailman then the answer is > false. It's very easy to move lists to a new server. > > It may be that they are actually using Cpanel (or will be using Cpanel). > This app does "who-knows-what" to Mailman. Actually we know a few > things it does, thanks to the many, many complaints we receive on a > regular basis from folks stuck using Cpanel. > > Even then, the movements of the lists can be relatively painless - if > they allow you command line access to dump out your list configurations > into text files. > > Good luck - Jon Carnes > > >

2 1

Problem with Sendmail SMTP-AUTH and Mailman
by Christopher Tyler 26 Jun '04

26 Jun '04

I had Mailman working fine with Sendmail up until I enabled SMTP-AUTH in Sendmail. The messages get to Mailman but are not delivered to the list members anymore because Mailman does not authenticate. Disabling SMTP-AUTH is not an option as we are an ISP and have users that require email on the road and such, and we do not wish to be blacklisted as an open relay. There aren't any messages in the archive that deal with this specifically, so my question is what EXACTLY do I have to do to get it to work with SMTP-AUTH. I have included my sendmail.mc file for review. I am running Fedora Core 1 with the latest stable versions of Sendmail and Mailman. Mailman is set to deliver to SMTPdirect if that is any help. SENDMAIL.MC -------------------------------- divert(-1)dnl dnl # dnl # This is the sendmail macro config file for m4. If you make changes to dnl # /etc/mail/sendmail.mc, you will need to regenerate the dnl # /etc/mail/sendmail.cf file by confirming that the sendmail-cf package is dnl # installed and then performing a dnl # dnl # make -C /etc/mail dnl # include(`/usr/share/sendmail-cf/m4/cf.m4')dnl VERSIONID(`setup for Red Hat Linux')dnl OSTYPE(`linux')dnl dnl # dnl # Uncomment and edit the following line if your outgoing mail needs to dnl # be sent out through an external mail server: dnl # dnl define(`SMART_HOST',`smtp.your.provider') dnl # define(`confDEF_USER_ID',``8:12'')dnl dnl define(`confAUTO_REBUILD')dnl define(`confTO_CONNECT', `1m')dnl define(`confTRY_NULL_MX_LIST',true)dnl define(`confDONT_PROBE_INTERFACES',true)dnl define(`PROCMAIL_MAILER_PATH',`/usr/bin/procmail')dnl define(`ALIAS_FILE', `/etc/aliases')dnl dnl define(`STATUS_FILE', `/etc/mail/statistics')dnl define(`UUCP_MAILER_MAX', `2000000')dnl define(`confUSERDB_SPEC', `/etc/mail/userdb.db')dnl define(`confPRIVACY_FLAGS', `authwarnings,novrfy,noexpn,restrictqrun')dnl dnl # dnl # The following allows relaying if the user authenticates, and disallows dnl # plaintext authentication (PLAIN/LOGIN) on non-TLS links dnl # define(`confAUTH_OPTIONS',`A') TRUST_AUTH_MECH(`DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl define(`confAUTH_MECHANISMS',`DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl define(`confCACERT_PATH',`/usr/share/ssl/certs')dnl define(`confCACERT',`/usr/share/ssl/certs/ca-bundle.crt')dnl define('confSERVER_CERT',`/usr/share/ssl/certs/sendmail.pem')dnl define(`confSERVER_KEY',`/usr/share/ssl/certs/sendmail.pem')dnl FEATURE(delay_checks)dnl dnl # dnl # PLAIN is the preferred plaintext authentication method and used by dnl # Mozilla Mail and Evolution, though Outlook Express and other MUAs do dnl # use LOGIN. Other mechanisms should be used if the connection is not dnl # guaranteed secure. dnl # dnl TRUST_AUTH_MECH(`EXTERNAL DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl dnl define(`confAUTH_MECHANISMS', `EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl dnl # dnl # Rudimentary information on creating certificates for sendmail TLS: dnl # make -C /usr/share/ssl/certs usage dnl # dnl define(`confCACERT_PATH',`/usr/share/ssl/certs') dnl define(`confCACERT',`/usr/share/ssl/certs/ca-bundle.crt') dnl define(`confSERVER_CERT',`/usr/share/ssl/certs/sendmail.pem') dnl define(`confSERVER_KEY',`/usr/share/ssl/certs/sendmail.pem') dnl # dnl # This allows sendmail to use a keyfile that is shared with OpenLDAP's dnl # slapd, which requires the file to be readble by group ldap dnl # dnl define(`confDONT_BLAME_SENDMAIL',`groupreadablekeyfile')dnl dnl # dnl define(`confTO_QUEUEWARN', `4h')dnl dnl define(`confTO_QUEUERETURN', `5d')dnl dnl define(`confQUEUE_LA', `12')dnl dnl define(`confREFUSE_LA', `18')dnl define(`confTO_IDENT', `0')dnl dnl FEATURE(delay_checks)dnl FEATURE(`no_default_msa',`dnl')dnl FEATURE(`smrsh',`/usr/sbin/smrsh')dnl FEATURE(`mailertable',`hash -o /etc/mail/mailertable.db')dnl FEATURE(`virtusertable',`hash -o /etc/mail/virtusertable.db')dnl FEATURE(redirect)dnl FEATURE(always_add_domain)dnl FEATURE(use_cw_file)dnl FEATURE(use_ct_file)dnl dnl # dnl # The -t option will retry delivery if e.g. the user runs over his quota. dnl # FEATURE(local_procmail,`',`procmail -t -Y -a $h -d $u')dnl FEATURE(`access_db',`hash -T<TMPF> -o /etc/mail/access.db')dnl FEATURE(`blacklist_recipients')dnl EXPOSED_USER(`root')dnl dnl # dnl # The following causes sendmail to only listen on the IPv4 loopback address dnl # 127.0.0.1 and not on any other network devices. Remove the loopback dnl # address restriction to accept email from the internet or intranet. dnl # dnl DAEMON_OPTIONS(`Port=smtp, Addr=127.0.0.1, Name=MTA')dnl dnl # dnl # The following causes sendmail to additionally listen to port 587 for dnl # mail from MUAs that authenticate. Roaming users who can't reach their dnl # preferred sendmail daemon due to port 25 being blocked or redirected find dnl # this useful. dnl # DAEMON_OPTIONS(`Port=submission, Name=MSA, M=Ea')dnl DAEMON_OPTIONS(`Port=smtp, Name=MSA, M=Ea')dnl dnl # dnl # The following causes sendmail to additionally listen to port 465, but dnl # starting immediately in TLS mode upon connecting. Port 25 or 587 followed dnl # by STARTTLS is preferred, but roaming clients using Outlook Express can't dnl # do STARTTLS on ports other than 25. Mozilla Mail can ONLY use STARTTLS dnl # and doesn't support the deprecated smtps; Evolution <1.1.1 uses smtps dnl # when SSL is enabled-- STARTTLS support is available in version 1.1.1. dnl # dnl # For this to work your OpenSSL certificates must be configured. dnl # dnl DAEMON_OPTIONS(`Port=smtps, Name=TLSMTA, M=s')dnl dnl # dnl # The following causes sendmail to additionally listen on the IPv6 loopback dnl # device. Remove the loopback address restriction listen to the network. dnl # dnl # NOTE: binding both IPv4 and IPv6 daemon to the same port requires dnl # a kernel patch dnl # dnl DAEMON_OPTIONS(`port=smtp,Addr=::1, Name=MTA-v6, Family=inet6')dnl dnl # dnl # We strongly recommend not accepting unresolvable domains if you want to dnl # protect yourself from spam. However, the laptop and users on computers dnl # that do not have 24x7 DNS do need this. dnl # dnl FEATURE(`accept_unresolvable_domains')dnl dnl # dnl FEATURE(`relay_based_on_MX')dnl dnl # dnl # Also accept email sent to "localhost.localdomain" as local email. dnl # LOCAL_DOMAIN(`localhost.localdomain')dnl dnl # dnl # The following example makes mail from this host and any additional dnl # specified domains appear to be sent from mydomain.com dnl # dnl MASQUERADE_AS(`mydomain.com')dnl dnl # dnl # masquerade not just the headers, but the envelope as well dnl # dnl FEATURE(masquerade_envelope)dnl dnl # dnl # masquerade not just @mydomainalias.com, but @*.mydomainalias.com as well dnl # dnl FEATURE(masquerade_entire_domain)dnl dnl # dnl MASQUERADE_DOMAIN(localhost)dnl dnl MASQUERADE_DOMAIN(localhost.localdomain)dnl dnl MASQUERADE_DOMAIN(mydomainalias.com)dnl dnl MASQUERADE_DOMAIN(mydomain.lan)dnl MAILER(smtp)dnl MAILER(procmail)dnl -- Christopher Tyler Operations Manager Nexlink Communications, Inc. http://www.nexlinkinc.net (417) 520-0670

2 1

News -> Mail: no mail! (repost)
by NFN Smith 16 Jun '04

16 Jun '04

I posted this one last week, but no response, yet. Any takers on this one? I thought this was a fairly simple one -- or is it just uninteresting? Thanks. Smith ---- I'm in the process of setting up a server with the following: - Fedora Core 1 - Mailman 2.1.4 - Sendmail 8.12.10 - INN 2.3.5 Mailman, Sendmail and INN all have been installed from the .RPM bundled with Fedora. I'm doing this setup as an internal server, so I'm not exchanging traffic with the Internet at larger. Where I currently am is that I have Mailman working fine as a mailing list server, and no problems at all with INN as a news server. I also am not having any difficutly of getting mail to news. However, where I am having difficulties is in getting messages composed in news back to mail. In my mailman configs, I'm pretty much running with default settings -- in fact, the only things I'm specifying in my mm_cfg.py are the necessary settings for the server name. I do have all the supplied activities running in the mailman user's crontab, and those are running on the specified schedules. The specific place where I'm having problems is when I run gate_news, I'm getting no response, other than a single log entry in /var/log/cron: Apr 27 15:00:01 bronze CROND[12436]: (mailman) CMD (/usr/bin/python -S /var/mailman/cron/gate_news) If I run gate_news from a shell prompt, I get a pause for a few seconds, and then a new prompt, but no other output. I've checked all of my logs, including /var/log/maillog and /var/log/mailman/*, and there are no updates to any of these logs following gate_news runs. I also checked all the steps in the troubleshooting section (3.14) of the Mailman FAQ. The only thing that turned up other than what should be is that that a check_perms check showed that the permissions of the files in /var/mailman/qfiles were incorrect. On the advice of check_perms, I ran 'chmod 02775 *' on the directory. (These files have owner:group set to: mailman:mailman ). I then restarted all the mailman services by rebooting the machine. Following that, I'm still having the same behavior. What I'm missing has to be something small, but I'm not seeing it. Any clues? Thanks in advance. Smith Composed by sacbeemail. Get Your Free E-mail at http://www.sacbeemail.com . Or visit Northern Californias premiere news and information website at http://www.sacbee.com .

3 3

How to configure Mailman to just send news letters
by Andreas Sheriff 09 Jun '04

09 Jun '04

Hi, Does anyone know how to configure Mailman to just send newsletters? The documentation is kinda 0bfusT1c@t3d/non-existent when it comes to that. Andreas

5 5