Re: [Mailman-Users] Amazon SES and Verified Senders
Have you tried working directly with Amazon SES to resolve the issue? I have not personally, but on their forums, others have posed have the same problem, and following is a reply directly from AWS: We want to accommodate as many ways to send email as we can, while also providing strong protections against phishing and other abusive email. If the email address verification feature did not exist, then anyone could send to the members of your mailing list using the email address of your organization ( @nearzero.org ), for example. We realize that this creates some roadblocks to your users communicating with each other using Amazon SES as the medium. Here are some partial solutions to consider: When sending through Amazon SES, instead of using the From address of your user, instead use your organization's email address with a friendly name which identifies the user. Only the email address portion is verified, so you can send with From addresses like so: * From: Seth mail...@nearzero.org * From: Justin C. mail...@nearzero.org You may also consider adding a Reply-To header identifying the original user's actual email address. A regular reply will be sent there, directly to that user. A Reply All will include the mailman address which you can treat as a message to the list. If I knew how to replace the Friendly name with something else, that /might/ be another solution, but I haven't been able to figure out how to do that. I'm guessing that is a Postfix question. 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. That's not an option. We use lists for minute-by-minute round table conversations and tech support. If find it hard to believe that this isn't a common issue, since many people need a 3rd party SMTP relay Is it possible that this just doesn't come up much because people who run Mailman run everything, including their own SMTP relay in-house? -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
[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
[Mailman-Users] Displaying the sender email
Hello, Is there a way to configure Mailman lists so the From: line can say: From listn...@mymanserver.com [On Behalf of john@yahoo.com] We are using a 3rd-party SMTP relay for all outbound mail, so we need to approve all senders for the service to allow the email to go through. This poses a problem with the dozens of mailing lists we host, since it is not practical to approve hundreds (if not thousands) of members. So what we are doing is configuring the mailman lists to Hide the sender of a message, replacing it with the list address (Removes From, Sender and Reply-To fields) , setting it to Yes. So now all members of the list will see posts as: From: listn...@mymailmanserver.com Instead of the address of the poster. This is actually a good thing for us, and we actually prefer this behavior to ensure that discussions will stay on the lists, but also this solves the problem of the SMTP relay service, since now we only need to approve the wildcard for *@mymailmanserver.com so the service will relay the email. The problem is that posters don't always include signatures, and we need to know who sent them, but by stripping out the original sender, unless they do include a signature in the body, members might not always be able to tell who posted to the list. Thanks in advance. -- 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] Migration to new server, new domain name
Hello, Can anybody point me to a document or explain to me what is necessary to complete these steps? We have a mailman server hosted on a FreeBSD box and need to migrate it an Ubuntu box and change domain names on all the lists. We have several dozen lists, all under the foo.org domain. We need to change foo.org to bar.org The current mail.foo.org server on FreeBSD is getting long in the tooth, and we need to move anyway to Ubuntu. So I need to set up a new Ubuntu server w/ Postfix, Mailman and Apache and call this server mail.bar.org and this will be the MX server for bar.org. For each *...@foo.org list, I need to move it to the new server, and it's archives to mail.bar.org and that list will be called *...@bar.org But I also want to be able to protect users with forwarding.if they still send mail to their old respective *...@foo.org list, how do I configure to foward and process to the new *...@bar.org list? Thanks in advance for any links, docs, or advice. 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] best way to make announce list for members of lots of other lists?
Hello, Question: We host a few dozen lists for clients who run our software. Each client has a unique list for their own organization, and it is used to correspond with us (the developers), etc., but not with each client. However, whenever we release a new version of software for ALL the clients, we would like an announce list, so one of us can post an announcement, and all the clients get. 1) Each client should not see who the other clients are. 2) Is there an easy way to take members of the existing lists so extra work does not have to be done to populate the announce list with same members? 3) Just as an aside, our clients do not subscribe to the lists -- we do it for them, and then only give them access to the archives. Thanks for any info, DW -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
