Mailman 3 August 2008 - Mailman-Users

Rejection notice substitution variables (member_moderation_notice)
by Rodriguez Gomez Pedro 21 Aug '08

21 Aug '08

Hi there!, I'm using Mailman 2.1.11 and in the context of defining the rejection notice for moderated members (member_moderation_notice) am trying to use substitution variables like: %(real_name)s %(web_page_url)s %(cgiext)s %(_internal_name)s or even if possible at all in that context : %(user_optionsurl)s As far as I see this is not an option now. Not being shy of modifying the code, can anybody point me in the right direction? Thanks, Pedro Rodriguez Gomez ________________________________________________________________________ This e-mail has been scanned for all known viruses by EMEA. ________________________________________________________________________

2 1

changing Digest formatting
by Alan.Rubin＠nt.gov.au 20 Aug '08

20 Aug '08

Hello, Is there any way to remove/re-arrange the "header" that is printed with every digest? Send Change_Notification mailing list submissions to list(a)list.example.com To subscribe or unsubscribe via the World Wide Web, visit http://list.example.com/mailman/listinfo/list or, via email, send a message with subject or body 'help' to list-request(a)list.example.com You can reach the person managing the list at list-owner(a)list.example.com When replying, please edit your Subject line so it is more specific than "Re: Contents of List digest..." ... We're using digests for announcements and we'd rather not send all that information to the recipients, at least at the beginning of the message. We wouldn't want them to miss the meat of the message. We'd like to get the message started with "Today's Topics". Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: alan.rubin(a)nt.gov.au

2 1

Re: [Mailman-Users] several questions.
by Mark Sapiro 19 Aug '08

19 Aug '08

Copying the list. James - Dunn Deal PR wrote: >> See the FAQ article at <http://wiki.list.org/x/3YA9> for >> suggestions on setting up a "one-way" list. Post using an Approved: >> header as discussed in that FAQ to avoid having authorized posts >> held. > > > I'm checking the http://wiki.list.org/x/3YA9 link you sent me. First > of all, how do I find out if I'm running MailMan 2.0 or 2.1? At the bottom of pages like <http://lists.dunndealpr.com/mailman/listinfo> you will see "version 2.1.9" > Regarding "3.11. How do I create a newsletter/announcement/one-way > list?": > > - Will people be able to reply to an email I send with this function? > I would like them to be able to, but only to be able to reply to the > sender himself. If you set the list settings first_strip_reply_to to No and reply_goes_to_list to Poster, then an ordinary reply will go to the original sender of the message. There's no way you can control how the user addresses the reply, but if the list members are moderated, you can control what happens when they attempt to post to the list. >is there a way to set this list up where I can just > subscribe them as usual, instead of them having to visit a site and > subscribe themselves and deal with confirmation emails and all that? The list admin can always add members to the list. The problem is when they complain to their ISP that you're spamming them, and their ISP starts blocking your ISP and your ISP comes to you and says "why are you spamming people?", you want evidence that the complainer actually wanted to be on your list. Thus you want to keep the email or other document that they sent you where they asked to be on the list. It's safer to always 'invite' people to join the list. At least that way you can say you only sent an invitation, they accepted it and there is a log entry that says they were added by email confirmation. >> It is not clear to me from the above where the post was received. >> If it was received by the gmail address and not by the local server >> addresses, it's possible there's some issue relating to that, but >> did these addresses receive their list welcome or other mail from >> Mailman? If so, then Mailman can send to them and that isn't the >> problem. > >> The address that sent the post will not receive it if 'not metoo' >> is checked in the admin Membership List. Also, addresses which have >> 'digest' checked will only receive digests, not messages (for an >> announcement type list, you probably want Digest options -> >> digestable set to No). > > > I'm sorry if my language was a little confusing. The gmail account is > the only email that DID receive the test message. The two that are > housed on the same server as my MailMan did not. Just a minute ago, I > deleted all the test email addresses from the databases to see if I > would receive unsubscribe messages. As usual, only the gmail received > one. Then I tried re-adding them, along with two other email > addresses I have (one hotmail, one yahoo) to see who would receive > subscribe emails. Well, out of the five emails total, only the > hotmail, the yahoo and the gmail accounts have received subscribe > emails. And although the gmail account did receive a subscribe email, > it is not even listed in the list of members on the admin page. The > only emails that appear are the new ones - the hotmail and yahoo > accounts - while the ones that were initially entered, deleted and > re-added are nowhere to be seen. Is it the case that once an email is > unsubscribed, it cannot be re-subscribed? See <http://wiki.list.org/x/A4E9>. You will need to look at Mailman's logs (bounce, smtp and smtp-failure) and possibly the MTA logs to see what's happening to this mail. It appears that your MTA is unable to deliver mail from Mailman to local users. The MTA's logs would probably be the best place to start looking to find out why. No. There is nothing that prevents an unsubscribed address from being resubscribed. How are you subscribing these addresses. If via the Mass Subscription page, it reports what it did. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

stopping a message post in progress?
by Wallace Winfrey 19 Aug '08

19 Aug '08

Hello We're running a list with about 1100+ subscribers, and this list is also integrated with some web forum software (FudForum, specifically). Every once in a while, a spammer or someone else will post something inappropriate to the forum. Often times we will catch this post right away, before mailman has been able to send the post out to all our subscribers. How might I prevent the post from going out to the rest of list? Is there any way to do this? Note, I'm not asking about emergency moderation, just how to stop a post in the progress of being sent out. TIA, w

3 3

No outgoing mails with Postfix when sending mail to list
by Matthias Laug 19 Aug '08

19 Aug '08

Hello everybody, I'm stuck with a problem. I've installed mailman and postfix via apt (debian 4.0). If I register a user or a bounce message is sent to the list owner, the emails go through and are received by the recipient. But if any user sends an email to the list, it will be archieved but not send to all llist members. There seems to be something wrong with the aliases, because if I change postfix config (main.cf) from alias_maps = hash:/var/lib/mailman/data/aliases alias_database = hash:/var/lib/mailman/data/aliases.db to alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases email are send to list members, but along with an error message 550, that the adress is not available. I hope anybody can help me with this problem. I post my config down below: *mm_config (mailman)* *# The name of the list Mailman uses to send password reminders # and similar. Don't change if you want mailman-owner to be # a valid local part. MAILMAN_SITE_LIST = 'mailman' #------------------------------------------------------------- # If you change these, you have to configure your http server # accordingly (Alias and ScriptAlias directives in most httpds) DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/' PRIVATE_ARCHIVE_URL = '/cgi-bin/mailman/private' IMAGE_LOGOS = '/images/mailman/' #------------------------------------------------------------- # Default domain for email addresses of newly created MLs DEFAULT_EMAIL_HOST = 'berliner-wingolf.de' #------------------------------------------------------------- # Default host for web interface of newly created MLs DEFAULT_URL_HOST = 'berliner-wingolf.de' #------------------------------------------------------------- # Required when setting any of its arguments. add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) #------------------------------------------------------------- # The default language for this server. DEFAULT_SERVER_LANGUAGE = 'de' #------------------------------------------------------------- # Iirc this was used in pre 2.1, leave it for now USE_ENVELOPE_SENDER = 0 # Still used? #------------------------------------------------------------- # Unset send_reminders on newly created lists DEFAULT_SEND_REMINDERS = 0 #------------------------------------------------------------- # Uncomment this if you configured your MTA such that it # automatically recognizes newly created lists. # (see /usr/share/doc/mailman/README.{EXIM,...}) # MTA=None # Misnomer, suppresses alias output on newlist #------------------------------------------------------------- # Uncomment if you use Postfix virtual domains, but be sure to # read /usr/share/doc/mailman/README.POSTFIX first. MTA='Postfix' POSTFIC_STYLE_VIRTUAL_DOMAINS = ['berliner-wingolf.de']* *main.cf (postfic)* *# Debian specific: Specifying a file name will cause the first # line of that file to be used as the name. The Debian default # is /etc/mailname. #myorigin = /etc/mailname smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) biff = no # appending .domain is the MUA's job. append_dot_mydomain = no # Uncomment the next line to generate "delayed mail" warnings #delay_warning_time = 4h # TLS parameters smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key smtpd_use_tls=yes smtpd_tls_session_cache_database = btree:${queue_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${queue_directory}/smtp_scache # See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for # information on enabling SSL in the smtp client. myhostname = berliner-wingolf.de alias_maps = hash:/var/lib/mailman/data/aliases alias_database = hash:/var/lib/mailman/data/aliases.db #alias_maps = hash:/etc/aliases #alias_database = hash:/etc/aliases myorigin = /etc/mailname mydestination = berliner-wingolf.de, vs157059.vserver.de, localhost.vserver.de relayhost = mynetworks = 127.0.0.0/8 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all unknown_local_recipient_reject_code = 550 owner_request_special = no *

2 1

Manually bouncing messages to a mailman list
by Cristian Rigamonti 19 Aug '08

19 Aug '08

Hi list. Here's an interesting (at least for me :) mailman problem that I could not manage to solve. If I manually bounce messages to a mailman list (I mean: using the "bounce" command in mutt, or the "mail redirect" thunderbird plugin), the messages seems to disappear: - they don't get delivered to the list (as I would expect when the original sender address is subscribed to the list) - they don't go into the moderation queue (as I would expect when the original sender address is not subscribed to the list) - they don't bounce back to the original sender (nor to the address who bounced the message to the list, nor to the list administrator) Please note that I am a subscriber (and administrator) of the list in question, but I don't have shell access to the server running mailman (version 2.1.9), so I can't debug the problem myself. Could it be that the "Resent-*" headers that get added to the bounced message are somehow confusing mailman? Or is this a feature? Or a mis-configuration? I couldn't find anything relevant in the list archives and the documentation, except for this page, which mentions manually bouncing messages to a list: http://wiki.list.org/pages/viewpage.action?pageId=4030683 I tried following the procedure described in that page (i.e. including an "Approved: " header with the admin password) but the result is still the same. Any ideas? Cri -- GPG/PGP Key-Id 0x943A5F0E - http://www.linux.it/~cri/cri.asc

2 6

(no subject)
by Jon Hind 19 Aug '08

19 Aug '08

-- Jon -- Jon

1 0

Re: [Mailman-Users] Redirecting Mailman URL
by Mark Sapiro 19 Aug '08

19 Aug '08

Alan.Rubin(a)nt.gov.au wrote: >Thanks, Mark. That seems to be working. We don't currently support virtual >hosts and their lists. If we did, is there another simple way to make www.lists >appear the same as just lists? No. And you'll probably have problems anyway with what you have. Each list has a hidden 'web_page_url' attribute. See the FAQ at <http://wiki.list.org/x/mIA9> for more detail on this. If VIRTUAL_HOSTS_OVERVIEW is On, the only lists that appear on the listinfo and admin overview pages are those for which the host name in web_page_url matches the host name in the URL that invoked the page. If VIRTUAL_HOSTS_OVERVIEW is Off, all public list appear on the overview pages regardless of invoking URL. So setting VIRTUAL_HOSTS_OVERVIEW = Off has solved your overview issue, but web_page_url is used as the initial part of lots of links on various pages, so if the host in web_page_url is lists..., those links won't work from the outside where the host needs to be www.lists... You really need to have one host name which is set as DEFAULT_URL_HOST and is probably the www.lists... host and which is used for both internal and external access. Also see <http://wiki.list.org/x/gIA9>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Redirecting Mailman URL
by Alan.Rubin＠nt.gov.au 19 Aug '08

19 Aug '08

Hello, We have an internal Mailman server. The service is up and running for our internal clients, but now we need to have it accessible to the world. We have a reverse-proxy that will allow us to redirect to port 80 for our internal Mailman server, but our Security group seems to have a fondness for external hosts with hostnames that only begin with "www". Internally, and in the Mailman configuration, the hostname is just "lists". If I add a ServerAlias of "www.lists..." to my Apache configuration, listinfo interprets www.lists in a different manner and claims there are no lists published for www.lists... Is there a way I can have "www.lists" get the same results as "lists" either through mm_cfg.py or the Apache configuration? Perhaps with add_virtualhost? Any help would be appreciated. Regards, Alan Rubin Technician Unix DCS Midrange Services Phone: +61 (08) 8999 6814 Fax: +61 (08) 8999 7493 e-Mail: alan.rubin(a)nt.gov.au

2 1

Messages just began to be shunted, can't figure out why.
by Gary Goldberg 18 Aug '08

18 Aug '08

Hello. I've had a long running Mailman installation with about a dozen lists spread over four domain names on a Dell PowerEdge with 3GB RAM running CentOS 3.9 (fully patched). We're using the non-default Sendmail 8.14.1. I've upgraded to 2.1.11 in June and everything was working fine/clean until last Friday night. We had a problem with our SpamAssassin subsystem dropping offline for a few hours, and we rebooted the machine to reset everything. Since then, messages I attempt to post to a Cub Scout list hosted in Mailman have been shunted. Unshunting them just requeues them again. This is the error message text I'm getting: ----------------- Aug 18 11:19:54 2008 (14837) Uncaught runner exception: recips Aug 18 11:19:54 2008 (14837) Traceback (most recent call last): File "/home/digimark/www-mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/home/digimark/www-mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/digimark/www-mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/digimark/www-mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/digimark/www-mailman/Mailman/Handlers/AvoidDuplicates.py", line 39, in process recips = msgdata['recips'] KeyError: recips Aug 18 11:19:54 2008 (14837) SHUNTING: 1219015598.1364529+cd4fcf44c07ffa9b1b0bfa53882233f59121be5f Aug 18 11:19:54 2008 (14837) Uncaught runner exception: recips Aug 18 11:19:54 2008 (14837) Traceback (most recent call last): File "/home/digimark/www-mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/home/digimark/www-mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/digimark/www-mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/digimark/www-mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/digimark/www-mailman/Mailman/Handlers/AvoidDuplicates.py", line 39, in process recips = msgdata['recips'] KeyError: recips Aug 18 11:19:54 2008 (14837) SHUNTING: 1219015818.240051+5a69da3e2069c3651120d6d82780d698a34d8450 Aug 18 11:19:54 2008 (14837) Uncaught runner exception: recips Aug 18 11:19:54 2008 (14837) Traceback (most recent call last): File "/home/digimark/www-mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/home/digimark/www-mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/digimark/www-mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/digimark/www-mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/digimark/www-mailman/Mailman/Handlers/AvoidDuplicates.py", line 39, in process recips = msgdata['recips'] KeyError: recips Aug 18 11:19:54 2008 (14837) SHUNTING: 1219027815.2000761+2a51d7a1d8075b0725278b944eeac7be2eac54e3 ----------------- The system doesn't appear to be out of memory, as suggested by another message exchange here. The system has python 2.2.3 installed. Can anyone suggest a line of attack for figuring this out and dealing with it? I reinstalled mailman over top of the current installation -- no apparent difference. Thanks in advance for any insight. -Gary -- -- "Gentleman, you can't fight in here! This is the War Room." -President Muffley Gary Goldberg KA3ZYW <og(a)digimark.net> V:301/249-6501 F:301/390-1955 AIM:OgGreeb Digital Marketing/Bowie MD/Internet Systems & Networks <http://www.digimark.net/>

2 8