Re: [Mailman-Users] Disappearing message

2007-10-29 Thread Anne Ramey


Mark Sapiro wrote:
 Anne Ramey wrote:

   
 snip
 
 Way 2 is to modify scripts/post to log something. At the end of the
 main() function following:

 inq = get_switchboard(mm_cfg.INQUEUE_DIR)
 inq.enqueue(sys.stdin.read(),
 listname=listname,
 tolist=1, _plaintext=1)

 add

 print  sys.stderr, _('post to %(listname)s received and queued')


 This will write the 'post to %(listname)s received and queued' message
 with the listname filled in to both the error and post logs for every
 post. This again will tell you if the post got to the post script.

   
   
 snip

 OK, I added this code, but I get this:
 Oct 26 16:18:41 2007 post(17996): post to %(listname)s received and queued
 in the error log (it doesn't replace the listname with the variable) and 
 nothing in the post log.  Did I do something wrong?
 


 Nothing in the post log is correct. I forgot what the
 LogStdErr(error, post) call in the script does. I thought the
 second argument was a second log, but it's the identifying label.

 The non-replacement of %(listname)s with the name is puzzling. The i18n
 _() function should do this replacement. I copied the print directly
 from below and it worked for me. However, you could do the
 interpolation directly as in

 print  sys.stderr, 'post to %s received and queued' % listname

 and that should work.


   
I tried this and he re-sent the problem child message this morning.  I 
got the message in the error log that it was received and queued for 
both list1 and list2, but it only went out to list2.  There is only the 
one entry in the post log (for list 2), and the message never was 
received by the list1 membership.  He later resent (forwarded) the 
message to only list1 and it went through fine.  This tells me that 
Mailman is correctly receiving the message from exim, queuing it up, 
then it vanishes and never gets posted.  Here was the problem:I was 
Bcc'd on the message and these are what the headers looked like (I've 
taken out the received headers)

Return-Path: [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED] (added by [EMAIL PROTECTED])
From: sender [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: 'person1' person1
@ncmail.net,
'person2' person2
@ncmail.net,
'List2' List2
@lists.ncmail.net
Subject: [ITS.CAB] Agenda Change Advisory Board - Oct 30,2007 3:30pm - CCS 
Conference room
Date: Mon, 29 Oct 2007 10:39:34 -0400
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary==_NextPart_000_006F_01C81A17.FEDB8B30
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-SeenV-Signature: 380cab9dbfff031d1ef4ebe96869db18
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.1.9rc1
List-Unsubscribe: 
http://lists.ncmail.net/mailman/listinfo/List1,mailto:[EMAIL PROTECTED]
List-Help: mailto:[EMAIL PROTECTED]
List-Subscribe: http://lists.ncmail.net/mailman/listinfo/List1,mailto:[EMAIL 
PROTECTED]
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Acfu5oRLJ2rqVU9SRmCpWPWGXW+9IA==


He was copying a message from before that he had received, editting it 
and sending it to the list, so it already had the x-been-there headers.  
I'd never run into this before, so I thank Mark very much for 
recommending the BCC. 

Thanks for all the help,
Anne

--
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] Disappearing message

2007-10-26 Thread Anne Ramey
snip
 Way 2 is to modify scripts/post to log something. At the end of the
 main() function following:

 inq = get_switchboard(mm_cfg.INQUEUE_DIR)
 inq.enqueue(sys.stdin.read(),
 listname=listname,
 tolist=1, _plaintext=1)

 add

 print  sys.stderr, _('post to %(listname)s received and queued')


 This will write the 'post to %(listname)s received and queued' message
 with the listname filled in to both the error and post logs for every
 post. This again will tell you if the post got to the post script.

   
snip

OK, I added this code, but I get this:
Oct 26 16:18:41 2007 post(17996): post to %(listname)s received and queued
in the error log (it doesn't replace the listname with the variable) and 
nothing in the post log.  Did I do something wrong?

def main():
# TBD: If you've configured your list or aliases so poorly as to get
# either of these first two errors, there's little that can be done to
# save your messages.  They will be lost.  Minimal testing of new lists
# should avoid either of these problems.
try:
listname = sys.argv[1]
except IndexError:
print  sys.stderr, _('post script got no listname.')
sys.exit(1)
# Make sure the list exists
if not Utils.list_exists(listname):
print  sys.stderr, _('post script, list not found: %(listname)s')
sys.exit(1)
# Immediately queue the message for the incoming qrunner to 
process.  The
# advantage to this approach is that messages should never get lost --
# some MTAs have a hard limit to the time a filter prog can run.  
Postfix
# is a good example; if the limit is hit, the proc is SIGKILL'd 
giving us
# no chance to save the message.
inq = get_switchboard(mm_cfg.INQUEUE_DIR)
inq.enqueue(sys.stdin.read(),
listname=listname,
tolist=1, _plaintext=1)
print  sys.stderr, _('post to %(listname)s received and queued')


Anne
--
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] Disappearing message

2007-10-26 Thread Mark Sapiro
Anne Ramey wrote:

snip
 Way 2 is to modify scripts/post to log something. At the end of the
 main() function following:

 inq = get_switchboard(mm_cfg.INQUEUE_DIR)
 inq.enqueue(sys.stdin.read(),
 listname=listname,
 tolist=1, _plaintext=1)

 add

 print  sys.stderr, _('post to %(listname)s received and queued')


 This will write the 'post to %(listname)s received and queued' message
 with the listname filled in to both the error and post logs for every
 post. This again will tell you if the post got to the post script.

   
snip

OK, I added this code, but I get this:
Oct 26 16:18:41 2007 post(17996): post to %(listname)s received and queued
in the error log (it doesn't replace the listname with the variable) and 
nothing in the post log.  Did I do something wrong?


Nothing in the post log is correct. I forgot what the
LogStdErr(error, post) call in the script does. I thought the
second argument was a second log, but it's the identifying label.

The non-replacement of %(listname)s with the name is puzzling. The i18n
_() function should do this replacement. I copied the print directly
from below and it worked for me. However, you could do the
interpolation directly as in

print  sys.stderr, 'post to %s received and queued' % listname

and that should work.


def main():
# TBD: If you've configured your list or aliases so poorly as to get
# either of these first two errors, there's little that can be done to
# save your messages.  They will be lost.  Minimal testing of new lists
# should avoid either of these problems.
try:
listname = sys.argv[1]
except IndexError:
print  sys.stderr, _('post script got no listname.')
sys.exit(1)
# Make sure the list exists
if not Utils.list_exists(listname):
print  sys.stderr, _('post script, list not found: %(listname)s')
sys.exit(1)
# Immediately queue the message for the incoming qrunner to 
process.  The
# advantage to this approach is that messages should never get lost --
# some MTAs have a hard limit to the time a filter prog can run.  
Postfix
# is a good example; if the limit is hit, the proc is SIGKILL'd 
giving us
# no chance to save the message.
inq = get_switchboard(mm_cfg.INQUEUE_DIR)
inq.enqueue(sys.stdin.read(),
listname=listname,
tolist=1, _plaintext=1)
print  sys.stderr, _('post to %(listname)s received and queued')


-- 
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] Disappearing message

2007-10-24 Thread Anne Ramey

Mark Sapiro wrote:
 Anne Ramey wrote:

   
 Have a new and different one.  One of my users that has two lists, let's 
 call them list1 and list2.  If he sends a message to list1 and cc's 
 list2, list1 never receives the message.  If he sends the same message 
 only to list1, it goes through fine.  According to my exim logs, it is 
 delivering both messages to list1:
 


 The exim log certainly says the the first post was delivered to both
 lists, but ...


   
 The first message is successfully posted to list2, the second message is 
 successfully posted to list1.  The first message has absolutely no MM 
 longs relative to list1.  Nothing in the vette, smtp, post, error, 
 bounce, etc.  Nothing at all related to message one for List1.  This is 
 a weekly message and this has happened for the last 4+ weeks.  Before 
 that it appears to have worked fine.  I haven't made any system changes 
 in that time.  What could cause something like this.  Is is possible a 
 list setting could do this?  I checked the sender filters on both lists 
 but saw nothing that looked wrong.
 


 I can't offhand think of any way the a post can evaporate from Mailman
 without a trace.

 There are two ways to verify that the post actually reached Mailman.

 Way 1 is somewhat disruptive. Stop Mailman, send the post to list1 with
 cc to list2, examine the files in Mailman's qfiles/in queue with
 bin/dumpdb (bin/show_qfiles won't show the metadata which says which
 list the post is for) to see if the post is there twice, once for each
 list, then start Mailman.  If the post is in the in queue for list1
 and then evaporates, it is a Mailman problem, but I don't know what
 the problem might be. If the post doesn't get to the in queue then it
 could be an exim problem or possibly a problem with the post script.

 Way 2 is to modify scripts/post to log something. At the end of the
 main() function following:

 inq = get_switchboard(mm_cfg.INQUEUE_DIR)
 inq.enqueue(sys.stdin.read(),
 listname=listname,
 tolist=1, _plaintext=1)

 add

 print  sys.stderr, _('post to %(listname)s received and queued')


 This will write the 'post to %(listname)s received and queued' message
 with the listname filled in to both the error and post logs for every
 post. This again will tell you if the post got to the post script.

 Once we know whether or not the post gets this far, we can focus our
 attention and maybe come up with an answer or a way to get more
 information.

 One thing just occurred to me. Is it possible that the post to list1
 and list2 is somehow generated from a post from list1 and contains an

 X-BeenThere: [EMAIL PROTECTED]

 header, thus preventing it from being accepted by list1. Then perhaps
 the resend to list1 gets generated from the post from list2 and
 doesn't contain the

 X-BeenThere: [EMAIL PROTECTED]

 header.

   
Thank you for the reply.  I have to restart Mailman this weekend (during 
our maintenance window) anyway for another change.  I'll take way2 and 
see what I see the next week.  I'll let you know the results.

Thanks,

Anne 

--
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] Disappearing message

2007-10-24 Thread Mark Sapiro
Anne Ramey wrote:
   
Thank you for the reply.  I have to restart Mailman this weekend (during 
our maintenance window) anyway for another change.  I'll take way2 and 
see what I see the next week.  I'll let you know the results.


Note that the patch to scripts/post does not require a Mailman restart
to be effective or to be removed because the post script is run by the
mail wrapper in a new process invoked by the MTA for each message.

Also, if possible, have the poster of the message add a Bcc: directly
to you so you can see the headers in the incoming message in case
there's something there that's causing this.

-- 
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


[Mailman-Users] Disappearing message

2007-10-22 Thread Anne Ramey
Have a new and different one.  One of my users that has two lists, let's 
call them list1 and list2.  If he sends a message to list1 and cc's 
list2, list1 never receives the message.  If he sends the same message 
only to list1, it goes through fine.  According to my exim logs, it is 
delivering both messages to list1:

ex.

2007-10-22 08:28:48 1IjwOm-0002t6-2J = [EMAIL PROTECTED] H=myhost 
P=esmtp S=288168 [EMAIL PROTECTED] T=[List1] Agenda 
Change Advisory Board - Oct 23,2007 3:00pm
2007-10-22 08:28:48 1IjwOm-0002t6-2J = list1 [EMAIL PROTECTED] 
R=mailman_router T=mailman_transport
2007-10-22 08:28:48 1IjwOm-0002t6-2J = list2 [EMAIL PROTECTED] 
R=mailman_router T=mailman_transport
2007-10-22 08:28:48 1IjwOm-0002t6-2J Completed

2007-10-22 08:52:31 1Ijwli-0003WN-LD =  [EMAIL PROTECTED] H=myhost 
P=esmtp S=288873 [EMAIL PROTECTED] T=FW: [List2] 
[List1] Agenda Change Advisory Board -Oct 23, 2007 3:00pm
2007-10-22 08:52:31 1Ijwli-0003WN-LD = list1 [EMAIL PROTECTED] 
R=mailman_router T=mailman_transport
2007-10-22 08:52:31 1Ijwli-0003WN-LD Completed

The first message is successfully posted to list2, the second message is 
successfully posted to list1.  The first message has absolutely no MM 
longs relative to list1.  Nothing in the vette, smtp, post, error, 
bounce, etc.  Nothing at all related to message one for List1.  This is 
a weekly message and this has happened for the last 4+ weeks.  Before 
that it appears to have worked fine.  I haven't made any system changes 
in that time.  What could cause something like this.  Is is possible a 
list setting could do this?  I checked the sender filters on both lists 
but saw nothing that looked wrong.

Any assistance would be appreciated.

Anne
--
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