[Mailman-Users] Permission problems with /etc/mailman/*.db
This is a clean install on Fedora 12, which provides Mailman 2.1.12 This time my cookbook seemed to be all in order. Everything was going great. Mailman list created and user added, message sent, then I locked up the Mailman list so it would not be available to viewers once I moved this box to a public network. Then I went to create my first list via /mailman/create. I got a bug. On checking the error_log, I see that create does not have permissions to /etc/mailman/aliases.db I go over to /etc/mailman, and I see that both aliases and virtual-mailman were updated, but NOT the .db files. The permissions on the .db files is 640, not 660! How come? So I ran check_perm -f as Mark recommended for the last permission problem (that I caused, but this time it was straight install stuff), and it fixed a number of errors: # /usr/lib/mailman/bin/check_perms -f /usr/lib/mailman/cron bad group (has: root, expected mailman) (fixing) directory permissions must be 02775: /usr/lib/mailman/cron (fixing) /usr/lib/mailman/Mailman bad group (has: root, expected mailman) (fixing) directory permissions must be 02775: /usr/lib/mailman/Mailman (fixing) /usr/lib/mailman/Mailman/mm_cfg.pyc bad group (has: root, expected mailman) (fixing) Warning: Private archive directory is other-executable (o+x). This could allow other users on your system to read private archives. If you're on a shared multiuser system, you should consult the installation manual on how to fix this. /etc/mailman/aliases.db owned by root (must be owned by mailman (fixing) /etc/mailman/aliases.db permissions must be 066x (got 0100640) (fixing) /etc/mailman/virtual-mailman.db owned by root (must be owned by mailman (fixing) /etc/mailman/virtual-mailman.db permissions must be 066x (got 0100640) (fixing) Problems found: 9 Re-run as mailman (or root) with -f flag to fix That is a LOT of errors for just installing with yum and running the mailman mmsitepass and newlist scripts! Now this is Fedora 12 with is eol, so we IF the problem is Fedora's packaging, we probably won't get it fixed here. But what about Fedora 13 14? I won't be working with 13 for mailman. I will be working on a Fedora 14 migration probably around February, so I can't check this out there for a while. I hope I won't encounter this little supprise then... But other than this little speed bump, I GOT IT UP AND RUNNING THANK YOU for your help. I know have to configure all the users in the SQL database (not really that hard), then rsync to mail from the old server to the new (after stopping mail on the old), then switch the servers out. I could be in production tonight. -- 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] Problems with hostnames
Hi, On my debian leny I run the mailman 2.1.11 stable version in english language. I have different hostnames pointing to the server. Lets say, default is domain1. When I create a newlist and login to de admin-interface, I change the hostname to domain2. When the system sends mail to recipients (using postfix), it use only the default domain1 hostname in the links in the message. How could I change this/fix this so message sended to the users with links in it, points to the configured second domainname, domain2? Regards, Ruud -- 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] htdig integration patches to be updated for 2.1.14?
Great, thanks Mark. Will you or someone else be updating the sourceforge patches with these? Would be nice to keep the patches for various mm versions consolidated there. Chris On Mon, Dec 6, 2010 at 11:42 AM, Mark Sapiro m...@msapiro.net wrote: Chris Toomey wrote: Can somebody update those patches for 2.1.14, or should I just go with 2.1.10? Also, I've not been able to find any documentation on the changes made in each mailman release so it's hard to tell what I'd be giving up in going w/ 2.1.10 -- can someone point me to where that release info. is? There is a set of patches against the 2.1.14 base at http://www.msapiro.net/mm/. You can see the release by release changes in the NEWS file either in the 2.1.14 tarball or at http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/fileshttp://bazaar.launchpad.net/%7Emailman-coders/mailman/2.1/files . -- 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] Problems with different hostnames
Hi, On my debian leny I run the mailman 2.1.11 stable version in english language. I have different hostnames pointing to the server. Lets say, default is domain1. When I create a newlist and login to de admin-interface, I change the hostname to domain2. When the system sends mail to recipients (using postfix), it use only the default domain1 hostname in the links in the message. How could I change this/fix this so message sended to the users with links in it, points to the configured second domainname, domain2? Regards, Ruud -- 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] Interesting problem with gmail users
Note: this is NOT the frequently asked question about why GMail users don't see their own posts. I run a bunch of mailman mailing lists, and I'm subscribed to those lists from my GMail account. I also set up a filter to tag the posts from those mailing lists. However, the messages from some other GMail users on those mailing lists show a banner that says Due to a filter you created, this message was not sent to Spam. Edit Filters. Other GMail users do not show that banner. The ones who do show the banner show it consistently for every message they send to the list (although not on messages they send me directly) and the ones who do not show the banner never show it. I've never seen it for a non-GMail address. I suspect it has something to do with the way GMail puts a DKIM-Signature and DomainKey-Signature on outgoing mail. Something Mailman is doing is making the signatures invalid. As a matter of fact, doing a Show original on a couple of the flagged messages seems to confirm that, with messages like Authentication-Results: mx.google.com; spf=pass (google.com: domain of geeks-boun...@list.xcski.com designates 69.164.214.240 as permitted sender) smtp.mail=geeks-boun...@list.xcski.com; dkim=neutral (body hash did not verify) header...@gmail.com So what are my options here? Can I strip out the DKIM headers within Mailman? Or should I just configure my mailserver to add a DKIM header? -- http://www.linkedin.com/in/paultomblin http://careers.stackoverflow.com/ptomblin -- 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] Problems with different hostnames
Ruud wrote:
On my debian leny I run the mailman 2.1.11 stable version in english
language.
I have different hostnames pointing to the server. Lets say, default is
domain1. When I create a newlist and login to de admin-interface, I change
the hostname to domain2.
When the system sends mail to recipients (using postfix), it use only the
default domain1 hostname in the links in the message.
This is because there are two list attributes that contain the domain.
They are host_name and web_page_url, and web_page_url is not visible
in the admin GUI.
How could I change this/fix this so message sended to the users with links
in it, points to the configured second domainname, domain2?
You need to add a second domain/host in mm_cfg.py
add_virtualhost('domain2.tld', 'domain2.tld')
Then you fix the list by running the Mailman command
bin/withlist -l -r fix_url LISTNAME -u domain2.tld
Also, see the FAQ at http://wiki.list.org/x/lYA9.
--
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] Problems with hostnames
Ruud van den Bercken wrote: I have different hostnames pointing to the server. Lets say, default is domain1. When I create a newlist and login to de admin-interface, I change the hostname to domain2. When the system sends mail to recipients (using postfix), it use only the default domain1 hostname in the links in the message. How could I change this/fix this so message sended to the users with links in it, points to the configured second domainname, domain2? See the reply at http://mail.python.org/pipermail/mailman-users/2010-December/070707.html. -- 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] Interesting problem with gmail users
Paul Tomblin wrote: I suspect it has something to do with the way GMail puts a DKIM-Signature and DomainKey-Signature on outgoing mail. Something Mailman is doing is making the signatures invalid. If your list adds msg_header or msg_footer, that almost certainly breaks the signatures. If your list makes no alterations to the message body or subject or reply-to headers, it shouldn't break the signatures, but certain Python email library transformations over which Mailman has no control may break them anyway. As a matter of fact, doing a Show original on a couple of the flagged messages seems to confirm that, with messages like Authentication-Results: mx.google.com; spf=pass (google.com: domain of geeks-boun...@list.xcski.com designates 69.164.214.240 as permitted sender) smtp.mail=geeks-boun...@list.xcski.com; dkim=neutral (body hash did not verify) header...@gmail.com So what are my options here? Can I strip out the DKIM headers within Mailman? Or should I just configure my mailserver to add a DKIM header? Beginning in Mailman 2.1.7, these signatures were removed. Beginning in Mailman 2.1.10, this removal was made conditional on the new mm_cfg.py setting REMOVE_DKIM_HEADERS which defaults to No. So, assuming your Mailman is 2.1.10 or later, you can configure it to remove the headers by putting REMOVE_DKIM_HEADERS = Yes in mm_cfg.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] htdig integration patches to be updated for 2.1.14?
Chris Toomey wrote: Great, thanks Mark. Will you or someone else be updating the sourceforge patches with these? Would be nice to keep the patches for various mm versions consolidated there. The SourceForge tracker is no longer used for Mailman. The current tracker is at Launchpad. The specific patches are at https://bugs.launchpad.net/mailman/+bug/266553 and https://bugs.launchpad.net/mailman/+bug/266554. I have added a comment to these entries pointing to the later patches at http://www.openinfo.co.uk/mm/index.html and http://www.msapiro.net/mm/. -- 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] Interesting problem with gmail users
On Tue, Dec 7, 2010 at 1:13 PM, Mark Sapiro m...@msapiro.net wrote: REMOVE_DKIM_HEADERS = Yes Well, that worked in the sense that their messages no longer have the DKIM headers and the Authentication-Results header doesn't mention any problems: Authentication-Results: mx.google.com; spf=pass (google.com: domain of geeks-boun...@list.xcski.com designates 69.164.214.240 as permitted sender) smtp.mail=geeks-boun...@list.xcski.com However, those two users are still showing that banner Due to a filter you created, this message was not sent to Spam. Edit Filters. I guess it's just a Google thing now, not a Mailman problem. But if anybody on the list has any insight into that banner and how to get rid of it, I'd like to hear it. -- http://www.linkedin.com/in/paultomblin http://careers.stackoverflow.com/ptomblin -- 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] Interesting problem with gmail users
On Dec 7, 2010, at 1:40 PM, Paul Tomblin wrote: However, those two users are still showing that banner Due to a filter you created, this message was not sent to Spam. Edit Filters. I guess it's just a Google thing now, not a Mailman problem. But if anybody on the list has any insight into that banner and how to get rid of it, I'd like to hear it. Google knows better than you do what kinds of headers they're supposed to see on messages that claims to be coming from senders on Gmail. If you don't have those headers on your e-mail (maybe your mailing list management software removed them), then that would be likely to cause problems. -- Brad Knowles b...@shub-internet.org LinkedIn Profile: http://tinyurl.com/y8kpxu -- 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] Moving administrative information to bottom of digest
Take the digest from this list for example: Send Mailman-Users mailing list submissions to mailman-users@python.org To subscribe or unsubscribe via the World Wide Web, visit http://mail.python.org/mailman/listinfo/mailman-users or, via email, send a message with subject or body 'help' to mailman-users-requ...@python.org You can reach the person managing the list at mailman-users-ow...@python.org When replying, please edit your Subject line so it is more specific than Re: Contents of Mailman-Users digest... Is there a way to configure Mailman so this information is at the bottom of the digest? Thanks. Carl -- 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] Moving administrative information to bottom ofdigest
Carl Shuller wrote: Take the digest from this list for example: Send Mailman-Users mailing list submissions to mailman-users@python.org To subscribe or unsubscribe via the World Wide Web, visit http://mail.python.org/mailman/listinfo/mailman-users or, via email, send a message with subject or body 'help' to mailman-users-requ...@python.org You can reach the person managing the list at mailman-users-ow...@python.org When replying, please edit your Subject line so it is more specific than Re: Contents of Mailman-Users digest... Is there a way to configure Mailman so this information is at the bottom of the digest? Thanks. There are two ways to do this, neither of which is a configuration setting per se. The first way is to modify the code in Mailman/Handlers/ToDigest.py to move the addition of mastheadtxt and the masthead MIME part to the end of the digests. The second way is to make a list/domain/site specific masthead.txt template which is empty (See the FAQ at http://wiki.list.org/x/jYA9). This will remove the masthead from the plain format digest, but leave an empty MIME part in the MIME digest. Then you could add the masthead information to digest_footer. Either of these methods requires access to the server's Mailman file system to either edit the handler or install the template. -- 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] Mailman list sends but doesn't receive mail.
Mark, Thank you for your help and for taking the time to answer my questions. Some questions and answers below next to your responses. On 12/6/10 9:18 AM, Mark Sapiro m...@msapiro.net wrote: On 12/5/2010 10:22 PM, JRC Groups wrote: I am posting the output from sudo postconf -n in a following post to keep it separate from my answers here for clarity's sake. I tried to find the mm_cfg.py file but couldn't locate it. A spotlight search in OS X returned no entries under this name. Even a spotlight search under mailman returned no entries. Where would this file be located ? According to the FAQ at http://wiki.list.org/x/QoA9, it should be /usr/share/mailman/Mailman/mm_cfg.py. If it's not there, I don't know where it might be. I found it. The following are the contents of the /usr/share/mailman/Mailman/mm_cfg.py file I was able to display using the cat command: # -*- python -*- # Copyright (C) 1998,1999,2000,2001,2002 by the Free Software Foundation, Inc. # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. This module contains your site-specific settings. From a brand new distribution it should be copied to mm_cfg.py. If you already have an mm_cfg.py, be careful to add in only the new settings you want. Mailman's installation procedure will never overwrite your mm_cfg.py file. The complete set of distributed defaults, with documentation, are in the file Defaults.py. In mm_cfg.py, override only those you want to change, after the from Defaults import * line (see below). Note that these are just default settings; many can be overridden via the administrator and user interfaces on a per-list or per-user basis. ### # Here's where we get the distributed defaults. from Defaults import * ## # Put YOUR site-specific settings below this line. MTA = 'Postfix' DEFAULT_EMAIL_HOST = 'dentserv.main.private' DEFAULT_URL_HOST = 'dentserv.main.private' Did you create the list with Mailman's bin/newlist, Mailman's web interface or Apple's GUI? I created the list using Apple's GUI and then used Mailman's web interface to configure and change some settings according to the needs of the list I created. I don't know how Apple's GUI creates lists, but if it created entries for the list in /var/mailman/data/aliases it should also create virtual mappings in /var/mailman/data/virtual-mailman and that file should be referenced in Postfix main.cf virtual_alias_maps, e.g. virtual_alias_maps = hash:/etc/postfix/virtual_users, hash:/var/mailman/data/virtual-mailman If virtual-mailman is not created, there is something missing from mm_cfg.py. There should be POSTFIX_STYLE_VIRTUAL_DOMAINS = ['domain.com'] in mm_cfg.py. I've tried Apple but it has become quite clear that they are neither properly equipped nor interested in resolving the problems with Mailman (or with OS X Server for that matter). Can you guide me on how to correct these problems ? Thank you in advance for your help, Joe -- 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
