Re: [Mailman-Users] Evolution, GPG, and mailman 2.1.2 - blankmessage bodies
Jeremy there are a bunch of ways that we can handle this, but knowing "certain" people I'm sure the only acceptable solution is for us to modify the archived emails in the mbox, so that the past archives show up properly. Of course that would not deal with the on-going emails The settings to modify Pipermail behavior are all in ~mailman/Mailman/mm_cfg.py (look in Defaults.py for examples of items to change/set) There are a lot of options we can change there and then play with re-archiving. I've got a few test beds of 2.1 running on my home network so it's easy for me to do. Let me know if you want me to look at it. The best answer for Trilug is for someone to setup Mhonarc on the Mailman server and use that instead of Pipermail. I would volunteer to do that, but everytime I touch the servers Tanner and I come to blows, and I've had enough of him to last me the rest of my life. Jon On Thu, 2003-08-14 at 13:01, Jeremy Portzer wrote: > Hello. > > I feel like this must be an F.A.Q. but I could find no mention of it in > the searchable archives or the FAQ-O-Matic. > > Anyway, it seems that evolution has a bug in message display that > affects GPG-signed email sent to mailman 2.1.x lists (when the GPG > signature uses PGP/MIME). Mailman adds the list's signature as a MIME > attachment, and for some reason evolution shows ONLY the list signature, > and not the body of the message at all! > > This is apparently fixed in Evolution 1.4.3, but unfortunately a large > number of our users are using prior versions of evolution, like 1.2.2 > that's included in Red Hat Linux 9. I suspect this is true of many > users around the community. Though this is an evolution bug, most of > our users are seeing it as a "mailman problem," because suddenly they > cannot view their messages after we upgraded to mailman 2.1.x. > > Does anyone have any ideas or workarounds? Is there any way to make > mailman 2.1.2 go back to the old behavior that doesn't use MIME to add > the signature (or just skips it for MIME messages) ? > > Note: I've also heard that Outlook Express has a similar problem > reading GPG-signed emails with evolution's MIME-added signature, so this > isn't really uniquely an evolution problem. But Outlook Express handles > GPG pretty pitifully anyway, so I'm not worrying about that. > > Thanks for any advice, > > Jeremy -- 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] Archive dating problem - mailman 2.1.2,regenerating archives from mbox
Hay Jeremy, I'll be happy to take a look at this, if you can put a copy of the mbox in my user directory. I can probably track this down pretty quick. Jon On Thu, 2003-08-14 at 12:22, Jeremy Portzer wrote: > Hello, > > I'm having trouble getting the archives to show the correct dates in > mailman version 2.1.2 (running on Red Hat Linux 7.3). > > I have some lists that I copied to my current server from a previous > mail host (which was running 2.0.x, but that should be irrelevant). I > copied the archives and concatonated the mbox files of the new and old > archives. I made sure to include a blank line between messages in the > mbox files, as suggested in the FAQ, and the mbox file appears correct > when viewed with mailx (the "mail" comamnd in Linux) and pine. > > However, when I regenerate the archives from the mbox file, by removing > the old archive directory and running mailman/bin/arch , many of the > messages are dated incorrectly. Some of the messages archive fine, but > others are given the _current_ date and time, instead of the date on the > message. This is very annoying as it means I have a huge number of > messages in August 2003 which do not belong there, and the original > date/time information is lost! When I look at the messages in question > in the mbox file, they appear to be properly formatted with correct > Date: and "From " headers. > > In previous versions of mailman, there was a configuration flag on > whether to follow the date/time of the message Date: header, or the one > from the mbox format "From " line. However, I can't seem to find this > option in mailman 2.1.2. Has it been removed, and if so, why? > > Thanks for any ideas! > > --Jeremy -- 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] Changing the moderation default.
So, I've manage to get everything working, and I set up my first two or three lists. I set up the first one as moderated by default and then realized I didn't want to do that. I found the switch to unmoderate existing members, but I can't offhand find or determine if I can change the default behavior. Will I have to unmoderate new members for the life of this list, or can I hack the default behavior somehow? Thanks! David -- David - Offbeat http://www.dafydd.com dafydd - Online Fire2 - Burning Man ESD: Integrity*Commitment*Communication*Support Failure is not an option. It comes bundled with the software. --unknown -- 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: RE: [Mailman-Users] Managing archives
No... No... No... Setup SquirrelMail on one of your servers and you are there. Heck set it up on your Mailman server and use it just for this. If you need help in setting it up, I'm a wiz at setting this up remotely and my prices are great. Jon Carnes >On Fri, 15 Aug 2003 15:41:54 -0400 Victor Tsaran <[EMAIL PROTECTED]> wrote. >Hi, John! >Your idea and the advice sound great, however, this assumes that the person >has to use some kind of Unix-based E-mail client which, as you can imagine, >generally not the case. I was hoping for some kind web-based solution, but I >guess we will have to wait for this one. >Thanks for your help. Will let you know if I come up with something >interesting. >Regards, >Victor > > >-Original Message- >From: Jon Carnes [mailto:[EMAIL PROTECTED] >Sent: Wednesday, August 13, 2003 8:57 AM >To: [EMAIL PROTECTED] >Cc: [EMAIL PROTECTED] >Subject: RE: [Mailman-Users] Managing archives > > >oops... forgot to set the rights for the new archive mbox file... >I added that to the second script. > >Jon Carnes > >A script that creates the imap mbox and copies the mbox from the archive: > #! /bin/bash > # > # Used to move an archive into position for editing > # by anyone who can use an email client > # > # Assumptions: > # - mailman install is in /var/mailman > # - imap mailbox root is /home/user/mail/ > # This means that you already created the mbox > # using your email program. > #== $1 > # > # Input: a valid mailman list name (with archives) > # > PATH2ARC="/var/mailman/archives/private" > # Check that the list name is valid and the archives exist > if [ ! -f $PATH2ARC/$1.mbox/$1.mbox ]; then >echo ERROR: $1 is not a valid mailman list with archives >echo (be sure to use all lower case) >echo or path to archive files is incorrect: >echo $PATH2ARC >echo " " >exit 0 > fi > # > PATH2MB="/home/user/mail" > # > # Check that mbox has been created... > if [ ! -f $PATH2MB/$1 ]; then >echo ERROR: Please check that the path to your IMAP Mailbox >echo is: $PATH2MB >echo and that you have created a Mailbox called:$1 >echo >exit 0 > fi > # > cat $PATH2ARC/$1.mbox/$1.mbox >> $PATH2MB/$1 > >=== > >Now someone simply edits the mailbox using their email client. This >doesn't take anyone technically minded... > >When they are done, we put back the archives: > #! /bin/bash > # > # Used to move an edited mbox from an imap folder > # and put it back into the Mailman archive from > # which it was grabbed. > # > # Assumptions: > # - mailman install is in /var/mailman, > # with archives being in /var/mailman/archives/private/.. > # - imap mailbox root is /home/user/mail/ > # and the imap header for the file is 13 lines long > # including the blank line at the end of the message. > # > # Input: a valid mailman list name (with archives) > # > PATH2ARC="/var/mailman/archives/private" > # > # Check that the list name is valid and the archives exist > if [ ! -f $PATH2ARC/$1.mbox/$1.mbox ]; then >echo ERROR: $1 is not a valid mailman list with archives >echo (be sure to use all lower case) >echo " " >exit 0 > fi > # > PATH2MB="/home/user/mail" > # > # Check that mbox has been created... > if [ ! -f $PATH2MB/$1 ]; then >echo ERROR: could not find mailbox $1 in path: >echo $PATH2MB >echo Please check that root path to mailbox is correct. >echo " " >exit 0 > fi > # > # Number of lines in IMAP header > IHEAD=13 > # > mv $PATH2ARC/$1.mbox/$1.mbox $PATH2ARC/$1.mbox/$1.mbox.bak > # >j=`cat $PATH2MB/$1 |wc -l` >k=$(( j - IHEAD )) >tail -$k $PATH2MB/$1 > $PATH2ARC/$1.mbox/$1.mbox >chown mailman.mailman $PATH2ARC/$1.mbox/$1.mbox > # > # now lets remove the old archive files and regen > # the archives with the new mbox! > rm -rf $PATH2ARC/$1/* > /var/mailman/bin/arch $1 > >=== > >The scripts aren't tested, but should be good for a quick start! >Take care. Hope that helps someone. > >Jon Carnes > > > > >-- >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/[EMAIL PROTECTED]/ > >This message was sent to: [EMAIL PROTECTED] >Unsubscribe or change your options at >http://mail.python.org/mailman/options/mailman-users/[EMAIL PROTECTED] -- 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] add_members from another script?
On Friday, August 15, 2003, at 07:51 pm, Bill Goffe wrote: I'm running Mailman 2.1.2 on a Debian system, and I'd like to call add_members from another script. In my application, users can only get to this point via a password, so I'm reasonably sure that they don't need address verification that the normal subscription mechanism provides. But, when I call add_members from another CGI script, I get Traceback (most recent call last): File "/usr/local/mailman/bin/remove_members", line 186, in ? main() File "/usr/local/mailman/bin/remove_members", line 161, in main mlist = MailList.MailList(listname) File "/usr/local/mailman/Mailman/MailList.py", line 122, in __init__ self.Lock() File "/usr/local/mailman/Mailman/MailList.py", line 155, in Lock self.__lock.lock(timeout) File "/usr/local/mailman/Mailman/LockFile.py", line 243, in lock self.__write() File "/usr/local/mailman/Mailman/LockFile.py", line 422, in __write fp = open(self.__tmpfname, 'w') IOError: [Errno 13] Permission denied: '/usr/local/mailman/locks/a.lock.cook.20710.0' As Mailman and Apache run under different userids, I tried adding Mailman's group to Apache's, but I still get similar errors (I tried the reverse in case I got it reversed). Interestingly, if I run Apache *itself* as mailman, it works fine, but that seems like an awfully blunt mechanism. I read the FAQ, but didn't see anything. I also spent a lot of time in archives, and while this is talked about, it is never really answered. Mailman's own CGI scripts are run via compiled C wrappers that have set gid to the mailman group permission and which then execute the associated MM CGI script from $prefix/Mailman/Cgi/ directory. These wrappers do some security checking before running the script. The source of the wrapper is in $build/src/cgi-wrapper.c You do not necessarily have to copy this approach in all its detail, although, if your alternative CGI script is written in Python, it is not that difficult to do. But the general principle of doing it this way is good. Take a look at the permissions on the wrappers in $exec-prefix/cgi-bin/ and the C wrapper source code. Certainly this is preferable to opening up the permissions of your Apache server too far, especially if it is accessible from the internet. Another approach is to have your script drop stuff to a file where a cron script run by the mailman user picks the data up and does the real thing. But this puts a lag in response and lacks immediacy. But it can be made a bit more hacker proof. Thus, I'm most curious if anybody has any suggestions. - Bill -- *--* | Bill Goffe [EMAIL PROTECTED] | | Department of Economicsvoice: (315) 312-3444 | | SUNY Oswegofax: (315) 312-5444 | | 443 Mahar Hall | | Oswego, NY 13126| **-- *---* | "Our products just aren't engineered for security." | | -- Brian Valentine, Microsoft Senior VP for Windows Development, | | "Lead Windows Developer Bugged by Security," Matt Berger, InfoWorld | | www.infoworld.com/articles/hn/xml/02/09/05/020905hnmssecure.xml | *-- -* --- Richard Barrett http://www.openinfo.co.uk -- 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] Managing archives
Hi, John! Your idea and the advice sound great, however, this assumes that the person has to use some kind of Unix-based E-mail client which, as you can imagine, generally not the case. I was hoping for some kind web-based solution, but I guess we will have to wait for this one. Thanks for your help. Will let you know if I come up with something interesting. Regards, Victor -Original Message- From: Jon Carnes [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2003 8:57 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: [Mailman-Users] Managing archives oops... forgot to set the rights for the new archive mbox file... I added that to the second script. Jon Carnes A script that creates the imap mbox and copies the mbox from the archive: #! /bin/bash # # Used to move an archive into position for editing # by anyone who can use an email client # # Assumptions: # - mailman install is in /var/mailman # - imap mailbox root is /home/user/mail/ # This means that you already created the mbox # using your email program. #== $1 # # Input: a valid mailman list name (with archives) # PATH2ARC="/var/mailman/archives/private" # Check that the list name is valid and the archives exist if [ ! -f $PATH2ARC/$1.mbox/$1.mbox ]; then echo ERROR: $1 is not a valid mailman list with archives echo (be sure to use all lower case) echo or path to archive files is incorrect: echo $PATH2ARC echo " " exit 0 fi # PATH2MB="/home/user/mail" # # Check that mbox has been created... if [ ! -f $PATH2MB/$1 ]; then echo ERROR: Please check that the path to your IMAP Mailbox echo is: $PATH2MB echo and that you have created a Mailbox called:$1 echo exit 0 fi # cat $PATH2ARC/$1.mbox/$1.mbox >> $PATH2MB/$1 === Now someone simply edits the mailbox using their email client. This doesn't take anyone technically minded... When they are done, we put back the archives: #! /bin/bash # # Used to move an edited mbox from an imap folder # and put it back into the Mailman archive from # which it was grabbed. # # Assumptions: # - mailman install is in /var/mailman, # with archives being in /var/mailman/archives/private/.. # - imap mailbox root is /home/user/mail/ # and the imap header for the file is 13 lines long # including the blank line at the end of the message. # # Input: a valid mailman list name (with archives) # PATH2ARC="/var/mailman/archives/private" # # Check that the list name is valid and the archives exist if [ ! -f $PATH2ARC/$1.mbox/$1.mbox ]; then echo ERROR: $1 is not a valid mailman list with archives echo (be sure to use all lower case) echo " " exit 0 fi # PATH2MB="/home/user/mail" # # Check that mbox has been created... if [ ! -f $PATH2MB/$1 ]; then echo ERROR: could not find mailbox $1 in path: echo $PATH2MB echo Please check that root path to mailbox is correct. echo " " exit 0 fi # # Number of lines in IMAP header IHEAD=13 # mv $PATH2ARC/$1.mbox/$1.mbox $PATH2ARC/$1.mbox/$1.mbox.bak # j=`cat $PATH2MB/$1 |wc -l` k=$(( j - IHEAD )) tail -$k $PATH2MB/$1 > $PATH2ARC/$1.mbox/$1.mbox chown mailman.mailman $PATH2ARC/$1.mbox/$1.mbox # # now lets remove the old archive files and regen # the archives with the new mbox! rm -rf $PATH2ARC/$1/* /var/mailman/bin/arch $1 === The scripts aren't tested, but should be good for a quick start! Take care. Hope that helps someone. Jon Carnes -- 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] Changing the moderation default.
So, I've manage to get everything working, and I set up my first two or three lists. I set up the first one as moderated by default and then realized I didn't want to do that. I found the switch to unmoderate existing members, but I can't offhand find or determine if I can change the default behavior. Will I have to unmoderate new members for the life of this list, or can I hack the default behavior somehow? Thanks! David -- David - Offbeat http://www.dafydd.com dafydd - Online Fire2 - Burning Man ESD: Integrity*Commitment*Communication*Support There are no normal people. There are only people you don't know very well. --unknown -- 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] add_members from another script?
I'm running Mailman 2.1.2 on a Debian system, and I'd like to call add_members from another script. In my application, users can only get to this point via a password, so I'm reasonably sure that they don't need address verification that the normal subscription mechanism provides. But, when I call add_members from another CGI script, I get Traceback (most recent call last): File "/usr/local/mailman/bin/remove_members", line 186, in ? main() File "/usr/local/mailman/bin/remove_members", line 161, in main mlist = MailList.MailList(listname) File "/usr/local/mailman/Mailman/MailList.py", line 122, in __init__ self.Lock() File "/usr/local/mailman/Mailman/MailList.py", line 155, in Lock self.__lock.lock(timeout) File "/usr/local/mailman/Mailman/LockFile.py", line 243, in lock self.__write() File "/usr/local/mailman/Mailman/LockFile.py", line 422, in __write fp = open(self.__tmpfname, 'w') IOError: [Errno 13] Permission denied: '/usr/local/mailman/locks/a.lock.cook.20710.0' As Mailman and Apache run under different userids, I tried adding Mailman's group to Apache's, but I still get similar errors (I tried the reverse in case I got it reversed). Interestingly, if I run Apache *itself* as mailman, it works fine, but that seems like an awfully blunt mechanism. I read the FAQ, but didn't see anything. I also spent a lot of time in archives, and while this is talked about, it is never really answered. Thus, I'm most curious if anybody has any suggestions. - Bill -- *--* | Bill Goffe [EMAIL PROTECTED] | | Department of Economicsvoice: (315) 312-3444 | | SUNY Oswegofax: (315) 312-5444 | | 443 Mahar Hall | | Oswego, NY 13126| **--*---* | "Our products just aren't engineered for security." | | -- Brian Valentine, Microsoft Senior VP for Windows Development,| | "Lead Windows Developer Bugged by Security," Matt Berger, InfoWorld | | www.infoworld.com/articles/hn/xml/02/09/05/020905hnmssecure.xml | *---* -- 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] Email posts get posted to the wrong list!
On Friday, August 15, 2003, at 03:24 pm, Thomas Keller wrote: I have a similar problem if I have another mailing list on the mailing list as a recipient. I.e. each site in my company has its own list and then I have a general list which sends to each of those lists. The other time I have the problem is if I send an email to a list and to other recipients as well, i.e. TO: [EMAIL PROTECTED], [EMAIL PROTECTED] I have done newalias and can only assume that it is something in mailman that does not like sending automatically to other lists or when other recipients is included in the TO: line. Assuming MM 2.1.x Mailman has a feature which the above comments are describing. Take a look at the first two option fields on the Privacy->Recipients web admin GUI page. By default MM lists expect to be in the To: or Cc: mail header of messages incoming to it and holds for moderation posts for which this is not true. You can adjust this behaviour via the GUI. Thomas, in your case, put the higher level list in the regex for option 2 'acceptable aliases'. MM 2.0.13 had a similar feature but I cannot remember which of the web Admin GUI pages it was on. But I do no think this is the same problem as was originally posted about by Bill Knechtel. At 07:43 AM 08/15/2003 -0500, Brent Herring wrote: At the risk of stating the obvious, did you run the newaliases command after editing your aliases file? Brent. D. Brent Herring Computer Services University of Central Arkansas >>> "William Knechtel" <[EMAIL PROTECTED]> 8/14/2003 4:24:24 PM >>> Hello All! I'm trying to set up Mailman 2.1.2 on a FreeBSD 4.6 server. I'm using courier-MTA as my mail server software. I've gone through the install procedure, and set up the prescribed umbrealla list called "mailman", and set up a test list, which I'm calling "all". When I sent a message to [EMAIL PROTECTED], it's not actually posting to that list, it's posting to [EMAIL PROTECTED] Now, I've redone the install process (twice), I've verified that the aliases I'm giving courier are correct, and still, the post end up posting to the wrong list. The "mailman" list respond to my attempts to post to "all" with: Your mail to 'Mailman' with the subject Please Work Is being held until the list moderator can review it for approval. The reason it is being held: Message has implicit destination Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: I'm at a loss here. Would someone be so kind as to point me in the right direction?? Thanks in advance! Kindest Regards, Bill -- 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/brenth%40uca.edu -- 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/tkeller%40bbn.com -- 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/ r.barrett%40openinfo.co.uk -- 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] Email posts get posted to the wrong list!
I have a similar problem if I have another mailing list on the mailing list as a recipient. I.e. each site in my company has its own list and then I have a general list which sends to each of those lists. The other time I have the problem is if I send an email to a list and to other recipients as well, i.e. TO: [EMAIL PROTECTED], [EMAIL PROTECTED] I have done newalias and can only assume that it is something in mailman that does not like sending automatically to other lists or when other recipients is included in the TO: line. At 07:43 AM 08/15/2003 -0500, Brent Herring wrote: At the risk of stating the obvious, did you run the newaliases command after editing your aliases file? Brent. D. Brent Herring Computer Services University of Central Arkansas >>> "William Knechtel" <[EMAIL PROTECTED]> 8/14/2003 4:24:24 PM >>> Hello All! I'm trying to set up Mailman 2.1.2 on a FreeBSD 4.6 server. I'm using courier-MTA as my mail server software. I've gone through the install procedure, and set up the prescribed umbrealla list called "mailman", and set up a test list, which I'm calling "all". When I sent a message to [EMAIL PROTECTED], it's not actually posting to that list, it's posting to [EMAIL PROTECTED] Now, I've redone the install process (twice), I've verified that the aliases I'm giving courier are correct, and still, the post end up posting to the wrong list. The "mailman" list respond to my attempts to post to "all" with: Your mail to 'Mailman' with the subject Please Work Is being held until the list moderator can review it for approval. The reason it is being held: Message has implicit destination Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: I'm at a loss here. Would someone be so kind as to point me in the right direction?? Thanks in advance! Kindest Regards, Bill -- 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/brenth%40uca.edu -- 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/tkeller%40bbn.com -- 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] Contents of Mailman-Users digest
---Message original--- De : [EMAIL PROTECTED] Date : vendredi 15 août 2003 00:13:44 A : [EMAIL PROTECTED] Sujet : Mailman-Users Digest, Vol 11, Issue 38 Send Mailman-Users mailing list submissions to [EMAIL PROTECTED] To subscribe or unsubscribe via the World Wide Web, visit http://mail.python.org/mailman/listinfo/mailman-users or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of Mailman-Users digest..."-- 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] Email posts get posted to the wrong list!
Bill On Friday, August 15, 2003, at 12:31 am, William Knechtel wrote: Please forgive my misuse of the term "umbrella list". I made an incorrect correlation. :-) Now, for your peruasal, I'm posting the contents of my alias files. I have mailman installed in /usr/local/mailman/psi-np.org. My MTA uses maildirs, very much like Qmail, and in fact uses the same style of aliasing, if your familiar with the way .qmail works, though in my case, the files are .courier. My maildirs are in /usr/local/mail/psi-np.org/. So, here are my aliases for both "mailman" and "all": I do not use courier myself but, at first glance, your alias stuff looks OK to me, but what do I know. You might be able to check out what Mailman and courier think are happening by correlating the MTA mail log with Mailman's $prefix/logs/vette log. The vette log should have an entry for the mail being held for moderation by the 'wrong' list which confirms the list that MM thinks it was posted to, and the message ID. When you look at the MTA log entry for the message ID, does the expected listname appear as the list alias to which the MTA says it is delivering that message as recorded in the matching MTA log entry. If it does not, that would tend to reinforce the idea that this is an aliases handling problem with the MTA. If it does, it suggests a new and interesting problem in MM. Let me know how you get on. Richard mailman (found in /usr/local/mail/psi-np.org/mailman/): .courier: |/usr/local/mailman/psi-np.org/mail/mailman post mailman .courier-admin: |/usr/local/mailman/psi-np.org/mail/mailman admin mailman .courier-bounces: |/usr/local/mailman/psi-np.org/mail/mailman bounces mailman .courier-confirm: |/usr/local/mailman/psi-np.org/mail/mailman confirm mailman .courier-join: |/usr/local/mailman/psi-np.org/mail/mailman join mailman .courier-leave: |/usr/local/mailman/psi-np.org/mail/mailman leave mailman .courier-owner |/usr/local/mailman/psi-np.org/mail/mailman owner mailman .courier-request: |/usr/local/mailman/psi-np.org/mail/mailman request mailman .courier-subscribe: |/usr/local/mailman/psi-np.org/mail/mailman subscribe mailman .courier-unsubscribe: |/usr/local/mailman/psi-np.org/mail/mailman unsubscribe mailman And all (found in /usr/local/mail/psi-np.org/all/): .courier: |/usr/local/mailman/psi-np.org/mail/mailman post all .courier-admin: |/usr/local/mailman/psi-np.org/mail/mailman admin all .courier-bounces: |/usr/local/mailman/psi-np.org/mail/mailman bounces all .courier-confirm: |/usr/local/mailman/psi-np.org/mail/mailman confirm all .courier-join: |/usr/local/mailman/psi-np.org/mail/mailman join all .courier-leave: |/usr/local/mailman/psi-np.org/mail/mailman leave all .courier-owner: |/usr/local/mailman/psi-np.org/mail/mailman owner all .courier-request: |/usr/local/mailman/psi-np.org/mail/mailman request all .courier-subscribe: |/usr/local/mailman/psi-np.org/mail/mailman subscribe all .courier-unsubscribe: |/usr/local/mailman/psi-np.org/mail/mailman unsubscribe all So, the Aliases are correct. I don't blame you for doubting me on this one, and I don't think you argumentative, I'd do the same if the roles were switched. Would you have any ideas where else I could look?? Kindest regards, Bill -Original Message- From: Richard Barrett [mailto:[EMAIL PROTECTED] Sent: Thursday, August 14, 2003 4:36 PM To: William Knechtel Cc: [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Email posts get posted to the wrong list! On Thursday, August 14, 2003, at 10:24 pm, William Knechtel wrote: Hello All! I'm trying to set up Mailman 2.1.2 on a FreeBSD 4.6 server. I'm using courier-MTA as my mail server software. I've gone through the install procedure, and set up the prescribed umbrealla list called "mailman", Why do you refer to the 'mailman' list as an umbrella list? This term has a specific meaning for Mailman lists being that for a list whose members are other lists. and set up a test list, which I'm calling "all". When I sent a message to [EMAIL PROTECTED], it's not actually posting to that list, it's posting to [EMAIL PROTECTED] Now, I've redone the install process (twice), I've verified that the aliases I'm giving courier are correct, Without wishing to be argumentative, if the Mailman mail delivery wrapper is called correctly by the MTA then the mail will be accepted for and processed on behalf of the correct list. If it is getting to the wrong list then the Mailman mail delivery wrapper is not being called correctly and typically this is because the mail aliases are incorrect. and still, the post end up posting to the wrong list. The "mailman" list respond to my attempts to post to "all" with: Your mail to 'Mailman' with the subject Please Work Is being held until the list moderator can review it for approval. The reason it is be
[Mailman-Users] how to add more information about the users of alist
Hi : ALL How can I add more information (like name, phone office place etc.) for the subscribers of a mailing list Thanks in advance. Regards, Subhasis -- 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] Define stuff per list or language?
Hi,
You can re-define the charset for English language in mm_cfg.py.
Add following lines will do.
def _(s):
return s
add_language('en', _('English (USA)'), 'iso-8859-1')
del _
Anders Norrbring wrote:
Hiya all!
I've found the really nice feature in 2.1 to have custom templates for each
list and/or language available.
But, there's one important (to me, anyway) variable I can't seem to find any
possibility to customize per language, so if anyone knows how, please help!
The variable is 'member_moderation_notice'. Since we run a couple of dual
language lists it kinda important to set. We have both English and Swedish
languages on those lists, and as many of you know, we Scandinavians (and
others) use extended ASCII in our texts, so if I use any of those, they show
up correctly when a user have set his/her language to Swedish, but if the
language option is set to English, then it's a mess in the mail sent out as
moderation/reject e-mail.
Due to the fact that I haven't found any customization function for that
specific parameter, I have to include both Swedish and English explanatory
text in the response e-mail, and it really sucks when a user gets a mail
full of å and alikes just because I can't set one string per
language.
Please point out to me how it can be done!
Thank you!
Anders Norrbring
Norrbring Consulting
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
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] Email posts get posted to the wrong list!
At the risk of stating the obvious, did you run the newaliases command after editing your aliases file? Brent. D. Brent Herring Computer Services University of Central Arkansas >>> "William Knechtel" <[EMAIL PROTECTED]> 8/14/2003 4:24:24 PM >>> Hello All! I'm trying to set up Mailman 2.1.2 on a FreeBSD 4.6 server. I'm using courier-MTA as my mail server software. I've gone through the install procedure, and set up the prescribed umbrealla list called "mailman", and set up a test list, which I'm calling "all". When I sent a message to [EMAIL PROTECTED], it's not actually posting to that list, it's posting to [EMAIL PROTECTED] Now, I've redone the install process (twice), I've verified that the aliases I'm giving courier are correct, and still, the post end up posting to the wrong list. The "mailman" list respond to my attempts to post to "all" with: Your mail to 'Mailman' with the subject Please Work Is being held until the list moderator can review it for approval. The reason it is being held: Message has implicit destination Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: I'm at a loss here. Would someone be so kind as to point me in the right direction?? Thanks in advance! Kindest Regards, Bill -- 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/brenth%40uca.edu -- 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] SPAM getting through on moderated lists
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > "jam" == John A Martin > "Re: [Mailman-Users] SPAM getting through on moderated lists" > Thu, 14 Aug 2003 12:34:21 -0400 jam> 2. Cause something like the following to be run as root jam>either whenever the Mailman aliases are modified or, less jam>well, periodically by cron. This converts the Mailman jam>aliases file, excluding the loop detection alias, into a jam>Postfix access table. jam> egrep -v jam> '^$|^#|^mailman-loop' sed 's/^\([^:]*\):.*$/\1 550 Bogus Mail jam> From/'> /etc/postfix/check-list-bmf jam> postmap /etc/postfix/check-list-bmf jam>The above bash script assumes Mailman and Postfix jam>installed from recent Debian packages. That is pure rubbish. I should never post untested anything that even looks like a script or suchlike. I'm too prone to big oversights as above. The above produces 'email-address-pattern action' pairs from the aliases using only the 'name' part of the alias which does not (in general) give an appropriate 'email-address-pattern' for the Postfix access table. The script above could be modified to produce an 'email-address-pattern' of the form '[EMAIL PROTECTED]' which would work. However, if the Postfix/Mailman host is dedicated to the mailing lists with a hostname like lists.example.com and it also serves Postfix style virtual domain for mailing lists something like lists.foo.tld then the Postfix access table could look something like ,[ /etc/postfix/check-list-bmf ] lists.example.com 550 Bogus Mail From lists.foo.tld 550 Bogus Mail From lists.bar.tld 550 Bogus Mail From ` with a line for the Mailman host and each Postfix style virtual domain used for Mailman lists. This access table needs maintenance (postmap) only when virtual domains are added or removed. When employed in the context jam> 3. In /etc/postfix/main.cf jam> smtpd_recipient_restrictions = jam> ... jam>permit_mynetworks jam> ... check_sender_access jam> hash:/etc/postfix/check-list-bmf jam> ... jam> permit this will reject incoming mail using SMTP 'mail from:' our host or any of the FQDN hostnames used for (Postfix style) mail virtual domains. This should AFICT do no harm. The Sendmail equivalent should also be even easier without using the aliases, no? HTH jam -BEGIN PGP SIGNATURE- iD8DBQE/PM+WUEvv1b/iXy8RAohvAJ4tkWlcYUrNnloI1AlbTQkLRuXDDwCdGlGq l7w+o7uamuHHA+BhYuR87sY= =9Bp4 -END PGP SIGNATURE- -- 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] Define stuff per list or language?
Alright, thanks.. :)
I haven't tried it yet, I'll do it as soon as my server comes up again.
However, that's not "as nice" as I should prefer.. Isn't there a chance to
have separately defined messages for each list or language? That would be
really good to always have all messages, mails and web pages in the users
chosen language. With the solution you propose here, I still need to make
the outgoing e-mail a dual language one.
Later,
Anders Norrbring
Norrbring Consulting
-> Subject: Re: [Mailman-Users] Define stuff per list or language?
->
-> Hi,
->
-> You can re-define the charset for English language in mm_cfg.py.
-> Add following lines will do.
->
-> def _(s):
-> return s
-> add_language('en', _('English (USA)'), 'iso-8859-1')
-> del _
->
->
-> Anders Norrbring wrote:
->
-> > Hiya all!
-> >
-> > I've found the really nice feature in 2.1 to have custom templates for
-> each
-> > list and/or language available.
-> >
-> > But, there's one important (to me, anyway) variable I can't seem to
-> find any
-> > possibility to customize per language, so if anyone knows how, please
-> help!
-> >
-> > The variable is 'member_moderation_notice'. Since we run a couple of
-> dual
-> > language lists it kinda important to set. We have both English and
-> Swedish
-> > languages on those lists, and as many of you know, we Scandinavians
-> (and
-> > others) use extended ASCII in our texts, so if I use any of those, they
-> show
-> > up correctly when a user have set his/her language to Swedish, but if
-> the
-> > language option is set to English, then it's a mess in the mail sent
-> out as
-> > moderation/reject e-mail.
-> >
-> > Due to the fact that I haven't found any customization function for
-> that
-> > specific parameter, I have to include both Swedish and English
-> explanatory
-> > text in the response e-mail, and it really sucks when a user gets a
-> mail
-> > full of å and alikes just because I can't set one string per
-> > language.
-> >
-> > Please point out to me how it can be done!
-> >
-> > Thank you!
-> >
-> > Anders Norrbring
-> > Norrbring Consulting
--
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
