[Mailman-Users] Mass subscribe blunder
This is more of a list management question than a Mailman question, but I need your collective wisdom I just did a mass Subscribe (288 address) for a list where I had intended to do a mass Invite. The addresses come from a sign up sheet specifically for this list, but the combination of some not very legible addresses along with the potential for typos (I typed them all in) mean that will almost certainly be a handful of addresses subscribed that have no interest in the Wilson Middle School PTA Newsletter (Plano, TX). Obviously this was a situation where an Invite was what was needed. I had just overlooked the radio button for this. I'm hopeful that I will be able to explain and apologize to anyone who complains to me, but I fear that I won't have that opportunity and will get blocked by the likes of AoL right off the bat. Any advice is welcome. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Mass subscribe blunder
On Sep 1, 2009, at 6:48 PM, Mark Sapiro wrote: Adam McGreggor wrote: On Tue, Sep 01, 2009 at 02:51:45PM -0500, Jeffrey Goldberg wrote: I just did a mass Subscribe (288 address) for a list where I had intended to do a mass Invite. If you didn't send a welcome message, a slightly cheeky option is to unsub (without notification), and invite the folks. OTOH, if you did send a welcome, check Mailman's bounce log for bounces and delete those addresses from the list. Thank you! That is extremely obvious once you point it out, but since I've never run a list with unconfirmed addresses before that had completely slipped my mind. As it turns out, 31 out of 288 addresses were bouncing. So the transcription error rate was much worse than I'd anticipated. Cheers, -j -- 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
Re: [Mailman-Users] Question about account ownership, etc.
On Aug 17, 2009, at 12:26 PM, Dana Runkle wrote: If something should happen to the volunteer who runs our email lists and we, the remaining officers, do not have access to the lists, what would Python need from us to prove ownership of said email lists and to transfer administrative control of all our lists to a new person? Mailman has a site administrator password. Ideally, the person who operates things now can just let you know what that password is. With that password, you can do all of the list administration, including creating lists and resetting list passwords. If you cannot get that from the current site administrator, then you (or someone on your behalf) needs to be able to log on (shell access) to the machine running Mailman. In the mailman directory, there will be a subdirectory called bin. Use the command there ./mmsitepass NEW-PASSWORD The user on the host who runs that command-line command will need to have appropriate privileges. If you don't have those, you will need to talk to whoever (hosting company?) runs that machine. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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] Multiple instances of Mailman on FreeBSD
I'm posting this to both the mailman-users list and the freebsd-ports list. I realize that not all follow-up will make it to both lists. I would like to set up multiple instances of Mailman on a FreeBSD 7- STABLE system with using Postfix. Looking at the ports Makefile, it appears that if I set MM_DIR=mailman/vhosts/domain-for-this-instance everything should work file (plus add FORCE_PACKAGE_REGISTER allow this second instance to be installed.) But when I do % cd /usr/ports/mail/mailman % sudo make -DMM_DIR=mailman/vhosts/lists.wilson-pta.org - DFORCE_PKG_REGISTER install It just installs in the default location, /usr/local/mailman And this paradoxical report of various settings $ sudo make MM_DIR=mailman/vhosts/lists.wilson-pta.org - DFORCE_PKG_REGISTER install === Found saved configuration for mailman-2.1.12 You may change the following build options: MM_USERNAME=mailman The username of the Mailman user. MM_USERID=91The user ID of the Mailman user. MM_GROUPNAME=mailmanThe group to which the Mailman user will belong. MM_GROUPID=MM_USERIDThe group ID for the Mailman user. MM_DIR=mailman Mailman will be installed in /usr/local/mailman/vhosts/ lists.wilson-pta.org. CGI_GID=www The group name or id under which your web server executes CGI scripts. IMGDIR=www/iconsIcon images will be installed in /usr/local/www/icons. Notice the conflicting information on the line telling me about MM_DIR. Background on the issue As is well known to mailman users, mailman 2.X does not fully deal with virtual mail domains in that, say pta-bo...@lists.shepard-families.org And pta-bo...@lists.wilson-pta.org would have to be the same list. That is mailman does not provide a separate namespace for lists in different domains. The Wiki/FAQ at http://wiki.list.org/pages/viewpage.action?pageId=4030604 hints at patches (which I can't seem to locate) and mailing list discussion mentions an alternative of having a separate instance of Mailman for each virtual domain. This later approach seems easier if you don't anticipate having loads of domains. So that is what I intend to do. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Multiple instances of Mailman on FreeBSD
On Aug 12, 2009, at 2:12 PM, Brad Knowles wrote: Jeffrey Goldberg wrote: I would like to set up multiple instances of Mailman on a FreeBSD 7- STABLE system with using Postfix. Personally, I wouldn't use the [FreeBSD] ports version if you want to do multiple instances of Mailman. I would install each version from our official source tarballs that you can download from www.list.org and ftp.gnu.org. The FreeBSD Ports version contains a couple of patches which might be useful, though some are merely cosmetic. It also knows how to find the right gid and uid for working with various MTAs. Postfix, as we know, is finicky, and this port really does help people get it right. Otherwise, I would recommend that you find the port maintainer for Mailman, and discuss this subject with them. Already on the cc-line Anyway, what I have found is that if I manually edit the ports/mail/ mailman/Makefile to change #MM_DIR?= mailman MM_DIR?=mailman/vhosts/lists.wilson-pta.org The install works as expected, even though when I specified -DMM_DIR on the command line it worked for some purposes (built files contained the correct string in them) but not for other purposes (the files installed in the wrong place). So I suspect that the install stage must re-read the Makefile. So I do now have this other instance installed. One thing that I (and others doing things this way) will have to take care of is the startup script, /usr/local/etc/rc.d/mailman, for the queue runner. This installation did overwrite the original. So I'm either going to have to manually combine these in one startup script or set up a separate script for each instance. I'm sure that there will be other things to watch out for as well. I hope to contribute to the Wiki on this once I've got everything running. Let me just say that I am eagerly looking forward to Mailman 3. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Multiple instances of Mailman on FreeBSD
On Aug 12, 2009, at 3:21 PM, Paul Schmehl wrote:
--On Wednesday, August 12, 2009 13:55:18 -0500 Jeffrey Goldberg jeff...@goldmark.org
wrote:
I'm posting this to both the mailman-users list and the freebsd-ports
list. I realize that not all follow-up will make it to both lists.
But when I do
% cd /usr/ports/mail/mailman
% sudo make -DMM_DIR=mailman/vhosts/lists.wilson-pta.org -
DFORCE_PKG_REGISTER install
It just installs in the default location, /usr/local/mailman
This could be a really stupid question (because I've never tried to
do what you're doing), but shouldn't the above line be:
$ sudo make MM_DIR=/mailman/vhosts/lists.wilson-pta.org
In other words, don't you have to provide the *absolute* patch to
the install location?
No. Reading the Makefile it is clear that MM_DIR is relative to $PREFIX
The default setting in the Makefile is
MM_DIR?= mailman
And later on there is a
MAILMANDIR= ${PREFIX}/${MM_DIR}
With MAILMANDIR being the absolute install directory.
The problem is, I'm not exactly sure *where* you want mailman to
install, so it's hard to be correct without more information.
Mailman (under normal defaults) installs in various directories under
/usr/local/mailman
The python for all of the CGIs lives in
/usr/local/mailman/Mailman
and the programs that an administrator might run on the command line
live in
/usr/local/mailmain/bin
And there are various other directories for queues and logs and data
and per list configurations and such
I want to have instances installed in
/usr/local/mailman/vhosts/site1
/usr/local/mailman/vhosts/site2
/usr/local/mailman/vhosts/site3
Cheers,
-j
--
Jeffrey Goldberghttp://www.goldmark.org/jeff/
--
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
Re: [Mailman-Users] Multiple instances of Mailman on FreeBSD
On Aug 12, 2009, at 3:38 PM, Mel Flynn wrote: On Wednesday 12 August 2009 11:40:47 Bill Moran wrote: Were it me, I'd add jails to the system. [...] That's obviously not the only way to get what you want, just my suggestion. And mine. Thank you and Bill for the jail suggestion. I've never played with jails, as I really only have one public IP address available. FORCE_PKG_REGISTER abuse will hurt you sooner or later. I am living in fear of that. If you must, then set PKG_DBDIR, PORT_DBDIR and PREFIX correctly. I don't understand the Package and Port databases well enough to actually set them correctly, so I do suspect that I am causing trouble for myself this way. But things get much easier if you use seperate jails and a postfix in mailhub mode on the main IP if you have only one incoming IP. Ah. I hadn't thought of that. I do only have one IP. I hadn't realized that I could set up private addresses on the same host. Would the postfix on the main IP be able to run scripts that are on individual jails? If not, I'd have to set up a listening postfix in each jail which would accept mail forwarded to it only from the main IP. For outgoing mail, mailman can talk SMTP to a remote mail server. Another point of confusion with jails is that the HTTP interface for mailman would need to be on the public IP, but would need to access the appropriate mailman data that live within jails. So I really think that unless I can do full jails, each with their own SMTP and HTTP daemons on their own public IPs, this would be very complicated to maintain. But I am only guessing here as I don't really know what can and can't be done easily with jails. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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] Postfix vdomains with multiple instances of mailman
In trying to get things like pta-bo...@one-domain.example and pta-bo...@second-domain.example to be distinct lists on a site that is hosting both of those domains, I attempted to install multiple instances of Mailman on the same host. That is advice that I saw somewhere on this list. Unfortunately, it is still not working for me. From the web end of things it is actually working fine. Within the virtual domains in the Apache configuration file for each domain, I point to their respective (and distinct) mailman installations. But I am still having problems separating these as far as Postfix is concerned. For one mailman instance, I will have in /usr/local/mailman/vhosts/lists.wilson-pta.org/data/virtual-domains # STANZA START: pta-board # CREATED: Wed Aug 12 17:17:42 2009 pta-bo...@lists.wilson-pta.org pta-board pta-board-ad...@lists.wilson-pta.orgpta-board-admin pta-board-boun...@lists.wilson-pta.org pta-board-bounces pta-board-conf...@lists.wilson-pta.org pta-board-confirm pta-board-j...@lists.wilson-pta.org pta-board-join etc. And in /usr/local/mailman/data/virtual-domain # STANZA START: pta-board # CREATED: Fri Mar 30 14:20:25 2007 pta-bo...@lists.shepard-families.org pta-board pta-board-ad...@lists.shepard-families.orgpta-board-admin pta-board-boun...@lists.shepard-families.org pta-board-bounces pta-board-conf...@lists.shepard-families.org pta-board-confirm pta-board-j...@lists.shepard-families.org pta-board-join etc. The problem is that right hand side of those, something like pta-board-confirm with no domain at all, should sometimes go to the alias defined in /usr/local/mailman/data/aliases which says pta-board-bounces: |/usr/local/mailman/mail/mailman bounces pta-board But at other times, it should get delivered to the alias specified in /usr/local/mailman/vhosts/lists.wilson-pta.org/data/aliases which says pta-board-confirm: |/usr/local/mailman/vhosts/lists.wilson- pta.org/mail/mailman confirm pta-board Anyway, in my set up, it's always going to the first one first (which is listed earlier in postfix/main.cf) Both these aliases files and both virtual-domains files are generated by Mailman. So I don't see where I have scope to fix things. I would like to know how people who have run multiple instances of mailman have managed to keep lists in different namespaces. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Detecting Autoresponders
On Jun 28, 2009, at 5:34 PM, Karl Zander wrote: This particular autoresponder is not known to be broken. It's a bit dated, but I have a rant about broken autoresponder here: http://goldmark.org/netrants/auto-resp/ As others have said, if an autoresponder is responding repeatedly to the same address in the course of a few days it is certainly behaving badly. Lotus Notes and Exchange autoresponders should not be allowed near the Internet. I remove people from lists, sending a note to them and their postmaster saying that as long as they use broken autoresponders they should not join any Internet email discussion lists. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Can I enforce secure admin passwords?
On Jun 3, 2009, at 4:33 PM, Kirke Johnson wrote: What is bothering me is list owners who want to use their initials or the list name as list owner passwords. I feel like kind of a sitting duck when we can't see the passwords they have chosen and have no way to enforce decent choices. This isn't a mailman problem as you well know. And I don't think that the solution is to have mailman test for weak passwords. The real, long term solution is to encourage people to use good password management systems. The best password management system I've seen is sadly OS X only: 1Password. But there are also the password management systems built into web browsers, which are better than nothing. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] my mailman has been hacked !!
On May 27, 2009, at 1:23 PM, Khalil Abbas wrote: all members are moderated, except my own email address (m...@email.com) which I use to post to the list .. someone sent from my address the 'From' name is not me, Please clarify. Did the From line contain your email address (m...@email.com ) or not? You seem to be saying two different things. If, as I suspect, someone is merely forging your address to post to the list, there are two things that you can do (I would recommend that you do (1) as an immediate and temporary measure, until you can get (2) in place). (1) Moderate even your own postings, so that your list moderator password is required to post, even if from your own address. (2) Improve the spam/virus filtering on your mailserver. A forged message from an open relay containing a virus should have been stopped by your mail system long before it reached mailman. Cheers, -j -- 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
Re: [Mailman-Users] Question about the Group mismatch error when updating mailman service
On May 26, 2009, at 7:12 AM, Sean wrote: Currently, I had updated my mailman server to a new machine. (mailman-2.1.5_2 - mailman-2.1.9_5) My server is FreeBSD 7.0, Postfix + mailman 2.1.9_5 Now I create a new list by bin/newlist, but it got a error when I send mail to this new list which is /usr/local/mailman/mail/mailman post eos. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group nobody, but the system's mail server executed the mail script as group mailman. Try tweaking the mail server to run the script as group nobody, or re-run configure, providing the command line option `--with-mail-gid=mailman'. So I reinstall mailman server with --with-mail-gid=mailman setting. Then the new list can work correctly. Since you appear to be building mailman from ports/mail/mailman, do a cd /usr/ports/mail/mailman make config And then set the MTA option to POSTFIX, Then just make install or use portupgrade or your favorite ports management tool. Setting the POSTFIX option for building the port will build mailman correctly to run with the correct owner and group settings needed for postfix FreeBSD. But the other question happened. Group mismatch error happeded on the old lists which is /usr/local/mailman/mail/mailman post xip. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group mailman, but the system's mail server executed the mail script as group nobody. Try tweaking the mail server to run the script as group mailman, or re-run configure, providing the command line option `--with-mail-gid=nobody' After you have reinstalled mailman with all the proper group and ownerships (the port Makefile really does do it correctly), then in cd /usr/local/mailman/bin ./check_perms ./check_perms -f Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Unmoderated list member recieving msgs, but unable to post to the list
On May 21, 2009, at 10:50 PM, Stephen J. Turnbull wrote: Mark Sapiro writes: There is nothing left of his message after content filtering. Which at a guess means he was posting in HTML only, and your list is set to filter HTML. If that is the case, it is strongly recommended that you teach your member to set his mail client to post in plain text (with or without HTML). Depending on what is meant by nothing, I've seen something like this happen another way. Some clients will create a multipart/alternative message with a text/plain alternate and a text/html alternate. But these clients will just put a note in the text/plain part that says roughly, read the HTML part. So with normal stripping of the text/html alternative all that comes through is a text/plain message that says read the other part. This naturally confuses list members, although I consider mailman's behavior absolutely correct. The originating client is lying when it claims that it's produced a multipart/alternative message. And naturally I concur with what I've snipped of your message, encouraging people to send only text/plain email. Anyway, the OP should have the user cc the list administrator with their next posting attempt. That way, you can examine the structure of the message that got submitted. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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] Removing from retry queue
I have a couple of messages in my retry queue that will never go any where. I've been waiting for mailman to give up on them, but it's been several days now, and like to avoid the clutter in my SMTP logs. How long will mailman keep trying in the face of a 450 from the local SMTP server? And where is that length set. Also to dequeue these do I just remove the .pck files from qfiles/ retry ? Or is there a better way to remove them. I tried bin/discard but I complained that the messages weren't listed as suspended. The messages are confirmation requests to email addresses with bogus domains. My postfix installation is configured to give a temporary failure (450) to mail to address that don't resolve. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] mailman passwords
On May 9, 2009, at 4:51 PM, Bernd Petrovitsch wrote: - Depending on the security situation of your laptop/desktop/..., most browsers allow you to let them remember the password for you. So you have to really enter it only the first time. Everyone who is concerned about security should be very strongly encouraging users to use good password management systems. If a user doesn't switch between browsers and clients than the password management systems in most browsers is good enough. For other users, other solutions are needed. On the Mac, I'm a very big fan of 1password which works as a plug-in for several browsers, is set up for smart syncing of your keychain across systems and has a number of other very well thought out design elements. I've not really looked at password management systems for other platforms, but I'm sure that there must be some good ones out there. Bringing this back to discussion of mailman, mailman helps illustrate exactly why a good password management system is needed. Mailman passwords are low value, low security. That is, there really isn't too much damage that can be done with a password compromise (thus low value). Also they get sent around in unencrypted email and typically are used on unencrypted HTTP connections. Thus they are relatively easy to get at. But more most users they are very infrequently used. Thus, they are extremely unlikely to be remembered unless stored on the users system (reminder emails). But because they are unlikely to be remembered, if users do set them, then it is very likely that users will use a password scheme that is predictable. That is they will either use the same password that they use on more high value systems, or they will use a variant of such a password. That is, they might use mm-sekret for mailman and ba-sekret for their Bank of America account. But mailman systems shouldn't be asked to treat your password as your banking password, but only as your mailman password. A good password management system means that your individual passwords are not things that any human needs to remember. This frees them up to be both strong individually and independent of each other, so that the compromise of one of your passwords doesn't expose any of your others. In my instructions to users, I added some explanation about these low security passwords http://lists.shepard-families.org/#sec-passwd -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Mailman
On May 1, 2009, at 2:37 PM, Mike Hughes wrote: I have a mailing list that has been running under Mailman. Another fellow has been hosting the mailing list for me. I would like to begin doing so myself. I have a computer available for the task. What Linux version will work best? Use whatever version of Linux (or other Unix) you are most comfortable administering. Because it will be an Internet facing server, you (or someone) will have to keep up with security updates. Note that you can run Mailman on OS X, which you appear to have some familiarity with. Any modern Unix-like system will do, but choose something that you will be able to maintain. What will I need to do to set up mailman? You personally or someone else working with you will need to understand mail transport and what it means to be running a machine that receives and sends mail to the Internet. With apologies for sounding patronizing, but the fact that you asked the question above makes me doubt that you currently have that understanding. But that's okay as long as you are willing to learn. But there is much more to learn than just installing and configuring a couple of software packages. Getting your DNS records configured so that your mailserver doesn't look like a source of spam takes work and thought. This stuff is great fun to learn, but have someone close at hand who you can consult with and who can look over your shoulder and offer advice. If your question was what other packages does mailman depend on, that information is in the installation guide. But basically you will need Apache (other webservers will work, but all of the examples that you'll see for things use Apache), python, an MTA, (I use postfix; I like exim a whole lot, and sendmail remains very popular). cron (or on OS X, launchd.). You will probably want to have spam filtering as well, SpamAssassin is a popular choice. If you want to add virus checking of mail, then something like clamav is a good choice. Your server will need A static public IP address. Proper DNS PTR and A records (getting the proper PTR records can be a frustrating experience). DNS MX record Best wishes, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] How to remove a damaged email address from amailing list
On Apr 28, 2009, at 4:44 PM, Mark Sapiro wrote: When I checked my mailing list member email addresses, I came across an email account which contains a colon (:), which shouldn't be there of course. See the FAQ at http://wiki.list.org/x/UIA9. Shouldn't mailman check for 822 conformance? Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Sending bulk mail (400,000 users)
On Apr 17, 2009, at 11:45 PM, Phoenix Kiula wrote: I went into the mailman in cpanel [...] As others have pointed out, 400K addresses with full personalization is a big job that may well require some MTA tuning. And a hosting service using cpanel is unlikely to be one that provides you with what you need. And it is also likely that some of the mailman tuning you need to do won't be available through cpanel. The absolute first (well actually, second) thing you should do is talk to your hosting provider to see what they say about you sending to a list of 400K address with personalization. Only after they say that they are okay with that, should you be asking about the mechanics of actually doing this. And of course, the first thing that you need to do is make sure that you have evidence that each and every email address on that list is read by someone who how wants to be on that list. That is, do you have a positive response to a confirmation request that was sent to each address? Many of your earlier questions about proper SPF records and so on will depend on how your provider has set up mailman under cpanel. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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] Webbugs
This is kind of off-topic in that it is not specific to mailman based lists, but I am wondering whether any mailman site managers have developed something that might meet my needs. The short version of the question is that I would like to have one list that sends HTML messages that include images which are not the mail itself, and where the URL for at least one of these remotely hosted images is personalized for the specific recipient. OK. Now the background. I have recently been co-opted by a local community/non-profit to help with their web work. I also have a mailman installation that I use for other things and other groups. This particular group, however, has been using Constant Contact for their occasional newsletter. They are just using the free service which is very limited (no archiving, no user subscription page, etc). But it does offer two things that I don't really know how to do. One is having templates that make it easy for a very unskilled person to create an attractive and rich email to be sent out. The other is tracking via webbugs. I don't know whether the Constant Contact system for creating such messages is a server side thing or client side. Any client side portion (if there is to be one) would need to run on Windows. So does anyone know of any tools, preferably open source, that would help me set up a list that would add those two properties? I'm running on a FreeBSD system with all the usual suspects (Apache, perl, PHP, mailman (of course), ...). Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Linux Preferred?
On Jan 28, 2009, at 1:13 AM, Brad Knowles wrote: On another site I help administer, FreeBSD works just fine. But again, I run the version from our source and not the ports version. I have found that using the FreeBSD ports system installation of Mailman is just fine. When I first started there was a minor problem with postfix integration, but I sent of a note to the package maintainer and the problem was fixed very quickly. Anyway, the maintainer of the FreeBSD port for mailman is very good. It's been a while since I administered mailman on Redhat and SuSE. But I recall that in those cases I didn't use rpms, but just installed from the original source. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] monthly password reminders
On Sep 1, 2008, at 6:42 PM, [EMAIL PROTECTED] wrote: IT Security is a little antsy about having these passwords floating around through the email system (don't ask). Would they be willing to accept these passwords being mailed around if you were to disable individuals' ability to set their own password? That is, if the only passwords that mailman ever mailed were the mailman generated ones, would they be happier with those? And is there a way to prevent people from using their own passwords? Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Preventing accidental resubscription
On Aug 24, 2008, at 1:45 AM, Darrell Burkey wrote: I've had a client ask me how they can keep track of who unsubscribes from their lists so that they don't accidentally resubscribe the same address at some later point. If they are properly confirming subscriptions, then there really shouldn't be any accidental re-subscriptions. So this makes me suspicious about what your clients are up to. Unless anyone has any better advice I'm consider writinging a hack to copy unsubscribe addresses to a file that can be checked before subscribing someone. When someone unsubscribes from a list, they may not want you to keep their email address at all. I would recommend that you keep a hash of each unsubscribed email address instead of the email address itself. Of course that won't catch matches between, say, [EMAIL PROTECTED] and [EMAIL PROTECTED] Those may or may not be the same address. You can safely lowercase the domain part of the email address, but I'm not sure what to do when creating the hash for addresses with uppercase in the local-part. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Filtering SPAM/ Out of Office
On Aug 8, 2008, at 10:01 AM, Webmaster PF wrote: 1. How to filter out “Out of Office” replies to the list. I have found that putting the first few users who use broken autoresponders into a pillory has some deterrent effect, but memories need to be refreshed occasionally. If for piddling legal or other constraints such as not finding a pillory in working order prevent you from using that approach, I tend to set no mail for those uses, and if there is reason to believe that it is a site wide problem, I may bar users from that site, or at least threaten to, always informing the postmaster of the site with the broken autoresponders. I also direct people to my out-of-date rant on the subject. http://www.goldmark.org/netrants/auto-resp/ -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Need some lists
On Jul 25, 2008, at 3:21 PM, LindsayClinard wrote: Hi, I would like to request several listservs. Below are the names of the lists we need created. Instead of sending them piecemeal we decided to wait until we knew we had a good amount to send. All the below will have uufwilmington.org after each one. I think that you have sent your request to the wrong place. The mailman-users@python.org mailing list that you sent this to is a discussion list about the mailman (mailing list management) software. Most of the (hundreds?) of members of this list manage their own sites running mailman. Normally, you would install the mailman system on one of your servers and then you could use it to set up your mailing lists. The UU Church in Plano, Texas uses mailman and the people who run that would probably be able to advise you. I don't happen to know them (I was on one of the lists for a short time). So you might mail to [EMAIL PROTECTED] to ask to be in touch with the people who set up the mailing lists. Best wishes, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] virtual domain
[mailed and posted] On Jun 27, 2008, at 5:27 AM, Dony Tata wrote: i have sucsess create new mailing list [EMAIL PROTECTED] i have sucsess subscribe member,but if a member send mail to [EMAIL PROTECTED] , i have got error [EMAIL PROTECTED]Host or domain name not found. Name service error for name=doma.ac.id type=A: Host not found This sounds like the problem is not with the mailman configuration at all, but that DNS is not set up properly for doma.ac.id to receive mail. Can mail be sent to non-list addresses at doma.ac.id? Cheers, -j -- 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
Re: [Mailman-Users] virtual domain
On Jun 27, 2008, at 9:25 AM, Dony Tata wrote: I don't include doma.ac.id in DNS, must i include doma.ac.id in DNS? doma.ac.id is virtual domain in server xxx.mod..ac.id. If you want to people or other machines to be able to mail to @doma.ac.id, then there will need to be an MX record in DNS for doma.ac.id. The MX record can point to your server. I strongly recommend that work with someone at your university who is familiar with SMTP and DNS. You need to have some understanding of each to set up mailman and virtual domains. Cheers, -j -- 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
Re: [Mailman-Users] Trouble setting up Mailman 2.1.9 Web Interface (FreeBSD 7.0 Ports)
[mailed and posted] On Jun 3, 2008, at 11:47 AM, Mark Hennessy wrote: I'm trying to get Mailman 2.1.9 working. I'm running mailman on FreeBSD 7-RELENG installed through ports, also with postscript. I set it up with Postfix and as far as I can tell, e-mail and aliases are working and I'm able to create lists using the command- line scripts in mailman/bin, but whenever I try to control things through the Mailman web interface it seems to be ignored. The ports install process does not configure your apache configuration file. You still need to do that by hand. Did you follow the instructions in /usr/local/share/doc/mailman/FreeBSD-post-install-notes ? I looked in the log files that live in /usr/local/mailman/logs and in the web server logs and mail server logs and find nothing of consequence to explain this issue. I am able to go to the configuration web pages, log in with the passwords that I set at the command line, change form fields and submit the form. When I submit the form, I get prompted twice via what appaer to be javascript popups regarding the data submission being non-secure (even though this is an https URL) and then get returned to the form page. As already pointed out. Mailman pages don't use JavaScript. Are you certain that you are really seeing the mailman pages? Or maybe this is coming from the browser? What browser are you using? -j -- 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
Re: [Mailman-Users] sharing administrator passwords
On May 26, 2008, at 1:59 AM, Laura Creighton wrote: So what people _want_ is a way to log in with a password and then have mailman recognise them and make it possible for them to administer all the lists they run. I agree. And I look forward to something like this in Mailman 3, but for the time being I am going to preach: Rant Every system administrator or knowledgeable person should be trying to persuade people to use good password management systems so that they don't have to remember most passwords. For Windows, I recommend Password Safe and for OS X, I recommend 1Password. Users of other systems are probably already using password management systems. pwsafe will maintain compatible databases with Password Safe. So, I would take the current poor situation with mailman's failure to distinguish between authorization and authentication as an opportunity to educate people about password management systems. /Rant Cheers, -j -- 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
Re: [Mailman-Users] Hint: mmdsr.sh and Mac OS X Leopard
On Jan 6, 2008, at 5:56 PM, Brad Knowles wrote: On 1/6/08, Jeffrey Goldberg wrote: Isn't this the kind of thing that can be dealt with in the configure script? For mmdsr, there is no configure script. [...] This is an officially unsupported tool that is provided in a totally separate subdirectory, OK. Thanks for the explanation. Makes sense. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] bots subscribing to lists via web forms to avoidmember-only restrictions
On Jan 6, 2008, at 7:01 PM, Stephen J. Turnbull wrote: Jeffrey Goldberg writes: [...] it is worth considering captchas. Captchas have been discussed, and were not considered worthwhile. [snip of explanation of the lack of effectiveness and annoyance of capchas] Thank you. I've always disliked the things. Now I know that there is actually good reason to. I suspect that with a Confirm subscription policy (which is the minimum anyone should run) there really isn't too much to worry about in that we can always end up requiring approval for subscriptions (or moderate) associated with domains that show a history of allowing spammers to send subscription requests. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
[Mailman-Users] Message templates not available to list-admins
Hello, One of my list admins (whom I've copied on this message) wanted to know what the default invitation message before sending out an invite. It appears that this information is only available to those who have shell access to the mailman server. (I found it quickly in templates/invite.txt). I suppose that she could have sent a test invitation to herself to an address that wasn't already a list member, but that's hardly the first thing that's going to jump into people's minds. One of the great things about mailman is that it separates out various administrative functions. But in this case, the separation isn't in the right place. Those templates, either directly or in documentation, should be available to list-admins who don't have site admin nor shell access. This isn't a big issue, and I could always simply make the templates directory readable through Apache, but it might be something for the team working on version 3 to consider. Cheers, -j -- 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
Re: [Mailman-Users] Comcast, Yahoo, Hotmail blocking us
On Sep 1, 2007, at 1:09 PM, Mark Sapiro wrote: I suppose that's possible, but before going down that road, I would make sure that the domain that the server identifies itself as in SMTP HELO or EHLO is the same domain returned by an rDNS lookup of its IP address. Let me add to this. I fully agree that there are DNS related things that can and should be done to make a legitimate mailing list system less likely to be blacklisted. I run a mailing list server at 72.64.118.118. Before I set that up I had to have the rDNS (aka PTR record) for that IP changed from static-72-64-118-118.dllstx.fios.verizon.net. to n118.ewd.goldmark.org. Doing this was the hardest part of the job because it took two painful hours on the phone with Verizon Business Internet support. However painful that was, it really was necessary. I would not have set up a mailing list server until I had that sorted out. I also have SPF records for all of the domains that might appear in HELO or MAIL FROM addresses for anything coming off of my net. Having a proper rDNS and SPF records to match should demonstrate to most reasonable systems that the mail from my IP really is under my (fully traceable) control. Of course I have postmaster and abuse addresses working for all of the domains that mail may come from. Still, with all of this, I got blocked by 1and1.com as being a dynamic address (which of course I'm not). What was also annoying was that 1and1.com rejected the mail with a 4xx, so the mail just sat in my outgoing queue, retrying every now and then until I removed the messages from the queue. It took several attempts to contact 1and1.com support (they don't publish a telephone number for non-customers) before this finally got fixed. But other than that, I've had no problems with comcast, yahoo or hotmail and only minimal problems with AOL. AOL has a document on the web someplace about what they want from mailing list providers. Most of their requirements are pretty much what people should be doing anyway. This is a long winded way of saying that before looking at exotic solutions like throttling, there are other steps you should be taking anyway that may resolve the problems. -j -- 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
Re: [Mailman-Users] problems with new web host and too many complaints
On Aug 30, 2007, at 9:24 PM, Jonathan Dill wrote: I have a customer who has a fairly large opt-in only mailman mailing list (~40,000 subscribers) that they use to send out a weekly newsletter, How was the opt-in done? Was it done with Mailman's confirmation process, or would it have been possible for person A to accidently or maliciously get person B on the list? If the latter, I would consider the list mailing unacceptable. people seem to primarily subscribe for the weekly contest for free tickets to events. Unsubscribe links are conspicuous, and people who otherwise complain are unsubscribed from the list. A great deal of spam contains fake unsubscribe information. Indeed following the unsubscribe information in spam often gets you opted in to more lists because you have proved (1) that a human actually reads the mail sent to that address, and (2) that the human who does read that mail is gullible. Recently, they moved their web hosting to a new service, and the new service shut down their website because they had received too many complaints about the newsletter, which mentions the website address. Obviously there are too many members of the list who do not believe that they opted in to it. Why might that be? I would have thought it would be easier to follow the unsubscribe link than track down the hosting company for the website, which makes me wonder if these complaints are being generated by some kind of antispam software. You sound like someone defending opt-out mass mailing. I've described above why people (correctly) avoid the opt-out instructions in what the think might be spam. The host forwarded a sample but stripped out some of the message headers, so all I can tell is that it really was in response to the newsletter. This is normal practice to prevent the list managers from merely engaging in list washing (removing the complainers while continuing to send the spam to many people who never really wanted it but don't bother to complain. Now the web host is talking about requiring that all of the subscribers be required to opt in again or be unsubscribed from the list--to be honest, that might not be a bad idea, but the customer wants to avoid this. That is a good idea. This is really the only way your customer can continue with the mass mailing. There may have been things that your customer might have done earlier to prevent this state of affairs, but at this point, what the hosting providers are suggesting is the only way forward, unless your customer can document how each address came to be added to the list with some evidence that the person who reads mail at that addresses confirmed the process. Has anyone else run into a situation like this and have some practical advice? I certainly have experience from the other end. A few years ago some unknown person signed me up to scores of lists that didn't do proper confirmation. Apparently, this bit of abuse is known as list bombing. They have been asking me about technical ways to circumvent the problem, but that sounds like a really bad idea to me for several reasons, Your customer will either have to (1) do what the hosting company says (and that can be done with mailman) or (2) prove that each address was added by the person behind that address or (3) close up shop or (4) find a spammer friendly hosting service. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Mailman post being blocked / filtered
On Aug 30, 2007, at 12:42 PM, Fitzpatrick, Ted wrote: How can I ensure that their spam filters aren't blocking mailman messages? It really depends on why the mail filters are blocking the mail. Do you see anything in your MTA logs that is useful? You can improve your chances by doing things like making sure that all of the DNS checks that spam filters might run against your mail server succeed. Having an SPF record for your mailserver might help. But these are general sorts of answers. Without details of who's blocking and why such vague help is the best anyone can offer. -j -- 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
Re: [Mailman-Users] Disabling confirmtionless subscriptions by listadmins
On Aug 22, 2007, at 10:03 PM, Mark Sapiro wrote: Jeffrey Goldberg wrote: And, the heart of my question, can I disable those [ways a list admin could add addresses without confirmation]? Of course, you can do anything if you're willing to hack the code, but short of that, all you can do is eliminate the entire Membership Management... section including the Membership List from the admin interface. I don't want to do that. I do want the list admin to be able send out invites, for example. I think I will just have to either leave things as they are or modify the code. Probably the easiest modification would simply be to remove the subscribe option from the mass subscription page. Of course someone could work around that by sending a properly crafted HTTP POST, but those aren't the sorts of list-admins I'm worried about. -j -- 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
[Mailman-Users] Disabling confirmtionless subscriptions by list admins
Hello, I'm a site administrator running mailman 2.1.9 and am beginning to delegate some responsibility to list administrators. While I trust (the integrity of) these people, I am not fully confident that they completely grasp the importance of the confirmation process (particularly since some list members seem to have trouble with it). I do not want any of these list administrators to subscribe anyone (or change email addresses of members) without the member having to go through the confirmation process. To my knowledge, the one place that a list administrator could by- pass the confirmation process for members is on the mass subscription page. Are there other locations as well? And, the heart of my question, can I disable those? Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
[Mailman-Users] Outlook user's reply went to -bounce address
I have a member of a list who attempted to reply to a posting to one of my lists and her reply went to the -bounces address instead of to the address in the From field of the message that she should have received. Here is a header fragment of what see sent. To: [EMAIL PROTECTED] Message-id: [EMAIL PROTECTED] MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600. X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Content-type: multipart/alternative; boundary==_NextPart_000_0006_01C7E1E8.D4BDA890 Thread-index: AcfiEr1Ir6dhRiUeQQ+HOAlSF6YEwg== She doesn't know what she did. In fact she has asked me what she did wrong. The list is a perfectly ordinary list with no reply-to manipulation or the like. And the message that she replied to others have successfully replied to without problem. I really don't think that she's behind some stupid gateway that is mangling incoming mail. She has a perfectly normal verizon.net address. Does anyone know how an Outhouse user could have managed to reply to the -bounces address? It strikes me that that would take a special effort. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Mailman roadmap
On Jul 7, 2007, at 3:23 PM, Krystal F. Zipfel wrote: Currently, Mailman looks at the list-name as strictly list-name, instead of [EMAIL PROTECTED]. This is by far and away my biggest feature request as well. Each virtual domain should be its own private name space for list names. I also think that the other grander suggestions are good. It is important to get those things sorted out well. But my most immediate concern is avoiding list name collisions across (pseudo) virtual domains. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Mail from GioMBG hack this into /etc/httpd/modsecurity.d/modsecurity_crs_30_http_policy.conf to alowed mod_security + mailman into fedora 7 moonshine with mod_security
On Jun 26, 2007, at 7:26 PM, Gio MBG Canepa root wrote: MANY Thanks Jeffrey! SINCERLY! I have resolved with this hack into my: /etc/httpd/modsecurity.d/modsecurity_crs_30_http_policy.conf Simply I have commented: SecRule REQUEST_BASENAME as # SecRule REQUEST_BASENAME I think that is the minor hack to prevent this kind of apache +mod_security+mailman error and to alowed the .shtml file extension in my html... YES You have just resolved not one but the 2 unique most bad problem into my newest monshine (fedora7)! MANY THANKs! Thank you. I think that the lesson here is that any time you get an error from the webs erver, look at the error logs. Once you posted the logs as Mark requested, the answer to the problem was clear. But prior to seeing the log entry, nobody could have help. I'm pleased things are now working. Cheers, -j -- 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
Re: [Mailman-Users] mail from GioMBG fresh installation of mailman but Internal Server Error (only on edit some users) remain!
[mailed and posted]
On Jun 26, 2007, at 10:10 AM, Gio MBG Canepa root wrote:
Hi Mark!
---| Here the apache error Log: |---
[Tue Jun 26 17:03:00 2007] [error] [client 127.0.0.1] ModSecurity:
Access
denied with code 500 (phase 1). Pattern match .(?:c(?:o(?:nf
(?:ig)?|m)|
s(?:proj|r)?|dx|er|fg|md)|p(?:rinter|ass|db|ol|wd)|v(?:b(?:proj|s)?|
sdisco)|
a(?:s(?:ax?|cx)|xd)|s(?:html?|ql|tm|ys)|d(?:bf?|at|ll|os)|i(?:d
[acq]|n[ci])|
ba(?:[kt]|ckup)|res(?:ources|x)|l(?:icx|nk|og)|w{,5}~|webinfo|ht
[rw]|
xs ... at REQUEST_BASENAME. [id 960035] [msg URL file extension is
restricted by policy] [severity CRITICAL] [hostname home.
9records.com]
[uri /mailman/options/mailman/alexkenji--at--alexkenji.com]
That answers the question. Your apache add-on of mod_security is not
allowing access to any URI ending with .com.
You may wish to disable mod_security for the mailman directory. I
don't know how to do that, having never used mod_security (which
isn't part of the normal apache distribution).
Looking at the documentation at
http://www.modsecurity.org/documentation/modsecurity-apache/2.1.0/
html-multipage/03-configuration-directives.html
it looks like setting
SecRuleEngine off
within the appropriate Location or VirtualHost of your apache
configuration should solve the problem.
But keep in mind that this is the first time I've ever looked at
mod_security, so don't put a great deal of trust in my suggestion.
-j
--
Jeffrey Goldberghttp://www.goldmark.org/jeff/
--
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
Re: [Mailman-Users] Temporarily Diable Entire List
On May 7, 2007, at 10:44 AM, Robin Bartholomew wrote: I want to make sure some lists are definitely not used before deleting them. To temporarily disable a list, is moving the list directory (/home/mailman/lists/list_name) to a temporary directory an acceptable solution or is there a better way to go about this? I would just change the alias for the list to go to some auto- responder or to the list owner. So instead of having something like listname: |/usr/local/mailman/mail/mailman post listname just have it be something like listname: |/path/to/some/autoresponder or listname: owner-listname You can do similar things with the request-listname address. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] postfix/mailman
On Apr 29, 2007, at 2:27 PM, Teck wrote: i have been trying to figure this out for the last day and a half google is not my friend !:( config suse 10.0 postfix spanassassin amavisd clamd freshclam all running mailman DID work. im not sure just yet when it quit. anyone of the members can send to it and mailman does its thing and mail gets delivered to any members of MY domain. it will not send to outside domains in the mail log all i get it connection timed out and the mail returned to postfix deferred. everytime i try to flush it same result. Can you post an excerpt from your postfix logs? -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Placing a copyright notice in list messages.
On Apr 27, 2007, at 1:37 PM, Brandon Sussman wrote: Can a copyright notice containing the sender's name be automatically placed in regular mailman list messages? As others have pointed out, it would probably be a mistake to do that unless you can be absolutely certain that all of those who post to the list want such a copyright statement. There will be cases where it won't be appropriate. I suspect that your intention as a list manager isn't so much as to assert copyright, but to disclaim responsibility. For this you could just add text to the footer saying that the responsibility for the content of a posting belongs to the poster. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Mailman gid problem
On Apr 20, 2007, at 10:41 AM, David Southwell wrote: ___ Extract from /var/maillog Apr 20 08:24:58 dns1 Mailman mail-wrapper: Group mismatch error. Mailman expected the mail wrapper script to be executed as group nobody, but the system's mail server executed the mail script as group mailman. Try tweaking the mail server to run the script as group nobody, or re- run configure, providing the command line option `--with-mail- gid=mailman'. This is the third and final time I'll ask you give a long directory listing of your mailman/data directory. (Twice here and once on the FreeBSD list). That information is needed to diagnose and fix the problem. In all likelihood, the problem will be fixed by a simple chown command. But the reason that I ask for information is because it is useful in getting the problem sorted out. If you have some privacy concerns or something that is making you reluctant to provide the information I asked for please say so. Or if you don't understand the questions, please say so. Asking for help, getting requests for more information, ignoring those requests, and than asking for more help on things that could have most likely been solved if you'd provided the requested information can get annoying. I recently set up mailman on a system extremely similar to yours (FreeBSD 6.*, postfix). And I've been a long time user of mailman (although with sendmail and exim). I really am in a good position to help, but I might have to leave it to people with more patience. Please see my previous post http://www.mail-archive.com/mailman-users%40python.org/msg44296.html where I ask for this information and ask a series of yes or no questions. I have tried to rebuild mailman BUT the configuration option screen does not appear. I have tried # make with-mail-gid=mailman but still get the same results #./configure --with-mail-gid=mailman is not available If you wish to override this when doing the build from BSD ports then you would use make -DMAIL_GID=mailman reinstall However, I STRONGLY advise against that. It is best to keep things as close to the default settings as possible. I do think that these problems are better served by doing the appropriate chown on the mailman/data directory instead of tinkering with the build which would probably lead to harder to diagnose problems. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Mailman GID problem
On Apr 20, 2007, at 10:42 AM, David Southwell wrote: Extract from /var/maillog Apr 20 08:24:58 dns1 Mailman mail-wrapper: Group mismatch error. Mailman expected the mail wrapper script to be executed as group nobody, but the system's mail server executed the mail script as group mailman. Try tweaking the mail server to run the script as group nobody, or re- run configure, providing the command line option `--with-mail- gid=mailman'. I've given a complementary response on the mailman-users list (to which I'm also cc'ing this) Nothing I say below takes away from what I said in that previous post. The answers to the questions I've asked would have resolved this problem long ago. There appears to be a bug in the pkg-install file that comes with the current mailman port. When one installs (through FreeBSD ports) mailman selecting postfix as the MTA, the MAIL_GID correctly gets set to nobody But in the pkg-install script all of the mailman files get set with echo --- Creating Mailman directory (/usr/local/mailman) (umask 002 /bin/mkdir -p /usr/local/mailman) || exit 1 /usr/sbin/chown -R mailman:mailman /usr/local/mailman || exit 1 /bin/chmod g+s /usr/local/mailman || exit 1 Which is correct for everything except for /usr/local/mailman/data which should actually be set with chown -R nobody:mailman /usr/local/mailman/data I don't know enough about ports to actually find the source pkg- install fine (the one I looked at and quoted from is after make has edited it with sed). So I'm not certain whether the problem is in the Makefile or in the source for the pkg-install. I experienced the same problem David had just a few weeks ago, but I attributed the problem (which I fixed by manually doing the chown) to me having moved my mailman set up from one machine to another. So I thought that I had the wrong permissions for /usr/local/mailman/data as a consequence of the move and not because the mailman FreeBSD port was broken. When I saw some of David's problems I started to have some suspicions, but I wasn't able to get enough information from him to really look at the ownerships the port set up. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Mailman gid problem
[I'm adding [EMAIL PROTECTED] to the cc in the hopes of making it easier for everyone following this discussion to follow it.] On Apr 20, 2007, at 1:38 PM, David Southwell wrote: I'm sorry -- I did in fact try to send it but mailman trashed my mail system and I lost the thread. OK, thanks. Here it is -rw-r- 1 root mailman 41 Apr 16 07:51 adm.pw -rw-rw 1 root mailman 4364 Apr 20 06:39 aliases -rw-rw 1 mailman mailman 16384 Apr 20 06:39 aliases.db -rw-r- 1 root mailman 41 Apr 16 07:52 creator.pw -rw-r--r-- 1 root mailman 10 Apr 20 07:11 last_mailman_version -rw-rw 1 mailman mailman 5 Apr 20 02:49 master-qrunner.pid -rw-r--r-- 1 root mailman 14114 Apr 20 07:11 sitelist.cfg -rw-rw-r-- 1 mailman mailman 0 Apr 17 09:52 virtual-aliases -rw-rw 1 www mailman 2275 Apr 20 06:39 virtual-mailman -rw-rw-r-- 1 mailman mailman 16384 Apr 20 06:39 virtual-mailman.db OK, the aliases files need to be owned by nobody so chown nobody aliases* virtual-aliases* virtual-mailman* will fix that. When new files are added, we want them to be owned by nobody so also do a chown nobody /usr/local/mailman/data Those chown's will have to be done as root. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Mailman GID problem
On Apr 20, 2007, at 1:44 PM, David Southwell wrote: On Friday 20 April 2007 09:38:03 Jeffrey Goldberg wrote: chown -R nobody:mailman /usr/local/mailman/data Here is what happens if I do that command: [EMAIL PROTECTED] /usr/local/mailman]# bin/check_perms /usr/local/mailman/data/aliases.db owned by nobody (must be owned by mailman /usr/local/mailman/data/virtual-mailman.db owned by nobody (must be owned by mailman Problems found: 2 Re-run as mailman (or root) with -f flag to fix [EMAIL PROTECTED] /usr/local/mailman]# Hmmm. Now that I check, I get the same warning. However, my system does work with owners and permissions like this Still, I guess this isn't a proper solution to the problem since the next time we run bin/check_perms -f we will actually break things on our systems. Maybe the correct solution is use owner mailman and MAIL_GID as mailman, which means a simple fix to the mailman ports Makefile. In which case, your attempt to recompile with mailman as the GID would have been the right approach. The way to reset the OPTIONS for a FreeBSD port is to run make config in the port directory. But the MAIL_GID is not among the options settable that way. I believe that if you use make -DMAIL_GID=mailman reinstall then that will pass the correct option to the configure script that comes with mailman. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Mailman GID problem
On Apr 20, 2007, at 1:44 PM, Paul Schmehl wrote: *If* what you say is true [...] which I am increasingly doubtful of. then this should fix it: --- pkg-install.origFri Apr 20 13:42:17 2007 +++ pkg-install Fri Apr 20 13:42:47 2007 @@ -43,6 +43,7 @@ (umask 002 /bin/mkdir -p %%MAILMANDIR%%) || exit 1 /usr/sbin/chown -R %%USER%%:%%GROUP%% %%MAILMANDIR%% || exit 1 /bin/chmod g+s %%MAILMANDIR%% || exit 1 +/usr/sbin/chown -R nobody %%MAILMANDIR%%/data || exit 1 fi ;; Can you tell me where to find the unprocessed version of pkg- install? What is in work/ has already been processed by sed, and I didn't see anything obvious in files/ I know I should read the porters' handbook, but at this point I'm just poking around to try to get some sense of how the pieces come together. I'm beginning to think that the fix will be as simple as --- Makefile.orig Fri Apr 20 14:17:08 2007 +++ MakefileFri Apr 20 14:18:14 2007 @@ -88,7 +88,7 @@ .if defined(WITH_SENDMAIL) || defined(WITH_EXIM3) || defined(WITH_EXIM4) BROKEN=choose only one MTA integration .endif -MAIL_GID?= nobody +MAIL_GID?= mailman .endif .if defined(WITH_CHINESE) But I haven't tested. And I don't know what the original reason was for using nobody, so I may very well be talking nonsense. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Mailman GID problem
On Apr 20, 2007, at 4:31 PM, Paul Schmehl wrote:
--On Friday, April 20, 2007 14:23:14 -0500 Jeffrey Goldberg
[EMAIL PROTECTED] wrote:
Can you tell me where to find the unprocessed version of pkg-install?
What is in work/ has already been processed by sed, and I didn't see
anything obvious in files/
/usr/ports/mail/mailman/pkg-install
Ah. It was right under my nose.
I'm beginning to think that the fix will be as simple as
--- Makefile.orig Fri Apr 20 14:17:08 2007
+++ MakefileFri Apr 20 14:18:14 2007
@@ -88,7 +88,7 @@
.if defined(WITH_SENDMAIL) || defined(WITH_EXIM3) || defined
(WITH_EXIM4)
BROKEN=choose only one MTA integration
.endif
-MAIL_GID?= nobody
+MAIL_GID?= mailman
.endif
.if defined(WITH_CHINESE)
No, that's *absolutely* the wrong fix. The group required for
mailman to work depends on the mail server you are using.
Sendmail, postfix, qmail, etc. all require different groups. So
using a fixed group might work for you, but it would break it for a
lot of other people's setups.
I think I'm beginning to understand where that nobody comes from
and why you are right about that.
Here is an excerpt from the postfix aliases(5)
In the absence of a user context, the local(8) daemon uses
the owner
rights of the :include: file or alias database. When those
files are
owned by the superuser, delivery is made with the rights specified
with
the default_privs configuration parameter.
I had been looking at the first half of that (which I was already
aware of). So I thought that if the wrapper were compiled to only
run as nobody than the relevant alias files had to be owned by
nobody. I wasn't, until looking this up, aware of what happens
when the aliases file is owned by root.
In the postfix out of ports on FreeBSD, default_privs is set to
nobody.
So the first fix (modifying the owner of data/aliases{,.db}) is the
right way to go, but instead of making those files owned by
nobody (which does seem dangerous because than anything running as
nobody could change those file) they should be owned by root with
mailman as the group and permissions like 664.
Let me just test that now... Yes. Mail delivery seems to work with
[EMAIL PROTECTED] /usr/local/mailman/data]$ ls -la .
total 78
drwxrwsr-x 2 root mailman 1024 Apr 19 16:03 .
drwxrwsr-x 20 mailman mailman512 Mar 30 13:57 ..
-rw-r- 1 root mailman 41 Sep 11 2006 adm.pw
-rw-rw 1 root mailman 3523 Mar 31 16:10 aliases
-rw-rw-r-- 1 root mailman 16384 Mar 31 16:10 aliases.db
-rw-rw-r-- 1 root mailman 12288 Sep 13 2006 aliases.db.rpmsave
-rw-r- 1 root mailman 41 Sep 11 2006 creator.pw
-rw-r--r-- 1 root mailman 10 Mar 30 13:57 last_mailman_version
-rw-rw 1 root mailman 4 Apr 17 14:34 master-qrunner.pid
-rw-r--r-- 1 root mailman 14114 Mar 30 13:57 sitelist.cfg
-rw-rw 1 root mailman 3334 Mar 31 16:10 virtual-mailman
-rw-rw-r-- 1 root mailman 16384 Mar 31 16:10 virtual-mailman.db
I haven't yet tested list creation, but the permissions look fine to
me. All of the relevant files (as well as the data directory itself)
are writable by members of the mailman group.
But I think I now see the problem
$ ../bin/check_perms
/usr/local/mailman/data/aliases.db owned by root (must be owned by
mailman
/usr/local/mailman/data/virtual-mailman.db owned by root (must be
owned by mailman
Problems found: 2
Re-run as mailman (or root) with -f flag to fix
Somehow check_perms doesn't seem to know how postfix does things. If
I were to actually run
check_perms -f
it would break to ownership of the aliases file so that we would have
the mismatch between what the uid postfix gives the the wrapper
(mailman) and what the wrapper demands (nobody).
So maybe the problem is with check_perms and not with the port at all
(well the port would still need to get the aliases files owned by root).
While setting the aliases files to be owned by nobody or by making
the wrapper want mailman instead of nobody would be work-arounds,
both of those lose out on the security achieved by having the aliases
files owned by root.
Of course my two previous understandings of how things were
supposed to work were wrong. So please take my current analysis with
a large grain of salt.
And thank you all for your patience in putting up with my half-baked
postings.
Cheers,
-j
--
Jeffrey Goldberghttp://www.goldmark.org/jeff/
--
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
Re: [Mailman-Users] Mailman GID problem
On Apr 20, 2007, at 9:26 PM, Paul Schmehl wrote:
--On April 20, 2007 7:54:45 PM -0500 Jeffrey Goldberg
[EMAIL PROTECTED] wrote:
So the first fix (modifying the owner of data/aliases{,.db}) is the
right way to go, but instead of making those files owned by nobody
(which does seem dangerous because than anything running as nobody
could change those file) they should be owned by root with mailman as
the group and permissions like 664.
Nobody is an unprivileged user.
Thank you. I forgot about that. I was treating nobody like www
or mail. It entirely slipped my mind that nobody really is
different.
it would break to ownership of the aliases file so that we would have
the mismatch between what the uid postfix gives the the wrapper
(mailman) and what the wrapper demands (nobody).
Nope. I've been running mailman for years now, and it works
perfectly fine. The owner of the data directory is mailman, and
the group is mailman.
ls -lsa /usr/local/mailman/data/
total 132
2 drwxrwsr-x 2 mailman mailman512 Apr 7 19:47 .
2 drwxrwsr-x 20 mailman mailman512 Nov 28 17:48 ..
48 -rw-r--r-- 1 mailman mailman 65536 Sep 6 2005 .db
2 -rw-r- 1 mailman mailman 41 Sep 6 2005 adm.pw
6 -rw-r--r-- 1 root mailman 4383 Oct 14 2005 aliases
4 -rw-r- 1 mailman mailman 3984 Sep 8 2005 aliases.bak
48 -rw-r- 1 mailman mailman 49152 May 5 2006 aliases.db
0 -rw-rw-rw- 1 mailman mailman 0 Sep 9 2005 bounce-
events-00446.pck
0 -rw-rw-rw- 1 mailman mailman 0 Sep 9 2005 bounce-
events-00449.pck
0 -rw-rw-rw- 1 mailman mailman 0 Sep 9 2005 bounce-
events-00467.pck
0 -rw-rw-rw- 1 mailman mailman 0 Jan 27 2006 bounce-
events-00567.pck
0 -rw-rw-rw- 1 mailman mailman 0 Oct 13 2005 bounce-
events-38840.pck
2 -rw-r- 1 mailman mailman 41 Sep 6 2005 creator.pw
2 -rw-r--r-- 1 root mailman 10 Nov 28 17:48
last_mailman_version
2 -rw-rw 1 mailman mailman 4 Apr 1 08:31 master-
qrunner.pid
14 -rw-r--r-- 1 root mailman 14114 Nov 28 17:48 sitelist.cfg
I am fairly confident that if that is working for you, than you are
not running with /usr/local/mailman/mail/mailman that was compiled
with the current port with the postfix option set. The binary
mailman has a gid compiled into it. Given the current port
WITH_POSTFIX.
Installing the current port WITH_POSTFIX will produce a mailman
binary which will only allow itself to be run by nobody. Yours
must have mailman compiled in where nobody is in what I (and
David) get.
[EMAIL PROTECTED] /usr/local/mailman/mail]$ strings mailman | tail
leave
post
owner
request
unsubscribe
Mailman mail-wrapper
nobody
Illegal command: %s
Usage: %s program [args...]
$FreeBSD: src/lib/csu/i386-elf/crtn.S,v 1.6 2005/05/19 07:31:06 dfr
Exp $
What is your result on your system? If you get mailman where I
have nobody then one of my earlier suggestions (change MAIL_GID for
the postfix setting from nobody to mailman in the port Makefile)
may be the right thing. That is what is most consistent with the
mailman install instructions.
From /usr/local/share/doc/mailman/mailman-install.txt
In section 6.1.1 Integrating Postfix and Mailman
* When you configure Mailman, use the --with-mail-gid=mailman
switch;
However, the current ports Makefile compiles mailman --with-mail-
gid=nobody
The same section also says
Make sure that the owner of the data/aliases and data/aliases.db
file is mailman, that the group owner for those files is
mailman,
or whatever user and group you used in the configure command,
and
that both files are group writable:
% su
% chown mailman:mailman data/aliases*
% chmod g+w data/aliases*
It is the *group* that matters to postfix, *not* the owner. Per
the pkg-message file:
Mailman has been installed, but requires further configuration
before use!
You will have to configure both your MTA (mail server) and web
server to
integrate with Mailman. If the port's documentation has been
installed,
extensive post-installation instructions may be found in:
%%DOCSDIR%%/FreeBSD-post-install-notes
Note (1): If you use an alternate (non-Sendmail) MTA, you MUST be
sure
that the correct value of MAIL_GID was used when this port or package
was built. Performing a make options in the Mailman port directory
will list required values for various mail servers.
Note that MAIL_GID is what matters. That is the *group* not the
owner of the files. Note also that the group only has read writes
to the aliases file, although it does have read/write access to the
bounce-events files.
However it is the owner of the file containing the pipe alias that
matters to postfix local deliveries. See local(8).
So maybe the problem is with check_perms and not with the port at all
(well the port
Re: [Mailman-Users] List owner changes anomalies
On Apr 19, 2007, at 3:30 PM, David Southwell wrote: This seems to be a bug where the [list-owner_ID] is not being properly maintained. I realize I have a possible clue that may help someone who is familiar with mailman's logic. The original email address for the owner was given in error. It was an email address that would not have been validatable! Does that help anyone to get to the bottom of this? Can you please post the result of ls -la mailman/data As I understand things, you installed mailman from FreeBSD ports. Am I correct in that assumption? If you did, did you modify the Makefile or use any special settings when installing? Did you use the Postfix option when installing mailman from ports? If so the mailman wrapper should have been compiled with mail-gid=nobody Did you also install postfix from ports? Did you modify the installation process at all? Postfix (at least the version installed with ports on FreeBSD is happy to have the various aliases files and databases owned by nobody Anyway, answering these questions should help clear things up. Especially give that directly listing I asked for. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Placing a list member on hold
On Apr 19, 2007, at 5:38 PM, Mark Sapiro wrote: A list admin can set a member to nomail and change the members password so the member can't log in, but there's no way for a list admin without additional access to the Mailman installation to find the original password before changing it so it can be changed back. Also the member can always request to have their password mailed to them. So this really isn't a solution. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] DEFAULT_SUBSCRIBE_POLICY
On Apr 16, 2007, at 10:36 PM, kalin mintchev wrote: i'm really tired of clients batching over the subscription confirmation: but why?, nobody will do it and we goanna lose people?, it's to difficult, can we do it without it?!, our list is special.., etc, etc... I agree that for many lists and many users the confirmation step is a point where legitimate subscription attempts fail. But ... List bombing (maliciously subscribing people to lots of lists) does happen. (I have been a victim of it several times). What I've seen is that known anti-spammers get their addresses added to lists that don't do proper confirmation. Maybe not this year, or maybe not the next year, but it is almost certain that you will end up getting yourself blacklisted. Anyway, I see from a later post of yours that you found out how to do the configuration you want. Please consider that step carefully. Also look at enabling VERP_CONFIRMATIONS, which will result in having confirmation requests go out with a more helpful Subject header. You need to configure your MTA appropriately for VERP (basically handling username+whatever local parts correctly). -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
[Mailman-Users] Are edits to data/aliases preserved
I'm using mailman with postfix. Mailman creates and modifies the file mailman/data/aliases which is (indirectly) used by postfix for the aliases that mailman uses. I would like to edit some of the content of that file by hand, in particularly I want bounces to both be processed by mailman and sent to the list owner. So I'd like to change the line spirit-bounces: |/usr/local/mailman/mail/mailman bounces spirit to spirit-bounces: |/usr/local/mailman/mail/mailman bounces spirit, spirit-owner Will such an edit survive any future mailman additions to data/ aliases? Also, is there some other/better way of achieving what I want to achieve (seeing all bounces and having mailman process them Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Are edits to data/aliases preserved
On Apr 10, 2007, at 3:45 PM, Mark Sapiro wrote: Making the listname-bounces alias go to both 'bounces' and 'owner' is probably the most convenient way for the owner to see every bounce. OK. That is what I will do then. With list settings, you can see unrecognized bounces and those bounces that cause a disable, but the normal bounces that are recognized as such but do not cause a disable Yes. I did see that. (i.e. are not the bounce that puts the score over the threshold) will not be seen unless you either modify the code or do something with the alias as you suggest. I'm interested in doing this for a very low frequency announce-only list with less than 300 members. So while I'm happy to have mailman do its bounce processing, there really is no configuration for it that will do the job needed. A human (me) will need to look at each bounce. I now see that I can get the bounce information from bin/dumpdb lists/ listname/config.pck, so I can look through my mail logs and see if that gives me a clue for the reason for the bounce. As far as the edit surviving changes is concerned, it will as long as you don't run Mailman's bin/genaliases. Normal addition or deletion of lists only adds or removes stanzas to/from the data/aliases file, but bin/genaliases rebuilds it from scratch. Thanks. I might move or disable genaliases since I'm bound to forget this tidbit years from now. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Privacy policy
[mailed and posted] On Apr 8, 2007, at 5:54 PM, Paul Tomblin wrote: Juno and NetZero are refusing email from my mailing list server because they think that 25 messages over the course of 3 days makes me some sort of spammer. They're refusing to whitelist me until I can provide a link to a Privacy Policy and Terms of Service. Has anybody else encountered this, and do you have samples of those two documents, and information how to embed this in my mailman listinfo page? I have those on the main (only) static page for my site http://lists.shepard-families.org/ I doubt that they are as formal as what Juno and NetZero are asking for. At least you actually got to talk to someone about white listing. For similar problems with AOL, I found that making sure that my HELO string had an appropriate DNS PTR record back to the same IP. Getting my provider, Verizon, to understand what I was asking for was the hard part. -j -- 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
Re: [Mailman-Users] Two Problems with Mailman
On Apr 6, 2007, at 7:04 PM, Mark Sapiro wrote: See https://sourceforge.net/tracker/ index.phpfunc=detailaid=1495122group_id=103atid=100103 for a description of the problem that I think is probably causing this and a patch to fix it. It makes no sense for the newest posts to be at the bottom of the list. I suggest that it does make sense to some people, particularly those who like to read the question before the answer, Somebody has to point out that the link you gave points to a discussion in which the most recent contribution is at the top. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Mailman scripts running with wrong group
On Apr 4, 2007, at 8:38 PM, Mark Sapiro wrote: I think in most cases, Postfix excecutes the pipe to Mailman using the user and group of the file in which it found the alias that contains the pipe to Mailman. I can confirm this. I had the problem that the original poster described after moving my mailman installation from one machine to another. Postfix does instead use the owner of the particular .db file to determine what user delivery (whether to files or pipes) should be run under. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
[Mailman-Users] Getting users to confirm
I run list for some very non-technical users, with my site being their only experience with any MLM system for many of them. The single biggest problem that I have is that users fail to recognize that they need to act on confirmation requests. As far as I can tell, they treat the confirmation request as an actual confirmation that everything is done. Where would I go about changing the subject line of the confirmation requests, and what would people recommend. Am I the only experiencing this? I believe that I've made things clear to users on my static pages http://lists.shepard-families.org/ and in all of the administrative messages I send to the list. But this just doesn't seem to be enough. Also is there a way to get a listing of all things pending confirmation (not just subscriptions, but address changes as well)? -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Getting users to confirm
[mailed and posted] On Apr 2, 2007, at 2:39 PM, Mark Sapiro wrote: Jeffrey Goldberg wrote: Where would I go about changing the subject line of the confirmation requests, and what would people recommend. You may have already done this, but if the subject you are seeing is confirm hex token, You can change it to Your confirmation is required to join the %(listname)s mailing list by setting VERP_CONFIRMATIONS = Yes in mm_cfg.py, assuming your MTA can handle the VERP like address in the reply. Great. That does exactly what I want. I believe that I've already set up postfix to do the right thing with username+something addresses. Yes. I've just tested and it works like a charm. Also is there a way to get a listing of all things pending confirmation (not just subscriptions, but address changes as well)? bin/dumpdb lists/listname/pending.pck will show them, albeit in a cryptic form. Thanks that works. Also, it shows some that are expired so you have to look at the timestamps in the 'evictions' dictionary. Where do I find the evictions dictionary? And how do I query it? find /usr/local/mailman -name evict* -ls turned up nothing. (In my set-up, FreeBSD, the stuff that's typically in /var/lib/mailman is under /usr/local/mailman) Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Let me try this again ;-)
On Mar 25, 2007, at 9:09 AM, Dave Foran wrote: Is there an option to have mailman ignore anonymous posts and not even acknowledge the post. Just let it go to /dev/null ?? There is probably some way to do that, but I don't know it. But I'm not sure that that is the right approach in the first place, since once your server accepts some incoming mail it has certain responsibilities. Right now, I am seriously blacklisted by the anonymous posts being sent by spammers and mailman trying to send back a message your post is not allowed You should be doing your spam blocking earlier. Are you using DNSbl's and or filters to reject incoming spam? If you reject most of the spam at SMTP time, then mailman will never see the spam in the first place and you won't have to generate any bounces. -j -- - Dave Foran Internet ONLY:[EMAIL PROTECTED] Cruise Missile Coordinates 41.36.46N 81.25.53W -- - Not enough information. We need altitude as well for setting the target of a missile. -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] double attachments
On Dec 7, 2006, at 4:27 PM, tonya kay wrote: Hello! I am new to the Mailman Mailing List. My email client is Mac's Mail, running on the Mac OSX operating system. When I send an email to my Mailman mailing list, the .jpg files I attach are duplicated in the recipient's email. How can I assure that only one of each attachment is received? I use Apple's Mail.app (2.1) and have not had this problem with PDF attachments (the only attachments I've ever sent to a mailing list). Can you double check your Sent folder to make sure that the attachment really is only in there once for what you sent? Also never check Send Windows Friendly Attachment box. That may do something that shows up like doubling the attachment. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Duplicate password reminders
On Dec 6, 2006, at 9:56 AM, Mark Sapiro wrote: Jeffrey Goldberg wrote: There is a single crontab entry for mailman calling mailpasswords. Is there some additional mechanism by which mailman might be calling mailpasswords? Not unless someone at your site created it. Are you sure there aren't two crontabs; one for the mailman user (/var/spool/cron/mailman or ??) and a system one in /etc/cron.d? That's it. I feel like an idiot. There is a /etc/cron.d/mailman which is identical to crontab -l -u mailman. This explains some other repetitions in logs. I installed the latter, so I guess the rpm (SuSE 10.0) installed the former. I should have thought to look there, but I forgot about /etc/cron.d Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
[Mailman-Users] Duplicate password reminders
All of the members of all of the lists on my site appear to be getting duplicate reminders. There is a single crontab entry for mailman calling mailpasswords. Is there some additional mechanism by which mailman might be calling mailpasswords? This is mailman 2.1.6 Thank you. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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
Re: [Mailman-Users] Different URL PATTERNS per virtual host?
On Sep 18, 2006, at 1:24 PM, Dragon wrote: Is there some reason you would not want to run https on all of the lists? I can't speak for the original poster, but in my case it is a question of which domains I'm willing to get site certificates for. -j -- 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
Re: [Mailman-Users] Mailman, Exim and Wrapper..,
On Mon, 13 Oct 2003, Brad W. Galiette wrote: CPanel is configured in such a way so that Exim is launches under *many* different GIDs as opposed to a single such identifier. Is there any way in which I can disable the wrapper GID check, modify it so that it operates with CPanel, or obtain a version (source or binary) of Mailman that does not have this check? Better still, you can modify your exim configure file to have a special director for the mailman alias which specified the GID that any such deliveries be run under. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ Relativism is the triumph of authority over truth, convention over justice Hate spam? Boycott MCI! http://www.goldmark.org/jeff/anti-spam/mci/ -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Minor doc suggestion. Location of smrsh directory
This is just a minor suggestion of an improvement that could be made to README.SENDMAIL in the documentation. Recent versions of sendmail tend to have a default of /usr/adm/sm.bin instead of /etc/smrsh as the location where smrsh wants pipable executables. I don't blame the current documentation for my hours of frustration. That was a combination of having installed sendmail from source, where RPMs are typically expected and somehow ending up reading the wrong smrsh man page. Still, as sendmail is moving to /usr/adm/sm.bin as the place where the mailman wrapper should go, a note of that in README.SENDMAIL would help. Another note is that the INSTALL document orders the editing of mm_cfg.py AFTER creating the mailman list. That will create the list with some bad information if Default.py is not exactly what you need. Other than that, my mailmain 2.1.3 installation went great. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ Relativism is the triumph of authority over truth, convention over justice Hate spam? Boycott MCI! http://www.goldmark.org/jeff/anti-spam/mci/ -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Newby Question...
On Wed, 1 Oct 2003, John Berry wrote: Hello all! I am new to the list. Please direct me to where I can get specific instructions on how to setup mailman that is already installed on an RH9.0 install. I have upgraded it to the latest RPM version using up2date. The RPM from RedHat will have put what you need in /usr/share/doc/mailman-VERSION There you should see a file called INSTALL.REDHAT which has the instructions you need. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ Relativism is the triumph of authority over truth, convention over justice Hate spam? Boycott MCI! http://www.goldmark.org/jeff/anti-spam/mci/ -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
