Mailman 3 September 2006 - Mailman-Users

Admin Functions Failing
by Gerald Edwards 02 Sep '06

02 Sep '06

I have installed Mailman 2 with Postfix 2.1.5 on Debian Sarge 3.2 running VirtualDomains on Apache2. After some trial and error, several remove and purge (start all over) It's up and delivering mail as it should. Before I went to bed (in the wee hours of Friday morning) I ran a final check and tested the mass add of 3 users (3 of my email accounts at various servers). All appeared to be working very nicely. I even created two other mailing lists without incident. Friday morning (closer to noon) when I went to "show it off" the Administration portion fails to function. It allows me to login but any action bounces back to the login screen and does not perform the requested function. I have four mailing lists with Mailman as the primary list and all four behave the same way. I have checked the cookies and they're setting fine. I did reboot the server before retiring and after performing the tests, so I'm sure that I've made an error or failed to save a change but can't figure out what I did wrong. Any help or clue as to where to look would be most helpful. I've gone through the installation instructions several times and checked the various config files and all appear to be set correctly. I'm stumped and need a shove. Thanks Gerald

3 2

Some basic how-to questions
by Ken Winter 02 Sep '06

02 Sep '06

Using the Mailman web admin interface, can I / how can I: 1. Delete an entire mailing list? 2. Clone the entire setup of a list, creating a new list with a different name but the same configuration? 3. Rename a list? I looked for these how-tos in the available documentation, but I can't find them. ~ Thanks in advance for your help ~ Ken Winter PS: I sent this query two weeks ago, and have heard no response, so I'm sending it again. Am I barking up the wrong tree?

4 6

Re: [Mailman-Users] query re "message has implicit destination"
by Dragon 02 Sep '06

02 Sep '06

Oops... forgot to send my reply to the list too. Sorry about that Bretton, I did not mean for you to receive it twice. Bretton Vine wrote: <snip> >I understand the reason, but I need a non-technical, max 4 line rationale. >Failing that I've been instructed to switch it off for /all/ the lists we >host for corporate clients. Mind you that instruction stands regardless. <snip> >Can anyone shed some light (and yes, I've googled and gone through numerous >FAQ answers which have bought me some time but not a reason why the default >installation behaviour is as it is for BCC to lists etc) ---------------- End original message. --------------------- I think that the answer is quite simply that it was a design decision made based upon what the designers thought would be desirable for most users. This is because quite often spammers use the BCC: mechanism to try to avoid being pegged by certain anti-spam measures that look at the number of destination addresses to help identify bulk-mail attempts. Personally, I believe it to be a reasonable default. Of course, there is absolutely nothing stopping you from turning the setting off. You probably would want some pretty aggressive anti-spam filtering and possibly graylisting enabled on your incoming queue of your MTA if you do that. To override the default setting for NEW lists, you can add the following to your mm_cfg.py file: DEFAULT_REQUIRE_EXPLICIT_DESTINATION = No This will not change anything on the existing lists, you will have to change them individually or en mass with a withlist script. Dragon ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

9 56

quick script to rebuild subscriber list from logs
by William Yardley 01 Sep '06

01 Sep '06

So I had a list configuration get hosed recently, and unfortunately, my only backups were from after the configuration got hosed. Fortunately, I had a Mailman subscription log dating back to before the list was created, so I decided to throw together a little script to rebuild the subscriber list. Anyway, this isn't perfect / well thought-out, and isn't really designed in a super user-friendly way, but thought I'd throw it out there in case it helps out someone in a similar spot in the future. The script reads a file named "subscribe" in the current directory, and writes out a list of regular and digest subscribers based on that log (you'd have to change the paths around if you don't want to write to /tmp/digestfile and /tmp/regularfile). w

1 1

Re: [Mailman-Users] [exim] Mailman with exim4 on Debian Sarge
by Oliver König 01 Sep '06

01 Sep '06

On Saturday 02 September 2006 00:03, Stephen Gran wrote: > On Fri, Sep 01, 2006 at 11:45:19PM +0200, Oliver König said: > > > You seem to have case issues here, i.e., MAILMAN_DOMAINS vs. > > > MAILMAN_domains. The documentation shows this all lower case. I don't > > > know if that is significant or not, but it may be. > > > > > > Also, you don't indicate whether or not you have server.windfinder.com > > > and news.server.windfinder.com in local_domains. If not, I think this > > > is the cause of your relaying problem. > > > > The lists are in the local domain (windfinder.com). So I just deleted the > > following: > > domainlist mailman_domains= server.windfinder.com > > MAILMAN_LISTCHK=MAILMAN_HOME/lists/${lc::$local_part}/config.pck > > .. and any additional RCPT ACL should be obsolte because the lists ARE in > > the local domain. > > > > When a subscriber posts to the list /var/log/exim4/mainlog still says. > > 2006-09-01 23:40:08 H=mailout03.sul.t-online.com [194.25.134.81] > > F=<k.oliver(a)t-online.de> rejected RCPT > > <News-request(a)server.windfinder.com>: relay not permitted > > > > .ifndef MAIN_LOCAL_DOMAINS > > MAIN_LOCAL_DOMAINS = @:localhost:windfinder.com:server.windfinder.com > > .endif > > domainlist local_domains = MAIN_LOCAL_DOMAINS > > That should set the domainlist local_domains to be the list > MAIN_LOCAL_DOMAINS, which is what you wnat, unless of course it is > elsewhere defined (command line or something). Should be OK, though. > > [snip] > > > accept > > domains = +local_domains > > endpass > > message = unknown user > > verify = recipient > > > > accept > > domains = +relay_to_domains > > endpass > > .ifdef CHECK_RCPT_GIVE_UNKNOWN_USER > > message = ${if eq{$acl_verify_message}{Unrouteable address}{unknown > > user} {$acl_verify_message}} > > .else > > message = unrouteable address > > .endif > > verify = recipient > > > > accept > > hosts = +relay_from_hosts > > > > accept > > authenticated = * > > > > deny > > message = relay not permitted > > This should accept the message, unless the local part isn't routeable. > > So, run: > > /usr/sbin/exim4 -bhc 194.25.134.81 > > (output from exim) > EHLO mailout03.sul.t-online.com > (output from exim) > MAIL FROM:<k.oliver(a)t-online.de> > (output from exim) > RCPT TO:<News-request(a)server.windfinder.com> > > (the part you type begins in caps) > And post the bit after RCPT TO. someone will spot the flaw. My dynamic IP address has changed so I used H=mailout02.sul.t-online.com [194.25.134.17] F=<k.oliver(a)t-online.de>. Here is the output after RCPT TO RCPT TO:<News-request(a)server.windfinder.com> >>> using ACL "acl_check_rcpt" >>> processing "accept" >>> check hosts = : >>> host in ":"? no (end of list) >>> accept: condition test failed >>> processing "warn" >>> check hosts = +relay_from_hosts >>> no IP address found for host MAIN_RELAY_NETS (during SMTP connection from mailout02.sul.t-online.com [194.25.134.17]) LOG: no IP address found for host MAIN_RELAY_NETS (during SMTP connection from mailout02.sul.t-online.com [194.25.134.17]) >>> host in "127.0.0.1 : ::::1 : 127.0.0.1 : ::::1 : MAIN_RELAY_NETS"? no (failed to find IP address for MAIN_RELAY_NETS) >>> host in "+relay_from_hosts"? no (end of list) >>> warn: condition test failed >>> processing "deny" >>> check domains = +local_domains >>> server.windfinder.com in "@:localhost:windfinder.com:server.windfinder.com"? yes (matched "server.windfinder.com") >>> server.windfinder.com in "+local_domains"? yes (matched "+local_domains") >>> check local_parts = ^[.] : ^.*[@%!/|\'`#&?] >>> News-request in "^[.] : ^.*[@%!/|'`#&?]"? no (end of list) >>> deny: condition test failed >>> processing "deny" >>> check domains = !+local_domains >>> server.windfinder.com in "!+local_domains"? no (matched "! +local_domains" - cached) >>> deny: condition test failed >>> processing "accept" >>> check local_parts = postmaster >>> News-request in "postmaster"? no (end of list) >>> accept: condition test failed >>> processing "deny" >>> check !acl = acl_whitelist_local_deny >>> using ACL "acl_whitelist_local_deny" >>> processing "accept" >>> check hosts = ${if exists{/etc/exim4/local_host_whitelist} {/etc/exim4/local_host_whitelist}{}} >>> host in ""? no (end of list) >>> accept: condition test failed >>> processing "accept" >>> check senders = ${if exists{/etc/exim4/local_sender_whitelist} {/etc/exim4/local_sender_whitelist}{}} >>> k.oliver(a)t-online.de in ""? no (end of list) >>> accept: condition test failed >>> end of ACL "acl_whitelist_local_deny": implicit DENY >>> check senders = ${if exists{/etc/exim4/local_sender_blacklist} {/etc/exim4/local_sender_blacklist}{}} >>> k.oliver(a)t-online.de in ""? no (end of list) >>> deny: condition test failed >>> processing "deny" >>> check !acl = acl_whitelist_local_deny >>> using ACL "acl_whitelist_local_deny" >>> processing "accept" >>> check hosts = ${if exists{/etc/exim4/local_host_whitelist} {/etc/exim4/local_host_whitelist}{}} >>> host in ""? no (end of list) >>> accept: condition test failed >>> processing "accept" >>> check senders = ${if exists{/etc/exim4/local_sender_whitelist} {/etc/exim4/local_sender_whitelist}{}} >>> k.oliver(a)t-online.de in ""? no (end of list) >>> accept: condition test failed >>> end of ACL "acl_whitelist_local_deny": implicit DENY >>> check hosts = ${if exists{/etc/exim4/local_host_blacklist} {/etc/exim4/local_host_blacklist}{}} >>> host in ""? no (end of list) >>> deny: condition test failed >>> processing "deny" >>> check !acl = acl_whitelist_local_deny >>> using ACL "acl_whitelist_local_deny" >>> processing "accept" >>> check hosts = ${if exists{/etc/exim4/local_host_whitelist} {/etc/exim4/local_host_whitelist}{}} >>> host in ""? no (end of list) >>> accept: condition test failed >>> processing "accept" >>> check senders = ${if exists{/etc/exim4/local_sender_whitelist} {/etc/exim4/local_sender_whitelist}{}} >>> k.oliver(a)t-online.de in ""? no (end of list) >>> accept: condition test failed >>> end of ACL "acl_whitelist_local_deny": implicit DENY >>> check senders = ${if exists{/etc/exim4/local_sender_callout} {/etc/exim4/local_sender_callout}{}} >>> k.oliver(a)t-online.de in ""? no (end of list) >>> deny: condition test failed >>> processing "deny" >>> check !acl = acl_whitelist_local_deny >>> using ACL "acl_whitelist_local_deny" >>> processing "accept" >>> check hosts = ${if exists{/etc/exim4/local_host_whitelist} {/etc/exim4/local_host_whitelist}{}} >>> host in ""? no (end of list) >>> accept: condition test failed >>> processing "accept" >>> check senders = ${if exists{/etc/exim4/local_sender_whitelist} {/etc/exim4/local_sender_whitelist}{}} >>> k.oliver(a)t-online.de in ""? no (end of list) >>> accept: condition test failed >>> end of ACL "acl_whitelist_local_deny": implicit DENY >>> check recipients = ${if exists{/etc/exim4/local_rcpt_callout} {/etc/exim4/local_rcpt_callout}{}} >>> News-request(a)server.windfinder.com in ""? no (end of list) >>> deny: condition test failed >>> processing "accept" >>> check domains = +local_domains >>> server.windfinder.com in "+local_domains"? yes (matched "+local_domains" - cached) >>> check verify = recipient >>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>> routing News-request(a)server.windfinder.com >>> calling mailman_router router >>> routed by mailman_router router >>> ----------- end verify ------------ >>> accept: condition test succeeded 250 Accepted

1 0

Mailman with exim4 on Debian Sarge
by Oliver König 01 Sep '06

01 Sep '06

Hello, I installed and configured mailman on Debian Sarge running apache2 and exim4. I set up a list and the list adminstrator / owner can post to the list from a remote client. I am pretty sure that the mailman config is right and that there is a problem with the exim4 config. Non local subscribers cannot post to the list. The Exim4 log always says that relay is not permitted. /var/log/exim4/mainlog: 2006-09-01 00:00:52 H=mailout01.sul.t-online.com [194.25.134.80] F=<k.oliver(a)t-online.de> rejected RCPT <news(a)server.windfinder.com>: relay not permitted Here are parts of my exim4 config: [..] # On Debian systems, the main binary is installed as exim4 to avoid # conflicts with the exim 3 packages. exim_path = /usr/sbin/exim4 # Macro defining the main configuration directory. # We do not use absolute paths. .ifndef CONFDIR CONFDIR = /etc/exim4 .endif # This sets a macro DC_minimaldns if dc_minimaldns=true. If # dc_minimaldns=false, this expands to an empty line. .ifndef DC_minimaldns DEBCONFminimaldnsDEBCONF .endif # Create other macros from Debconf. Macros created here are used in # other places in exim config. .ifndef DC_visiblename DC_visiblename=DEBCONFvisiblenameDEBCONF .endif # Create domain and host lists for relay control # '@' refers to 'the name of the local host' .ifndef MAIN_LOCAL_DOMAINS MAIN_LOCAL_DOMAINS = DEBCONFlocal_domainsDEBCONF .endif domainlist local_domains = MAIN_LOCAL_DOMAINS .ifndef MAIN_RELAY_TO_DOMAINS MAIN_RELAY_TO_DOMAINS = DEBCONFrelay_domainsDEBCONF .endif domainlist relay_to_domains = MAIN_RELAY_TO_DOMAINS .ifndef MAIN_RELAY_NETS MAIN_RELAY_NETS = DEBCONFrelay_netsDEBCONF .endif hostlist relay_from_hosts = 127.0.0.1 : ::::1 : MAIN_RELAY_NETS # Specify the domain you want to be added to all unqualified addresses # here. Unqualified addresses are accepted only from local callers by # default. The recipient_unqualified_hosts option can be used to permit # unqualified addresses from remote sources. # If qualify_domain is not set, the primary_hostname value is used for # qualification. # The ifdef bracket makes sure that an empty debconf value is correctly # translated to "unset". .ifdef DC_visiblename qualify_domain = DC_visiblename .endif [..] # Home dir for your Mailman installation -- aka Mailman's prefix # directory. # By default this is set to "/usr/local/mailman" # On a Red Hat/Fedora system using the RPM use "/var/mailman" # On Debian using the deb package use "/var/lib/mailman" # This is normally the same as ~mailman MAILMAN_HOME=/var/lib/mailman # # User and group for Mailman, should match your --with-mail-gid # switch to Mailman's configure script. # Value is normally "mailman" MAILMAN_USER=list MAILMAN_GROUP=daemon # # Domains that your lists are in - colon separated list # you may wish to add these into local_domains as well domainlist MAILMAN_DOMAINS=news.server.windfinder.com # # -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= # # These values are derived from the ones above and should not need # editing unless you have munged your mailman installation # # The path of the Mailman mail wrapper script MAILMAN_WRAP=MAILMAN_HOME/mail/mailman # # The path of the list config file (used as a required file when # verifying list addresses) MAILMAN_LISTCHK=MAILMAN_HOME/lists/${lc::$local_part}/config.pck [..] begin routers mailman_router: driver = accept require_files = MAILMAN_HOME/lists/$local_part/config.pck local_part_suffix_optional local_part_suffix = -bounces : -bounces+* : \ -confirm+* : -join : -leave : \ -owner : -request : -admin transport = mailman_transport [..] begin transports mailman_transport: driver = pipe command = MAILMAN_WRAP \ '${if def:local_part_suffix \ {${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}} \ {post}}' \ $local_part current_directory = MAILMAN_HOME home_directory = MAILMAN_HOME user = MAILMAN_USER group = MAILMAN_GROUP Any idea how to configure Exim4 to allow posting to mailing list for subscribers like someone(a)somedomain.tld?

2 4

Re: [Mailman-Users] [exim] Mailman with exim4 on Debian Sarge
by Oliver König 01 Sep '06

01 Sep '06

On Friday 01 September 2006 17:47, Marc Haber wrote: > On Fri, 1 Sep 2006 14:22:33 +0200, Oliver König <k.oliver(a)t-online.de> > > wrote: > >domainlist MAILMAN_DOMAINS= server.windfinder.com : > > news.server.windfinder.com > > > >After exim4 restart the mail delivery failed completely (even for non > > mailman mail): > > > >/var/log/exim4/mainlog > >2006-09-01 10:39:13 1GJ4YH-0004nB-ND <= user(a)server.windfinder.com U=user > >P=local S=11314 > >2006-09-01 10:39:13 1GJ4YH-0004nB-ND unknown named domain > >list "+MAILMAN_domains" > > I suspect that names of named lists are case sensitive, and > MAILMAN_DOMAINS does not equal MAILMAN_domains. > > Greetings > Marc I made the changes to match case sensitivity butdelivery still does not work: server:~# exim4 -bt news(a)server.windfinder.com news(a)server.windfinder.com router = mailman_router, transport = mailman_transport server:~# exim4 -d -bt news(a)server.windfinder.com Exim version 4.50 uid=0 gid=0 pid=2790 D=fbb95cfd Berkeley DB: Sleepycat Software: Berkeley DB 4.2.52: (December 3, 2003) Support for: iconv() IPv6 PAM Perl GnuTLS Content_Scanning Old_Demime Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql Authenticators: cram_md5 cyrus_sasl plaintext spa Routers: accept dnslookup ipliteral iplookup manualroute queryprogram redirect Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp Fixed never_users: 0 changed uid/gid: forcing real = effective uid=0 gid=0 pid=2790 auxiliary group list: <none> configuration file is /var/lib/exim4/config.autogenerated log selectors = 00000ffc 00020800 trusted user admin user user name "root" extracted from gecos field "root" originator: uid=0 gid=0 login=root name=root sender address = root(a)server.windfinder.com Address testing: uid=0 gid=102 euid=0 egid=102 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Testing news(a)server.windfinder.com >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Considering news(a)server.windfinder.com >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> routing news(a)server.windfinder.com --------> mailman_router router <-------- local_part=news domain=server.windfinder.com checking require_files file check: /var/lib/mailman/lists/$local_part/config.pck expanded file: /var/lib/mailman/lists/news/config.pck stat() yielded 0 calling mailman_router router mailman_router router called for news(a)server.windfinder.com domain = server.windfinder.com set transport mailman_transport queued for mailman_transport transport: local_part = news domain = server.windfinder.com errors_to=NULL domain_data=NULL localpart_data=NULL routed by mailman_router router envelope to: news(a)server.windfinder.com transport: mailman_transport news(a)server.windfinder.com router = mailman_router, transport = mailman_transport search_tidyup called >>>>>>>>>>>>>>>> Exim pid=2790 terminating with rc=0 >>>>>>>>>>>>>>>> Gruss,

2 1

Re: [Mailman-Users] How to create a list with an approved list of posters? (not answered by FAQ?)
by Elizabeth Schwartz 01 Sep '06

01 Sep '06

Thanks but I am still not getting this. On 8/30/06, Brad Knowles <brad(a)stop.mail-abuse.org> wrote: > > At 2:12 PM -0400 2006-08-30, Elizabeth Schwartz wrote: > > > I have been charged with creating two lists, each with a limited set of > > people who are allowed to **post** to the list. > > One list is an umbrella list ; the other is not. The people who are > allowed > > to post are a subset of members of the list. > > That would be required for the umbrella list situation, unless you > want to apply the patch where you can use the @list notation to call > in the list of subscribers from another list and then put that in the > set of approved senders. I never want the whole list to be approved, I just want a few people to be approved. > I see how to allow them to post if they are *not* members of the list , > but > > not if they *are*. > > Just turn off their moderation bits, but leave everyone else moderated. The people who are in the sub-lists don't have moderation bits, though. If I make them unmodearted members of the umbrella list, and they are also members of the sub-lists, will they get everything twice? (I will make some dummy lists to play with. This is all fraught with peril because much FUD exists about email at high levels. Many phone calls accompany use of these umbrella lists. To my knowledge, our mailman installations have NEVER lost or mis-delivered a message. But it's hard to prove that they never will)

2 1

Feature request
by David Dyer-Bennet 01 Sep '06

01 Sep '06

It'd sure be nice if there were a CSS file associated with the web archives that mailman generates. Perhaps, ideally, a different one for the individual message files and for the various index files. Perhaps there could be a default one that was put in by default (it could be pretty much null), and then each list could be configured to use a specific other one if the list owner wanted. This gives a LOT of flexibility to spruce up (and make conform to site style) the appearance of the archives, for very little (it seems to me) work by the Mailman developers. The other thing is that the various sections of the messages would need to be tagged in appropriate ways to make the style sheets more able to access individual bits. How do people go about fitting the archives into their site style now? Frames? -- David Dyer-Bennet, <mailto:dd-b@dd-b.net>, <http://www.dd-b.net/dd-b/> RKBA: <http://www.dd-b.net/carry/> Pics: <http://www.dd-b.net/dd-b/SnapshotAlbum/> Dragaera/Steven Brust: <http://dragaera.info/>

3 3

View Subscriber list format
by Tom Kavanaugh 01 Sep '06

01 Sep '06

Hello, Currently "View subscribers list" displays members in the following format: first.last at my.domain.com Is it possible to change the format to: first.last(a)my.domain.com Thanks Tom

2 5

Mailman-Users September 2006