Re: [Mailman-Users] take me off the list
On Monday 14 July 2003 21:01, Dana Hollar wrote: please rmove my email [EMAIL PROTECTED] from your email posting lists. Thank you At the bottom of EVERY POST to the list appears this statement: Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/user%40domain.tld Of course, your information is in the posts you receive instead of the generic information I used for this example. Kyle -- It is better to know nothing than to have learned nothing. --Chinese fortune cookie -- 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] Where are the user lists?
On Wednesday 28 May 2003 11:15, Raquel Rice wrote: You're so smart, figuring that out. Perhaps, you should do my CC:ing for me, since I can't handle it myself? Raquel, I sent that note to you off-list. I don't appreciate you sending your impertinent reply to the list. I apologized to you off-list if you misinterpreted my note, but that was before I saw that you had included the list in your reply -- I now publicly retract that apology. I have found your previous posts to the list to be informed, helpful, and friendly, which leaves me a bit puzzled about your notes from today. If you wish to discuss this matter further, please do so privately as I'm sure none of the list subscribers cares to see any more details of what is apparently turning into a personal spat over nothing. My apologies to the rest of the list, but since Raquel brought this matter public I felt I should rebut publicly. At this point I don't intend to make any more on-list comments about this matter. Kyle -- 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] Plain Text
On Monday 24 March 2003 16:06, Staven Bruce wrote: We have a RedHat 8.0 Linux server running the latest version of Mailman atop a Sendmail MTA. Whenever I send a message to a mailing list, it always arrives to the recipients in plain text, even when I'm using another font. I compose the messages in Outlook usually, and want to be able to use different colored backgrounds, different fonts, etc. Can I do this with Mailman? Staven, don't take the following comments personally. Although I would strongly discourage you from sending HTML email (it's annoying, usually unnecessary, and most competent sysadmins consider it a security hazard), if you really, *really* want to pass HTML through your mailing list you should have a look at the content filtering settings for your list. convert_html_to_plaintext defaults to on (for good reason). You should also check with your Exchange administrator to see whether the Exchange server is the one converting to plain text (again, for good reason). Bear in mind that even if you change your Mailman and Exchange settings, there is no guarantee the recipient will view the HTML -- I have my MUA configured to show only plain text due to security and spam control considerations. Kyle -- It is better to know nothing than to have learned nothing. -fortune cookie proverb -- 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
On Thursday 13 March 2003 10:20, Bolanle Akinpelu wrote: I can't add members from the stdin using the add_member command. For some reason, EOF characters does not bring an end to the members list addedd via stdin I've had that problem too, so now I use echo (when I'm not using the web-based interface): [mailman:~]$ echo Jane Doe [EMAIL PROTECTED] | bin/add_members -n - list Kyle -- It is better to know nothing than to have learned nothing. -fortune cookie proverb -- 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] Old question, oft repeated
On Wednesday 12 March 2003 21:42, Jon Carnes wrote: You might want to check around for a different rpm (or install from source). The first time I installed Mailman, I tried to do it from the Red Hat binary RPM. Red Hat apparently packaged the Mailman RPM on the assumption that it would be used with Sendmail. I futzed around for a while and finally decided to just install from source. Now whenever I install Mailman I don't even bother with the provided RPMs, I download the latest source package and use it to create my own binary RPM on that system. It's just like doing a make install except that you still get the benefits RPM brings to the table. It doesn't add more than about 5 minutes or less to the process. BTW I entered a bug report on this subject in Red Hat's Bugzilla quite a long time ago, but to my knowledge there has been no action on it. Kyle -- It is better to know nothing than to have learned nothing. -fortune cookie proverb -- 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] Problem solved: it was the MTA
But, from the point of view of mailman, once the correct Delivery_Module was specified in Defaults.py, it works fast as a whistle. That was a typo, right? There is ample warning in the documentation (and, IIRC, in the Defaults.py file itself) that changes go in mm_cfg.py, not in Defaults.py. Kyle -- It is better to know nothing than to have learned nothing. -fortune cookie proverb -- 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] restrict unsubscribe?
On Tuesday 14 January 2003 13:53, Christopher Adams wrote: Is there a way to prevent users from unsubscribing without list administrator approval? With v2.1, yes. Kyle -- It is better to know nothing than to have learned nothing. -fortune cookie proverb -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Re: Every day
On Wednesday 08 January 2003 08:40, Ivan Van Laningham wrote: What makes you think that message is coming from Mailman? That looks like a message from stock Redhat processes. You might be right, but I never received those messages until Mailman was installed on RH 6.1, and I have continued to receive them daily through several changes/upgrades of RH to and including 7.3. I think it's perfectly normal to suspect something that was install the day before the messages started. It may be perfectly normal, but it's also perfectly presumptuous. From the tmpwatch man page: When changing directories, tmpwatch is very sensitive to possible race conditions and will exit with an error if one is detected. It does not follow symbolic links in the directories it's cleaning (even if a symbolic link is given as its argument), will not switch filesystems, and only removes empty directories and regular files. Since it will not switch filesystems, tmpwatch needs to know on what mount point each filesystem is mounted. The way to do that is to read /etc/mtab. There is no direct connection between Mailman and tmpwatch or /etc/mtab, so your assumption that Mailman is at fault is plain wrong. It is possible that if you installed Mailman from a binary RPM some random person created, it might fiddle with /etc/mtab; however, your gripe then would be with the person who created the package incorrectly. It's also possible (neigh, likely) that other (unrelated) changes were made or software installed in the same session with Mailman. If you've only done in situ upgrades since the time your /etc/mtab permissions got hosed, it's quite likely that the permissions haven't been changed. An rpm -qf /etc/mtab will reveal that the file isn't part of any RPM package thus an upgrade wouldn't in and of itself touch the file. This is all a very drawn-out way of saying it's not Mailman's fault. It's a system administration issue. Kyle -- Since the general civilizations of mankind, I believe there are more instances of the abridgment of the freedom of the people by gradual and silent encroachments of those in power than by violent and sudden usurpations. -James Madison -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman needs a silently discard option
On Tuesday 07 January 2003 16:27, Dustin Clampitt wrote: Mailman needs a mechanism for either silently discarding posts from non-members, Upgrade to 2.1. It's the admins who are getting spammed. Throw the crap away and send the admin notification of the discard. How is that silently discarding the post? All you've done is replace the spam from random miscreants with spam from your own system. Kyle -- Since the general civilizations of mankind, I believe there are more instances of the abridgment of the freedom of the people by gradual and silent encroachments of those in power than by violent and sudden usurpations. -James Madison -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Converting 2.0 to 2.1
On Thursday 02 January 2003 21:40, Barry A. Warsaw wrote: MJ 2.) can we switch back to 2.0.13 easily in case we encounter a MJ problem or do the DBs get converted somehow? Yes, of course they do! No, you cannot easily downgrade, so I'd suggest making backups first if you're concerned. This might be a good opportunity to remind folks that prudent system administration practice dictates one make not only frequent, scheduled backups, but also a one-off backup before upgrading software. I'm sure we all know that already, but it's easy to become complacent. Kyle -- Since the general civilizations of mankind, I believe there are more instances of the abridgment of the freedom of the people by gradual and silent encroachments of those in power than by violent and sudden usurpations. -James Madison -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] How many is too many?
On Friday 27 December 2002 01:03, The Berean wrote: I'm doing some research in an attempt to find the ceiling on how many users I can have on a Mailman powered listserv. I don't mean to be pedantic, but you used the term listserv eight times in your note. Listserv is a registered trademark for mailing list manager software by Lsoft Inc. I believe the generic term you were looking for is list server. I have no connection with Lsoft and have never used their software. I just feel it's important to make the distinction between their commercial software and the freeware Mailman. Of course we all know Mailman is better! :) Sorry I don't have an answer to your question about the practical limit on the size of an interactive list. I imagine it depends largely on how active the subscribers are. Kyle -- Since the general civilizations of mankind, I believe there are more instances of the abridgment of the freedom of the people by gradual and silent encroachments of those in power than by violent and sudden usurpations. -James Madison -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] New lists do not work
On Friday 15 November 2002 09:31, Ralph Boersema wrote: Our installation set up by a good programmer who is not too familiar with mailman. He doesn't have the time to participate in this list. I would suggest that the first order of business is to hire a system administrator. As long as you have people who don't have time to keep your infrastructure up and running and familiarize themselves with the software the company is using, you will continue to have problems. For example, who is going to apply security patches? Who is going to perform backups? Who is going to get new machines up and running? Who is going to install and configure new software? Who is going to ensure that the infrastructure continues to meet the needs of the company? These are just some of the functions required to maintain the technology assets of any company, large or small. Then there's the obvious question of who is going to fix things when they stop working. 3. New lists that are created do not work. 4. It is initially possible to administer the list, but when the first message is sent, it does not forward and, after that, it is no longer possible to access the administration page. The admin access page comes up, you type in the password, but, then, nothing happens. On the subject of mail from new lists not forwarding, did you forget to update the aliases file and/or run newaliases? As for the problems accessing the administration page, more information would be helpful. Was there anything of significance in the logs? Are your Mailman and Python up to date? What version of Mailman are you running? Are there files in the locks directory that could be hosing things? Seriously, think about hiring a system administrator. Every company larger than three or four people that uses computers should have one. If your company is small and doesn't have the resources to retain a full-time administrator, you could hire someone part-time or outsource the function. Kyle -- Since the general civilizations of mankind, I believe there are more instances of the abridgment of the freedom of the people by gradual and silent encroachments of those in power than by violent and sudden usurpations. -James Madison -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] New lists do not work
On Friday 15 November 2002 09:31, Ralph Boersema wrote: 4. It is initially possible to administer the list, but when the first message is sent, it does not forward and, after that, it is no longer possible to access the administration page. The admin access page comes up, you type in the password, but, then, nothing happens. One other suggestion I just thought of... run ~mailman/bin/check_perms. Kyle -- Since the general civilizations of mankind, I believe there are more instances of the abridgment of the freedom of the people by gradual and silent encroachments of those in power than by violent and sudden usurpations. -James Madison -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] installation difficulties
On Wednesday 13 November 2002 21:48, Emil Volcheck wrote: Upgrading to Python 2.2.2 and Mailman 2.0.13 did the job. We also had to redo the aliases in /etc/postfix/mailinglist . What I do on my boxes is put mailman's alias file in /var/mailman, along with the rest of the mailman installation. It is uid gid mailman so that I don't have any problems doing a bin/newlist -o, and it means I can back up /var/mailman and have everything I would need if I had to restore. Another benefit is I can give someone else the mailman password and they can do everything they would need to do without giving them root access. Kyle -- Since the general civilizations of mankind, I believe there are more instances of the abridgment of the freedom of the people by gradual and silent encroachments of those in power than by violent and sudden usurpations. -James Madison -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] installation difficulties
On Monday 11 November 2002 17:26, Emil Volcheck wrote:
Question: do the aliases for individual lists as well as the
mailman and mailman-owner have to be in /etc/aliases or
/etc/aliases.db or does it suffice to put them in the MySQL (?)
databases used by Postfix?
The standard location for the aliases file in Postfix as delivered by
Red Hat is /etc/postfix/aliases[.db]. If you (either knowingly or
unknowingly) also installed Sendmail then you will have an /etc/aliases
as well, but don't be fooled. Postfix does not use MySQL out of the
box -- you would have to configure it to do so.
The problem I'm encountering is that a posting to the list results
in error code 1:
---
...Command died with status 1:
/home/mailman/scripts/post concerns
---
I assume you've checked to see that /home/mailman/scripts/post exists?
You don't mention which version of Red Hat you're using, but the
Mailman RPM that comes with the 7.x series puts everything in
/var/mailman. Make sure your alias shouldn't be
/var/mailman/scripts/post concerns.
Nov 11 09:23:01 2002 qrunner(15283): precedence =
msg.get('precedence', '').lower()
Nov 11 09:23:01 2002 qrunner(15283): AttributeError : 'string'
object has no attribute 'lower'
I've seen this error before but I don't remember how I fixed it. Make
sure everything is up to current versions (Mailman and Python in
particular). You might have better results getting the source code for
the current Mailman (2.0.13 IIRC) and compiling it yourself instead of
using Red Hat's RPM. I had a lot of trouble with Mailman on Red Hat
7.2 and 7.3 until I compiled it from source, and it's been running
absolutely trouble-free since.
Kyle
--
Since the general civilizations of mankind, I believe there are more
instances of the abridgment of the freedom of the people by gradual
and silent encroachments of those in power than by violent and sudden
usurpations.
-James Madison
--
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: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Another newlist aliases problem?
On Sunday 10 November 2002 14:03, David Gordon wrote: Set up test list list. Web interface working. Subscription requests generates confirmation of subscription mail. Replying to that mail (to [EMAIL PROTECTED]) sees that mail routed via my catch-all mail account for that domain. The answer is quite simple... Yes, I have done the business with the aliases document. Here's what it says... mailman: [EMAIL PROTECTED] mailman-owner: mailman test-request: mailman ## test mailing list ## created: 09-Nov-2002 mailman test:|/home/mailman/mail/wrapper post test test-admin: |/home/mailman/mail/wrapper mailowner test test-request:|/home/mailman/mail/wrapper mailcmd test test-owner: test-admin As you can see, you have test-request defined twice. I don't know about Sendmail specifically, but some other MTAs use the first definition of an alias that they encounter. Take out the test-request: mailman line and that will probably solve your problem. Kyle -- Since the general civilizations of mankind, I believe there are more instances of the abridgment of the freedom of the people by gradual and silent encroachments of those in power than by violent and sudden usurpations. -James Madison -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Another newlist aliases problem?
Oops, I jumped the gun a little bit on my last reply. On Sunday 10 November 2002 14:03, David Gordon wrote: Somewhere in Sendmail I have a line @mydomain1.tld user1 You should probably remove that. Kyle -- Since the general civilizations of mankind, I believe there are more instances of the abridgment of the freedom of the people by gradual and silent encroachments of those in power than by violent and sudden usurpations. -James Madison -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mail List Encryption
On Wednesday 25 September 2002 12:40, [EMAIL PROTECTED] wrote: I am inclined to agree with Jon (that what you really want is for your list members to do the encrypting) That would only work in a shared-secret environment. If you want to use public key crypto, then Mailman would have to decrypt the message from the sender using Mailman's private key and recrypt a copy to each recipient using the recipient's public key. If its important that the messages be encrypted on their way -out-, its important that they be encrypted on their way -in-. Absolutely! -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Mail List Encryption
On Wednesday 25 September 2002 13:43, J C Lawrence wrote: A common definition of a crypted list: Mail sent to the list is crpyted with the list's public key. The list uncrypts the mail and broadcasts it to each member. Prior to transmission each message is crypted with that individual member's public key. Guess I should have read all the new messages before replying :) -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Subscription options help
On Thursday 19 September 2002 22:38, Jim Popovitch wrote: rant Mailman should allow unsubscriptions via confirmed email w/o requiring a password, there is no valid reason to require the password when unsubscribing via email. /rant Do you know how easy it is to spoof email? That's the valid reason Mailman requires a password even when unsubscribing via email. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] strip-mime and aol
On Monday 09 September 2002 09:39, Barry A. Warsaw wrote: IMO, HTML mail isn't the problem, HTML-only mail is. As far as universal readability goes, you are correct. However, HTML mail can (whether it includes a text/plain part or not) have security implications that RFC-compliant (plain text only) mail does not. Some of the security problems include embedded active content and web bugs. Some clients let the user disable those features, but in that case the mail becomes about as functional as text/plain and you might as well not waste the overhead for HTML. Kyle -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] RPM'ed version of Mailman
On Monday 09 September 2002 15:20, Joel Webb wrote: Is there anyway to change the options inside of a RPM'ed version of Mailman?? I would like to change the --with-cgi-ext extension. Install the source rpm, edit the spec file to your liking, then rpm -bb mailman.spec. You will end up with a binary RPM than you can then install. The advantages of doing the extra work of generating the binary RPM are that you can save the RPM off for future use (rebuilding the system or installing on an additional system) and the package is recorded in the RPM database for easy verification, dependency checking, or uninstallation Kyle. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] strip-mime and aol
On Saturday 07 September 2002 01:47, Fuzzy wrote: Get real, Rickie, this is the 21st Century, HTML here to stay. It's called freedom to send email in whatever format I want. And we have the freedom to not read mail in whatever format we want. If you want your mail to have the widest possible readership, keep that in mind. You seem to be unaware of the costs... Don't forget about the security implications, which is the main reason I dislike HTML mail. I agree that it takes up too much space, isn't RFC-compliant, and not all clients can read it. Those are good reasons not to send it. However, being a security specialist, HTML mail's security risks are tops on my sh** list. I suppose that if two people with the tools to view such an email, want to correspond via non-text email, that's thier business. For mailing list mail one has to insure the usablity of the information. To me that means text/plain format. Good point. Kyle -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Mail Man Problems - No aliases being created.
On Saturday 07 September 2002 08:50, Angel Gabriel wrote: Everytime I create a new list, no aliases are being added to sendmail. Mail cannot be recieved, and I get user not found. Are you remembering to use the -o option to $mailman/bin/newlist? -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Question:
On Friday 06 September 2002 01:17, Rajib A. Momen wrote: It seems kind of redundant to sign up on a web site, enter a password, and then have to reply to a message to confirm, since you just signed up! This seems to be a FAQ, although I don't recall if it is addressed in the actual FAQ document. Anyway, there are two reasons to have the confirmation message even when signing up on the web site. First, it verifies that the email address the web user entered is valid and can receive mail. Second, it helps prevent one person from maliciously subscribing another. Remember that anyone can enter any email address on the web form, but it's likely that only the subscribee will receive (and therefore reply to) the confirmation message. Secondly, I was wondering if it was possible to set a list so that you could unsubscribe from it by email without inputting the password. Another pseudo-FAQ. The password requirement helps prevent malicious or unauthorized unsubscribes. Anyone who is capable of using an Internet email client should also be capable of providing the password in order to unsubscribe. It's really not difficult. Kyle -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] SMTPDirect.py using sleep command
On Thursday 05 September 2002 17:12, Kory Wheatley wrote: What I have done to maybe slow down the delivery to sendmail that creates the queue files then delivers them to our mail server is in the Mailman SMTPDirect.py I have used the sleep command to sleep after delivering so that our mail server can catch up before the next batch is delivered, this way its not being bombarded. It seems to me like the right way to handle your situation would be to adjust the QueueLA and RefuseLA parameters on the HP/UX box's sendmail. That way you fix the situation no matter what the source of the bombardment is, as opposed to just fixing it from your Mailman server. From /etc/sendmail.cf on a generic system: # load average at which we just queue messages O QueueLA=8 # # load average at which we refuse connections O RefuseLA=12 Just change QueueLA to, say, 1 and RefuseLA to, say, 2 or 3. Once the load average drops back below the threshold, sendmail will start accepting/delivering mail as appropriate. Just a thought. Kyle -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Fwd: Adding 1 user to a list via command line?
On Monday 26 August 2002 11:03, Devin Atencio wrote: I can't seem to figure out the correct syntax to add 1 e-mail address to a list from the command line? /home/maiman/bin/add_members -n - -w n test [EMAIL PROTECTED] any help with the correct syntax? try: echo [EMAIL PROTECTED] | bin/add_members -n - -w n test -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] NAT translation problems?
On Thursday 22 August 2002 13:10, Drew Krause wrote: Hello, a few subscribers with city and county government email addresses are complaining that our list mail is not getting to them. A peek at our mail logs confirms this. One of their system administrators noted that their server makes use of 'NAT translation', a concept new to me. NAT stands for Network Address Translation. Therefore, NAT translation is a redundant and incorrect term. That aside, it is a scheme whereby one set of IP addresses is dynamically translated (usually by a firewall or firewall-like device) to another address or set of addresses and back again. For example, say machine A has an IP address of 192.168.1.5, machine B's address is 192.168.1.6, and machine F is the firewall. Let's also say that F is configured to translate between 192.168.1.0 and 192.168.50.0. If A tries to browse www.python.org, it has to go through F to get to the Internet. F translates A's address to something in the 192.168.50/24 address space, for the sake of simplicity let's say it's 192.168.50.5. F then sends the address-translated packet on to its destination (www.python.org). The destination has no way of knowing that the packet came from any address other than 192.168.50.5. It sends a reply back, which F translates back to A's address and A eventually receives it. Similarly, B might also try to browse www.python.org, and F might translate B's address to 192.168.50.6. Or, F could translate B's address to the same 192.168.50.5 address to which A's was translated, in which case F would have to keep state information in order for returning packets to make their way back to the proper destination (A or B). What I've explained above is greatly simplified in the interest of space. For a more in-depth explanation of NAT, go to http://www.itp-journals.com/Network_address_translation_NAT_page1.htm. Has anyone else had this problem? (Is it indeed a mailman issue?) It is not a Mailman issue per sé. Mailman only works in conjunction with an MTA (mail transport agent) and an HTTP server. If NAT is properly configured so that SMTP and HTTP pass to the proper destinations, Mailman should work. From what you described, it sounds like the problem is on the government agency's end. Kyle -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Members vs. Subscribers
On Tuesday 16 July 2002 11:09, Bob Weissman wrote: This is a linguistic subtlety in the English version of Mailman. [...] In my own Mailman 2.0.11 installation, I've scoured the sources for user-visible strings and changed member to subscriber everywhere I thought it was important. I would like to suggest this become an official terminology change for future versions of Mailman. I'd like to reinforce the point. When posts to my lists from dues-paying members are rejected because they are from non-members it raises some hackles. The distinction between a member of the organization and a subscriber to one of the organization's lists needs to be clear. I'm also eagerly awaiting the capability mentioned in a previous thread to summarily reject (or simply ignore) posts from non-subscribers to a subscribers-only list instead of requiring the list administrator to reject them. Kyle -- 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] Admin mail interface?
Forgive me if this has been discussed already, but I wonder about a mail interface for admin functions like approving subscription requests. It would be really convenient if the list owner could simply reply with some incantation to the notice that there is a request pending. Does this feature already exist? I didn't see it mentioned in the listed features or in the feature request database. -- 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
