[Mailman-Users] Any way to prevent password reminders from being set at a server level?
I am in the process of configuring a secondary mailman system for use as a hotspare. I noticed just a few days ago that both the primary and the backup system sent out list password reminders. There really is no reason to send out both reminders as they contain the exact same text. Is there a way to tell the server not to send those out. I know each user can set this up on a per list basis, but since the backup does an rsync of the list data from the primary any such change in the list would be short lived. I found in Defaults.py DEFAULT_SEND_REMINDERS, but this seems to set the default upon list creation. I am just looking for a way to suspend those messages so that my live backup system doesn't confuse the users. The FAQ didn't seem to have anything helpful (at least not that I could find). Pat -- 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=show&file=faq01.027.htp
[Mailman-Users] Simple way to change archive settings
I know that this falls under the withlist command, but I am not really python savvy so How exactly would I go about deleting the archives for about 15 lists and setting their archive attributes to off? Pat -- 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=show&file=faq01.027.htp
[Mailman-Users] mailman clustering?
I am trying to build a nice failover system for random parts of our infrastructure. Does anyone know how to force mailman to replicate changes over to another identically configured system? I thought about using rsync for this but I am trying to keep the sync triggered by updates on the primary server rather than just seeing if in the last few minutes any files have changed. Ideally I would like to round robin the primary and the secondary to split the load up, but I cannot do that without being sure that they are kept in sync with each other. How close to possible is this idea? Is there something I should read? I checked the FAQ and didn't see anything... Pat -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] (no subject)
I am not exactly sure how this faq applies, I should have been clearer in my request I can email the list easily enough, what I am looking for is a way to modify subscriptions to the list (either add or remove users) from an email only interface. For example, listproc has a command you can email it to allow a user to be subscribed, and another command to unsubscribe users as the list admin, not just as the user who wants on/off. I believe majordomo has one as well (I haven't ever used it, but since it is email/commandline only it probably should). I would like to be able to make many subscription changes via the email interface as the list admin. I was not clear enough in my previous email, I should have thought through it more before sending it. I hope this is clearer. pat - The lines which your eye falls on first here were written last. Their purpose is to make yet another attempt to force into the form of a letter the detailed investigation which is sent to you herewith. These lines correspond, then, with the last lines and together they form an envelope, thus indicating in an external way what interal proofs in many ways will convince you of, that this is a letter you are reading. ~Kierkegaard On Sat, 17 Jul 2004, Brad Knowles wrote: > At 7:14 PM -0500 2004-07-16, Pat Riehecky wrote: > > > I was wondering if anyone knew a way to send an invitation email to an > > address using only an email program? I would like to be able to send an > > email to one of the program's addresses so that it invites a user to join > > the list. I was thinking that there should be a way to email > > [EMAIL PROTECTED] with the list password and some how tell it to > > invite [EMAIL PROTECTED] > > See <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq02.004.htp>. > > -- 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/
[Mailman-Users] (no subject)
I was wondering if anyone knew a way to send an invitation email to an address using only an email program? I would like to be able to send an email to one of the program's addresses so that it invites a user to join the list. I was thinking that there should be a way to email [EMAIL PROTECTED] with the list password and some how tell it to invite [EMAIL PROTECTED] Does anyone have a pure email way to do that? Or is the web interface required for that? pat - The lines which your eye falls on first here were written last. Their purpose is to make yet another attempt to force into the form of a letter the detailed investigation which is sent to you herewith. These lines correspond, then, with the last lines and together they form an envelope, thus indicating in an external way what interal proofs in many ways will convince you of, that this is a letter you are reading. ~Kierkegaard -- 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/
[Mailman-Users] how to cripple a list?
basiclly i am wondering how to set some sitewide defaults for a list that cannot be changed. ie. i want all lists to always have private archives and always have the list headers, never have the news gateway options presented and the like. I am asking this merely because several not so computer literate people will be put in charge of their own lists and there are some defaults that make more sense then others as nobody should be changing the host_name field since the machiene only has one name and one address associated with it. I am not looking for a list of fields to leave accessible or a recomendation that documentation be provided telling users what not to change. we have tried that before and nobody cares because IT always is able to fix it when they screw it up. i am hoping that there are just some directives i can put in mm_cfg.py or another file to edit to make this happen. pat - The lines which your eye falls on first here were written last. Their purpose is to make yet another attempt to force into the form of a letter the detailed investigation which is sent to you herewith. These lines correspond, then, with the last lines and together they form an envelope, thus indicating in an external way what interal proofs in many ways will convince you of, that this is a letter you are reading. ~Kierkegaard -- 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/
[Mailman-Users] fixing group mismatch error?
I get the following error, May 12 19:57:32 [Mailman mail-wrapper] 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'. where exactly is the 'configure' command, I checked inside of the mailman bin directory but it was not there. My guess is that it refers to the ./configure script to be run before installing. Unfortuatly I installed using a premade package and do not have the source on hand. Any way to have the program expect group nobody without doing that or a way to make postfix use that group to run /only/ that script? pat - The lines which your eye falls on first here were written last. Their purpose is to make yet another attempt to force into the form of a letter the detailed investigation which is sent to you herewith. These lines correspond, then, with the last lines and together they form an envelope, thus indicating in an external way what interal proofs in many ways will convince you of, that this is a letter you are reading. ~Kierkegaard -- 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/
[Mailman-Users] autoupdate /etc/aliases?
I'm playing around a bit with mailman and was wondering how to get it to update /etc/aliases automatically using postfix. Here is the stuff from Defaults.py MTA = 'Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS = [] # not using virtual domains POSTFIX_ALIAS_CMD = '/usr/sbin/postalias POSTFIX_MAP_CMD = '/usr/sbin/postmap' and I have symlinked /etc/aliases to mail/aliases, but running addlist as either root or (after chown mailman /etc/mail/aliases) mailman it is not updated. What obvious thing have I missed? pat - The lines which your eye falls on first here were written last. Their purpose is to make yet another attempt to force into the form of a letter the detailed investigation which is sent to you herewith. These lines correspond, then, with the last lines and together they form an envelope, thus indicating in an external way what interal proofs in many ways will convince you of, that this is a letter you are reading. ~Kierkegaard -- 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/
[Mailman-Users] two classes of people within a list
Lets say that I have a list (games) and subscribed to the list are both the game players and the game planers. Is there a way to use the aliases to allow email to circulate between the planers only without creating a second list, as that is a site restriction (one list per group). I was thinking the games-admin alias would be about perfect, but I have no idea if it will even do what I want it to, nor how to go about adding people to that field if it does what I want. I figure that most people can't even remember one email address, so having [EMAIL PROTECTED] be pubic chat and [EMAIL PROTECTED] be planing would allow for things to be simpler for changing admins around and what not pat - The lines which your eye falls on first here were written last. Their purpose is to make yet another attempt to force into the form of a letter the detailed investigation which is sent to you herewith. These lines correspond, then, with the last lines and together they form an envelope, thus indicating in an external way what interal proofs in many ways will convince you of, that this is a letter you are reading. ~Kierkegaard -- 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/
Re: [Mailman-Users] Send to list error
hmmm try doing a reverse dns lookup on the server you are sending from and see if it is a valid client to be sending mail through your exchange server. if not you may have to add it to your dns or agents to relay mail for (at least i think that is what that version of exchange calles it) i am also noticing that you are getting "5.1.2" as your 'from' host. i know you know that that isnt a valid ip address, so you may want to check Mailman\mm_config.py and Mailman\Defaults.py for a typo in the EMAIL_HOST area. pat - The lines which your eye falls on first here were written last. Their purpose is to make yet another attempt to force into the form of a letter the detailed investigation which is sent to you herewith. These lines correspond, then, with the last lines and together they form an envelope, thus indicating in an external way what interal proofs in many ways will convince you of, that this is a letter you are reading. ~Kierkegaard On Tue, 11 May 2004, Brian York wrote: > I tried it with brackets and still get the same error. I can ping the mailman > server from the mailserver (nkuaxp.nku.edu). In the error it strips off the > brackets. > > From nkuaxp: > > Sending failed: > Message sending failed since the following recipients were rejected by the > server: > [EMAIL PROTECTED] (The server responded: "5.1.2 unknown host or domain: > [EMAIL PROTECTED]") > > > > From exchange 5.5 server > > Sending failed: > Message sending failed since the following recipients were rejected by the > server: > [EMAIL PROTECTED] (The server responded: "Relaying is prohibited") > > > the address in the To: field was[EMAIL PROTECTED] for both. > > > Sendmail is being used on the mailman server. > I don't understand why the exchange server would say that relaying is > prohibited. Is this a problem on the mailman server. If so what do i need to > do to fix it. > > Thanks > Brian > > On Tuesday 11 May 2004 15:31, Kai Schaetzl wrote: > > Brian York wrote on Mon, 10 May 2004 22:33:44 -0400: > > > [EMAIL PROTECTED] > > > > There's your answer, that's not a valid domain or email address. Try with > > [] brackets around the IP. > > > > > > Kai > > -- > 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/ > -- 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/
[Mailman-Users] generalized specs question
The site where I work is considering replacing our current listprocessor (ListProc 6.0c) with either Mailman or Majordomo. So I was going to as a benchmarking type question, what sort of a system would be required to run 100 lists each sending out 100 emails a day? Obviously a 486 /can/ do it, but reasonibly fast sending is nice. (ie would something like a pentium2 250 with 128 RAM be enough) Secondly how long (estimate, please) would it take to send all 1 emails should they be sent to the lists at the same time? Thanks a bunch! pat - The lines which your eye falls on first here were written last. Their purpose is to make yet another attempt to force into the form of a letter the detailed investigation which is sent to you herewith. These lines correspond, then, with the last lines and together they form an envelope, thus indicating in an external way what interal proofs in many ways will convince you of, that this is a letter you are reading. ~Kierkegaard -- 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/
