Mailman 3 September 2006 - Mailman-Users

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

Need help: Failure_to_exec_script._WANTED_gid_12, _GOT_gid_110
by Heinrich, Maximilian 01 Sep '06

01 Sep '06

Hello again, thanks for your help so far with the strange unable-to-determine-caller's-group-id-thing. In fact I found out that the problem was that the either qmail or mailman expected the GID of user "popuser" to be 110. (it was 30). So I changed that by changing the GID in /etc/group and /etc/passwd to 110 and by performing this find / -gid 30 -print -exec chgrp 110 {} \; >gid30to110.log so far so good. NOW I get at least no "deferral" but "success" delivery message in my qmail log but with this error behind it: delivery 890: success: Failure_to_exec_script._WANTED_gid_12,_GOT_gid_110./Failed_to_start_/usr /lib/mailman/mail/mailman./did_0+0+1/ :'-( (gid 12 == mail) Since using a combination of Suse9.3, PLESK and a (obviously?) special distribution of mailmnan that comes with this combination I'm not able to compile this with those funky parameters like -with-mail-gid=12 or something. What can I do? Thanks in advance - Regards Maxi

2 1

Setting up mailman
by Robert Bannocks 01 Sep '06

01 Sep '06

Hi, A few simple questions. I want to run mail man as part of the main name space, i.e. listnames(a)nhm.ac.uk, however the machine it runs on will be called someother.nhm.ac.uk, and the alias I want for the web front end will be lists.nhm.ac.uk. Am I correct in doing this by setting the following variables in ~mailman/Mailman/mm_cfg.py and that this will acheive the following DEFAULT_EMAIL_HOST = 'nhm.ac.uk' DEFAULT_URL_HOST = 'lists.nhm.ac.uk' DEFAULT_URL_PATTERN = 'http://%s/mailman/' VIRTUAL_HOSTS.clear() 1. When users go to http://lists.nhm.ac.uk, they will be able to view the lists 2. mail from the lists will come from listname(a)nhm.ac.uk Thanks RB

2 1

Re: [Mailman-Users] Mailman working, but very slow delivery of posted mails
by Dragon 01 Sep '06

01 Sep '06

Mal did speak thusly: >Dear Patrick, >Thank you very much for your reply. > > > What MTA are you using? >Postfix latest version. > >Checking the logs that you suggested, I found the cause for this >delay, however, do not know how to get around it... > >When I am sending mails to the list from any other smtp server than my >isp's (from webmail etc), the delivery is instant! >However, when I send a mail from my isp's smtp server (which is the >same smtp that postfix is using to send all mails that are posted to >my list), then delivery takes about 1 hour!! > >Does anyone know why that could be? Is it confusing my isp's smtp server??? > >Thank you for your help. >Mal ---------------- End original message. --------------------- Sounds like they have implemented greylisting as an anti-spam measure and have set the retry period to an hour. Do you see anything in your MTA logs that looks something like this? reject=451 4.7.1 Greylisting in action, please come back in 00:10:00 If so, you need to get with their sysadmin and have them whitelist your mailman server. Dragon ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

Re: [Mailman-Users] Mailman working, but very slow delivery of posted mails
by Mal 01 Sep '06

01 Sep '06

OK! Thank you, Ill ask the isp. Thanks for the suggestions at the start, it really helped me pinpoint the problem, even though it doesnt seem to be mailman!

1 0

peculiar problem
by Francis Jayakanth 01 Sep '06

01 Sep '06

We have been using Mailman software for almost 6 years now without much of a problem. Occasionally, some of our subscribers complain that they do not receive mails from the mailman list. What I have been doing as a list moderator in such situations is, deleting the existing id of such a user and re-create the same id. Many-a-times this solution has worked. However, it doesn't work for particular user. I have re-created the id for this user at least 5 times but still the user in question doesn't get mailman mails. what do u think could be the problem. we are using 2.1.3, which quite out-dated as compared to the latest version, 2.1.8 I will be upgrading the version shortly. Many thanks, - Francis

4 3

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 13:51, Stephen Gran wrote: > On Fri, Sep 01, 2006 at 01:40:49PM +0200, Oliver König said: > > When a subscriber posts to the list /var/log/exim4/mainlog says: > > 2006-09-01 13:37:27 H=mailout09.sul.t-online.com [194.25.134.84] > > F=<k.oliver(a)t-online.de> rejected RCPT <news(a)server.windfinder.com>: > > relay not permitted > > > > Any idea how to allow postings from subscribers? Thanks. > > It sounds to me like you don't have +MAILMAN_DOMAINS in any accept > statements in your rcpt acl. I would just add it to one of the verify = > recipient stanzas towards the end of the rcpt acl (given a stock > configuration). Hello Stephen, thanks for for reply. I added +MAILMAN_DOMAINS whereever I thought it might help. I am still getting the same error: relay not permitted. Here are excerpts from my exim config: [..] .ifndef MAIN_LOCAL_DOMAINS MAIN_LOCAL_DOMAINS = DEBCONFlocal_domainsDEBCONF .endif domainlist local_domains = MAIN_LOCAL_DOMAINS : MAILMAN_DOMAINS : server.windfinder.com .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 [..] # Home dir for your Mailman installation -- aka Mailman's prefix # directory, see: /usr/share/doc/mailman/README.exim. MAILMAN_HOME=/var/lib/mailman MAILMAN_WRAP=MAILMAN_HOME/mail/mailman # User and group for Mailman, should match your --with-mail-gid # switch to Mailman's configure script. 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= 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 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 domains = server.windfinder.com : MAILMAN_DOMAINS transport = mailman_transport [..] # Accept if the address is in a local domain, but only if the recipient can # be verified. Otherwise deny. The "endpass" line is the border between # passing on to the next ACL statement (if tests above it fail) or denying # access (if tests below it fail). # accept domains = +local_domains : +MAILMAN_DOMAINS endpass message = unknown user verify = recipient # Accept if the address is in a domain for which we are relaying, but again, # only if the recipient can be verified. # # If you want to use the more conservative "unknown user" error # message in case of a non-existing local part, you might want to # set CHECK_RCPT_GIVE_UNKNOWN_USER. However, this might reveal # local information, which is the cause for it not being enabled by # default. accept domains = +relay_to_domains : +MAILMAN_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 [..] 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 Regards, Oliver

1 0

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 12:21, Marc Haber wrote: > On Fri, 1 Sep 2006 00:22:35 +0200, Oliver König <k.oliver(a)t-online.de> > > wrote: > >/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 > > if mailout01.sul.t-online.com is your smarthost, then that box doesn't > like to relay for you. Please note that T-Online has a rather severe > daily mail volume limit and thus you won't have much fun with running > a mailing list server via the T-Online mail servers. > > Additional to that, please make sure to read the documentation that > came with your Debian package. May I ask how you managed to miss the > pointers to the Debian specific mailing list and where you found the > pointer to exim-users? > > Greetings > Marc Sorry, I forgot to say that I actually read /usr/share/doc/mailman/README.EXIM and changed my config. Still could not fix the problem: This is my actual configuration: /etc/mailman/mm_cfg.py: [..] # Default domain for email addresses of newly created MLs DEFAULT_EMAIL_HOST = 'server.windfinder.com' [..] ------ /etc/exim4/exim4.conf.template (accepted after exim4 restart): # Home dir for your Mailman installation -- aka Mailman's prefix # directory. MAILMAN_HOME=/var/lib/mailman MAILMAN_WRAP=MAILMAN_HOME/mail/mailman # User and group for Mailman, should match your --with-mail-gid # switch to Mailman's configure script. MAILMAN_USER=list MAILMAN_GROUP=daemon [..] 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 [..] ----- When a subscriber posts to the list /var/log/exim4/mainlog says: 2006-09-01 13:37:27 H=mailout09.sul.t-online.com [194.25.134.84] F=<k.oliver(a)t-online.de> rejected RCPT <news(a)server.windfinder.com>: relay not permitted Any idea how to allow postings from subscribers? Thanks. Oliver

1 0