Mailman 3 February 2006 - Mailman-Users

Re: [Mailman-Users] add_members
by Allan Hansen Feb. 28, 2006

Feb. 28, 2006

Mark, Bingo! The script from the sourceforge site works fine. Here are the diffs between that version and the version that Apple is providing. Note the change of address of Foundation and the ill-fated option in the Apple-supplied version to disable mail for the new subscriber. (< is official version, > is Apple's version). A bit of nosing around on the sourceforge site shows that the address was changed on the main cvs branch from version 2.16 to version 2.17 on 8/17/05. The copyright notice on both 2.17 and Apple's version are both 1998-2003. None of the versions 2003 and later has Apple's changes, as you also noted. So Apple's version does, indeed, appear to be an Apple hack gone awry. I suppose it could be fixed by extracting the address before sending the member to setDeliveryStatus, but I'll refrain from that. Thank you for the sourceforge reference. It will simplify my scripts. Allan The differences: 17c17 < # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. --- > # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. 54a55,58 > --enable-mail=<y|n> > -e <y|n> > Enable user mail deilvery options. > 79a84 > from Mailman import MemberAdaptor 127c132 < def addall(mlist, members, digest, ack, outfp): --- > def addall(mlist, members, digest, ack, outfp, enable): 137a143,146 > if enable == 1: > mlist.setDeliveryStatus(member, MemberAdaptor.ENABLED) > else: > mlist.setDeliveryStatus(member, MemberAdaptor.BYADMIN) 146a156,160 > if enable == 1: > mlist.setDeliveryStatus(member, MemberAdaptor.ENABLED) > else: > mlist.setDeliveryStatus(member, MemberAdaptor.BYADMIN) > 149d162 < 153c166 < 'a:n:r:d:w:h', --- > 'a:n:r:e:d:w:h', 154a168 > 'enable-mail=', 168a183 > enable_mail = 1 184a200,206 > elif opt in ('-e', '--enable-mail'): > if arg.lower()[0] == 'y': > enable_mail = 1 > elif arg.lower()[0] == 'n': > enable_mail = 0 > else: > usage(1, _('Bad argument to -3/--enable-mail: %(arg)s')) 235c257 < addall(mlist, nmembers, 0, send_welcome_msg, s) --- > addall(mlist, nmembers, 0, send_welcome_msg, s, enable_mail) 238c260 < addall(mlist, dmembers, 1, send_welcome_msg, s) --- > addall(mlist, dmembers, 1, send_welcome_msg, s, enable_mail) 256d277 < At 22:20 -0800 2/27/06, Mark Sapiro wrote: >Allan Hansen wrote: >> >>I'm starting with an empty list called Test and a file, Long, >>with a subscriber (me) in long format, and another file, Short, >>with a subscriber (me) in short format: >> >>// Empty list >>$/usr/share/mailman/bin/list_members -f Test >><nothing> >> >>// The files Long and Short >>$cat Long >>Allan Hansen <hansen(a)rc.org> >> >>$cat Short >>hansen(a)rc.org >> >>// Here's the traceback from add_members: >>$add_members -r Long Test >>Traceback (most recent call last): >> File "/usr/share/mailman/bin/add_members", line 277, in ? >> main() >> File "/usr/share/mailman/bin/add_members", line 257, in main >> addall(mlist, nmembers, 0, send_welcome_msg, s, enable_mail) >> File "/usr/share/mailman/bin/add_members", line 157, in addall >> mlist.setDeliveryStatus(member, MemberAdaptor.ENABLED) >> File "/usr/share/mailman/Mailman/OldStyleMemberships.py", line 338, in setDeliveryStatus >> self.__assertIsMember(member) >> File "/usr/share/mailman/Mailman/OldStyleMemberships.py", line 113, in __assertIsMember >> raise Errors.NotAMemberError, member >>Mailman.Errors.NotAMemberError: Allan Hansen <hansen(a)rc.org> > > >This is apparently some Apple modified add_members script. The line >numbers don't correlate with any distributed Mailman 2.1.x, and the >standard script does not call the setDeliveryStatus() method at all. > > ><snip> >> >>// Now, let's try removing same. We have a problem: >>$/usr/share/mailman/bin/remove_members -f Long Test >>No such member: Allan Hansen <hansen(a)rc.org> > > >Yes, I mentioned this previously. remove_members does not accept the >'long' format, but then if you're removing a member, you probably >don't care about the 'name'. > > >>The above shows that 'add_members' and 'remove_members' don't understand >>the long format that is readily accepted by 'sync_members' and output by >>'list_members'. > > >Well, my add_members does. I think Apple broke yours. You might try >getting a recent add_members from ><http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/bin/add_members>, >and see if that works for you. > >-- >Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, >San Francisco Bay Area, California better use your sense - B. Dylan -- _________________________________________________________________ | Allan Hansen, Ph.D. | | P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home: | | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: allan.hansen(a)ugs.com hansen(a)rc.org | | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_|

2 2

Re: [Mailman-Users] Question about g-zipped mail archives -attachment folders/files?
by Mark Sapiro Feb. 28, 2006

Feb. 28, 2006

Dave Yeats wrote: >On 2/28/06, Mark Sapiro <msapiro(a)value.net> wrote: >> Also, a .gz (gzipped) file does not contain a hierarchy of folders and >> files unless it is a gzip of a .tar or other archive. Where are these >> coming from in your case? > >I'm looking at http://mail.gnome.org/archives/evince-list/ > >> This looks like some mail.gnome.org specific way of dealing with the >> plain text archive. > >Must be. I thought it was weird, too. I'll double-check that the >child folders don't contain anything new, and go from there. Actually, I've looked at http://mail.gnome.org/archives/evince-list/2006-January.txt.gz, and I see the issue is with the way you are expanding the gzip file. If I expand the file with gunzip, I get 2006-January.txt = 98890 bytes. If I expand with Stuffit Deluxe with the "create surrounding folder" and "further expansion" options off, I get the same thing, but if I set those options on, I get a 2006-January.txt folder containing files 2006-January.txt.attachment00 = 1876 bytes 2006-January.txt.attachment01 = 277 bytes 2006-January.txt.attachment02 = 88537 bytes signature.asc = 188 bytes signature_1.asc = 188 bytes What is happening is Stuffit is parsing the email into separate messages. The answer is don't use Stuffit, or if you do, turn off the "further expansion" option. -- Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Re: [Mailman-Users] Question about g-zipped mail archives - attachment folders/files?
by Dave Yeats Feb. 28, 2006

Feb. 28, 2006

I'm looking at messages posted to a mailman-driven open-source development email list (on mail.gnome.org/archives), and I've downloaded the g-zip archives I want. When I extract the files, I get one .txt file, and one or more "attachment" folders (with the suffix .txt.attachment00, .txt.attachment01, etc.) which, in turn, contain additional "attachment" files (with suffixes .txt.attachment00.attachment00, .txt.attachment00.attachment01, etc.). I don't think these are attachments in the usual sense of "attachment" in email programs. I don't think other file attachments are allowed on this list. It looks like the the first .txt document (at the root) contains all of the messages, but I was hoping someone could verify that for me. Have you ever dealt with this? Any help you could offer would be appreciated. Dave Yeats

2 1

Reg CallId in CRCX
by geetha Feb. 28, 2006

Feb. 28, 2006

Hi all, Can any of you tell me how to validate the below scenario? "Ensure that the IUT sends CRCX including Callid which is unique within the list of call agents that control the same gateway." IUT in the above scenario is Call Agent(MGC). Kindly tell me the test procedure for the above scenario? Any help will be appreciated. Thanks in advance, Geetha. -- geetha geethkrish_t(a)fastmail.net -- http://www.fastmail.fm - I mean, what is it about a decent email service?

1 0

add_members
by Allan Hansen Feb. 28, 2006

Feb. 28, 2006

Problem: list_members -f -o <file> <list> generates a file of members in the following format: name_of_subscriber <email_of_subscriber> sync_members -f <file> <list> takes a file of members in the above format. add_members -r <file> <list> crashes with a traceback when given a file in the above format. The crash appears to happen in OldStyleMemberships.py add_members appears to strip all whitespace from the file. Do I have a mixed bag of incompatible scripts or is this the expected behavior at this time. I'm running Mac OS X 10.4.5 The above is not terribly critical, as I can combine list_members and sync_members to do what I otherwise would do with just add_members. Thanks, Allan -- _________________________________________________________________ | Allan Hansen, Ph.D. | | P.O. Box 2423, Cypress, CA 90630, U.S.A. | | | | Work: Home: | | Phone: +1-714/952-6015 +1-714/875-8870 | | Fax: +1-714/952-6746 | | Email: allan.hansen(a)ugs.com hansen(a)rc.org | | WWW: http://www.ugs.com http://www.rc.org/ | | | |_Anything is possible with the right tools and right information_|

2 3

Multiple mailing lists
by Nigel Ridley Feb. 27, 2006

Feb. 27, 2006

Hi, I read the documentation: http://www.gnu.org/software/mailman/mailman-install/index.html and it looks pretty complicated (and I'm not sure if I could do all of what is required on my hosted website). I have a website with a Mailman list (using cpanel - which came with the hosting plan) and I would like to have multiple mailing lists. Basically they would be announcement lists having the same content but in several different languages. Q. What is the best way to set up such a system? The problem using cpanel is that it defaults Mailman to English and my hosting company said it would be better to install Mailman in my own space: <quote> You would have to install a copy of mailman under your own space to take advantage of the language packs. Any change we would make to the serverwide install would just be overwritten by cpanel when next it updated. <end quote> Any suggestions would be appreciated. Nigel Ridley -- It's not a problem -- it's a learning opportunity. --

7 8

Re: [Mailman-Users] How to stop these Non-sense mails?
by Steven Jones Feb. 27, 2006

Feb. 27, 2006

I would suggest; 1) Sendmail ~ has settings to filter spam like if the domain (DNS lookup) does not exist, reject it. Other smtp/mta applications have similar settings. Do a google, for these things, there is lots of info. 2) The single most effective anti-spam system I have seen is grey listing, take a look at it. 3) Also setting mailman to not take posts from anyone but subscribers. Regards Steven -----Original Message----- From: mailman-users-bounces+steven.jones=vuw.ac.nz(a)python.org [mailto:mailman-users-bounces+steven.jones=vuw.ac.nz@python.org] On Behalf Of Jim Popovitch Sent: Monday, 27 February 2006 4:55 p.m. To: Kabilan L Cc: mailman-users(a)python.org Subject: *****SPAM***** Re: [Mailman-Users] How to stop these Non-sense mails? Get some good spam prevention software. Also make sure that your MTA is properly validating who is sending you email (check for thinks like reverse DNS lookups, RBL listings, SPF, DKIM, etc). -Jim P. Kabilan L wrote: > Hai!!!! > > I am getting lot spam-mails.The following are the examples. > How can i stop these things!!! > > From: carolwhitaker_tc(a)pacbell.net on Sun Feb 26 21:34:01 2006 > Subject: Stocks That Rock > Cause: Post by non-member to a members-only list > > From: attorney(a)ci.garland.tx.us on Sun Feb 26 21:58:59 2006 > Subject: S0FT C1alis, branded quality > Cause: Post by non-member to a members-only list > > From: wilmawallace(a)fordofsouthholland.com on Sun Feb 26 23:41:36 2006 > Subject: Photoshop software for 80 % 0ff at Diane's softgroup > Cause: Post by non-member to a members-only list > > From: mallory.ncamp_bc(a)land-5.com on Mon Feb 27 01:58:17 2006 > Subject: The Stock Profiler > Cause: Post by non-member to a members-only list > > From: jrobison(a)1-800-arkansas.com on Mon Feb 27 03:00:06 2006 > Subject: (no subject) > Cause: Post by non-member to a members-only list > > > Help me Please! Thank You all > > > Kabilan.L > Department of Electrical Engineering > IIT Madras > Chennai - 600 036 > Tamil Nadu, INDIA > > > "The secret to winning football games is working more as a team, less as > individuals. I play not my 11 best, but my best 11." ->Knute Rockne > > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users(a)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/jimpop%40yahoo.com > > Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp > ------------------------------------------------------ Mailman-Users mailing list Mailman-Users(a)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/steven.jones%40vuw. ac.nz Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

1 0

Re: [Mailman-Users] add_members
by Patrick Bogen Feb. 27, 2006

Feb. 27, 2006

I don't know the answer, but you could always use a bit of perl glue to convert the first format to something add_members will understand more readily... If I knew what the second part was, I'd offer a script to do so. As a stopgap, you can get just a list of addresses by: cat <file> | cut -d'<' -f 2 | cut -d'>' -f 1 (Append this with '> <file>' without quotes if you want to save it back to some file) - Patrick Bogen On 2/26/06, Allan Hansen <hansen(a)rc.org> wrote: > Problem: > > list_members -f -o <file> <list> > generates a file of members in the following format: > name_of_subscriber <email_of_subscriber> > > sync_members -f <file> <list> > takes a file of members in the above format. > > add_members -r <file> <list> > crashes with a traceback when given a file in the above format. > > The crash appears to happen in OldStyleMemberships.py > add_members appears to strip all whitespace from the file. > > Do I have a mixed bag of incompatible scripts or is this the expected > behavior at this time. I'm running Mac OS X 10.4.5 > > The above is not terribly critical, as I can combine > list_members and sync_members to do what I otherwise would do with > just add_members. > > Thanks, > > Allan > -- > _________________________________________________________________ > | Allan Hansen, Ph.D. | > | P.O. Box 2423, Cypress, CA 90630, U.S.A. | > | | > | Work: Home: | > | Phone: +1-714/952-6015 +1-714/875-8870 | > | Fax: +1-714/952-6746 | > | Email: allan.hansen(a)ugs.com hansen(a)rc.org | > | WWW: http://www.ugs.com http://www.rc.org/ | > | | > |_Anything is possible with the right tools and right information_| > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users(a)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/pdbogen%40gmail.com > > Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp > -- - Patrick Bogen

3 3

[Fwd: problem migrating mailman 2.0.8 to 2.1.7]
by apap+mailman-users＠auth.gr Feb. 27, 2006

Feb. 27, 2006

I have trouble upgrading an old installation of mailman-2.0.8 into mailman-2.1.7 (Gentoo Linux with Python 2.4.2). While installing the new version on top of the old, the "update" utility is invoked, but then it fails with "AttributeError: topics". No list gets migrated. The same error is produced if I use "withlist" with any old list. Recreating the lists seems to loose too much user configuration, although it is fairly easy to accomplish. The system currently serves approx 60 mailing lists. I found relevant discussions on this list, but not any really helpful answers (yet) How can I overcome the "AttributeError: topics" error? Is it trivial? Apostolis Papayanakis ---------------------------------------------------------------------------------------------------- mailman # update -f # "acc" is a list created with 2.0.8 Upgrading from version 0x20008f0 to 0x20107f1 getting rid of old source files Updating mailing list: acc Traceback (most recent call last): File "/usr/local/mailman/bin/update", line 790, in ? errors = main() File "/usr/local/mailman/bin/update", line 680, in main errors = errors + dolist(listname) File "/usr/local/mailman/bin/update", line 193, in dolist mlist = MailList.MailList(listname, lock=0) File "/usr/local/mailman/Mailman/MailList.py", line 130, in __init__ self.Load() File "/usr/local/mailman/Mailman/MailList.py", line 664, in Load self.CheckValues() File "/usr/local/mailman/Mailman/MailList.py", line 746, in CheckValues for name, pattern, desc, emptyflag in self.topics: File "/usr/local/mailman/Mailman/MailList.py", line 146, in __getattr__ raise AttributeError, name AttributeError: topics alpha mailman # cat logs/error Feb 16 16:46:43 2006 (28917) couldn't load config file /usr/local/mailman/lists/acc/config.pck [Errno 2] No such file or directory: '/usr/local/mailman/lists/acc/config.pck' Feb 16 16:46:43 2006 (28917) couldn't load config file /usr/local/mailman/lists/acc/config.pck.last [Errno 2] No such file or directory: '/usr/local/mailman/lists/acc/config.pck.last' ---------------------------------------------------------------------------------------------------- mailman # bin/withlist test1 # "test1" is a list created with 2.0.8 Loading list test1 (unlocked) Traceback (most recent call last): File "bin/withlist", line 297, in ? main() File "bin/withlist", line 275, in main r = do_list(listname, args, func) File "bin/withlist", line 194, in do_list m = MailList.MailList(listname, lock=LOCK) File "/usr/local/mailman/Mailman/MailList.py", line 130, in __init__ self.Load() File "/usr/local/mailman/Mailman/MailList.py", line 664, in Load self.CheckValues() File "/usr/local/mailman/Mailman/MailList.py", line 746, in CheckValues for name, pattern, desc, emptyflag in self.topics: File "/usr/local/mailman/Mailman/MailList.py", line 146, in __getattr__ raise AttributeError, name AttributeError: topics ---------------------------------------------------------------------------------------------------- mailman # bin/withlist mailman # "mailman" is a list created with 2.1.7 Loading list mailman (unlocked) The variable `m' is the mailman MailList instance >>> Finalizing

3 2

Restricting Members Posts
by Ashif Zubair Feb. 26, 2006

Feb. 26, 2006

Hi, I am using Mailman Ver: 2.1.6 I want to make my Mailing list a newsletter subscription type service.. where the Subscriber can not post.. On the documentation its written that in the privacy options page, i can find the option of disabling of posting of subscribers except Moderators and Administrator... But i am unable to find that setting in the privacy option of Mailman.. so i want to inquire that where is that option.. i am unable to find it in any page of Mailman (ver:2.1.6) all i wnat is that the subscribers to my list can't post except administrator or moderators. Thanks alot.. awaitng reply.. Thanking you in anticipation.. Webmaster www.milano-pizza.co.uk

3 3