[Mailman-Users] mailman an sendmail receiveing mails
hi, i have set up mailman on a suse machine with sendmail. when i open the administration site and subscribe i get mails (), but when i sent to the list, the mail never arrives. i have added the aliases in the alias file: ## point mailing list point: |/usr/local/mailman/mail/mailman post point point-admin:|/usr/local/mailman/mail/mailman admin point point-bounces: |/usr/local/mailman/mail/mailman bounces point point-confirm: |/usr/local/mailman/mail/mailman confirm point point-join: |/usr/local/mailman/mail/mailman join point point-leave:|/usr/local/mailman/mail/mailman leave point point-owner:|/usr/local/mailman/mail/mailman owner point point-request: |/usr/local/mailman/mail/mailman request point point-subscribe:|/usr/local/mailman/mail/mailman subscribe point point-unsubscribe: |/usr/local/mailman/mail/mailman unsubscribe point and used the command newaliases with no errors. MTA is manual. whats wrong? thanks yavuz -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] paper clip
I'm sorry to come to the list with this. I have searched for an answer but have not been able to help myself. What can I do about the paper clip that shows up with each post that ha a hyperlinked signature? I allow attachments on my small list, but I would like to get rid of the paper clip Jessie ~ Keepsake Pomeranians ~ web ~ www.mykeepsakes.net New Ch. Keepsakes Star Spangled Banner -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] config.pck user: wwwrun group:mailman
Hi, i have problems with mailman webinterface: when is start and want to login i get the error access denied for data/adm.pw usr= root grp=mailman others = denied when i manually set others to read it works. the same with the lists config files. everytime when i change the configuration or add users to a list, i get an error access denied list/config.pck usr= wwwrun group=mailman others=denied when i again set others to denied than it works, but nect time when i save a change its set to denied again and mailman web dont open. thanks yavuz -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman an sendmail receiveing mails
TRON478 wrote: i have set up mailman on a suse machine with sendmail. when i open the administration site and subscribe i get mails (), but when i sent to the list, the mail never arrives. i have added the aliases in the alias file: ## point mailing list point: |/usr/local/mailman/mail/mailman post point point-admin:|/usr/local/mailman/mail/mailman admin point point-bounces: |/usr/local/mailman/mail/mailman bounces point point-confirm: |/usr/local/mailman/mail/mailman confirm point point-join: |/usr/local/mailman/mail/mailman join point point-leave:|/usr/local/mailman/mail/mailman leave point point-owner:|/usr/local/mailman/mail/mailman owner point point-request: |/usr/local/mailman/mail/mailman request point point-subscribe:|/usr/local/mailman/mail/mailman subscribe point point-unsubscribe: |/usr/local/mailman/mail/mailman unsubscribe point and used the command newaliases with no errors. MTA is manual. whats wrong? What happens to the mail you send to the list? If it bounces, what does the bounce email say? If not, what's in sendmail's maillog? See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.014.htp. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] paper clip
Jessie wrote: I'm sorry to come to the list with this. I have searched for an answer but have not been able to help myself. What can I do about the paper clip that shows up with each post that ha a hyperlinked signature? I allow attachments on my small list, but I would like to get rid of the paper clip If this 'attachment' is the list footer, see http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.039.htp. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] config.pck user: wwwrun group:mailman
TRON478 wrote: i have problems with mailman webinterface: when is start and want to login i get the error access denied for data/adm.pw usr= root grp=mailman others = denied when i manually set others to read it works. the same with the lists config files. everytime when i change the configuration or add users to a list, i get an error access denied list/config.pck usr= wwwrun group=mailman others=denied when i again set others to denied than it works, but nect time when i save a change its set to denied again and mailman web dont open. It seems that either the wrappers in Mailman's cgi-bin/ directory are not group mailman and SETGID, or the SETGID bit is somehow not being honored. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.016.htp. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Nomail members
Paul Tomblin wrote: I'm having two problems with members of a list who are set to no mail but whose email address is no longer valid: - The bounce of the monthly password reminder, even though it is VERPed, is not sufficient to remove them from the list because it's only one bounce. It would be nice if that bounce would trigger some additional probing, possibly immediately going to the you are disabled warnings. It would not be difficult to do a withlist script to list those members with current bounce info and disabled delivery. You could run this a day or so after the password reminders are sent to get a manual list for further manual action. I'm not sure that treating a bounce of a password reminder as an immediate disable for bounce is a good idea. It is after all, just one bounce. If you don't disable members for bounce after one single post bounces, It probably isn't a good idea to do it for password reminders either. Another thought is that password reminders are sent from the 'mailman' list. You could set the alias for mailman-bounces to deliver these to a person. - I send the membership list of one particular list off as a cron job to a friend who has a backup list for that one. But there is no easy way to remove addresses that are set to no mail from the output of list_members. What I want is the opposite of list_members -n to show only members who aren't set to no mail. Have you tried list_members -n enabled? It's not documented, but it works. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Nomail members
Quoting Mark Sapiro ([EMAIL PROTECTED]): I'm having two problems with members of a list who are set to no mail but whose email address is no longer valid: - The bounce of the monthly password reminder, even though it is VERPed, is not sufficient to remove them from the list because it's only one bounce. It would be nice if that bounce would trigger some additional probing, possibly immediately going to the you are disabled warnings. It would not be difficult to do a withlist script to list those members with current bounce info and disabled delivery. You could run this a day or so after the password reminders are sent to get a manual list for further manual action. I'm not sure that treating a bounce of a password reminder as an immediate disable for bounce is a good idea. It is after all, just one bounce. If you don't disable members for bounce after one single post bounces, It probably isn't a good idea to do it for password reminders either. The problem is that the bounce thresholds are set for the people who get mail every mail. The nomail members only get mail once a month, so they'll never be removed. - I send the membership list of one particular list off as a cron job to a friend who has a backup list for that one. But there is no easy way to remove addresses that are set to no mail from the output of list_members. What I want is the opposite of list_members -n to show only members who aren't set to no mail. Have you tried list_members -n enabled? It's not documented, but it works. Oh, shiny! I might have tried that if it was documented. Thanks. -- Paul Tomblin [EMAIL PROTECTED] http://blog.xcski.com/ Panic kills -- Rick Grant (quoting RCAF pilot training) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman an sendmail receiveing mails
On 3/8/07 1:52 AM, TRON478 [EMAIL PROTECTED] wrote: i have set up mailman on a suse machine with sendmail. when i open the administration site and subscribe i get mails (), but when i sent to the list, the mail never arrives. You sent the message to which I'm replying from Gmail. If you sent the test message that way, and it was intended to go back to the Gmail account, it won't. Google is being helpful, and hiding the message that comes back from the list since it thinks you already have a copy. I'm pretty sure this is in the Mailman FAQ, but I seem to be too dumb to find it. (This morning, anyhow.) Of course, if you didn't send the test message from Gmail, then the above isn't the problem. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman an sendmail receiveing mails
The esteemed TRON478 has said: hi, i have set up mailman on a suse machine with sendmail. when i open the administration site and subscribe i get mails (), but when i sent to the list, the mail never arrives. i have added the aliases in the alias file: ## point mailing list point: |/usr/local/mailman/mail/mailman post point point-admin:|/usr/local/mailman/mail/mailman admin point (snip) and used the command newaliases with no errors. MTA is manual. whats wrong? Your aliases file looks correct. I'm not sure what you mean by manual. Sendmail normally runs as background daemons. smmsp 6626 1 0 Feb 17 ?0:01 /usr/lib/sendmail -Ac -q15m root 6628 1 0 Feb 17 ?1:29 /usr/lib/sendmail -bd -q15m Check that all your Mailman qrunners are running. mailman 6903 1110 0 Mar 02 ?0:01 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=RetryRunner:0:1 - mailman 6902 1110 0 Mar 02 ?0:01 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=CommandRunner:0:1 mailman 6897 1110 0 Mar 02 ?1:20 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=BounceRunner:0:1 mailman 6901 1110 0 Mar 02 ? 37:35 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=ArchRunner:0:1 -s mailman 6898 1110 0 Mar 02 ? 46:29 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=OutgoingRunner:0: mailman 6899 1110 0 Mar 02 ?2:47 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=IncomingRunner:0: vancleef 602 493 0 10:24:12 pts/30:00 grep qrun mailman 6900 1110 0 Mar 02 ?0:44 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=VirginRunner:0:1 mailman 6904 1110 0 Mar 02 ?0:01 /usr/local/bin/python /usr/local/mailman/bin/qrunner --runner=NewsRunner:0:1 -s If you can send mail to and from a local non-Mailman account, then your sendmail installation is OK. Important thing is to configure sendmail properly and test it first. You should have sendmail checked out and running in daemon mode before trying to integrate it with Mailman Try sending mail to the -owner account (point-owner) and see if it gets sent to the list administrator addresses. That bypasses any options in the Mailman configuration that apply to list postings. Once that is working try sending a message to your list address. Read your logs. Sendmail shows the send to Mailman (example below, includes demime filter in the pipe) Mar 5 05:32:12 julie sendmail[18773]: [ID 801593 mail.info] l25CW9qH018772: to= |/usr/local/mailman/bin/demime -8bit -x '==' '==/usr/local/mailman/mail/mailman post mylist', ctladdr=[EMAIL PROTECTED] (1/0), delay=00:00:02, xde lay=00:00:02, mailer=prog, pri=33715, dsn=2.0.0, stat=Sent That says that the message went to Mailman. Go to the Mailman logs and check them. If Mailman is not sending out messages to list addresses, the logs generally tell you why it isn't. Hank -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Slow delivery
Hello, I'm using Mailman in conjunction with Exim on FreeBSD 5.3 to support a small mailing list (60 members). All messages have been taking just over 105 seconds to deliver, according to /usr/local/mailman/log/smtp. After searching through the archives to this list, I found that a garbage line in /etc/hosts was responsible for 75 seconds worth of that. Now we're down to consistently just over 30 seconds. Where else should I look for things that could be causing this? Exim only has problems with mail routed through Mailman. Herman Looking for earth-friendly autos? Browse Top Cars by Green Rating at Yahoo! Autos' Green Center. http://autos.yahoo.com/green_center/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Slow delivery
Herman Privyhum sent the message below at 15:14 3/8/2007: I'm using Mailman in conjunction with Exim on FreeBSD 5.3 to support a small mailing list (60 members). All messages have been taking just over 105 seconds to deliver, according to /usr/local/mailman/log/smtp. After searching through the archives to this list, I found that a garbage line in /etc/hosts was responsible for 75 seconds worth of that. Now we're down to consistently just over 30 seconds. Where else should I look for things that could be causing this? Exim only has problems with mail routed through Mailman. End original message. - This may just be the time needed to resolve the dns lookups for the outgoing mail. You may want to consider using a caching dns resolver to cache the sddresses for some reasonable period. Getting the resolved addresses out of cache will be much faster than attempting to resolve them over the network every time. Then again, I could be completely off here and something else is causing the delay. I don't know Exim at all and sendmail only in the barest manner so I cannot be much help beyond this. Dragon ~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Slow delivery
At 3:14 PM -0800 3/8/07, Herman Privyhum wrote: Where else should I look for things that could be causing this? Exim only has problems with mail routed through Mailman. Look at your MTA logs. They should show you when a given message comes in for a given user, and when that is successfully transmitted. I'd be willing to bet you're waiting on DNS timeouts at the remote end for one or more of your users -- their MTA is slowing you down, maybe as a result of trying to do a reverse DNS lookup on your IP address. If you haven't already enabled it, try turning on full personalization, so that you send a unique copy of the message to each recipient. For each recipient, look at the date/time stamp of when the message goes into Exim and when Exim says that the remote end has accepted the message. That should tell you where things are slowing down. Maybe it's not a DNS timeout, maybe it's a timeout of some other sort. Maybe it's a result of doing anti-spam/anti-virus processing on inbound as well as outbound e-mail. Maybe their mail servers are just very slow. But at least you should know where the slowdown is coming from. You may also be able to turn on some increased parallelism in the delivery process, so that other recipients can be handled while you're waiting on the slower sites to respond. But I wouldn't feel bad at getting everything out in 30 seconds. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Nomail members
Paul Tomblin wrote: Quoting Mark Sapiro ([EMAIL PROTECTED]): I'm not sure that treating a bounce of a password reminder as an immediate disable for bounce is a good idea. It is after all, just one bounce. If you don't disable members for bounce after one single post bounces, It probably isn't a good idea to do it for password reminders either. The problem is that the bounce thresholds are set for the people who get mail every mail. The nomail members only get mail once a month, so they'll never be removed. I understand that that is the problem, but they'll never be removed anyway because password reminders come from the site (mailman) list, and any bounced password reminder is returned to mailman-bounces and ignored since the user being reminded is not a member of the mailman list. That being the case, my previous suggestion that you could list delivery disabled members that have current bounce info with a withlist or other script won't work either, because they won't have any bounce info for a bounced password reminder. Thus, I think I'm back to my other thought which is that in the short term, the best you can do is arrange for mail to the mailman-bounces address to be seen by a human. In the longer term (Mailman 2.2) password reminders and the site list are both going away. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Slow delivery
Herman Privyhum wrote: All messages have been taking just over 105 seconds to deliver, according to /usr/local/mailman/log/smtp. After searching through the archives to this list, I found that a garbage line in /etc/hosts was responsible for 75 seconds worth of that. Now we're down to consistently just over 30 seconds. Where else should I look for things that could be causing this? Exim only has problems with mail routed through Mailman. Keep in mind that this SMTP transaction with Exim has 60 RCPT TO commands and responses which is probably where most of the time is spent. If Exim is doing DNS verifies on the recipient domains during the incoming SMTP, 0.5 sec per recipient may not be that bad. The solution is to not do DNS verification on mail from localhost. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.011.htp. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Nomail members
Quoting Mark Sapiro ([EMAIL PROTECTED]): In the longer term (Mailman 2.2) password reminders and the site list are both going away. *All* password reminders are going away? I'm kind of worried about that - I get enough emails from people who say can you change my email address to [EMAIL PROTECTED], I'm pretty sure that without the monthly reminders I'd get three times as many. -- Paul Tomblin [EMAIL PROTECTED] http://blog.xcski.com/ Please say this was followed by a very serious discussion on Right and Wrong involving a blow torch, 220V, a cobra and three East Germans named Georg... -- Robert Uhl -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman an sendmail receiveing mails
[EMAIL PROTECTED] wrote: The esteemed TRON478 has said: and used the command newaliases with no errors. MTA is manual. whats wrong? Your aliases file looks correct. I'm not sure what you mean by manual. MTA = 'Manual' is what you put in mm_cfg.py (actually, you don't need to because it's the default) in order to have Mailman mail you a list of aliases to be manually inserted in /etc/aliases or wherever when you create a new list. Note however that it is 'Manual', not 'manual'. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Nomail members
Paul Tomblin wrote: *All* password reminders are going away? I'm kind of worried about that - I get enough emails from people who say can you change my email address to [EMAIL PROTECTED], I'm pretty sure that without the monthly reminders I'd get three times as many. User passwords are (finally) going to be encrypted, so there's no way to send a reminder. The existing, on demand reminder will be replaced by a reset function of some kind. See http://wiki.list.org/display/DEV/Mailman+2.2. My experience is that the users who take responsibility for themselves will remember their passwords or figure out how to get a reset. The others will ask the list owner even if they received a reminder yesterday. It would be interesting to keep track of requests from users for things they can do for themselves to see if the frequency of requests is greater towards the end of the month. I haven't done this, but I suspect it's not. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mail delivery fails with (-2, 'Name or service not known')
[EMAIL PROTECTED] wrote: When I try to access to python shell with mailman user ( @# su mailman ) I've got a error : This account is currently not available. Try running these as any 'ordinary' user - not root. Also try sending mail using the example in the post at http://mail.python.org/pipermail/mailman-users/2005-May/044746.html. If the x = smtplib.SMTP() in this script succeeds, but there is a failure after that, try adding x.set_debuglevel(1) immediately following x = smtplib.SMTP() -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Nomail members
Quoting Mark Sapiro ([EMAIL PROTECTED]): User passwords are (finally) going to be encrypted, so there's no way to send a reminder. The existing, on demand reminder will be replaced Ohh, good idea. It would be interesting to keep track of requests from users for things they can do for themselves to see if the frequency of requests is greater towards the end of the month. I haven't done this, but I suspect it's not. In my experience, the first day or two of the month is where most people do their own maintenance (unsubscribe, change their address, subscribe a new address), and also where I get the majority of the requests that need the form letter. -- Paul Tomblin [EMAIL PROTECTED] http://blog.xcski.com/ It's 106 light-years to Chicago, we've got a full chamber of anti-matter, a half a pack of cigarettes, it's dark, and we're wearing visors. Engage. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Slow delivery
The esteemed Dragon has said: This may just be the time needed to resolve the dns lookups for the outgoing mail. You may want to consider using a caching dns resolver to cache the sddresses for some reasonable period. Getting the resolved addresses out of cache will be much faster than attempting to resolve them over the network every time. Then again, I could be completely off here and something else is causing the delay. I don't know Exim at all and sendmail only in the barest manner so I cannot be much help beyond this. Maybe this is a good time to ask just how DNS-intensive the non-sendmail MTA's are. I am finishing off the basics on installing sendmail with Mailman, and am including some discussion of the need to install a good fast-response caching DNS server to work with sendmail. There is very little discussion in the sendmail literature about DNS, except for an acknowledgement that sendmail uses DNS intensively if it's in the hosts line in nsswitch.conf (Solaris name). I have to confess that I was a bit slow on the uptake to install local DNS on my systems. The folks at upstream feed, whose DNS servers I was using, said, you do plan to install local DNS, don't you, with a certain pointedness. I dawdled until I could get the 5th edition of Liu and Albitz DNS and BIND (O'Reilly, 2006), which has a chapter on DNS and SMTP mail, and after reading through sat down to install a caching server immediately. The results were just plain startling. I wish I'd done this five years ago. Since then I've installed master and slave servers for my Intranet LAN, but I would heartly recommend having at least a plain caching server on the box that's running the MTA. While all of my experience is with sendmail, I'm inclined to suspect that the other MTA's all can stand a shot of local DNS service. Anybody who can confirm this for Postfix, Exim, etc.? Hank -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Slow delivery
At 8:46 PM -0700 3/8/07, [EMAIL PROTECTED] wrote: Maybe this is a good time to ask just how DNS-intensive the non-sendmail MTA's are. I am finishing off the basics on installing sendmail with Mailman, and am including some discussion of the need to install a good fast-response caching DNS server to work with sendmail. All MTAs I know of are pretty DNS-intensive in their operation. The more anti-spam or anti-virus filtering you do, or the more other things you do to check the incoming mail, the more DNS-intensive that work is going to be. Of course, most MTAs should give you options on how to configure them so that they don't generate any DNS traffic at all, but then what you're doing is effectively turning off about 99.99% of what the MTA is intended to do when handling mail. In this respect, I don't think that sendmail is necessarily much worse or much better than any other MTA. Since then I've installed master and slave servers for my Intranet LAN, but I would heartly recommend having at least a plain caching server on the box that's running the MTA. Years ago, this was actually a bit of a sore point amongst the experts. Some said that you were better off having a smaller number of centralized caching nameservers, which handled all DNS traffic for the entire network. Others said that you're better off having caching nameservers running on each box, to spread that load out. Of course, the issue there is that Box A might do a DNS query of some sort, and retrieve data that could later be used by Box B, but if both machines are running their own nameservers as opposed to a centralized caching nameserver, then both machines will end up doing the same query, causing increased load on the remote end, etc Moreover, large caching nameservers can take up hundreds of megabytes (or even a couple of gigabytes) of RAM, so if you've got servers that are already using lots of RAM to process all their real work, then you may not have enough RAM to also run a large caching nameserver on the box. Finally, sometimes consistency is more important than raw speed. In other words, sometimes it's more important that the clients see that they get the same answers regardless of which server they ask, and the actual raw performance is not quite so important. For example, when an AOL user sends e-mail to a remote recipient, it would be really bad for that user to get okay, message accepted on the first try and then invalid domain on the second try, and then get okay, message accepted on the third try, or whatever. Since the DNS changes frequently, you could easily wind up with some pretty radically different views of the world on different servers, based on when they asked what questions. To solve all these issues, what was recommended was a hybrid approach. Run local caching-only servers on each box, but then have them forward all outgoing queries to a central set of caching-only nameservers. The local nameserver would short-circuit all the repetitive queries from the same application to talk to the same remote system, while the centralized caching nameservers would ensure that everyone gets the same answer to a particular question, and would ensure that you don't actually send your queries to the outside world unless no machine at that site had asked that question within the time-to-live of the answer. DNS experts now agree that it's a generally a bad idea to have hierarchies of nameservers, although the overall problems have not otherwise changed. So, pick your poison, but don't try to go with the hybrid approach. It creates too much of a central bottleneck and slows things down, and it also reduces your overall reliability of the system. Of course, all detailed DNS questions should be asked on the appropriate mailing lists and/or newsgroups, although I can try to summarize as best I can -- I was a technical reviewer of 2nd edition of Cricket's book, and I'm in the process of writing my own book on DNS security. While all of my experience is with sendmail, I'm inclined to suspect that the other MTA's all can stand a shot of local DNS service. Anybody who can confirm this for Postfix, Exim, etc.? All MTAs I know of make intensive use of the DNS -- sendmail, postfix, Exim, etc -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Nomail members
At 9:19 PM -0700 3/8/07, [EMAIL PROTECTED] wrote: Tell me that isn't true, Mark. From this mail list administrator's perspective, I can't find/use my password ranks just below the AOL flaming demands that we unsubscribe them NOW! Who needs periodic reminders, when there will be a reset mechanism that the user can make use of at any time of their choosing? I'm sorry, I'm just not seeing the reason why you would ever want to continue using the reminder mechanism, when you can just go to a page, enter in your e-mail address, and have the system generate a new password for you and send it to you by e-mail. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Slow delivery
--- Brad Knowles [EMAIL PROTECTED] wrote: I'd be willing to bet you're waiting on DNS timeouts at the remote end for one or more of your users -- their MTA is slowing you down, maybe as a result of trying to do a reverse DNS lookup on your IP address. Thanks to all for the thorough replies. It appears that the solution actually lies in disabling ident. In Exim, this is achieved by setting the timeout to 0. #rfc1413_query_timeout = 30s rfc1413_query_timeout = 0s I may go back and turn it on again with a smaller timeout (suggestions as to how long is reasonable?). Before: Mar 08 15:18:33 2007 (35218) [EMAIL PROTECTED] smtp for 60 recips, completed in 211.309 seconds After: Mar 08 19:48:40 2007 (553) [EMAIL PROTECTED] smtp for 61 recips, completed in 1.792 seconds Cheers, Herman Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. http://answers.yahoo.com/dir/?link=listsid=396545367 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Slow delivery
At 9:44 PM -0800 3/8/07, Herman Privyhum wrote: Thanks to all for the thorough replies. It appears that the solution actually lies in disabling ident. Ahh, yes. You should definitely disable IDENT. I didn't know that any modern MTAs actually used it. I may go back and turn it on again with a smaller timeout (suggestions as to how long is reasonable?). Just leave it turned off. Using it means that you trust the other end to not lie to you, and on the modern Internet you can't trust the other end to do much of anything. You have to assume that all remote machines will always lie to you, and therefore you can't trust anything they send you. At the very least, if you're going to use it, make sure you only use it on your local network of machines that you control. On those machines, you could use a lower timeout, such as ten or fifteen seconds. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Slow delivery
--- Brad Knowles [EMAIL PROTECTED] wrote: Ahh, yes. You should definitely disable IDENT. I didn't know that any modern MTAs actually used it. Here's Philip Hazel's rationale: http://xrl.us/u8pf (Link to www.exim.org) Herman Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Slow delivery
At 10:16 PM -0800 3/8/07, Herman Privyhum wrote: http://xrl.us/u8pf (Link to www.exim.org) So Phil says that he runs a trustworthy IDENT server on his box. Fine. But plenty of spammers, phishers, and other nefarious types out there will try to use IDENT as another vector to exploit for use in breaking into your system, or for tricking you into believing whatever lies they want you to believe. Unfortunately, there isn't a trustworthy system to tell you which sites run trustworthy IDENT servers. So, you've got to decide what the relative risks and values are. Moreover, damn few sites run multiuser systems like that anymore. With NAT, you could hide hundreds or millions of machines behind a single IP address, and IDENT to the NAT/firewall box would be pretty meaningless. Sorry. IDENT was useful fifteen or twenty years ago, but there are far too many holes in that technique these days. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Slow delivery
At 1:04 AM -0600 3/9/07, Brad Knowles quoted Herman Privyhum: http://xrl.us/u8pf (Link to www.exim.org) So Phil says that he runs a trustworthy IDENT server on his box. BTW, that article is eight years old now. Eight years in real time is over five Internet generations. We were still working on Web 0.9 at the time, much less Web 2.0. RFC 2780 was published in March of 2000. RFC 4856 was just recently published, in February of 2007. That's 2076 RFCs published since Phil's article was originally posted. Thanks mostly to the Hobbes Internet Timeline (see http://www.zakon.org/robert/internet/timeline/), we know that 2000 was the year that Internet2 backbone network deployed IPv6. The year that Mexico finally got a fully operational connection to Internet2. The year that the French court ruled Yahoo! must block French users from accessing hate memorabilia in its auction site. Technologies of the year were ASP, Napster, and DeCSS. 2001 was the year of Grid Computing and P2P. 2002 was the year of the FBI teaming up with Terra Lycos to disseminate virtual wanted posts across the Web portal's properties -- does anyone even remember Terra Lycos anymore? 2003 was the year that PIR took over as the .org registry operator, the Recording Industry Association of America (RIAA) sued 261 individuals on 8 Sep for allegedly distributing copyright music files over peer-to-peer networks, and VeriSign deployed a wildcard service (Site Finder) into the .com and .net TLDs causing much confusion as URLs with invalid domains are redirected to a VeriSign page. 2004 was the year that Network Solutions began offering 100 year domain registration, VeriSign Naming and Directory Service (VNDS) began updating all 13 .com/.net authoritative name servers in near real-time vs. twice each day, and the Internet Worm called MyDoom (or Novarg), spread through Internet servers. 2005 was the year that YouTube.com was launched. Estimates of the size of the Internet, by year: 01/0072,398,092 07/0093,047,785 01/01 109,574,429 07/01 125,888,197 01/02 147,344,723 07/02 162,128,493 01/03 171,638,297 01/04 233,101,481 07/04 285,139,107 01/05 317,646,084 07/05 353,284,187 01/06 394,991,609 07/06 439,286,364 Growth factor = 439286364/72398092 = 6.06765 According to the wikipedia page at http://en.wikipedia.org/wiki/Phishing, the first known example of Phishing outside of AOL didn't occur until June of 2001. I quote: By 2004, phishing was recognized as fully industrialized, in the sense of an economy of crime: specializations emerged on a global scale and provided components for cash which were assembled into a finished attack. I'm sorry. I don't see how Phil's views from eight years ago on this subject are relevant to how computer systems should be operated in this modern world. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
