[Mailman-Users] ?? MM2.1b2 Contains code of W32/Nimda.eml ??
== mailman-2.1b2.tgz ArchiveType: GZ -- mailman-2.1b2.tar Contains code of W32/Nimda.eml == Someone please put my mind at ease. Is this a false virus find? Before testing the beta (2 mo's ago) I checked with symantec --No virus. With AntiVir (current personal release) the above Nimda virus is 'found'. I do not remember the mirror on http://sourceforge.net/project/showfiles.php used but I believe it to be the same as Virginia, North America or telia.dl.sourceforge.net_sourceforge ... I repeated the virgina download and rescanned .. same 'virus' code found... should I be concerned?
Re: [Mailman-Users] ?? MM2.1b2 Contains code of W32/Nimda.eml ??
At 11:32 PM 7/10/02 -0700, you wrote: == mailman-2.1b2.tgz ArchiveType: GZ -- mailman-2.1b2.tar Contains code of W32/Nimda.eml == Someone please put my mind at ease. Is this a false virus find? Before testing the beta (2 mo's ago) I checked with symantec -- No virus. With AntiVir (current personal release) the above Nimda virus is 'found'. I do not remember the mirror on http://sourceforge.net/project/showfiles.phphttp://sourceforge.net/project/showfiles.php used but I believe it to be the same as Virginia, North America or telia.dl.sourceforge.net_sourceforge ... I repeated the virgina download and rescanned .. same 'virus' code found... should I be concerned? There's an inactive piece of a nimda file in one of the test files, not even complete, it's just the mime wrapper that a nimda once came, in, with the payload replaced by X; apparently it's just enough to trigger *that* scanner, but the other scanners realize that it's not the same file. Your scanner is operating on a *really* narrow pattern, since there's no payload in the note, it has to be picking up either the subject of the message in the test file, or the filename of the fake mime attachment... -- 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
Re: [Mailman-Users] Hardware Requirements
On Thursday 11 July 2002 09:13 am, [EMAIL PROTECTED] wrote: Agree with all that. Am using Compaq 380, 5 x 36 Gb hard discs and hardware Raid5, 1Gb RAM and 512Mb swap, Reiserfs. However on these machines mailman is sending batches of mail to separate MTA/relays. That's a good idea, too, because it offloads the retries of failed SMTP from the Mailman server to the separate relays. In that kind of an environment, my idea for a RAMDISK-based /var/spool/mqueue might not be so far-fetched, on the Mailman machine iteslf, because the mail would only be there for a matter of seconds rather than for hours or days. What method are you using to determind what relay gets each outbound message transaction? Scott -- ---+-- Scott Courtney | I don't mind Microsoft making money. I mind them [EMAIL PROTECTED] | having a bad operating system.-- Linus Torvalds http://4th.com/| (The Rebel Code, NY Times, 21 February 1999) | PGP Public Key at http://4th.com/keys/courtney.pubkey -- 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
Re: [Mailman-Users] Subscribe/Un-Subscribe via e-mail, notweb
Hello! --On Tuesday, July 09, 2002 2:51 PM +0200 Detlef Neubauer [EMAIL PROTECTED] wrote: | I would prefer to create some sort of an HTML link on my web site | which, when clicked, will launch the users on mail software and | have the Send and Subject line already filled in that will either | SUBSCRIBE or UNSUBSCRIBE the user. | | a | href=mailto:[EMAIL PROTECTED]?subject=subscribe;body=sub | scribe The subscribe e-mail works great! But, passing unsubcribe or un-subscribe is not recognized. Do you have an idea as to how I can accomplish this? Thanks! Best regards, Gerry Doyon | | | Mit freundlichen Grüßen | Detlef Neubauer | | -- | .oO GnuPG Key auf http://www.keyserver.net/ Oo. | | | -- | 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 | -- Gerry Doyon -- 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
Re: [Mailman-Users] Mailman with Postfix and OS X
Greg Westin hath declared on Thursday the 11 day of July 2002 :-: I think I'm all set now... sorry about the trouble. But if anyone can tell me any particular changes I should make to my configuration so that things work better with Postfix, please let me know. I think I did what the install FAQ recommends for Postfix, creating another aliases database in the mailman folder, etc, but other than that I don't think I've done anything Postfix-specific. 3. I know there was something else, but I've forgotten it. Here's a question: can anyone tell me how to get Postfix to start automatically when I log in? The tutorial I used to set it up gave instructions to do so, but I still have to start it manually every time I restart. If I recall correctly you can replace the sendmail startup script in /System/Library/StartupItems/Sendmail/ with a script that starts postfix, generally /path/to/postfix start. I don't recall if there are Start/Stop/Restart/etc options in that script, I'm sure that you can figure it out... Then just make sure that you have `` MAILSERVER=-YES- '' in /etc/hostconfig so that sendmail (now postfix) will be automatically started on boot. Note, this is from my shabby memory, so I could be mistaken, I'm sure a bit of googling should set you straight. - bobb -- 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
Re: [Mailman-Users] Subscribe/Un-Subscribe via e-mail, not web
Gerry Doyon [EMAIL PROTECTED] writes: Detlef Neubauer [EMAIL PROTECTED] wrote: | a | href=mailto:[EMAIL PROTECTED]?subject=subscribe;body=sub | scribe The subscribe e-mail works great! But, passing unsubcribe or un-subscribe is not recognized. For unsubscribe a password will needed. Do you have an idea as to how I can accomplish this? a href=mailto:[EMAIL PROTECTED]?subject=unsubscribe;body=unsubscribe%20replace%20this%20with%20your%20password;Replace the string replace this with your password with your password/a :-) Not tested. Please send no Cc:. I answer only via the list. Detlef Neubauer -- .oO GnuPG Key auf http://www.keyserver.net/ Oo. -- 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
Re: [Mailman-Users] Hardware Requirements
On Thu, 11 Jul 2002 08:43:06 -0400 Scott Courtney [EMAIL PROTECTED] wrote: On Thursday 11 July 2002 12:14 am, J C Lawrence wrote: a) Add more RAM. Number of queue runners for your MTA Here's a silly question: Is it worth considering *really* upping the RAM, say to two gigabytes, and then putting /var/spool/mqueue on a RAM disk? Probably not, for two simple reasons: 1) Too small. He has a fairly large number of lists and the high probability of flash bursts in traffic, both in terms of numbers of messages and total size of outbound spool. I could trivially see a RAM disk that small being exhausted. 2) No battery backup (the other side of the stability issue you mention). Doing it properly would involve something like a Rupp solid state disk (which is also big enough for a spool) with battery backup -- which would also happen to blow his budget. Another approach, much easier: Buy a lot of RAM, and rely on Linux using the excess as disk cache. This is probably a much better idea. MTAs are limited by physical disk IO. They do lots of reads and writes (which can be cached), and more importantly, do lots of calls to sync() and close() which explicitly flush those caches down to metal. I suspect my first paragraph above is not practical. I toss it out onto the list not so much in expectation of anyone trying it, but just to see if anyone thinks it's even worth experimentation. I would never even consider this for regular email service, but in many contexts lists are considered a lower priority with regard to reliability. And even if some outbound messages were lost in the (infrequent) crash scenario, they would still be available in the archives. Ignoring the use of battery backed up solid state disks (which I know of a few large mail shops using), this assumes that archiving is synchronous with receipt and broadcast. This is currently the case with mailman 2.0 if you still use Pipermail, and IIRC not true with v2.1. b) drop the CPU speed if it will save any money, though I suspect that's as low as you can buy these days. With respect, I disagree. The price difference between CPU speeds below about 1 GHz is insignificant. Err, that's what I said. It's nice to have some CPU headroom so that you can do things like compile the next version of Mailman on the same machine, in a test directory, without impacting production. That wouldn't be a problem even with a quite smaller CPU. Speaking of which, disabling locatedb on this machine is probably a good idea. True, along with other general system tuning. The big question is still what basic mail volumes are. Without that we're just guessing. A second reason for not short-changing this machine's processor: Any server in this kind of heavy-duty production will be tricky to upgrade from a logistical standpoint. If you build in some headroom, you postpone for more years the need to migrate all of this to a new machine. True. He asked for 3 years. c) go SCSI with /var/spool/MTA, /var/log, and /var/www on different spindles. Yes, definitely. Also, for a system that will have this many files on it, consider using a journaling filesystem rather than ext2. I have had superb success with Reiserfs, but there are also IBM's JFS, SGI's XFS, and the ext2-compatible ext3. Reiserfs has significant performance improvement over ext2 and ext3, especially on small files, and it might be a good choice for this system. Journalling actually is a loss in this sort of scenario due to the extra tracking and buffer copy overhead. The nice thing about ReiserFS and XFS in particular is that the other optimisations they make more than make up for that cost. Please see the large mail system stuff I wrote up in the FAQ last year. Just out of curiosity, what are you planning to do for backup media? You may need a secondary SCSI controller channel to prevent contention for bus bandwidth during large backup runs. It could be a lower-cost SCSI board than the primary, probably. Ahem. He doesn't have enough SCSI targets to make that a problem. Remember how SCSI disconnect works. -- J C Lawrence -(*)Satan, oscillate my metallic sonatas. [EMAIL PROTECTED] He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. -- 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
[Mailman-Users] archives only display list e-mail
I apologize if this gets posted multiple times. I accidentally sent the message from the wrong account, one not subscribed to the list, and so it's tied up waiting for admin approval. Hopefully the admin will see this and just delete it. --- I just set up Mailman, and everything seems to be working fine, but when I look at my archives, I notice that it displays the list e-mail address next to every person's name, rather than that person's e-mail address. Is that normal? Is there any way to change that? Any help would be appreciated. Thank you, Greg Westin [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
Re: [Mailman-Users] Hardware Requirements
On Thu, 2002-07-11 at 16:59, J C Lawrence wrote: [I have reordered the quotes here - sorry if I have broken the meaning] Journalling actually is a loss in this sort of scenario due to the extra tracking and buffer copy overhead. The nice thing about ReiserFS and XFS in particular is that the other optimisations they make more than make up for that cost. But full data journalling on an MTA type system can gain you performance by having the disk head basically moving linearly as the journal writes. On a fast turnround system by the time it comes to writing out the actual file contents and directory entries and stuff, the file is no longer pertinant (ie already been processed/delivered etc) and so the write is optomised out MTAs are limited by physical disk IO. They do lots of reads and writes (which can be cached), and more importantly, do lots of calls to sync() and close() which explicitly flush those caches down to metal. ... for various definitions of metal - ie a flushed journal for ext3, and probably some form of NVRAM for a decent hardware RAID controller. c) go SCSI with /var/spool/MTA, /var/log, and /var/www on different spindles. Yes, definitely. Also, for a system that will have this many files on it, consider using a journaling filesystem rather than ext2. I have had superb success with Reiserfs, but there are also IBM's JFS, SGI's XFS, and the ext2-compatible ext3. Reiserfs has significant performance improvement over ext2 and ext3, especially on small files, and it might be a good choice for this system. SCSI or even better a *good* hardware RAID controller. Filesystems are a religious issue but I still keep hearing more mentions of resiserfs going completely tits-up for my liking. Great ideas but there still seem to be some problems there. Nigel. -- [ Nigel Metheringham [EMAIL PROTECTED] ] [ - Comments in this message are my own and not ITO opinion/policy - ] -- 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
Re: [Mailman-Users] Hardware Requirements
On Thu, 11 Jul 2002 09:39:00 -0400 Scott Courtney [EMAIL PROTECTED] wrote: On Thursday 11 July 2002 09:13 am, [EMAIL PROTECTED] wrote: In that kind of an environment, my idea for a RAMDISK-based /var/spool/mqueue might not be so far-fetched, on the Mailman machine iteslf, because the mail would only be there for a matter of seconds rather than for hours or days. Why bother? Just have Mailman deliver directly to the remote MTA, and then have that system sub-route from there if needed/wanted? -- J C Lawrence -(*)Satan, oscillate my metallic sonatas. [EMAIL PROTECTED] He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. -- 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
Re: [Mailman-Users] Hardware Requirements
On Thursday 11 July 2002 11:59 am, J C Lawrence wrote: On Thu, 11 Jul 2002 08:43:06 -0400 Scott Courtney [EMAIL PROTECTED] wrote: On Thursday 11 July 2002 12:14 am, J C Lawrence wrote: a) Add more RAM. Number of queue runners for your MTA Here's a silly question: Is it worth considering *really* upping the RAM, say to two gigabytes, and then putting /var/spool/mqueue on a RAM disk? Probably not, for two simple reasons: 1) Too small. He has a fairly large number of lists and the high probability of flash bursts in traffic, both in terms of numbers of messages and total size of outbound spool. I could trivially see a RAM disk that small being exhausted. Agreed, though with the addition of the dedicated MTA relay servers and just using the local SMTP to send to them at LAN speeds, this might not be an issue. 2) No battery backup (the other side of the stability issue you mention). Doing it properly would involve something like a Rupp solid state disk (which is also big enough for a spool) with battery backup -- which would also happen to blow his budget. I make the assumption of a UPS on *any* machine that is used as a server. [...] I wrote: I suspect my first paragraph above is not practical. [...] And from your comments, it appears that my first suspicion of my own idea was correct: it's not practical. Thanks for the enlightenment about Sendmail internals; I didn't realize it did so many explicity sync() calls. Ignoring the use of battery backed up solid state disks (which I know of a few large mail shops using), this assumes that archiving is synchronous with receipt and broadcast. Good point. b) drop the CPU speed if it will save any money, though I suspect that's as low as you can buy these days. With respect, I disagree. The price difference between CPU speeds below about 1 GHz is insignificant. Err, that's what I said. Sorry, then...that wasn't the way I read your post. I stand corrected. [...] c) go SCSI with /var/spool/MTA, /var/log, and /var/www on different spindles. Yes, definitely. Also, for a system that will have this many files on it, consider using a journaling filesystem rather than ext2. [...] Journalling actually is a loss in this sort of scenario due to the extra tracking and buffer copy overhead. The nice thing about ReiserFS and XFS in particular is that the other optimisations they make more than make up for that cost. Which was my point, though re-reading my post I appear not to have expressed it very well. I meant use of a journaled filesystem because (1) they are generally faster than ext2, though as you correctly point out this is for reasons other than the journaling itself, and (2) because in the event of an abrupt shutdown, doing an fsck on 120G would be, ummm, nontrivial. I'm sorry I wasn't very clear on this. My internal subtext was much more detailed than what I wrote. Please see the large mail system stuff I wrote up in the FAQ last year. I browsed that when I first started with Mailman, but I'll go back and re-read again for interest. :-) Just out of curiosity, what are you planning to do for backup media? You may need a secondary SCSI controller channel to prevent contention for bus bandwidth during large backup runs. It could be a lower-cost SCSI board than the primary, probably. Ahem. He doesn't have enough SCSI targets to make that a problem. Remember how SCSI disconnect works. Fair enough, and good point. Thanks for the enlightening reply to my post. Scott -- ---+-- Scott Courtney | I don't mind Microsoft making money. I mind them [EMAIL PROTECTED] | having a bad operating system.-- Linus Torvalds http://4th.com/| (The Rebel Code, NY Times, 21 February 1999) | PGP Public Key at http://4th.com/keys/courtney.pubkey -- 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
Re: [Mailman-Users] Hardware Requirements
On 11 Jul 2002 17:14:36 +0100 Nigel Metheringham [EMAIL PROTECTED] wrote: On Thu, 2002-07-11 at 16:59, J C Lawrence wrote: [I have reordered the quotes here - sorry if I have broken the meaning] Hehn. A favoured habit of mine. But full data journalling on an MTA type system can gain you performance by having the disk head basically moving linearly as the journal writes. On a fast turnround system by the time it comes to writing out the actual file contents and directory entries and stuff, the file is no longer pertinant (ie already been processed/delivered etc) and so the write is optomised out Excellent point. The added latency can allow a lazy journal to nuke the transaction. SCSI or even better a *good* hardware RAID controller. The real problem with proffering advice here is that we don't know his loading. Without some idea of his mail volumes and delivery targets (if he's lucky the majority will be local LAN) its really tough to say what he'd need for hardware. Still, I do like the Mylex DAC960 cards... Filesystems are a religious issue but I still keep hearing more mentions of resiserfs going completely tits-up for my liking. Great ideas but there still seem to be some problems there. I can't comment well to this other than to note that I've been running ReiserFS almost exclusively (I've generally left / and /boot as ext2, but that's less than 128Meg combined) for a couple years now on my list servers, desktops, web servers, etc. I had one problem in the early months which may have been exacerbated or caused by a failing drive and a known-bad kernel (the TLB IPI wait bug). Beyond that it has been flawless. As always, its the proverbial personal experience card... -- J C Lawrence -(*)Satan, oscillate my metallic sonatas. [EMAIL PROTECTED] He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. -- 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
Re: [Mailman-Users] Hardware Requirements
On Thu, 11 Jul 2002 13:32:35 -0400 Scott Courtney [EMAIL PROTECTED] wrote: On Thursday 11 July 2002 11:59 am, J C Lawrence wrote: On Thu, 11 Jul 2002 08:43:06 -0400 And from your comments, it appears that my first suspicion of my own idea was correct: it's not practical. Thanks for the enlightenment about Sendmail internals; I didn't realize it did so many explicity sync() calls. You might to look over the RFCs for SMTP and pay particular attention to the bits about guarantees and transaction handling. At each one of those points the systems on both ends have to push the current message state down to metal (or RAID cache etc) and synchronise their states in case one or both of the systems suffers a sudden catastrophic failure (eg power cord pulled) at just the wrong moment. It tends to define a whole lot of sync() and open()/close() calls (which latter force a buffer and inode flush). -- J C Lawrence -(*)Satan, oscillate my metallic sonatas. [EMAIL PROTECTED] He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. -- 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
[Mailman-Users] Archive problem...
I'm using Mailman 2.0.8 and have been having some problems with my archives. I hope someone can give me a suggestion as to how to clear up the mess. Some of the mailing lists are fine, but in a few mailing lists, only the last two months are available from the web menu. Looking in the /usr/local/mailbox/archive/public/newsgroup directory and at the /usr/local/mailbox/archive/public/newsgroup.mbox/newsgroup.mbox makes me think all the data is there. A look at the /usr/local/mailbox/logs/error files shows lots of corrupt file errors. I've copied the traceback for the most recent run on one of the mailing lists. Jul 11 11:46:00 2002 qrunner(1720): Traceback (most recent call last): Jul 11 11:46:00 2002 qrunner(1720): File /usr/local/mailman/Mailman/Archiver/Archiver.py, line 221, in ArchiveMail Jul 11 11:46:00 2002 qrunner(1720): h.processUnixMailbox(f, HyperArch.Article) Jul 11 11:46:00 2002 qrunner(1720): File /usr/local/mailman/Mailman/Archiver/pipermail.py, line 528, in processUnixMailbox Jul 11 11:46:00 2002 qrunner(1720): self.add_article(a) Jul 11 11:46:00 2002 qrunner(1720): File /usr/local/mailman/Mailman/Archiver/HyperArch.py, line 928, in add_article Jul 11 11:46:00 2002 qrunner(1720): self.__super_add_article(article) Jul 11 11:46:00 2002 qrunner(1720): File /usr/local/mailman/Mailman/Archiver/pipermail.py, line 567, in add_article Jul 11 11:46:00 2002 qrunner(1720): article.parentID = parentID = self.get_parent_info(arch, article) Jul 11 11:46:00 2002 qrunner(1720): File /usr/local/mailman/Mailman/Archiver/pipermail.py, line 587, in get_parent_info Jul 11 11:46:00 2002 qrunner(1720): refs = self._remove_external_references(article.references) Jul 11 11:46:00 2002 qrunner(1720): File /usr/local/mailman/Mailman/Archiver/pipermail.py, line 619, in _remove_external_references Jul 11 11:46:00 2002 qrunner(1720): if self.database.hasArticle(self.archive, ref): Jul 11 11:46:00 2002 qrunner(1720): File /usr/local/mailman/Mailman/Archiver/HyperDatabase.py, line 267, in hasArticle Jul 11 11:46:00 2002 qrunner(1720): self.__openIndices(archive) Jul 11 11:46:00 2002 qrunner(1720): File /usr/local/mailman/Mailman/Archiver/HyperDatabase.py, line 245, in __openIndices Jul 11 11:46:00 2002 qrunner(1720): t = DumbBTree(os.path.join(arcdir, archive + '-' + i)) Jul 11 11:46:00 2002 qrunner(1720): File /usr/local/mailman/Mailman/Archiver/HyperDatabase.py, line 68 , in __init__ Jul 11 11:46:00 2002 qrunner(1720): self.load() Jul 11 11:46:00 2002 qrunner(1720): File /usr/local/mailman/Mailman/Archiver/HyperDatabase.py, line 17 3, in load Jul 11 11:46:00 2002 qrunner(1720): self.dict = marshal.load(fp) Jul 11 11:46:00 2002 qrunner(1720): ValueError: bad marshal data Jul 11 11:46:00 2002 (1720) CORRUPT ARCHIVE FOR LIST: comp.unix.bsd.freebsd.misc Thanks, Mike -- Mike Avery [EMAIL PROTECTED] ICQ: 16241692AOL IM: MAvery81230 Phone: 970-642-0282 * Spam is for lusers who can't get business any other way * A Randomly Selected Thought For The Day: A clean desk is a sign of a cluttered desk drawer. -- 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
[Mailman-Users] Mailman home HTML
Am I correct in saying that, by default, accessing mydomain.com/mailman results in an error? Or did I mess something up in the installation? I was thinking about just setting the server to redirect all requests for /mailman to /mailman/listinfo, or something like that... would I run into some problems if I tried to do that? I don't know whether I'd have to set up an index.cgi in mailman's cgi folder, or if I could just set an alias in Apache or something like that. Also, I saw when administering a list that you can change the HTML for a list's home page, but how would one go about changing the HTML for other things, like the listinfo page or something? Would that be a poor idea on my part, or would it just be harmless fiddling? Thanks for contributing to this UNIX-newbie's education, Greg Westin [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
[Mailman-Users] error import paths in File bin/update
Hi First my System-Configuration RedHat 7.3 Python 2.2 Apache 1.3.23 gcc 2.96 sendmail 8.11 I have been tried to run Mailman 2.0.12 and that worked, but I need a german Mailman. So I tried Mailman 2.1b2 with Multi-Lingual Support. I removed the previous version of Mailman and configured the new one with the same configure parameters I used for the old one. But when running make install it ---begin quote--- Traceback (most recent call last): File bin/update, line 44, in ? import paths ImportError: No module named paths make: *** [update] Error 1 ---end quote--- Can anyone help me with that?? -- Best regards, Bjoern Kaiser mailto:[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
[Mailman-Users] customisable Welcome (subscribeack.txt) message
Hello Mailmen :), I've got a problem and hopefully you'll help me to find a way out. I need to customize a Welcome message (subscribeack.txt template) for every list, by other words - I need it to different things for different lists. Are there any way to customize it, as well as I can do subscribe.html or other HTML pages? It'd be just great. Thanks, hope to hear from you shortly. ps. Please, don't reply to the list, I'm not a subscriber yet. -- Alexander Prohorenko -- 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
[Mailman-Users] Migrating from majordomo to mailman
Hi :-) we are thinking of migrating from majordomo to Mailman mainly for 2 reasons : 1- French support 2- Web interface for users and lists administrators. We have over 450 lists in majordomo, with several different configurations. I suppose we are not the first institution to do this migration, so I was wondering if by any chance there would be a script somewhere that would create the mailman lists with the majordomo infos, i.e. subscribers and more important : the parameters for the configuration... I think I am hoping for a miracle with such a script... :-) Any idea that would automate as much as possible that transition would be greatly appreciated Thank you very much :-) Anne Moreau -- 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
[Mailman-Users] problem with Mailman address security?
Here's a wierd one. I run a mailing list which is set to subscriber list visible only to administrator, and it seems that some addresses (if not all) have leaked onto a spam list. - I'm (reasonably) certain the user did not simply use the same address elsewhere -- the user uses sneakemail.com, which generates one-time addresses randomly, and assures me that the addr was used only for my list. - the user has never *posted* to the list, it's an announce-only one. - the /roster/ page is definitely set to admin only visibility, and always has been. - the headers of the message the user received, indicate the spam was sent direct from spammer to user, not via the list itself. Anyway, the list is moderated ;) . Also, I got a copy of the spam to my own address used for that list. So I'm pretty certain the address was scraped somehow. Can anyone suggest a way this is possible with MailMan, without a spammer needing the admin password to scrape the list? Or without them hacking the box in general? --j. -- 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
[Mailman-Users] Delete Users question
On your program, you have a way to add many users at once without them recieving an email. However, I can not find a way to delete a bunch of users without them being notified. I tried setting them no nomail and then unsubscribing them, but they will still recieve the exit message. I thought since you have one way to massively add people, there is also a way to massively delete them as well. Any thoughts? Sorry I did not ask the main user mailing list, but I didnt think just one question merited me joining the list (but that might change as I use mailman more :) ). Thanks, Robert -- 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
[Mailman-Users] Question on Umbrella lists
I'm still using Mailman 2.0 beta - never bothered upgrading as it works fine as a one-way newsletter list. Waiting for 2.1. I understand the concept of Umbrella lists. We run several lists and the membership across the lists runs about 10% -- meaning about 10% of one list is also on a second list. Sometimes we wish to send the same information to both lists, hence the idea of an umbrella list. I guess the question is will that 10% who are members of both lists receive both messages or just one? We're a little worried about duplication. Some people still get mad at things like that not knowing there's such a thing as a delete key. --- The Tenant Network(tm) for Residential Tenants TenantNet(tm): http://tenant.net email: [EMAIL PROTECTED] Information from TenantNet is from experienced non-attorney tenant activists and is not considered legal advice. -- 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
Re: [Mailman-Users] Subscribe/Un-Subscribe via e-mail, not web
Unless the list is set to confirm ... then they will only get subscribed if they mail back the confirmation. My lists are set up to subscribe via the web using multiple checkboxes and PHP...it has worked excellent since it was installed in March 2002I did attempt the unsubscribe in the same way but it didn't function properly and it has since been removed. My site is at: http://lists.paulsfunhouse.com Paul At 01:36 PM 09/07/02, Support Desk wrote: Actually, a form like that could be dangerous; unscrupulous bum could subscribe enemy to multiple lists at once, and although the actual subscriptions would not activate, due to Mailman's required confirmation process, it could easily harass the receiver, and the list manager, for lists that require manager approval, or that send the manager notice of new subs/unsubs. That said, here are some links: Build a custom script for managing subscribers: http://subscriber.newfieldcash.com/ this is especially useful for lists that are on mutiple servers, running multiple listserve clients you mean there are others? and is not specific to Mailman. -- 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
[Mailman-Users] MBOX to Mailman's archive
Hello, I've got a mail list running under different mail list manager. I'd like to migrate the archive of this mail list to Mailman. Can you please help me how can I do this? All I've got is the mbox-styled messages archive from the previous manager. Thanks. -- Alexander Prohorenko -- 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
[Mailman-Users] Archiving and Replys
Hi, I am setting up mailman to replace Lyris as our listserv manager, and so far things are going great. Unfortunately I have come across a small problem, I'm using an external archiver (hypermail - my boss likes its output better than pipermail) which I have set up to work and it will automatically update the archives, but my problem is that replys to messages are not entered into the .mbox file and therefore aren't getting into the archives. I saw a similar question posted but there was no response, I hope someone might have an idea why the .mbox file is not being updated with replys to messages. Thanks for any help. Sherif Karaoglu University of South Florida Academic Computing Department -- 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
[Mailman-Users] Newcomer to Mailman
Hi I am a nex comer to the world of Mailman. I have installed Mailman on my system. I want to know how to attach a file to a mail whcih the mailman sends. Thanks and Regards Bharde Tajuddin -- 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
[Mailman-Users] RELEASED Mailman 2.0.12
I' released Mailman 2.0.12 which fixes a cross-site scripting vulnerability, among other changes. I recommend that folks upgrade their 2.0.x systems to this new version. See below for a NEWS file excerpt. As usual, I've made both full source tarballs and patches available. See http://sourceforge.net/project/showfiles.php?group_id=103 for links to download all the patches and the source tarball. If you decide to install the patches, please do read the release notes first: http://sourceforge.net/project/shownotes.php?release_id=97760 See also: http://www.gnu.org/software/mailman http://www.list.org http://mailman.sf.net Cheers, -Barry snip snip 2.0.12 (02-Jul-2002) - Implemented a guard against some reply loops and 'bot subscription attacks. Specifically, if a message to -request has a Precedence: bulk (or list, or junk) header, the command is ignored. Well-behaved 'bots should always include such a header. - Changes to the configure script so that you can pass in the mail host and web host by setting the environment variables MAILHOST and WWWHOST respectively. configure will also exit if it can't figure out these values (usually due to broken dns). - Closed another minor cross-site scripting vulnerability. -- 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
[Mailman-Users] Surveying list users
I just posted this to list-managers. I think it's relevant enough to mailman users that I'm posting a copy here. Apologies in advance to those who see this twice or see it as noise... I mentioned this a week or so ago as part of another thread. I've been thinking about it ever since, and I've decided to go ahead and try to pull together something to do this. The idea: try to get a real-world, statistically significant view of the average mailing list user. I plan on doing this by creating an online survey (maximum 25 questions), and asking list managers to post a pointer to it on their lists, and list users to ask the list manager to post the pointer (I'm going to explicitly tell users not to do it themselves; I expect to be ignored by some, of course) I'd like to get 10-25,000 users worth of data here. More would be even better. Front end PHP, back end MySQL. I plan on trying to limit it to one submission per email address (using MD5 hashes on the address -- your suggestion welcome for alternatives) so I can try to recognize that I've seen an e-mail address, but not actually store the address for privacy reasons. Failing that, I'll simply set it up so that multiple submissions overwrite each other (last in wins). Part of this is to try to figure out what users REAL preferences are on a large scale -- we've had endless fights over reply-to, over subject line flags, etc, etc. Let's see if we can figure it out once and for all. I also want to try to figure out how these preferences change based on various aspects of the users -- how do newer users differ from experienced ones? That sort of thing. Finally, I want to see if I can figure out where these users are heading -- see if we can get hints of where this stuff will be in a year, or 3. What's this mean for list-managers? I'd like feedback on things you'd like to find out here. Obviously, I'd like you to post the finished survey to your lists, but for now, what I really want are ideas of what to ask, and as I start building the survey forms, to comment on and help improve them, so this stuff will be generally useful to all of us. I don't expect to have a draft of the survey for a few weeks, but please start sending suggestions of what should be on it now. It'll help me focus what ought to be on it. Right now, I see splitting this up into a few sections: 1) about the user: how long on the net, platform, client, etc. 2) functionality issues: html, MIME, reply-to, subject flags, etc. 3) other tools: usenet, IM, etc. 4) lists subscribed to (one reason I want to be very careful about privacy; I don't want people to avoid listing, um, sensitive or adult lists) Since I want to keep this pretty short (25 questions or so, to keep from intimidating users into giving up), I don't think we'll get everything we want. But feel free to suggest things,a nd we'll decide later what to make the priorities... Your thoughts on this more than encouraged... Chuq -- Chuq Von Rospach, Architech [EMAIL PROTECTED] -- http://www.chuqui.com/ Someday, we'll look back on this, laugh nervously and change the subject. -- 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
Re: [Mailman-Users] Hardware Requirements
On Thu, 11 Jul 2002, Scott Courtney wrote: On Thursday 11 July 2002 01:42 pm, J C Lawrence wrote: You might to look over the RFCs for SMTP and pay particular attention to the bits about guarantees and transaction handling. [...] It tends to define a whole lot of sync() and open()/close() calls (which latter force a buffer and inode flush). You're right, of course. It's been several years since I've needed to get into SMTP RFCs in that level of detail. Here is the important section: When the receiver-SMTP accepts a piece of mail (by sending a 250 OK message in response to DATA), it is accepting responsibility for delivering or relaying the message. It must take this responsibility seriously. It MUST NOT lose the message for frivolous reasons, such as because the host later crashes or because of a predictable resource shortage. By my reading of this paragraph it is not acceptable to have a queue on a RAM disk unless the disk is battery backed and won't be affected by a server reboot. Various companies, such as cenatek.com, make hardware that meet these requirements. It isn't very affordable though, and most servers would probably do just as well with a well thought out RAID array (that means avoiding RAID 5, which has very poor performance for small disk writes, and SMTP servers are all about doing tons of small disk writes). alex -- 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
