Mailman 3 August 2001 - Mailman-Users

Cron <mailman@ultranet> /usr/local/bin/python -S /home/mailman/cron/checkdbs
by Jonathan Andrew Sheen Aug. 28, 2001

Aug. 28, 2001

My mailing list seems to be working, okay, but I've gotten a couple of these, and they concern me. "check_perms" seems happy enough. Do I need to do anything with this? >Return-Path: mailman(a)ultranet.kom.cx >Date: Tue, 28 Aug 2001 17:00:02 -0400 (EDT) >From: mailman(a)ultranet.kom.cx (Cron Daemon) >To: mailman(a)ultranet.kom.cx >Subject: Cron <mailman@ultranet> /usr/local/bin/python -S /home/mailman/cron/checkdbs >X-Cron-Env: <SHELL=/bin/sh> >X-Cron-Env: <… [View More]

1 0

Blocking users who do not match rule?
by Nathan V. Patwardhan Aug. 28, 2001

Aug. 28, 2001

All, I've checked out the Mailman docs and can't figure out if Mailman supports the reject recipe that I want to implement. Basically, we want to have "open" and "closed" subscription lists, where "open" lists are available to everyone and "closed" lists are only available to atg.com. To solve part of this problem, we used forbidden_posters[], which seems to do what we want. So, I guess that I have 2 questions: 1. Is there a way to advertise a different set of lists to internal and … [View More]

1 0

Re: [Mailman-Users] Couple of issues
by Marc Bitner Aug. 28, 2001

Aug. 28, 2001

I did a cd /etc/smrsh Then at $/etc/smrsh I typed: ln -s /home/mailman/mail/wrapper wrapper How do you go about clearing the mail queue?? Marc >>> Keith Howanitz <howanitz(a)nindo.com> 08/28/01 09:13AM >>> Have you linked your wrapper into /etc/smrsh/ ? Have you cleared the mail queue and resent the message? -- -Keith howanitz(a)nindo.com On Tue, 28 Aug 2001, Marc Bitner wrote: > Scott, don't know how my message came out in HTML code, probably because of … [View More]

3 2

bug?
by Ivy Wang Aug. 28, 2001

Aug. 28, 2001

When I go to our mailman admin page, and click "Tend to pending administrative requests", I get: Bug in Mailman version 2.0.4 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. I checked error log file, and it has a lot of : Traceback (most recent call last): File "/home/mailman/cron/checkdbs", line 92, … [View More]

1 0

html code in Digest Mode
by Christopher Jain Aug. 28, 2001

Aug. 28, 2001

Does anyone know how to configure mailman to filter out html code in the daily digests? Any advice appreciated! Thanks! Chris Jain --------------------------------- Do You Yahoo!? Make international calls for as low as $0.04/minute with Yahoo! Messenger.

4 4

no delivery of list postings
by Fabian Linzberger Aug. 28, 2001

Aug. 28, 2001

Hi! I am running a debian potato server using apache as webserver and exim as mta. I have installed mailman 2.0.6 according to the instructions found on www.list.org also I added configurations for exim according to the exim/mailman howto, the tests on the bottom of the howto all worked fine. We have several domain names pointing to this server: the main host name is granul.at, whereas the one that is used to access mailman lists is slp.at. All the Webpages and scripts seem to work fine (I … [View More]can create a test list, subscribe people to it, they get a welcome message, listinfo is there...), however if I post a message to the list or list-admin it disappears without further notice. The mailman logs are empty and exim only says: 2001-08-28 06:20:40 15binG-0004M7-00 => test2 <test2-admin(a)granul.at> D=list_admin_dire ctor T=list_admin_transport 2001-08-28 06:20:40 15binG-0004M7-00 Completed (the same without admin for the list posting case) There is no further delivery to any real-adresses... This also happens regardless of posting to test(a)slp.at or test(a)granul.at (test beeing the list name). I assume there is some problem with the director or transport, since this is the last trace that my messages leave before disappearing... I have included the exim.conf and slp.at.aliases file for your reference. If you need other info, please tell me and I will try to provide it. thanks a lot Fabian ----------------------------------------------------------------- slp.at.aliases # generally, forward all to user slp (we need this because we have another host with dialup connection using fetchmail to deliver most messages, who retrieves them from account slp, I don't think it is the problem since nothing changes if I comment it out...) *:slp # users not to be forwarded to slp root:somerealaddress@somewhere.net # system users mailman: root mailman-owner: root mailman-request: root !!other system daemon aliases and user aliases ommitted for brevity... ---------------------------------------------------------------------- exim.conf # 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 Mon Jun 18 10:16:53 PDT 2001 # 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 = granul.at # 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 = slp.at:localhost:granul.at:lists.granul.at # local_domains = /etc/exim.domains # 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 = # 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 = * # The setting below would, if uncommented, cause Exim to check the syntax of # all the headers that are supposed to contain email addresses (To:, From:, # etc). This reduces the level of bounced bounces considerably. # headers_check_syntax # 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 allows your host to be used as a mail relay only by # localhost: it 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. host_accept_relay = localhost # 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 = mail # If this option is true, the SMTP command VRFY is supported on incoming # SMTP connections; otherwise it is not. smtp_verify = true # added for mailman, fs receiver_verify_hosts = !127.0.0.1/8:0.0.0.0/0 sender_verify # 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 sets the maximum number of messages that will be accepted in one # connection. The default is 10, which is probably enough for most purposes, # but is too low on dialup SMTP systems, which often have many more mails # queued for them when they connect. smtp_accept_queue_per_connection = 100 # Send a mail to the postmaster when a message is frozen. There are many # reasons this could happen; one is if exim cannot deliver a mail with no # return address (normally a bounce) another that may be common on dialup # systems is if a DNS lookup of a smarthost fails. Read the documentation # for more details: you might like to look at the auto_thaw option freeze_tell_mailmaster = true # 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_rcvhost {from ${sender_rcvhost}\n\t}\ {${if def:sender_ident {from ${sender_ident} }}\ ${if def:sender_helo_name {(helo=${sender_helo_name})\n\t}}}}\ by ${primary_hostname} \ ${if def:received_protocol {with ${received_protocol}}} \ (Exim ${version_number} #${compile_number} (Debian))\n\t\ id ${message_id}\ ${if def:received_for {\n\tfor <$received_for>}}" # -- added for mailman, fs # home dir for mailman MAILMAN_HOME=/var/lib/mailman # wrapper script for mailman MAILMAN_WRAP=MAILMAN_HOME/mail/wrapper # user and group for mailman MAILMAN_UID=mail MAILMAN_GID=mail 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 envelope_to_add = true file = /var/spool/mail/${local_part} # This transport is used for handling pipe addresses generated by # alias or .forward files. 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. 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. address_reply: driver = autoreply # This transport is used for procmail procmail_pipe: driver = pipe command = "/usr/bin/procmail -d ${local_part}" return_path_add delivery_date_add envelope_to_add check_string = "From " escape_string = ">From " user = $local_part group = mail # This transport is used for delivering messages over SMTP connections. remote_smtp: driver = smtp # added for mailmain, fs ## Three transports for list mail, request mail and admin mail ## respectively ## Mailman is installed in MAILMAN_HOME ## Mailman is configured to be invoked as user mail list_transport: driver = pipe command = MAILMAN_WRAP post ${lc:$local_part} current_directory = MAILMAN_HOME home_directory = MAILMAN_HOME user = MAILMAN_UID group = MAILMAN_GID list_request_transport: driver = pipe command = MAILMAN_WRAP mailcmd ${lc:$local_part} current_directory = MAILMAN_HOME home_directory = MAILMAN_HOME user = MAILMAN_UID group = MAILMAN_GID list_admin_transport: driver = pipe command = MAILMAN_WRAP mailowner ${lc:$local_part} current_directory = MAILMAN_HOME home_directory = MAILMAN_HOME user = MAILMAN_UID group = MAILMAN_GID 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 # added for mailman, fs ## First 2 directors rewrite list-owner or owner-list to list-admin ## This is only done if the list exists. ## List existence checks are done by seeing if the file ## MAILMAN_HOME/lists//config.db ## exists. list_owner_director: driver = smartuser require_files = MAILMAN_HOME/lists/${lc:$local_part}/config.db suffix = "-owner" new_address = "${lc:$local_part}-admin@${domain}" owner_list_director: driver = smartuser require_files = MAILMAN_HOME/lists/${lc:$local_part}/config.db prefix = "owner-" new_address = "${lc:$local_part}-admin@${domain}" ## Next 3 directors direct admin, request and list mail to the appropriate ## transport.List existence is checked as above. list_admin_director: driver = smartuser suffix = -admin require_files = MAILMAN_HOME/lists/${lc:$local_part}/config.db transport = list_admin_transport list_request_director: driver = smartuser suffix = -request require_files = MAILMAN_HOME/lists/${lc:$local_part}/config.db transport = list_request_transport list_director: driver = smartuser require_files = MAILMAN_HOME/lists/${lc:$local_part}/config.db transport = list_transport # 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_transport = address_file pipe_transport = address_pipe file = /etc/exim.domains/$domain.aliases search_type = lsearch* user = list # Uncomment the above line if you are running smartlist # This director runs procmail for users who have a .procmailrc file procmail: driver = localuser transport = procmail_pipe require_files = ${local_part}:+${home}:+${home}/.procmailrc:+/usr/bin/procmail no_verify # 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 file_transport = address_file pipe_transport = address_pipe reply_transport = address_reply no_verify check_ancestor file = .forward modemask = 002 filter # This director matches local user mailboxes. localuser: driver = localuser transport = local_delivery 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 rewriting rule is particularly useful for dialup users who # don't have their own domain, but could be useful for anyone. # It looks up the real address of all local users in a file #*(a)granul.at ${lookup{$1}lsearch{/etc/email-addresses}\ # {$value}fail} bcfrF *(a)*.granul.at $1(a)granul.at Ffrs # End of Exim configuration file -- Fabian Linzberger - fabian(a)slp.at - (0699/1)9568768 Fighting for Socialism: www.worldsocialist-cwi.org - www.slp.at Do yourself a favor - use and support Debian/GNU Linux [View Less]

2 1

* Mailman Docs Moving *
by Christopher Kolar Aug. 28, 2001

Aug. 28, 2001

Hello everyone. I will be changing jobs this week and the mailman documentation will be moving with me. I will be looking through my logs to see if I can find people who have incoming links but things will be busy for me the next couple of days and I may note be able to contact people in a timely fashion; so if you link to the docs at www.aurora.edu/~ckolar/mailman please note that they will now be at: www.imsa.edu/~ckolar/mailman Cheers, --chris

1 0

disabling mailman's injected fields
by Sergio A. Kessler Aug. 28, 2001

Aug. 28, 2001

hi, is there a way to disable the inserting of List-Archive: List-Help: List-Id: etc... fields in messages that mailman take ? TIA, /sergio

1 0

Problem with a new installation
by Iain Shields Aug. 28, 2001

Aug. 28, 2001

I have recently installed mailman on my debian potato 2.2r2 system, which worked fine for a few days, but then over the weekend I received around 2000 emails from the machine with the following details. After a reboot it seems to be fine, but obviously I would like to ensure it never happens again. What have I done wrong? Any help much appreciated as I'm quite new to the whole thing. Subject: Cron <mailman@webster> /usr/bin/python -S /homespace/mailman/cron/qrunner /usr/bin/python: … [View More]

1 0

bug?
by Ivy Wang Aug. 28, 2001

Aug. 28, 2001

When I go to our mailman admin page, and click "Tend to pending administrative requests", I get: Bug in Mailman version 2.0.4 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. I checked error log file, and it has a lot of : Traceback (most recent call last): File "/home/mailman/cron/checkdbs", line 92, … [View More]

1 0