Mailman 3 August 2012 - Mailman-Users

data/aliases is created by mailman? or manually?
by Thufir 29 Aug '12

29 Aug '12

In going through an Ubuntu guide: "This build of mailman runs as list. It must have permission to read /etc/aliases and read and write /var/lib/mailman/data/aliases. Do this with these commands: sudo chown root:list /var/lib/mailman/data/aliases sudo chown root:list /etc/aliases" https://help.ubuntu.com/community/Mailman#Postfix_Configuration is data/aliases created by mailman? Or, do I manually create that file? How do I know that the aliases are correct? see: http://marc.info/?l=postfix-users&m=134615669604847&w=2 thanks, Thufir

2 1

Postfix and virtual user ( relay dovecot -> user unknown )
by Sébatien Andreatta 29 Aug '12

29 Aug '12

Hello, I have been looking for weeks on google , but i have not found valid answer : How to integrate Mailman with postfix without the use of postfix-to-mailman.py script wich is not officialy supported ? I have a working installation : Postfix -> Amavisd ( clamd , spamassassin ) And dovecot I followed all the howto that i have found but it still doesn't work. I would like to have all my lists on a subdomain : lists.mydomain.be So , now here is my configuration : postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases command_directory = /usr/sbin config_directory = /etc/postfix content_filter = amavisfeed:[127.0.0.1]:10024 daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 2 html_directory = no inet_interfaces = all inet_protocols = all mail_owner = postfix mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man mydestination = $myhostname, localhost.$mydomain, localhost, lists.mydomain.be mydomain = mydomain.be myhostname = smeagoln.mydomain.be myorigin = $mydomain newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.6.6/README_FILES recipient_delimiter = + relay_domains = $mydestination relayhost = relay.domain.be sample_directory = /usr/share/doc/postfix-2.6.6/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtpd_banner = $myhostname ESMTP $mail_name unknown_local_recipient_reject_code = 550 virtual_alias_maps = ldap:/etc/postfix/ldap-aliases.cf, hash:/etc/mailman/virtual-mailman virtual_gid_maps = static:493 virtual_mailbox_base = /var/mail/vhosts/ virtual_mailbox_domains = ldap:/etc/postfix/ldap-domains.cf virtual_mailbox_maps = ldap:/etc/postfix/ldap-accounts.cf virtual_transport = dovecot virtual_uid_maps = static:493 mm_cfg.py DEFAULT_URL_HOST ='www.mydomain.be' DEFAULT_EMAIL_HOST = 'smeagoln.mydomain.be' MTA = 'Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.mydomain.be'] maillog : Aug 18 19:22:47 mydomain postfix/qmgr[6085]: F05353E92: from=< crupuk(a)mydomain.be>, size=914, nrcpt=1 (queue active) Aug 18 19:22:47 mydomain dovecot: imap-login: Login: user=< crupuk(a)mydomain.be>, method=PLAIN, rip=::1, lip=::1, mpid=6139, secured Aug 18 19:22:48 mydomain amavis[4479]: (04479-05) Passed CLEAN, MYNETS LOCAL [127.0.0.1] [127.0.0.1] <crupuk(a)mydomain.be> -> <test(a)mydomain.be>, Message-ID: <1d504d6a1f2f9954ecc5ab2f4a193b9e(a)mydomain.be>, mail_id: zAsh0XT4N+qM, Hits: -0.999, size: 510, queued_as: F05353E92, 5437 ms Aug 18 19:22:48 mydomain dovecot: imap(crupuk(a)mydomain.be): Disconnected: Logged out bytes=82/572 Aug 18 19:22:48 mydomain postfix/lmtp[6123]: BE3CE3E8F: to=<test(a)mydomain.be>, orig_to=<test(a)lists.mydomain.be>, relay=127.0.0.1[127.0.0.1]:10024, delay=6.8, delays=0.31/0.49/0.25/5.7, dsn=2.0.0, status=sent (250 2.0.0 Ok, id=04479-05, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as F05353E92) Aug 18 19:22:48 mydomain postfix/qmgr[6085]: BE3CE3E8F: removed Aug 18 19:22:48 mydomain dovecot: imap(crupuk(a)mydomain.be): Disconnected: Logged out bytes=307/8873 Aug 18 19:22:49 mydomain postfix/pipe[6138]: F05353E92: to=<test(a)mydomain.be>, relay=dovecot, delay=2.4, delays=0.2/1.3/0/0.86, dsn=5.1.1, status=bounced (user unknown) Mailman version : 2.1.12 ( So , I can't use VIRTUAL_MAILMAN_LOCAL_DOMAIN ) So, how can I do for deliver all mail for test(a)lists.mydomain.be by local agent and so, use alias_maps ? Thanks for your help

5 6

subscribe @localhost
by Thufir 29 Aug '12

29 Aug '12

I want to subscribe thufir@localhost to a mailing list -- of course that's rejected for not being a FQDN. So I subscribed thufir(a)dur.bouncme.net. Presumably I need to configure postfix recognize that as localhost? In terms of mailman, is there a log of what happened. I don't expect the subscription message to make it all the way through, but how do I trace it through mailman to see the attempts to send confirmation, and what errors were reported, etc. I suppose this is similar to setting up mailman for an intranet? An intranet of one. thanks, Thufir

2 2

add_members with password
by Eric Smith 29 Aug '12

29 Aug '12

How do I add_members and allocate a password? For members who do not wish to subscribe through the web interface, what is the way to subscribe them so that they have a password for subsequent login? Thanks Eric Smith

3 2

Mailman and SpamAssassin
by Lindsay Haisley 29 Aug '12

29 Aug '12

I'm putting in a new server and would like to integrate SpamAssassin into Mailman (2.1.15) according to the directions previously posted online at http://www.jamesh.id.au/articles/mailman-spamassassin/, which I updated at http://wiki.list.org/pages/viewpage.action?pageId=4030589 and have been using successfully on another server. Unfortunately, the original article is no longer online. Does anyone know if there's a mirror or archive of it somewhere? -- Lindsay Haisley | "Everything works if you let it" FMP Computer Services | 512-259-1190 | --- The Roadie http://www.fmp.com |

2 1

Mailman and SpamAssassin
by Lindsay Haisley 29 Aug '12

29 Aug '12

I'm putting in a new server and would like to integrate SpamAssassin into Mailman (2.1.15) according to the directions previously posted online at http://www.jamesh.id.au/articles/mailman-spamassassin/, which I updated at http://wiki.list.org/pages/viewpage.action?pageId=4030589 and have been using successfully on another server. Unfortunately, the original article is no longer online. Does anyone know if there's a mirror or archive of it somewhere? -- Lindsay Haisley | "Everything works if you let it" FMP Computer Services | 512-259-1190 | --- The Roadie http://www.fmp.com |

1 0

Error: You are not authorized to create new mailing lists
by Thufir 28 Aug '12

28 Aug '12

While I can browse to http://localhost/cgi-bin/mailman/listinfo/comp.lang.java.help and see that there's such a list, I cannot create list from http://localhost/cgi-bin/mailman/admin which returns Error: You are not authorized to create new mailing lists whenever I try to create a list. However, it does work from the CLI: root@dur:~# root@dur:~# newlist comp.lang.java.help Enter the email of the person running the list: hawat.thufir(a)gmail.com Initial comp.lang.java.help password: To finish creating your mailing list, you must edit your /etc/aliases (or equivalent) file by adding the following lines, and possibly running the `newaliases' program: ## comp.lang.java.help mailing list comp.lang.java.help: "|/var/lib/mailman/mail/mailman post comp.lang.java.help" comp.lang.java.help-admin: "|/var/lib/mailman/mail/mailman admin comp.lang.java.help" comp.lang.java.help-bounces: "|/var/lib/mailman/mail/mailman bounces comp.lang.java.help" comp.lang.java.help-confirm: "|/var/lib/mailman/mail/mailman confirm comp.lang.java.help" comp.lang.java.help-join: "|/var/lib/mailman/mail/mailman join comp.lang.java.help" comp.lang.java.help-leave: "|/var/lib/mailman/mail/mailman leave comp.lang.java.help" comp.lang.java.help-owner: "|/var/lib/mailman/mail/mailman owner comp.lang.java.help" comp.lang.java.help-request: "|/var/lib/mailman/mail/mailman request comp.lang.java.help" comp.lang.java.help-subscribe: "|/var/lib/mailman/mail/mailman subscribe comp.lang.java.help" comp.lang.java.help-unsubscribe: "|/var/lib/mailman/mail/mailman unsubscribe comp.lang.java.help" Hit enter to notify comp.lang.java.help owner... root@dur:~# why won't the web interface accept the same password? Or, is it that the web interface itself, perhaps, isn't authorized. What's not authorized, the password I provided (which works from the CLI) or something about how the web interface is setup? thanks, Thufir

2 4

nntp -> dovecot POP3
by Thufir 28 Aug '12

28 Aug '12

I've seen mention that mailman can be used between nntp and e-mail. What I'm looking for is to send nntp messages to e-mail, just one way. I don't need a full gateway such as gmane, just one way is sufficient. Currently I'm using dovecot-postfix in Ubuntu with leafnode (http://leafnode.sourceforge.net/ )as the nntp server. What would be involved in directing mailman at leafnode, on localhost, to e-mail a particular newsgroup? thanks, Thufir

2 5

RTFM gate_news
by Thufir 28 Aug '12

28 Aug '12

Where is the documentation for mailman gate_news and how is it configured? I'm running Leafnode on localhost and am using a dovecot-postfix mail stack on Ubuntu. How can I wire them together with mailman to export usenet messages? The best info I've found about gate_news is: http://opensource.apple.com/source/mailman/mailman-117/mailman/cron/gate_ne… I'm sure it's on GNU as well, and the usage seems not terribly difficult, at least judging the comments in the above code. Am I just not seeing the manual/tutorial? thanks, Thufir

2 3

illegal list name (FQDN & hostname)
by Thufir 28 Aug '12

28 Aug '12

Why does mailman see or use @dur for the FQDN when it should be dur.bounceme.net? thufir@dur:~$ thufir@dur:~$ thufir@dur:~$ sudo newlist mailman Enter the email of the person running the list: hawat.thufir(a)gmail.com Initial mailman password: Create a new, unpopulated mailing list. Usage: /usr/sbin/newlist [options] [listname [listadmin-addr [admin-password]]] Options: -l language --language=language Make the list's preferred language `language', which must be a two letter language code. -u urlhost --urlhost=urlhost Gives the list's web interface host name. -e emailhost --emailhost=emailhost Gives the list's email domain name. -q/--quiet Normally the administrator is notified by email (after a prompt) that their list has been created. This option suppresses the prompt and notification. -h/--help Print this help text and exit. You can specify as many of the arguments as you want on the command line: you will be prompted for the missing ones. Every Mailman list has two parameters which define the default host name for outgoing email, and the default URL for all web interfaces. When you configured Mailman, certain defaults were calculated, but if you are running multiple virtual Mailman sites, then the defaults may not be appropriate for the list you are creating. You also specify the domain to create your new list in by typing the command like so: newlist --urlhost=www.mydom.ain mylist where `www.mydom.ain' should be the base hostname for the URL to this virtual hosts's lists. E.g. with this setting people will view the general list overviews at http://www.mydom.ain/mailman/listinfo. Also, www.mydom.ain should be a key in the VIRTUAL_HOSTS mapping in mm_cfg.py/Defaults.py if the email hostname to be automatically determined. If you want the email hostname to be different from the one looked up by the VIRTUAL_HOSTS or if urlhost is not registered in VIRTUAL_HOSTS, you can specify `emailhost' like so: newlist --urlhost=www.mydom.ain --emailhost=mydom.ain mylist where `mydom.ain' is the mail domain name. If you don't specify emailhost but urlhost is not in the virtual host list, then mm_cfg.DEFAULT_EMAIL_HOST will be used for the email interface. For backward compatibility, you can also specify the domain to create your new list in by spelling the listname like so: mylist(a)www.mydom.ain where www.mydom.ain is used for `urlhost' but it will also be used for `emailhost' if it is not found in the virtual host table. Note that '--urlhost' and '--emailhost' have precedence to this notation. If you spell the list name as just `mylist', then the email hostname will be taken from DEFAULT_EMAIL_HOST and the url will be taken from DEFAULT_URL (as defined in your Defaults.py file or overridden by settings in mm_cfg.py). Note that listnames are forced to lowercase. The list admin address need to be a fully-qualified address, like owner(a)example.com, not just owner. Illegal list name: mailman@dur thufir@dur:~$ thufir@dur:~$ cat /etc/hosts 127.0.0.1 localhost 127.0.1.1 dur.bounceme.net # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters thufir@dur:~$ thufir@dur:~$ cat /etc/hostname dur.bounceme.net thufir@dur:~$ thufir@dur:~$ hostname dur.bounceme.net thufir@dur:~$ thufir@dur:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.04 DISTRIB_CODENAME=precise DISTRIB_DESCRIPTION="Ubuntu 12.04 LTS" thufir@dur:~$ The help page: https://help.ubuntu.com/community/Mailman doesn't provide any troubleshooting which I see. However, I'm not the only one to get this message: http://mail.python.org/pipermail/mailman-users/2006-August/052587.html However, I see no solution available. thanks, Thufir

2 3

Mailman-Users August 2012