Mailman 3 April 1999 - Mailman-Users

Re: [Mailman-Users] Exim errors
by kevin＠vulcanind.com April 30, 1999

April 30, 1999

Don, I am using Debian's GNU/Linux ver 2.1 with exim as my MTA. I am also going to post this reply to eht Mailman-Users list also. First of all I would like to thank Michael Yount for his help. He was the person who solved the problem. *************** This is what Michael wrote: Okay, here's what's happening. The directors are run in order, and the system_aliases director appears first. The mailman list address is found in /etc/aliases, so exim says "aha, here it is," attempts to pipe the mail to the wrapper with no specified privileges, and bombs with the error you see. If you placed the mailman director first, you'd have a similar problem...every alias on your system would be considered to have user mailman and group list. That might cause problems with the other aliases. I'd suggest the following... * Take the mailman aliases that use pipes out of /etc/aliases and put them in their own file. * Change the mailman director to use that file instead of /etc/aliases. * If you're running exim as a standalone daemon, be sure to kill -HUP the daemon process after you modify the config file. I'll be offline until this evening. If something goes wrong, please send me the exim errors and I'll make further suggestions, probably tomorrow morning. Michael ***************** I followed Michael's instructions and moved my mailman aliases out of /etc/aliases and into /etc/mailman-aliases. My /etc/mailman-aliases file looks like the following: sales: "|/usr/lib/mailman/mail/wrapper post sales" sales-admin: "|/usr/lib/mailman/mail/wrapper mailowner sales" sales-request: "|/usr/lib/mailman/mail/wrapper mailcmd sales" owner-sales: sales-admin sales-owner: sales-admin estimating: "|/usr/lib/mailman/mail/wrapper post estimating" estimating-admin: "|/usr/lib/mailman/mail/wrapper mailowner estimating" estimating-requests: "|/usr/lib/mailman/mail/wrapper mailcmd sales" owner-estimating: estimating-admin estimating-owner: estimating-admin engineering: "|/var/lib/mailman/wrapper post engineering" engineering-admin: "|/var/lib/mailman/wrapper mailowner engineering" engineering-request: "|/var/lib/mailman/wrapper mailcmd engineering" owner-engineering: engineering-admin engineering-owner: engineering-admin I then deleted all of the code that I had added to my /etc/exim.conf as per FAQs, and archives. I added the following code as Micheal suggested at the very end of the directors configuration (just before the end statement) in the /etc/exim.conf file: mailman: driver = aliasfile search_type = lsearch file = /etc/mailman-aliases modemask = 002 user = mailman group = list I am still getting some cron errors when running run_queue, but the system is distributing e-mails correctly now. I just haven't had a chance to look at the cron errors yet. ****************** At 02:01 AM 4/30/99 -0700, Don wrote: > >I saw your post a few days ago regarding your errors with Mailman and >Exim, and was hoping to see some replies because I've been having the >very same problem, but have seen no replies. Have you gotten some >replies directly? If you have could you possibly forward them to me, >and if you haven't, have you gotten anywhere on solving your problem? > >Would appreciate any help I can get. I have tried some to get Mailman >running (actually it is running, I guess, but rather useless unless it >will actually forward mail) but, after getting stuck, have had to attend >to other matters for the last week or so, but now would like to get it >working. I am also using Debian linux and Exim. Exim seems to be >working fine in other respects. > >Don MacDougall >dmacdoug(a)hsc.usc.edu > > Kevin Lee Vulcan Industries (205) 640-2433 mailto:kevin@vulcanind.com http://www.vulcanind.com

1 0

list addressing
by Simon Berg April 29, 1999

April 29, 1999

hi there, i am *not* a unix guru. that's why i got some problems with list addressing. i am running mailman 1.0b11 under irix 6.2 on an sgi indy. when i'm posting to a list, let's say mailto:test@lists.kommwiss.fu-berlin.de , the message that's sent by mailman only contains the to-header test@lists . is this a bug or a feature? how do i modify this? btw: lists.kommwiss.fu-berlin.de is an alias (CNAME). so maybe my problem concerns sendmail configuration. in this case: where can i get information on that topic? thanks in advance -- best regards & peace Simon Berg (simonb(a)gmx.net)

1 0

installing on SCO
by Merrill Cook April 27, 1999

April 27, 1999

Trying to install mailman on SCO 5.04 with the developer package and a gcc. Can someone tell me what this means and what the next steps are to fix it? It looks like some symbol is undefined, but it doesn't say whose symbol it should be or where to go to add it. gcc -DSCRIPT="\"admin\"" -I. -DCGI_GID=28 -g -O2 -DHAVE_STRERROR=1 -DHAVE_SETREGID=1 -DSTDC_HEADERS=1 -DHAVE_SYSLOG_H=1 -DGETGROUPS_T=gid_t -DHAVE_VPRINTF=1 common.o -o admin ./cgi-wrapper.c Undefined first referenced symbol in file std_syslog common.o openlog common.o closelog common.o admin: fatal error: Symbol referencing errors. No output written to admin *** Error code 1 (bu21) *** Error code 1 (bu21)

2 1

Re: [Mailman-Users] NoMail option on membership
by Ken Manheimer April 27, 1999

April 27, 1999

Paul Barnett wrote: > One of the subscribers to my mailing list is out of the country for an > extended period, and I used "membership management" to check the "nomail" > option until he returns. > > However, it has no effect -- the mail is still being sent to him. I don't have a fix, but i do have a something to try - go to the user's actual options page, and see if resetting the delivery option (using the site or list manager's password to authorize) does the job. For that matter, check to make sure it is set as you expect. If this doesn't do it, i can only suggest entering a bug report in the jitterbug db - i think the url is http://www.python.org/mailman-bugs . (Bonus points for tracking down the bad code and reporting the fix!!-) Ken Manheimer klm(a)digicool.com

2 1

Exim errors
by kevin＠vulcanind.com April 26, 1999

April 26, 1999

I have been really impressed with the features of mailman and I would really like to get it to work. I am a newbie when it comes to Linux (debian) so I would appreciate any help you might be able to send. I am getting the following error in the /var/log/exim/mainlog: 1999-04-26 13:38:01 10boHL-0000BC-00 Neither the system_alias director nor the address_pipe transport set a uid for local delivery of |/usr/lib/mailman/mail/wrapper post sales Below I have listed my exim.conf file: # This is the main exim configuration file. # It was originally generated by `eximconfig', part of the exim package # distributed with Debian, but it may edited by the mail system administrator. # This file originally generated by eximconfig at Tue May 4 16:51:12 CDT 1999 # See exim info section for details of the things that can be configured here. # Please see the manual for a complete list # of all the runtime configuration options that can be included in a # configuration file. # This file is divided into several parts, all but the last of which are # terminated by a line containing the word "end". The parts must appear # in the correct order, and all must be present (even if some of them are # in fact empty). Blank lines, and lines starting with # are ignored. ###################################################################### # MAIN CONFIGURATION SETTINGS # ###################################################################### # Specify the domain you want to be added to all unqualified addresses # here. Unqualified addresses are accepted only from local callers by # default. See the receiver_unqualified_{hosts,nets} options if you want # to permit unqualified addresses from remote sources. If this option is # not set, the primary_hostname value is used for qualification. qualify_domain = Bahnstormin.vulcanind.com # If you want unqualified recipient addresses to be qualified with a different # domain to unqualified sender addresses, specify the recipient domain here. # If this option is not set, the qualify_domain value is used. # qualify_recipient = # Specify your local domains as a colon-separated list here. If this option # is not set (i.e. not mentioned in the configuration file), the # qualify_recipient value is used as the only local domain. If you do not want # to do any local deliveries, uncomment the following line, but do not supply # any data for it. This sets local_domains to an empty string, which is not # the same as not mentioning it at all. An empty string specifies that there # are no local domains; not setting it at all causes the default value (the # setting of qualify_recipient) to be used. local_domains = vulcanind.com # Allow mail addressed to our hostname, or to our IP address. local_domains_include_host = true local_domains_include_host_literals = true # Domains we relay for; that is domains that aren't considered local but we # accept mail for them. relay_domains = vulcanind.com # If this is uncommented, we accept and relay mail for all domains we are # in the DNS as an MX for. #relay_domains_include_local_mx = true # No local deliveries will ever be run under the uids of these users (a colon- # separated list). An attempt to do so gets changed so that it runs under the # uid of "nobody" instead. This is a paranoic safety catch. Note the default # setting means you cannot deliver mail addressed to root as if it were a # normal user. This isn't usually a problem, as most sites have an alias for # root that redirects such mail to a human administrator. never_users = root # The setting below causes Exim to do a reverse DNS lookup on all incoming # IP calls, in order to get the true host name. If you feel this is too # expensive, you can specify the networks for which a lookup is done, or # remove the setting entirely. #host_lookup_nets = 0.0.0.0/0 # Exim contains support for the Realtime Blocking List (RBL) that is being # maintained as part of the DNS. See http://maps.vix.com/rbl/ for background. # Uncommenting the following line will make Exim reject mail from any # host whose IP address is blacklisted in the RBL at maps.vix.com. #rbl_domains = rbl.maps.vix.com #rbl_reject_recipients = false #rbl_warn_header = true # The setting below locks out the use of your host as a mail relay by any # other host. See the section of the manual entitled "Control of relaying" # for more info. sender_host_reject_relay = * sender_host_reject = +allow_unknown # If you want Exim to support the "percent hack" for all your local domains, # uncomment the following line. This is the feature by which mail addressed # to x%y@z (where z is one of your local domains) is locally rerouted to # x@y and sent on. Otherwise x%y is treated as an ordinary local part. # percent_hack_domains=* # If this option is set, then any process that is running as one of the # listed users may pass a message to Exim and specify the sender's # address using the "-f" command line option, without Exim's adding a # "Sender" header. trusted_users = mailman # If this option is true, the SMTP command VRFY is supported on incoming # SMTP connections; otherwise it is not. smtp_verify = true # Some operating systems use the "gecos" field in the system password file # to hold other information in addition to users' real names. Exim looks up # this field when it is creating "sender" and "from" headers. If these options # are set, exim uses "gecos_pattern" to parse the gecos field, and then # expands "gecos_name" as the user's name. $1 etc refer to sub-fields matched # by the pattern. gecos_pattern = ^([^,:]*) gecos_name = $1 # This string defines the contents of the \`Received' message header that # is added to each message, except for the timestamp, which is automatically # added on at the end, preceded by a semicolon. The string is expanded each # time it is used. received_header_text = "Received: \ ${if def:sender_fullhost {from ${sender_fullhost} \ ${if def:sender_ident {(${sender_ident})}}\n\t}\ {${if def:sender_ident {from ${sender_ident} }}}}\ by ${primary_hostname} \ ${if def:received_protocol {with ${received_protocol}}} \ (Exim ${version_number} #${compile_number} (Debian))\n\t\ id ${message_id}" end ###################################################################### # TRANSPORTS CONFIGURATION # ###################################################################### # ORDER DOES NOT MATTER # # Only one appropriate transport is called for each delivery. # ###################################################################### # This transport is used for local delivery to user mailboxes. On debian # systems group mail is used so we can write to the /var/spool/mail # directory. (The alternative, which most other unixes use, is to deliver # as the user's own group, into a sticky-bitted directory) local_delivery: driver = appendfile group = mail mode = 0660 mode_fail_narrower = false file = /var/spool/mail/${local_part} # This transport is used for handling pipe addresses generated by alias # or .forward files. It has a conventional name, since it is not actually # mentioned elsewhere in this configuration file. (A different name *can* # be specified via the "address_pipe_transport" option if you really want # to.) If the pipe generates any standard output, it is returned to the sender # of the message as a delivery error. Set return_fail_output instead if you # want this to happen only when the pipe fails to complete normally. address_pipe: driver = pipe return_output # This transport is used for handling file addresses generated by alias # or .forward files. It has a conventional name, since it is not actually # mentioned elsewhere in this configuration file. address_file: driver = appendfile # This transport is used for handling file addresses generated by alias # or .forward files if the path ends in "/", which causes it to be treated # as a directory name rather than a file name. Each message is then delivered # to a unique file in the directory. If instead you want all such deliveries to # be in the "maildir" format that is used by some other mail software, # uncomment the final option below. If this is done, the directory specified # in the .forward or alias file is the base maildir directory. # # Should you want to be able to specify either maildir or non-maildir # directory-style deliveries, then you must set up yet another transport, # called address_directory2. This is used if the path ends in "//" so should # be the one used for maildir, as the double slash suggests another level # of directory. In the absence of address_directory2, paths ending in // # are passed to address_directory. address_directory: driver = appendfile no_from_hack prefix = "" suffix = "" # maildir_format # This transport is used for handling autoreplies generated by the filtering # option of the forwardfile director. It has a conventional name, since it # is not actually mentioned elsewhere in this configuration file. address_reply: driver = autoreply # This transport is used for delivering messages over SMTP connections. remote_smtp: driver = smtp # This transport is used for mailman. mailman_lists: driver = pipe allow_commands = /usr/lib/mailman/mail/wrapper user = mailman group = mail return_fail_output end ###################################################################### # DIRECTORS CONFIGURATION # # Specifies how local addresses are handled # ###################################################################### # ORDER DOES MATTER # # A local address is passed to each in turn until it is accepted. # ###################################################################### # This allows local delivery to be forced, avoiding alias files and # forwarding. real_local: prefix = real- driver = localuser transport = local_delivery # This director handles aliasing using a traditional /etc/aliases file. # If any of your aliases expand to pipes or files, you will need to set # up a user and a group for these deliveries to run under. You can do # this by uncommenting the "user" option below (changing the user name # as appropriate) and adding a "group" option if necessary. system_aliases: driver = aliasfile file = /etc/aliases search_type = lsearch mailman_aliases: driver = aliasfile search_type = lsearch file = /etc/aliases # user = list # Uncomment the above line if you are running smartlist # This director handles forwarding using traditional .forward files. # It also allows mail filtering when a forward file starts with the # string "# Exim filter": to disable filtering, uncomment the "filter" # option. The check_ancestor option means that if the forward file # generates an address that is an ancestor of the current one, the # current one gets passed on instead. This covers the case where A is # aliased to B and B has a .forward file pointing to A. # For standard debian setup of one group per user, it is acceptable---normal # even---for .forward to be group writable. If you have everyone in one # group, you should comment out the "modemask" line. Without it, the exim # default of 022 will apply, which is probably what you want. userforward: driver = forwardfile no_verify check_ancestor file = .forward modemask = 002 filter # This director matches local user mailboxes. localuser: driver = localuser transport = local_delivery # This director is for mailman. mailman_lists: driver = aliasfile search_type = lsearch file = /etc/aliases pipe_transport = mailman_lists end ###################################################################### # ROUTERS CONFIGURATION # # Specifies how remote addresses are handled # ###################################################################### # ORDER DOES MATTER # # A remote address is passed to each in turn until it is accepted. # ###################################################################### # Remote addresses are those with a domain that does not match any item # in the "local_domains" setting above. # This router routes to remote hosts over SMTP using a DNS lookup with # default options. lookuphost: driver = lookuphost transport = remote_smtp # This router routes to remote hosts over SMTP by explicit IP address, # given as a "domain literal" in the form [nnn.nnn.nnn.nnn]. The RFCs # require this facility, which is why it is enabled by default in Exim. # If you want to lock it out, set forbid_domain_literals in the main # configuration section above. literal: driver = ipliteral transport = remote_smtp end ###################################################################### # RETRY CONFIGURATION # ###################################################################### # This single retry rule applies to all domains and all errors. It specifies # retries every 15 minutes for 2 hours, then increasing retry intervals, # starting at 2 hours and increasing each time by a factor of 1.5, up to 16 # hours, then retries every 8 hours until 4 days have passed since the first # failed delivery. # Domain Error Retries # ------ ----- ------- * * F,2h,15m; G,16h,2h,1.5; F,4d,8h end ###################################################################### # REWRITE CONFIGURATION # ###################################################################### # There are no rewriting specifications in this default configuration file. # This is an example of a useful rewriting rule---it looks up the real # address of all local users in a file # *(a)Bahnstormin.vulcanind.com ${lookup{$1}lsearch{/etc/email-addresses}\ # {$value}fail} bcfrF # End of Exim configuration file Kevin Lee Vulcan Industries (205) 640-2433 mailto:kevin@vulcanind.com http://www.vulcanind.com

1 0

unknown mailer error
by Christopher Kolar April 26, 1999

April 26, 1999

Hello everyone. I have a feeling that this is a quick fix, but I could not find anything about it in the archives. I just did a new install on DEC OSF 4.0b of mailman b11 with Apache 1.3.4. Everything on the web side seems to work, but I am getting an error when trying to post or send things to the admin address. I am getting this response in the log files. +++++ ----- The following addresses had permanent fatal errors ----- "|/usr/users/mailman/mail/wrapper mailcmd istest" (expanded from: <istest-request(a)students.aurora.edu>) ----- Transcript of session follows -----554 "|/usr/users/mailman/mail/wrapper mailcmd istest"... unknown mailer error 2 +++++ The only configuration option that we set was for the main path. I am not sure if this means that we have to set a different uid/gid for the sendmail or what. Any suggestions would be much appreciated. Thanks in advance. --chris -- /////\\\\\/////\\\\\ Christopher G. Kolar Director of Instructional Technology Aurora University, Aurora, Illinois ckolar(a)aurora.edu -- www.aurora.edu [View full header for public key recovery information.]

1 0

NoMail option on membership management broken?
by Paul Barnett April 24, 1999

April 24, 1999

I'm running 1.0b11. One of the subscribers to my mailing list is out of the country for an extended period, and I used "membership management" to check the "nomail" option until he returns. However, it has no effect -- the mail is still being sent to him. One possible unusual situation: he has MIME-formatting of digests selected, but didn't enable digests. I would hope that makes no difference, but I thought I'd note it.

1 0

Re: [Mailman-Users] Reply-To, To, Sender, and other addresses
by Ben Gertzfield April 23, 1999

April 23, 1999

>>>>> "Darren" == Darren Boyd <dboyd(a)its.to> writes: Darren> Notice that the X-BeenThere header is correct but not the Darren> rest of the headers. Darren> Anyone have any ideas why this does this? Darren> The nonworking system is running RedHat Linux 5.2, Darren> Sendmail 8.8.7, python 1.5.1, apache 1.3.3. I'm not sure if Mailman can possibly fake these headers. To make sendmail fake the rest of the headers, I had to munge with my sendmail config thusly: (in /etc/mail/sendmail.mc) FEATURE(`genericstable', `hash /etc/mail/genericstable')dnl GENERICS_DOMAIN_FILE(`/etc/mail/sendmail.cG')dnl (in /etc/mail/genericstable) $ cat genericstable maillist-request maillist-request(a)domain.i.want.com maillist maillist(a)domain.i.want.com maillist-admin maillist-admin(a)domain.i.want.com maillist-owner maillist-owner(a)domain.i.want.com owner-maillist owner-maillist(a)domain.i.want.com (in /etc/mail/sendmail.cG) domain.i.want.com Ben -- Brought to you by the letters I and N and the number 2. "Hello! We are only joke. It is funny enough." Debian GNU/Linux maintainer of Gimp and GTK+ -- http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet/Open Projects IRC as Che_Fox.

1 0

Reply-To, To, Sender, and other addresses
by Darren Boyd April 23, 1999

April 23, 1999

Hi, I have two mailman servers setup and they seem to funtion differently with respect to the host part of the mail address that is put into the header. I have one mailman server putting the 'hostname this list prefers' hostname in correctly, but the other is not. As far as I can tell the two machines are setup the same. Note: I removed the headers I deamed unimportant. The one that works looks like this: To: security_audit(a)cal.montage.ca Reply-To: security_audit(a)cal.montage.ca Sender: security_audit-admin(a)cal.montage.ca Errors-To: security_audit-admin(a)cal.montage.ca X-Mailman-Version: 1.0b7 List-Id: Montage Security Audit List <security_audit.cal.montage.ca> X-BeenThere: security_audit(a)cal.montage.ca The other (that doesn't work) looks like this: To: test(a)a.calgary.linux.ca Reply-To: test(a)a.calgary.linux.ca Sender: test-admin(a)a.calgary.linux.ca Errors-To: test-admin(a)a.calgary.linux.ca X-Mailman-Version: 1.0b11 List-Id: A Test List <test.calgary.linux.ca> X-BeenThere: test(a)calgary.linux.ca Notice that the X-BeenThere header is correct but not the rest of the headers. Anyone have any ideas why this does this? The nonworking system is running RedHat Linux 5.2, Sendmail 8.8.7, python 1.5.1, apache 1.3.3. Thanks, Darren

1 0

Message Footer Option
by Steve Song April 22, 1999

April 22, 1999

In the help file for message footer options it says: " This text can include %(field)s format strings which are resolved against the list's attribute dictionary (__dict__). Some useful fields are: ....." How can we find out what is in the list's attribute directory? Are there more variables that can be used? The name of the sender for instance would be MOST useful. Thanks... Steve Song ______________________________________________________________ Steve Song <steve(a)unganisha.idrc.ca> Unganisha (Connectivity) Project <http://www.idrc.ca/unganisha>

1 0