Re: [Mailman-Users] Testing STEALTH_MODE = 1
Thanks, that was exactly what I needed! The version of Mailman is a bit later than 2.1.6, but it's still pretty old. Have to be a bit cagey as it's not my install. I suspect that whoever turned off stealth mode to test and then never turned it back on again. Out of interested, is there an ETA on a production release of Mailman 3.x ? Thanks again! Tom -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Migrating a list to a (Postfix) virtual host
Hey, I currently encounter the following problem: We have several mailing lists in our project, but we'll buy a new domain. The lists are currently running under our old domain. The new domain will point to the same server and will be registered as virtual_alias_domain in Postfix. Is it possible to move the lists which aren't virtual hosted yet (they appear only in data/aliases) to the virtual host (so they appear additionally in data/virtual-mailman)? I searched the web but I didn't find anything helpful about this topic. The problem is that I don't want to re-create the list because it'd be good to keep the passwords and settings of the subscribers. --Norbert -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Testing STEALTH_MODE = 1
On Jan 11, 2013, at 01:14 PM, Tom Skelley wrote: Out of interested, is there an ETA on a production release of Mailman 3.x ? At this point, we're mostly trying to get the web ui (Postorius) feature compatible with Mailman 2.1. We're also working on the new archiver (Hyperkitty). I think the core engine is pretty stable and would invite interested users to give it a go, but understand that it has to be managed from the command line for now. We will be sprinting on these components again at Pycon 2013. Cheers, -Barry -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] client denied by server configuration
Hi all. I have a strange problem.. most of the mailman site works well, but a few, don't, and give me 'client denied by server configuration' in the apache error log. for instance.. when I visit: https://linux3.dti.supsi.ch/mailman/admindb/cdl-elettro and try to accept a subscription request, I get this error in the apache log, and the request is still there waiting to be accepted.. [Fri Jan 11 10:02:44 2013] [error] [client myip] client denied by server configuration: /opt/www/cdl-elettro The same way, when I visit: https://linux3.dti.supsi.ch/mailman/admindb/prova01 and try to accept a held message, I get this error in the apache log, and the message is still there waiting to be accepted.. [Fri Jan 11 10:32:53 2013] [error] [client myip] client denied by server configuration: /opt/www/prova01 So.. in mm_cfg.py: DEFAULT_URL_PATTERN = 'http://%s/mailman/' PRIVATE_ARCHIVE_URL = '/mailman/private' and in apache.conf: Alias /pipermail/ /var/lib/mailman/archives/public/ Alias /images/mailman/ /usr/share/images/mailman/ ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/ Directory /usr/lib/cgi-bin/mailman/ AllowOverride None Options ExecCGI AddHandler cgi-script .cgi Order allow,deny Allow from all /Directory Directory /var/lib/mailman/archives/public/ Options Indexes FollowSymlinks AllowOverride None Order allow,deny Allow from all /Directory Directory /usr/share/images/mailman/ AllowOverride None Order allow,deny Allow from all /Directory Could anybody please try to help me out? Thank you and best regards. Robi -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] how to revert back to local domain only?
This is my first time posting. I am a relatively inexperienced Mailman administrator but have no trouble with CLI. Context is that I have version 2.1.14 installed on an Apple Mac mini running client Mac OS 10.6.8. I used Larry Stone's instructions (dated May 2, 2010) for installing into /usr/local/mailman. MTA is Postfix. I believe that integration with Postfix in my case does NOT require postfix-to-mailman.py, but I do not understand enough about that to say more. My goal is to learn more about how Mailman works, how to administer it. I am trying different configurations--getting my feet wet so to speak. Above question arises out of curiosity. Having successfully implemented virtual domains I now arbitrarily wish to revert this installation to local-domain only. (It's not so arbitrary: I learn by undoing. Born analyst, I guess.) I fully expect to have to delete from main.cf and mm_cfg.py what I had to insert there to enable virtual domains. Postfix's virtual_alias_maps configuration in main.cf comes to mind. Likewise, I'm thinking Mailman's add_virtualhost configuration in from mm_cfg.py would be another. But what about Mailman's VIRTUAL_HOSTS.clear config in mm_cfg.py? Do I take that out too? Furthermore, I am aware that once configured for virtual domains, mailman automatically generates certain files: /usr/local/mailman/data/virtual_mailman, among others. However, it is not clear to me whether these files will automatically be removed or whether their removal requires my intervention. Indeed I don't even know that they would need to be removed. Finally, there is bound to be more to this than I merely anticipate. Perhaps there are other files to modify or remove. Someone please advise. Many thanks, Graham Young -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] client denied by server configuration
Roberto Nunnari wrote: Hi all. I have a strange problem.. most of the mailman site works well, but a few, don't, and give me 'client denied by server configuration' in the apache error log. Hi. I finally managed to solve it myself.. I had a few configuration errors in the mailman configuration and in the lists dbs.. vi and withlist helped me out. Thank you anyways and sorry for the noise. Best regards. Robi -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Export messages to another archiver
Vincent Le Goff wrote: I'd like to find a way to export my list's messages to use a different archiver. Is it possible to export messages with the 'withlist' command? I didn't find how to retrieve the list's messages. It is possible, but probably more complex than you need. Or is there some hook system or something to execute a specific command when a message is received (I tried to find a postfix-side configuration, but it doesn't seem to be possible). I'm not sure what you want. If you want to get the list's current archive to move to another archiver, the entire archive is normally (unless you've changed default settings) contained in mbox format in Mailman's archives/private/LISTNAME.mbox/LISTNAME.mbox. If you want to invoke some process on each new message as it arrives, the easiest way is to subscribe a local address to the list and alias that address in Postfix to a pipe to the process. Also, see the FAQ at http://wiki.list.org/x/RAKJ and read the # # Archive defaults # section in Mailman's Defaults.py. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Migrating a list to a (Postfix) virtual host
Norbert Aschendorff wrote:
Is it possible to move the lists which aren't virtual hosted yet (they
appear only in data/aliases) to the virtual host (so they appear
additionally in data/virtual-mailman)? I searched the web but I didn't
find anything helpful about this topic. The problem is that I don't want
to re-create the list because it'd be good to keep the passwords and
settings of the subscribers.
It is not difficult, but requires a few steps.
1) add
add_virtualhost('new.web.domain', 'new.email.domain')
and
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['new.email.domain']
to mm_cfg.py
2) run Mailman's
bin/withlist -r fix_url LISTNAME -u new.web.domain
to move the LISTNAME list or run
bin/withlist -r fix_url -a -- -u new.web.domain
to do all lists.
3) run Mailman's
bin/genaliases
4) add
hash:/path/to/mailman/data/virtual-mailman
to virtual_alias_maps in Postfix main.cf and reload Postfix.
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Amazon SES and Verified Senders
Hello, Does anyone have any ideas on how to deal with this dilemma: I am running Mailman+Postfix+Ubuntu in Amazon AWS, and using Amazon SES as a relay. Although, this problem isn't unique to just SES. This problem is common among many relay services, DynDNS to name another. To prevent against spam and abuse, SES, DynDNS and other relay services require that you VERIFY each SENDER before you can send mail from that email address. When running Mailman, each member of every list is the SENDER, and it is not practical or even possible to verify every sender. I have two workarounds, but neither one is ideal. Option 1) In Mailman, I can enable: Hide the sender of a message, replacing it with the list address (Removes From, Sender and Reply-To fields) This will mean any post to a list will show only the list, and the list will be the return address (that is ok, even desirable). But the problem with this is, that unless the poster includes a signature, there is no way to know who it came from when the other list members receive the post. We need to know who posted to the lists, so we know who we're replying to, and if we need their email to take the conversation off-list, etc. Option 2) In Postfix, maintain the canonical file so that each member address will be rewritten with a mailman domain address. Example: In /etc/postfix/canonical: jon...@hotmail.com jondoe.at.hotmail@mymailmandomain.com Because I've approved the domain @mymailmandomain.com with DKIM in Amazon SES, and email from jon...@hotmail.com will be rewritten as From: jondoe.at.hotmail@mymailmandomain.com, and Amazon SES will permit it. The problem with this is that it still doesn't accurately reflect the senders real email anywhere, and another list member might pull the bogus jondoe.at.hotmail@mymailmandomain.com address, and try to send to this person off-list, or add the bogus email address to their address booknot good. Also, a cronjob will have to regularly build and update the canonical addresses, which in itself isn't that a big deal, but is another point of failure. Does anybody else have this problem, and how do you deal with it? Are there better solutions? Perhaps their is a better way to do #2 so that the From: address is rewritten to be acceptable to Amazon SES, but displays something that is more useful and friendly to recipients? Thanks for any input! DW -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Migrating a list to a (Postfix) virtual host
Yeah, sounds quite simple :) Small question: genaliases looks at the URL in the list configuration and generates the aliases from it? Thanks :) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] how to revert back to local domain only?
Graham Young wrote: But what about Mailman's VIRTUAL_HOSTS.clear config in mm_cfg.py? Do I take that out too? It depends. If the configured values for DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST in Defaults.py are correct, you don't need any add_virtualhost() or VIRTUAL_HOSTS.clear() directives in mm_cfg.py. If you need to change these or if you just want the settings in mm_cfg.py for documentation purposes, put DEFAULT_URL_HOST = '...' DEFAULT_EMAIL_HOST = '...' VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) in mm_cfg.py. Note that you must have one VIRTUAL_HOSTS entry for DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST. This is added in Defaults.py, but may not be the correct names. The purpose of VIRTUAL_HOSTS.clear() in mm_cfg.py is to remove the possibly erroneous entry added in Defaults.py. It isn't really necessary to do this in any case, but it's cleaner. Furthermore, I am aware that once configured for virtual domains, mailman automatically generates certain files: /usr/local/mailman/data/virtual_mailman, among others. However, it is not clear to me whether these files will automatically be removed or whether their removal requires my intervention. Indeed I don't even know that they would need to be removed. They won't be removed, and they don't need to be, but the reference to data/virtual-mailman in Postfix virtual_alias_maps needs to be removed. Finally, there is bound to be more to this than I merely anticipate. Perhaps there are other files to modify or remove. Probably not. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Migrating a list to a (Postfix) virtual host
Norbert Aschendorff wrote: Small question: genaliases looks at the URL in the list configuration and generates the aliases from it? Genaliases generates aliases for each list using only the list name. It also generates the virtual mappings (virtual-mailman) for those lists whose host_name attribute is in POSTFIX_STYLE_VIRTUAL_DOMAINS. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Migrating a list to a (Postfix) virtual host
Another possibility (sufficient for at least my situation) came just to my mind: Adapt the list's /host_name/ and set up an alias respectively an entry in Postfix' virtuals table pointing to the list's address on the new virtual host. It's not really elegant, but it works so far. --Norbert -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Export messages to another archiver
Vincent Le Goff wrote: Thanks, I didn't think about subscribing a local address to get the incoming messages. That could be what I need, but as I will try different solutions before choosing, could you tell me (if it's simple enough, redirect me otherwise to some web page) how to export messages with the 'withlist' command? withlist is probably not at all what you want. The only thing you could do with withlist is use archiver methods to retrieve messages from the built in archive. This would be difficult as the methods are designed to add messages to an archive, not to retrieve them. It would be easier to create a process which accesses the archives/private/LISTNAME.mbox/LISTNAME.mbox file and retrieves 'new messages from it. If you want this process to replace the built in archiving rather than supplement it, and you want it to apply to all lists or maybe just all lists with public archives or all lists with private archives, See the documentation for PRIVATE_EXTERNAL_ARCHIVER and PUBLIC_EXTERNAL_ARCHIVER in the # # Archive defaults # section in Mailman's Defaults.py. I would like to find a way to export (either periodically or every time a message is received) the list's posts, in order to use a different web interface for the archiver. I know that selecting ALL messages posted to a list could be a really bad idea, if the list is big enough, but maybe some ways (that I would look for later) would allow me to export only one post at a time. As noted above, if you want to replace the built in archiver, Mailman's facility for specifying an external archiver is the way to go unless you want to do it for just one or a few of many lists. If you want it for just a few lists, the easiest way is to subscribe a local address and alias it to a pipe to the archiving process. Another way would be a custom handler which would apply to only selected lists and pipe the message to the external archiver. See the FAQ at http://wiki.list.org/x/l4A9. If you want an external archiver for all lists to supplement rather than replace the built in archiver, see the FAQ at http://wiki.list.org/x/RAKJ. PS: The reply-to is set to your address, not to the list. I don't know if I'm supposed to reply to the mailman-users mailing list, or if I just have to summarize what you told me in a different post. You posted to the list. I 'replied all' which addressed my reply to both you and the list (you probably only received the direct copy because your subscription is set to Avoid duplicate copies of messages? - nodupes). There was no reply-to: in my message to you and there would not have been in the list copy either. You can either 'reply' to just me or 'reply all' to me and the list. The latter is usually, but not always what you want. I have Cc'd this reply to the list. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Amazon SES and Verified Senders
Duane Winner writes: Does anyone have any ideas on how to deal with this dilemma: I am running Mailman+Postfix+Ubuntu in Amazon AWS, and using Amazon SES as a relay. Although, this problem isn't unique to just SES. This problem is common among many relay services, DynDNS to name another. To prevent against spam and abuse, SES, DynDNS and other relay services require that you VERIFY each SENDER before you can send mail from that email address. When running Mailman, each member of every list is the SENDER, and it is not practical or even possible to verify every sender. AFAICS, you lose, then. Specifically, if you obfuscate the sender, you are probably in violation of the AUP for the relay service you are using. Have you tried working directly with Amazon SES to resolve the issue? I wonder if a third possibility, namely encapsulating every message in another message sent by Mailman, would do the trick. Ie, require all subscribers to subscribe to the digest edition of the list. Steve -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
