Re: [Mailman-Users] Emails Not Being Delivered to All on List

2006-10-31 Thread Brad Knowles
At 8:18 PM -0600 10/31/06, Bruce E. Breeding wrote:

>  "The drawback of this configuration is that it will work poorly on
>  systems supporting lists in several different mail domains.

How, exactly?  Turning off DNS verification within the MTA, *ONLY* 
for outgoing e-mail from the mailing list server, should speed up all 
lists on the server regardless of which domain they are hosted on.

>  While
>  Mailman handles virtual domains, it does not yet support having
>  two distinct lists with the same name in different virtual domains,
>  using the same Mailman installation.

True, but that has absolutely nothing to do with the issue of turning 
off DNS verification within the MTA.

>  Our mailservers are currently configured for optimal performance
>  with mailman,

If he's doing DNS verification on mail that is outbound from the 
mailing list server, then it most definitely is *NOT* optimally 
configured.

>this is all integrated by the Cpanel Program which
>  is used to configure all domains."

Ahh, there's the key.  He's totally freaking clueless, which explains 
why he's using cPanel.  So, he's spouting some complete garbage that 
is totally unrelated to the actual subject being discussed.  We can't 
really blame him for this, since he just doesn't know any better.

But you do know better, at least now you do.  And you can use this 
information to guide you in your choice of a new hosting provider 
that will actually be more clueful.

>  Would you comment on this?  Is there some misinformation here?

Yeah, it's pretty much all misinformation.

>  I'm only a poor user (can you hear the violins playing?)   I just
>  need a reliable email list ... free of course (not too picky, huh?)
>  I know I'm not his only user of mailman (making me wonder why his
>  other customers aren't complaining)...

Maybe they are complaining and you don't hear about it, or maybe they 
don't know what they could be getting and are willing to just settle 
for what they think is all they can get.

But now you know better.

-- 
Brad Knowles, <[EMAIL PROTECTED]>

Trend Micro has announced that they will cancel the stop.mail-abuse.org
mail forwarding service as of 15 November 2006.  If you have an old
e-mail account for me at this domain, please make sure you correct that
with the current address.
--
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=show&file=faq01.027.htp


Re: [Mailman-Users] Interesting Goings ons...

2006-10-31 Thread Mark Sapiro
Adam Morehead wrote:

>Both are correct Next idea?

Are you getting the daily summary of moderator requests?

Look in Mailman's SMTP log? When a held post is processed, there should
be two or three entries in the SMTP log with Mailman generated
message-ids of the form
<[EMAIL PROTECTED]>. One of these is
the notice to the poster if respond_to_post_requests is Yes and has 1
recipient. Two are first, the moderator notice to listname-owner with
1 recipient, and then the resend to the owner(s) and moderator(s) with
number of recipients = the number of owners and moderators. Do you see
these in the log?   

-- 
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=show&file=faq01.027.htp


Re: [Mailman-Users] Emails Not Being Delivered to All on List

2006-10-31 Thread Bruce E. Breeding
Thank you, Brad, for the clarification of DNS verification and its effect on 
mailman.  

So far, my web service provider has resisted changing his configuration of 
mailman.  When I suggested Turning OFF DNS verification per this list 
suggestion, [and provided the FAQ link] to the web service provider, he replied 
as follows:

"The drawback of this configuration is that it will work poorly on systems 
supporting lists in several different mail domains. While Mailman handles 
virtual domains, it does not yet support having two distinct lists with the 
same name in different virtual domains, using the same Mailman installation.  
Our mailservers are currently configured for optimal performance with mailman, 
this is all integrated by the Cpanel Program which is used to configure all 
domains."

Would you comment on this?  Is there some misinformation here?  
-- Bruce
I'm only a poor user (can you hear the violins playing?)   I just need a 
reliable email list ... free of course (not too picky, huh?)  I know I'm not 
his only user of mailman (making me wonder why his other customers aren't 
complaining)...
--
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=show&file=faq01.027.htp


Re: [Mailman-Users] undelivered mail, but only to some

2006-10-31 Thread Mark Sapiro
D. Alan Stewart wrote:
>
>> Sendmail claims it sent the mail to the users who didn't get it. I
>> recognize the symptoms say that Mailman is somehow involved, but I
>> don't see how.
>
>I recognize the difficulty of this particular problem.


I still stand by my assessment that in your case, Mailman is sending
the mail to the MTA, and the MTA is sending it on, and the loss must
occur downstream from there. That said, it is entirely possible that
the mail is lost/discarded because of something Mailman-specific in
the message. Things which could cause this problem might include the
[EMAIL PROTECTED] envelope sender (can the domain of this
address be looked up in DNS?) or some Mailman specific header.

BTW, is bounce processing enabled for the list, and are there any
entries in Mailman's 'bounce' log for the recipients missing posts? At
least for debugging this, bounce_processing should be Yes and so
should bounce_unrecognized_goes_to_list_owner and
bounce_notify_owner_on_disable.

-- 
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=show&file=faq01.027.htp


Re: [Mailman-Users] Interesting Goings ons...

2006-10-31 Thread Adam Morehead
Both are correct Next idea?

Adam


Mark Sapiro wrote:

>Adam Morehead wrote:
>
>  
>
>>We have mailman setup on our server... Everything is working fine except 
>>one thing, all the approved emails are going to the recipients, all 
>>denied are getting denied.. only one thing is bugging me... if theres a 
>>pending request, we used to get a email letting us know that we have 
>>email waiting for approval.. its not happening anymore.
>>
>>
>
>
>Go to the list's General Options and make sure the email addresses for
>owner and moderator (if any) are correct. Then scroll down to
>Notifications and make sure admin_immed_notify is set to Yes.
>
>  
>

--
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=show&file=faq01.027.htp


Re: [Mailman-Users] Emails Not Being Delivered to All on List

2006-10-31 Thread Mark Sapiro
D. Alan Stewart wrote:
>
>I did not receive either of your responses to my "undelivered email"  
>thread.


I just noticed you have a mac.com address. There was a period of a
couple of weeks about a month ago during which mac.com was seriously
delaying and possibly losing mail. This appears to be over. We'll see
if you get this one directly.

-- 
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=show&file=faq01.027.htp


Re: [Mailman-Users] Interesting Goings ons...

2006-10-31 Thread Mark Sapiro
Adam Morehead wrote:

>We have mailman setup on our server... Everything is working fine except 
>one thing, all the approved emails are going to the recipients, all 
>denied are getting denied.. only one thing is bugging me... if theres a 
>pending request, we used to get a email letting us know that we have 
>email waiting for approval.. its not happening anymore.


Go to the list's General Options and make sure the email addresses for
owner and moderator (if any) are correct. Then scroll down to
Notifications and make sure admin_immed_notify is set to Yes.

-- 
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=show&file=faq01.027.htp


Re: [Mailman-Users] Emails Not Being Delivered to All on List

2006-10-31 Thread Brad Knowles
At 4:56 PM -0600 10/31/06, Bruce E. Breeding wrote:

>  I went to the URL and read it.  Thank you (and thank you for the other
>  comments in your email).   However, the FAQ merely said that it (leaving the
>  verification turned on) will "slow delivery rates from mailman to your MTA
>  significantly".

Correct.

>  Can you elaborate?  (I'm looking for something substantive to convey to my
>  web service provider.)

As one of the authors of a lot of material in that FAQ entry, I will 
try to answer your questions.

>  Is the delay minutes?  hours?  "it depends [on ___ ]"?

Officially, it depends.  But turning on DNS verification of e-mail 
addresses can cause messages that could be delivered in just a few 
seconds to take minutes or hours or more.  Do this across your whole 
list, and you might be able to go from handling thousands (or tens of 
thousands) of users with DNS verification turned off, to having 
difficulty handling hundreds of users with DNS verification turned on.

DNS verification is very, very bad news for proper operation of 
mailing lists.  So is anti-spam or anti-virus scanning.  All that 
kind of stuff should be done *ONLY* on message input into the mailing 
list system, and *NEVER* on message output from the mailing list 
system.

>  Does the delivery eventually take place, or, do some recipients really never
>  get the emails?

Maybe.  Maybe not.  But your throughput could go down substantially, 
and it may be impossible to reliably deliver mail to certain users.

-- 
Brad Knowles, <[EMAIL PROTECTED]>

Trend Micro has announced that they will cancel the stop.mail-abuse.org
mail forwarding service as of 15 November 2006.  If you have an old
e-mail account for me at this domain, please make sure you correct that
with the current address.
--
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=show&file=faq01.027.htp


[Mailman-Users] IOError: Broken pipe on long mails

2006-10-31 Thread Dan Young
Python version:  python-2.3.4-14.3
Mailman version: mailman-2.1.5.1-34.rhel4.5


I've been getting a broken pipe error when sending log mails (usually
triggered by those with attachments) through SMTPDirect (DELIVERY_MODULE
= 'Sendmail' delivers, but obviously is not preferred):

Oct 30 12:59:13 2006 (25556) Low level smtp error: [Errno 32] Broken
pipe, msgid: <[EMAIL PROTECTED]>

Watching the local MTA, I can see the connection time out 300 seconds
after the connection is opened.

I'm able to trigger a similar broken pipe error trying to unpickle the
queued message (/root/test.pck is a copy of a pickled message):

# /usr/lib/mailman/bin/show_qfiles /root/test.pck  | head
> /root/test.pck
Return-Path: <[EMAIL PROTECTED]>
X-Original-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Received: from mrelay-i2.mesd.k12.or.us (mrelay-i2.mesd.k12.or.us
[198.236.68.99])
by .x.k12.or.us (Postfix) with ESMTP id 205A370C0AF
for <[EMAIL PROTECTED]>;
Thu, 26 Oct 2006 15:29:39 -0700 (PDT)
Traceback (most recent call last):
  File "/usr/lib/mailman/bin/show_qfiles", line 74, in ?
main()
  File "/usr/lib/mailman/bin/show_qfiles", line 69, in main
sys.stdout.write(fp.read())
IOError: [Errno 32] Broken pipe

I can suppress the IOError by patching show_qfiles:

21a22,24
> import signal
> signal.signal(signal.SIGPIPE, signal.SIG_DFL)
>

Any way I can get mailman to close the connection to the MTA, short of
"pass"ing on except IOError?

-- 
Dan Young <[EMAIL PROTECTED]>
Multnomah ESD - Technology Services
503-257-1562
--
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=show&file=faq01.027.htp


[Mailman-Users] mailman: how to display subject and date for archives when listing of archives?

2006-10-31 Thread Jana Nguyen
Hi,


How do I get the archive list to display the subject, author and date 
when I go to list archives? For example:

Archive View by:Downloadable version
11 May 2006:  [ Next Meeting for Workshop] [Jana Nguyen] [11 May 
2006]   [ Text 1 KB ] 






 The default that comes with mailman display the heading and we don't 
want this (see below).


You can get more information about this list 
.

Archive View by:Downloadable version
11 May 2006:[ Thread ] 
 
[ Subject ] 
 
[ Author ] 
 
[ Date ] 
 
[ Text 1 KB ] 

5 May 2006: [ Thread ] 
 
[ Subject ] 
 
[ Author ] 
 
[ Date ] 
 
[ Text 438 bytes ] 



Thanks!
--
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=show&file=faq01.027.htp


Re: [Mailman-Users] Emails Not Being Delivered to All on List

2006-10-31 Thread Bruce E. Breeding
Mark Sapiro wrote:
> This indicates that your provider's MTA is doing DNS verification on
> outgoing mail from Mailman. This is not good. See
> .

I went to the URL and read it.  Thank you (and thank you for the other
comments in your email).   However, the FAQ merely said that it (leaving the
verification turned on) will "slow delivery rates from mailman to your MTA
significantly".

Can you elaborate?  (I'm looking for something substantive to convey to my
web service provider.)

Is the delay minutes?  hours?  "it depends [on ___ ]"?

Does the delivery eventually take place, or, do some recipients really never
get the emails?

-- Bruce

--
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=show&file=faq01.027.htp


Re: [Mailman-Users] Emails Not Being Delivered to All on List

2006-10-31 Thread D. Alan Stewart
Mark,

You're correct, I did have the option set to eliminate duplicates.  
I've unset that now, because I'm having trouble trusting Mailman  
these days.

I did not receive either of your responses to my "undelivered email"  
thread.

I've forwarded all messages to my provider in hopes that he can make  
sense of something.

Alan

On Oct 31, 2006, at 5:05 PM, Mark Sapiro wrote:

> D. Alan Stewart wrote:
>>
>> Thanks for the responses, Mark Sapiro, but I never got them - this
>> list is broken too! I'll respond to your questions in my next  
>> posting.
>
>
> This list is *not* broken. When I reply to posts, I normally include
> the poster as a direct addressee of my reply (I have removed your
> address from this reply). Most people are set to not receives dups
> from the list in this case, so the list does not send you a copy and
> the only copy you get is the direct mail from me.
>
> If for some reason, direct mail from me to you is returned to me, I
> will make every effort to get the mail to you by sending from a
> different server or whatever it takes, but if as apparently happened
> in your case, the direct mail from me to you just disappears, you
> never see it, and I don't know.
>
> -- 
> 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/ 
> d.alan.stewart%40mac.com
>
> Security Policy: http://www.python.org/cgi-bin/faqw-mm.py? 
> req=show&file=faq01.027.htp

--
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=show&file=faq01.027.htp


[Mailman-Users] Interesting Goings ons...

2006-10-31 Thread Adam Morehead
We have mailman setup on our server... Everything is working fine except 
one thing, all the approved emails are going to the recipients, all 
denied are getting denied.. only one thing is bugging me... if theres a 
pending request, we used to get a email letting us know that we have 
email waiting for approval.. its not happening anymore.

I went through aliases and made sure it is 'mailman' not 'wrappers' 
(Since we used to have the older version.

made sure that the aliases file is being called.

and even the email addy is in the admin and moderator spot on the webform...

what am I missing? Please let it be simple? lol.

Adam
--
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=show&file=faq01.027.htp


Re: [Mailman-Users] rename mailman hostname

2006-10-31 Thread mardin
Mark ,

In my Defaults.py:
$ more Defaults.py
DEFAULT_EMAIL_HOST = 'mailman_server1.admin.net'
DEFAULT_URL_HOST = 'mailman_server1.admin.net'

Since I need to rename hostname to mailman_server2.admin.net, I have to change 
it in mm_cfg.py. Thanks for your explanation, I will add these two lines to 
mm_cfg.py as follows:

DEFAULT_EMAIL_HOST = 'mailman_server2.admin.net'
DEFAULT_URL_HOST = 'mailman_server2.admin.net'
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
DEFAULT_URL_PATTERN = 'https://%s/mailman/'

Thanks for your help!
Mardin


 -- Original message --
From: Mark Sapiro <[EMAIL PROTECTED]>
> [EMAIL PROTECTED] wrote:
> >
> >My question is how to use the following two lines:
> >
> >VIRTUAL_HOSTS.clear()
> >add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
> >
> >For our case, is it necessary to add the above two lines? When I did a quick 
> test, the mailman server was working without adding these two lines.
> 
> It depends on what you're doing and what's in Defaults.py. If the
> settings in Defaults.py for DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST
> are correct, then you don't need the two lines in mm_cfg.py (and you
> also don't need to set DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST in
> mm_cfg.py).
> 
> If the settings in Defaults.py for DEFAULT_URL_HOST and/or
> DEFAULT_EMAIL_HOST need changing in mm_cfg.py, then you also need the
> two above lines. This affects mostly creation of new lists, but also
> fix_url and the domain of the site email address on the listinfo pages
> and some other places.
> 
> -- 
> 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=show&file=faq01.027.htp


Re: [Mailman-Users] undelivered mail, but only to some

2006-10-31 Thread D. Alan Stewart
Responding to Mark Sapiro:

> If the sendmail log says the post is sent to the user in question,
> Mailman delivered it to sendmail for the user, and it's not Mailman's
> problem.

I agree, it's not clear whether this is a sendmail or a Mailman  
problem. However, I have never, AFAIK, failed to receive an email  
from my provider's domain, unless that email originated from this  
specific Mailman list. That seems suspicious, doesn't it? Of course,  
I may be missing other emails that I am not aware of. Not getting  
something you did not know to expect is not an easy problem to trap.

Since I now know that I am not receiving all emails from this list,  
possibly the problem is common but not often detected because the  
severity varies, list by list.

> Mailman's 'smtp' log. This will tell you how many recipients the post
> was sent to.

My provider has checked Mailman's smtp log. It shows emails were sent  
to all subscribers.

> Also check if the list is personalized. You may not even have
> personalization options on your Non-digest options page which means
> that OWNERS_CAN_ENABLE_PERSONALIZATION is not set to Yes in mm_cfg.py
> and delivery is almost certainly not personailzed.

I'm not certain, but I think this answers your question: the list  
does have digest options available to the users.

> Check the settings of VERP_DELIVERY_INTERVAL and SMTP_MAX_RCPTS if any
> in mm_cfg.py

I looked, there are no settings for these in Mailman/mm_cfg.py. There  
don't appear to be any site-specific settings here.

> You should also see this in the sendmail log, i.e. that the mail was
> delivered to sendmail in one transaction.

The provider has given me sendmail logs that I have analyzed. I was  
able to identify entries in the sendmail log that correspond with  
mailing list transmissions that were not received by the subscriber  
(me).

> Sendmail claims it sent the mail to the users who didn't get it. I
> recognize the symptoms say that Mailman is somehow involved, but I
> don't see how.

I recognize the difficulty of this particular problem.

Thanks,
Alan


--
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=show&file=faq01.027.htp


Re: [Mailman-Users] Emails Not Being Delivered to All on List

2006-10-31 Thread Mark Sapiro
Bruce E. Breeding wrote:

>Symptom:  some list recipients are not receiving their emails from the list 
>[Four resulting questions below]
>
>In attempting to determine WHY the above symptom is occurring, I contacted my 
>web service provider.  We're getting to know each other well due to frequency 
>of communication.  ;)
>He seems to be trying hard to help me out.  
>Here is his latest helpful hint:
>
> Web service provider's suggestions start here ...
>"I happened to catch some of your mailing lists trying to deliver a little 
>while ago and caught an example of why you sometimes have problems. This is a 
>good example of a list doing a partial delivery because it stalls at a bad 
>address which causes delays etc for other addresses that are on the same list 
>and this particular address you have on for lists currently unable to finish 
>delivery...
>
>Getting MX record for .org (from local DNS server, may be 
>cached)...   Received a SERVER FAILURE response.


This indicates that your provider's MTA is doing DNS verification on
outgoing mail from Mailman. This is not good. See
.


>This should be treated as an ERROR (per RFC974), and the E-mail delivery 
>should PROBABLY be retried later.
>
>Here is what has been delivered so far, anything with a "Y" has been 
>delivered, anything without is stalled because of the bad email address which 
>doesn't allow the mailserver to continue.
>
>with either
>YY, YN, NY, or NN>
>
>


It doesn't come in that form from any Mailman log.


>http://www.dnsreport.com (which 
>I have, although I had already checked one by one to be sure the addresses 
>were correctly entered.  I have most of them in a contact list and so there 
>was little doubt in my mind of their accuracy.)>
> Web service provider's suggestions end here ...
>
>So, my Question(1):  Is it normal to expect a substantial amount of 
>non-delivery to valid email addresses?  I would presume, "No."  But, in case 
>I'm really missing the obvious, here, please enlighten me.


It *shouldn't* be normal, but there is no accounting for the things
that ISP's do to protect their users from spam (or to protect
themselves from complaints from their users about spam).

ISPs will discard mail for any number of reasons, and there's not much
you can do about it.

Go to  and do a DNSBL lookup on the IP address
that your list mail comes from. If the IP address is on any black
lists, you'll have problems with delivery to some ISPs.


>Question (2):  Is it normal for Mailman to "stall", or "stop" processing the 
>rest of a list because of one bad email?  (I'm asking that somewhat 
>rhetorically, expecting an emphatic "NO" answer.)


It depends on the exact response from the MTA. If the MTA refuses a
recipient as undeliverable, Mailman will process that address as a
bounce and will continue to send to the others, possibly after a delay
of up to 15 minutes.


>Question (3):  Please explain the YY, YN, NY, and NN indicators [preceding the 
>email addresses] from the above referenced log.  I understand that YY means 
>the email was delivered to the recipient, and NN means the email was NOT 
>delivered to the recipient.  But, YN and NY?  maybe yes, maybe no?


They don't come from a Mailman log.


>Question (4):  Do you have further suggestions as to troubleshooting the 
>reason that some of these addresses did not receive the email?  Are there 
>specific places (other logs in mailman) I should ask him to look that could 
>give further information?


If the addresses are valid, he should be able to see delivery from the
MTA to the recipient. If the mail is sent from his server towards the
destination, the problem is somewhere downstream.

-- 
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=show&file=faq01.027.htp


Re: [Mailman-Users] Emails Not Being Delivered to All on List

2006-10-31 Thread Mark Sapiro
D. Alan Stewart wrote:
>
>Thanks for the responses, Mark Sapiro, but I never got them - this  
>list is broken too! I'll respond to your questions in my next posting.


This list is *not* broken. When I reply to posts, I normally include
the poster as a direct addressee of my reply (I have removed your
address from this reply). Most people are set to not receives dups
from the list in this case, so the list does not send you a copy and
the only copy you get is the direct mail from me.

If for some reason, direct mail from me to you is returned to me, I
will make every effort to get the mail to you by sending from a
different server or whatever it takes, but if as apparently happened
in your case, the direct mail from me to you just disappears, you
never see it, and I don't know.

-- 
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=show&file=faq01.027.htp


Re: [Mailman-Users] reviving broken mailman ???

2006-10-31 Thread Mark Sapiro
Patrick Bogen wrote:
>
>P.s.,
>Please CC the list on all replies, so that more well-versed folk can
>chime in when I might not know the answer.


Yes. Please try to keep conversations on the list.

Patrick has pretty much covered it. If you want another view, see
.
This is in the context of moving lists, but the directories and files
would be the same.

However, I *think* you should be able to reinstall Mailman without
moving your list data aside and get the same end result, but it would
be good to back up your data anyway.

Also, re: Patrick's concern that the issue may be caused by something
in the list data rather than Mailman itself is quite valid in general,
but is almost certainly not the case with your specific issue.

-- 
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=show&file=faq01.027.htp


Re: [Mailman-Users] Emails Not Being Delivered to All on List

2006-10-31 Thread D. Alan Stewart
Hey, this sounds like the same problem I posted on Oct. 26! Our list  
has had the problem for five months now.

It gets worse - this list has the same problem. In looking at the  
Mailman-Users archive, I see severals responses to my plea for help,  
"undelivered mail, but only to some" that I never received.

Thanks for the responses, Mark Sapiro, but I never got them - this  
list is broken too! I'll respond to your questions in my next posting.

Alan


On Oct 31, 2006, at 4:23 PM, Bruce E. Breeding wrote:

> Symptom:  some list recipients are not receiving their emails from  
> the list [Four resulting questions below]
>
> In attempting to determine WHY the above symptom is occurring, I  
> contacted my web service provider.  We're getting to know each  
> other well due to frequency of communication.  ;)
> He seems to be trying hard to help me out.
> Here is his latest helpful hint:
>
>  Web service provider's suggestions start here ...
> "I happened to catch some of your mailing lists trying to deliver a  
> little while ago and caught an example of why you sometimes have  
> problems. This is a good example of a list doing a partial delivery  
> because it stalls at a bad address which causes delays etc for  
> other addresses that are on the same list and this particular  
> address you have on for lists currently unable to finish  
> delivery...
>
> Getting MX record for .org (from local DNS server, may  
> be cached)...   Received a SERVER FAILURE response.
>
> This should be treated as an ERROR (per RFC974), and the E-mail  
> delivery should PROBABLY be retried later.
>
> Here is what has been delivered so far, anything with a "Y" has  
> been delivered, anything without is stalled because of the bad  
> email address which doesn't allow the mailserver to continue.
>
>  each prefaced with either
> YY, YN, NY, or NN>
>
> 
>
>  www.dnsreport.com (which I have, although I had already checked one  
> by one to be sure the addresses were correctly entered.  I have  
> most of them in a contact list and so there was little doubt in my  
> mind of their accuracy.)>
>  Web service provider's suggestions end here ...
>
> So, my Question(1):  Is it normal to expect a substantial amount of  
> non-delivery to valid email addresses?  I would presume, "No."   
> But, in case I'm really missing the obvious, here, please enlighten  
> me.
>
> Question (2):  Is it normal for Mailman to "stall", or "stop"  
> processing the rest of a list because of one bad email?  (I'm  
> asking that somewhat rhetorically, expecting an emphatic "NO" answer.)
>
> Question (3):  Please explain the YY, YN, NY, and NN indicators  
> [preceding the email addresses] from the above referenced log.  I  
> understand that YY means the email was delivered to the recipient,  
> and NN means the email was NOT delivered to the recipient.  But, YN  
> and NY?  maybe yes, maybe no?
>
> Question (4):  Do you have further suggestions as to  
> troubleshooting the reason that some of these addresses did not  
> receive the email?  Are there specific places (other logs in  
> mailman) I should ask him to look that could give further information?
>
> Thank you for you help.
> Bruce
>
>
>
>
> --
> 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/ 
> d.alan.stewart%40mac.com
>
> Security Policy: http://www.python.org/cgi-bin/faqw-mm.py? 
> req=show&file=faq01.027.htp

--
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=show&file=faq01.027.htp


[Mailman-Users] Emails Not Being Delivered to All on List

2006-10-31 Thread Bruce E. Breeding
Symptom:  some list recipients are not receiving their emails from the list 
[Four resulting questions below]

In attempting to determine WHY the above symptom is occurring, I contacted my 
web service provider.  We're getting to know each other well due to frequency 
of communication.  ;)
He seems to be trying hard to help me out.  
Here is his latest helpful hint:

 Web service provider's suggestions start here ...
"I happened to catch some of your mailing lists trying to deliver a little 
while ago and caught an example of why you sometimes have problems. This is a 
good example of a list doing a partial delivery because it stalls at a bad 
address which causes delays etc for other addresses that are on the same list 
and this particular address you have on for lists currently unable to finish 
delivery...

Getting MX record for .org (from local DNS server, may be 
cached)...   Received a SERVER FAILURE response.

This should be treated as an ERROR (per RFC974), and the E-mail delivery should 
PROBABLY be retried later.

Here is what has been delivered so far, anything with a "Y" has been delivered, 
anything without is stalled because of the bad email address which doesn't 
allow the mailserver to continue.





http://www.dnsreport.com (which I 
have, although I had already checked one by one to be sure the addresses were 
correctly entered.  I have most of them in a contact list and so there was 
little doubt in my mind of their accuracy.)>
 Web service provider's suggestions end here ...

So, my Question(1):  Is it normal to expect a substantial amount of 
non-delivery to valid email addresses?  I would presume, "No."  But, in case 
I'm really missing the obvious, here, please enlighten me.

Question (2):  Is it normal for Mailman to "stall", or "stop" processing the 
rest of a list because of one bad email?  (I'm asking that somewhat 
rhetorically, expecting an emphatic "NO" answer.)

Question (3):  Please explain the YY, YN, NY, and NN indicators [preceding the 
email addresses] from the above referenced log.  I understand that YY means the 
email was delivered to the recipient, and NN means the email was NOT delivered 
to the recipient.  But, YN and NY?  maybe yes, maybe no?

Question (4):  Do you have further suggestions as to troubleshooting the reason 
that some of these addresses did not receive the email?  Are there specific 
places (other logs in mailman) I should ask him to look that could give further 
information?

Thank you for you help.
Bruce




--
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=show&file=faq01.027.htp


Re: [Mailman-Users] rename mailman hostname

2006-10-31 Thread Mark Sapiro
[EMAIL PROTECTED] wrote:
>
>My question is how to use the following two lines:
>
>VIRTUAL_HOSTS.clear()
>add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>
>For our case, is it necessary to add the above two lines? When I did a quick 
>test, the mailman server was working without adding these two lines.

It depends on what you're doing and what's in Defaults.py. If the
settings in Defaults.py for DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST
are correct, then you don't need the two lines in mm_cfg.py (and you
also don't need to set DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST in
mm_cfg.py).

If the settings in Defaults.py for DEFAULT_URL_HOST and/or
DEFAULT_EMAIL_HOST need changing in mm_cfg.py, then you also need the
two above lines. This affects mostly creation of new lists, but also
fix_url and the domain of the site email address on the listinfo pages
and some other places.

-- 
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=show&file=faq01.027.htp


Re: [Mailman-Users] rename mailman hostname

2006-10-31 Thread mardin
Mark,

You are great! It works now!

If renaming the mailman (2.1.5) hostname from mailman_server1.admin.net to 
mailman_server2.admin.net, I know that I have to modify and add the following 
three lines:
# vi mm_cfg.py  
DEFAULT_EMAIL_HOST = 'mailman_server2.admin.net'
DEFAULT_URL_HOST = 'mailman_server2.admin.net'
DEFAULT_URL_PATTERN = 'https://%s/mailman/'

My question is how to use the following two lines:

VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

For our case, is it necessary to add the above two lines? When I did a quick 
test, the mailman server was working without adding these two lines.

Thanks,
Mardin


 -- Original message --
From: Mark Sapiro <[EMAIL PROTECTED]>
> [EMAIL PROTECTED] wrote:
> >
> >After I used URL of https://mailman_server2.admin.net/mailman/admin/, I 
> >could 
> log in the list successfully. But I could not modify the contents of 
> configurations and do other administration work. When I tried to submit the 
> changes, I got the following message:
> >
> >"Although this page is encrypted, the information you have entered is to be 
> sent over an unencrypted connection and could easily be read by a third party.
> >Are you sure you want to continue sending this information? -> Continue"
> >
> >After I clicked the Continue Botton, nothing changed about the list.
> >
> >I did add the "DEFAULT_URL_PATTERN = 'http://%s/mailman/'" to mm_cfg.py and 
> restart mailman. Did I miss some steps for renaming the mailman hostname?
> 
> If you want to use SSL, you should set
> 
> DEFAULT_URL_PATTERN = 'https://%s/mailman/'
> 
> and then run fix_url again. Also see
> .
> 
> -- 
> 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=show&file=faq01.027.htp


Re: [Mailman-Users] reviving broken mailman ???

2006-10-31 Thread Patrick Bogen
On 10/31/06, Dr. Scott S. Jones <[EMAIL PROTECTED]> wrote:
> Broken, in that it won't send out through my MTA, which in my case is Exim4,
> or in another who's had trouble with mailman on debian, through Postfix. It
> seems that when he moved his data files, and purged mailman and then
> reinstalled it. He claims it works now
Well, my point was, if your mailman is broken because something is
wrong with your list config files, keeping the list config files and
reinstalling everything else won't help anything. :)

> My question then is which files does one move out of the way of the wrecking
> ball, a la apt-get --purge mailman etc so that one doesn't have to
> recreate the list after reinstallation?

If you aren't concerned about list archives, I believe you only need
the files in (on Debian) /var/lib/mailman/lists/*
Each list should have its own directory, with a config.pck, possibly
config.pck.last, and (possibly?) a request.pck.

Archives are in /var/lib/mailman/archives; they can be regenerated
from some subset of the files in this hierarchy (I believe its those
under listname.mbox/), but I'm not sure if that's all that's required.

If you can read bash script, FAQ 4.18

might help you figure all this out.

P.s.,
Please CC the list on all replies, so that more well-versed folk can
chime in when I might not know the answer.

-- 
- Patrick Bogen
--
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=show&file=faq01.027.htp


Re: [Mailman-Users] sendigest error

2006-10-31 Thread Mark Sapiro
Kory Wheatley wrote:
>
>I receive the following error when the below cron job is ran, or just 
>running it from the command line.  Any suggestion on what would fix this 
>issue?  Do I have a bad digest.mbox somewhere?


Probably not. You have a digest.mbox that has a message with an unusual
rfc2231 encoded header (a long filename= parameter in the
Content-Disposition: header of an attachment with an apostrophe in the
name), but the header is probably correct. It is the Python
email.Utils.decode_params() function that has the problem. This has
been fixed in Python email 2.5.8 which ships with Mailman 2.1.9


> /usr/local/bin/python -S /home/mailman/cron/senddigests
>
>Traceback (most recent call last):
>  File "/home/mailman/cron/senddigests", line 94, in ?
>main()
>  File "/home/mailman/cron/senddigests", line 86, in main
>mlist.send_digest_now()
>  File "/home/mailman/Mailman/Digester.py", line 60, in send_digest_now
>ToDigest.send_digests(self, mboxfp)
>  File "/home/mailman/Mailman/Handlers/ToDigest.py", line 133, in 
>send_digests
>send_i18n_digests(mlist, mboxfp)
>  File "/home/mailman/Mailman/Handlers/ToDigest.py", line 315, in 
>send_i18n_digests
>msg = scrubber(mlist, msg)
>  File "/home/mailman/Mailman/Handlers/Scrubber.py", line 299, in process
>url = save_attachment(mlist, part, dir)
>  File "/home/mailman/Mailman/Handlers/Scrubber.py", line 411, in 
>save_attachment
>filename = Utils.oneline(msg.get_filename(''), lcset)
>  File "/home/mailman/pythonlib/email/Message.py", line 724, in get_filename
>filename = self.get_param('filename', missing, 'content-disposition')
>  File "/home/mailman/pythonlib/email/Message.py", line 607, in get_param
>for k, v in self._get_params_preserve(failobj, header):
>  File "/home/mailman/pythonlib/email/Message.py", line 554, in 
>_get_params_preserve
>params = Utils.decode_params(params)
>  File "/home/mailman/pythonlib/email/Utils.py", line 337, in decode_params
>charset, language, value = decode_rfc2231(EMPTYSTRING.join(value))
>  File "/home/mailman/pythonlib/email/Utils.py", line 284, in decode_rfc2231
>charset, language, s = parts
>ValueError: unpack list of wrong size

-- 
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=show&file=faq01.027.htp


Re: [Mailman-Users] reviving broken mailman ???

2006-10-31 Thread Patrick Bogen
On 10/31/06, Dr. Scott S. Jones <[EMAIL PROTECTED]> wrote:
> Just for curiosity's sake, what would happen if one were to backup one's
> list files, purge mailman and then reinstall, and move the list files back?
> Might this revive a system running on debian, which is currently broken?

It depends on why it's broken.

That said, if you follow the procedures given for moving a list to
another machine (except, instead, just move all the files aside while
you purge/reinstall), it shouldn't be any more broken than it was
before.

-- 
- Patrick Bogen
--
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=show&file=faq01.027.htp


[Mailman-Users] reviving broken mailman ???

2006-10-31 Thread Dr. Scott S. Jones
Just for curiosity's sake, what would happen if one were to backup one's
list files, purge mailman and then reinstall, and move the list files back?
Might this revive a system running on debian, which is currently broken? 

Scott
--
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=show&file=faq01.027.htp


Re: [Mailman-Users] rename mailman hostname

2006-10-31 Thread Mark Sapiro
[EMAIL PROTECTED] wrote:
>
>After I used URL of https://mailman_server2.admin.net/mailman/admin/, I could 
>log in the list successfully. But I could not modify the contents of 
>configurations and do other administration work. When I tried to submit the 
>changes, I got the following message:
>
>"Although this page is encrypted, the information you have entered is to be 
>sent over an unencrypted connection and could easily be read by a third party.
>Are you sure you want to continue sending this information? -> Continue"
>
>After I clicked the Continue Botton, nothing changed about the list.
>
>I did add the "DEFAULT_URL_PATTERN = 'http://%s/mailman/'" to mm_cfg.py and 
>restart mailman. Did I miss some steps for renaming the mailman hostname?

If you want to use SSL, you should set

DEFAULT_URL_PATTERN = 'https://%s/mailman/'

and then run fix_url again. Also see
.

-- 
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=show&file=faq01.027.htp


[Mailman-Users] rename mailman hostname

2006-10-31 Thread mardin
Hi,

I needed to rename the mailman server (2.1.5) from mailman_server1.admin.net to 
mailman_server2.admin.net. I followed the FAQ 4.29.

(1) I changed the hostname to mailman_server2.admin.net on the system.

(2) I modified the mm_cfg.py as follows:
 
DEFAULT_EMAIL_HOST = 'mailman_server2.admin.net'
DEFAULT_URL_HOST = 'mailman_server2.admin.net'
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
DEFAULT_URL_PATTERN = 'http://%s/mailman/'

I restart mailman and run fix_url:
$ ./mailmanctl restart
$ ./withlist -l -r fix_url listname

(3) I changed httpd.conf and ssl.conf to match new hostname of 
mailman_server2.admin.net.

The new mailman_server2..admin.net server was working (such as posted to 
mailing lists and run command line).  But I found a problem:

After I used URL of https://mailman_server2.admin.net/mailman/admin/, I could 
log in the list successfully. But I could not modify the contents of 
configurations and do other administration work. When I tried to submit the 
changes, I got the following message:

"Although this page is encrypted, the information you have entered is to be 
sent over an unencrypted connection and could easily be read by a third party.
Are you sure you want to continue sending this information? -> Continue"

After I clicked the Continue Botton, nothing changed about the list.

I did add the "DEFAULT_URL_PATTERN = 'http://%s/mailman/'" to mm_cfg.py and 
restart mailman. Did I miss some steps for renaming the mailman hostname?

Thanks for your help! 
Mardin
--
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=show&file=faq01.027.htp


[Mailman-Users] sendigest error

2006-10-31 Thread Kory Wheatley
I receive the following error when the below cron job is ran, or just 
running it from the command line.  Any suggestion on what would fix this 
issue?  Do I have a bad digest.mbox somewhere?


/usr/local/bin/python -S /home/mailman/cron/senddigests

Traceback (most recent call last):
 File "/home/mailman/cron/senddigests", line 94, in ?
   main()
 File "/home/mailman/cron/senddigests", line 86, in main
   mlist.send_digest_now()
 File "/home/mailman/Mailman/Digester.py", line 60, in send_digest_now
   ToDigest.send_digests(self, mboxfp)
 File "/home/mailman/Mailman/Handlers/ToDigest.py", line 133, in 
send_digests

   send_i18n_digests(mlist, mboxfp)
 File "/home/mailman/Mailman/Handlers/ToDigest.py", line 315, in 
send_i18n_digests

   msg = scrubber(mlist, msg)
 File "/home/mailman/Mailman/Handlers/Scrubber.py", line 299, in process
   url = save_attachment(mlist, part, dir)
 File "/home/mailman/Mailman/Handlers/Scrubber.py", line 411, in 
save_attachment

   filename = Utils.oneline(msg.get_filename(''), lcset)
 File "/home/mailman/pythonlib/email/Message.py", line 724, in get_filename
   filename = self.get_param('filename', missing, 'content-disposition')
 File "/home/mailman/pythonlib/email/Message.py", line 607, in get_param
   for k, v in self._get_params_preserve(failobj, header):
 File "/home/mailman/pythonlib/email/Message.py", line 554, in 
_get_params_preserve

   params = Utils.decode_params(params)
 File "/home/mailman/pythonlib/email/Utils.py", line 337, in decode_params
   charset, language, value = decode_rfc2231(EMPTYSTRING.join(value))
 File "/home/mailman/pythonlib/email/Utils.py", line 284, in decode_rfc2231
   charset, language, s = parts
ValueError: unpack list of wrong size



--
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=show&file=faq01.027.htp

Re: [Mailman-Users] How to move a list from 2.1.2

2006-10-31 Thread Dan Young
[EMAIL PROTECTED] wrote:
> Carl Zwanzig writes:
>  > I mean, how many people that install from RPMs even know that there
>  > might be a README file to read, let along to and find it?
> 
> This is something that has peeved me for a decade.  Installers for
> commercial software usually offer you the README after installation.
> Why don't pkgsrc and dpkg and rpm and portage and MacPorts do that?

If rpm asked me if I wanted to read the README every time I installed a
package, I'd claw my eyes out. rpm has always worked in a fully
automated fashion, i.e. no prompting for EULAs, etc.

"rpm -qld mailman" tells me where all the docs are, thankyouverymuch. ;-)

-- 
Dan Young <[EMAIL PROTECTED]>
Multnomah ESD - Technology Services
503-257-1562

--
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=show&file=faq01.027.htp


[Mailman-Users] RESOLVED: Cron <[EMAIL PROTECTED]> /usr/bin/python -S/var/mailman/cron/senddigests

2006-10-31 Thread Charles Gregory
Hi and thanks!

On Mon, 30 Oct 2006, Mark Sapiro wrote:
> I think the error comes from a messahe part that has
> Content-Transfer-Encoding: base64 and has incorrect padding at the
> end. You haven't seen it before, because it is the result of an
> encoding error by one person's broken MUA or possibly a message
> garbled in transit.

(nod) That is what I gathered from the web. But it keeps happening
every day. And thanks to your next comment I figured it out.

> You have to find the problem message which will be in some list's
> lists/listname/digest.mbox file and edit the file to either fix or
> remove the problem message. The list will be the first one in
> alphabetical order that isn't getting it's periodic digests.

THANKS! I keep forgetting that apart from our main list we have a couple
of other small 'unused' ones. Unused, except that they attract the
occasional piece of spam! While the digest.mbox for the main list was
cycling properly, the digest.mbox for one of the smaller ones was 'stuck'
starting with the date the error appeared!

Fortunately no one gets the digest on that list, so I just trashed it.
And I am also happy because this means there is no 'regular poster'
on the main list using a broken MUA. (wipe brow with relief)

Excellent! So the cause was what I thought. I just had to look in the
right list for the 'bad' message. Thanks again!

- Charles

--
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=show&file=faq01.027.htp