[Mailman-Users] sending messages after problem gone

2006-08-22 Thread Imre Gergely

hi

i had some problems with one of my lists, when i sent a message to the list, it
didnt get delivered, because some incorrect member adresses.
the mails landed in /var/spool/mailman/out. now, that the problem is resolved,
how can i resend the messages from out?
i have fedora core 2, with mailman version 2.1.8.
--
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] mailman and mysql

2006-06-20 Thread Imre Gergely

are there plans for using mysql to store lists/users data in a near future
version of mailman?

-- 
Imre Gergely
SysAdmin NOCS-CJ
Astral Telecom S.A.
Plugarilor 28, Cluj-Napoca
http://www.astral.ro
--
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] shunting

2006-05-27 Thread Imre Gergely

hi

mailman just started to behave strangely. i have a couple (20-30) lists, and
one or two started to 'now work' all of a sudden. mail sent to that list
disappears.
i looked in /var/log/mailman/error, and there i found these errors:

May 27 12:02:42 2006 (10050) Uncaught runner exception: unpack list of wrong 
size
May 27 12:02:42 2006 (10050) Traceback (most recent call last):
  File /var/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop
self._onefile(msg, msgdata)
  File /var/mailman/Mailman/Queue/Runner.py, line 167, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
  File /var/mailman/Mailman/Queue/IncomingRunner.py, line 130, in _dispose
more = self._dopipeline(mlist, msg, msgdata, pipeline)
  File /var/mailman/Mailman/Queue/IncomingRunner.py, line 153, in _dopipeline
sys.modules[modname].process(mlist, msg, msgdata)
  File /var/mailman/Mailman/Handlers/ToDigest.py, line 91, in process
send_digests(mlist, mboxfp)
  File /var/mailman/Mailman/Handlers/ToDigest.py, line 132, in send_digests
send_i18n_digests(mlist, mboxfp)
  File /var/mailman/Mailman/Handlers/ToDigest.py, line 306, in
send_i18n_digests
msg = scrubber(mlist, msg)
  File /var/mailman/Mailman/Handlers/Scrubber.py, line 240, in process
url = save_attachment(mlist, part, dir)
  File /var/mailman/Mailman/Handlers/Scrubber.py, line 359, in save_attachment
fnext = os.path.splitext(msg.get_filename(''))[1]
  File /var/tmp/mailman-root/var/mailman/pythonlib/email/Message.py, line
725, in get_filename
  File /var/tmp/mailman-root/var/mailman/pythonlib/email/Message.py, line
608, in get_param
  File /var/tmp/mailman-root/var/mailman/pythonlib/email/Message.py, line
555, in _get_params_preserve
  File /var/tmp/mailman-root/var/mailman/pythonlib/email/Utils.py, line
337, in decode_params
  File /var/tmp/mailman-root/var/mailman/pythonlib/email/Utils.py, line
284, in decode_rfc2231
ValueError: unpack list of wrong size

May 27 12:02:42 2006 (10050) SHUNTING:
1148720560.9632571+35d167125b7f3e005510df99b4728c1c6452c257

i have no idea what this means. i sent a couple of emails to this list, and
to others lists on the same mailman, from the same email client (firefox),
through the same server (postfix), and this particular list always gives this
error.

somebody got a hint to what to do? until yesterday, everything was ok. i
don't see any strange updates, or modifications in the packages.

[EMAIL PROTECTED] mailman]# rpm -qa | grep mailman
mailman-2.1.5-10.fc2

[EMAIL PROTECTED] mailman]# rpm -qa |grep ^python
python-devel-2.3.3-6
python-2.3.3-6
--
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] shunting

2006-05-27 Thread Imre Gergely

Mark Sapiro wrote:
 Mark Sapiro wrote:
 There is a malformed message - something wrong with an attachment
 filename - in lists/listname/digest.mbox for the offending list.

 See
 http://mail.python.org/pipermail/mailman-users/2006-May/051147.html
 where the actual message problem is different, but the solution is the
 same.
 
 
 BTW, I don't think it is mentioned in the above thread, but after
 fixing the problem in digest.mbox, you can run bin/unshunt to
 reprocess the shunted messages, but before doing that, look at all the
 messages in the shunt queue (qfiles/shunt/*) with bin/show_qfiles or
 bin/dumpdb, to make sure there aren't old, no longer wanted messages
 there. If there are unwanted messages in the shunt queue, just remove
 the unwanted files before running bin/unshunt.
 

it was kinda urgent, that's why i tried on the list first. after that i did
some search and found the solution, exactly what you said.
thx a lot for the help tho.

after solving this, i figured, on my lists nobody ever uses digest mode, so i
just disabled it on all lists, then deleted digest.mbox. i guess with this
setup, if a list gets a broken message which mailman can't handle, it will be
shunted and that's it, the rest of the list and messages won't be affected,
am i right?

and what happens with the archiving? the message gets archived before, or
after a successful delivery? in another words, is there a chance that a
broken message will be archived?

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

2006-05-19 Thread Imre Gergely

Mark Sapiro wrote:
 Patrick Bogen wrote:
 
 On 5/18/06, Imre Gergely [EMAIL PROTECTED] wrote:
 i have some problems with a mailman list.
 if i send from user A, to list L, and CC to B and C (where A,B,C are list
 members on the same list), the mail i got back from the list (to user A) is
 missing a CC address.
 i mean when i look at the message (using firefox) there is only one user 
 (B) in
 the CC list, the other one is gone.
 Is user C a member of list L? Mailman tries to not send duplicates,
 and it may in fact do this by stripping the address from the CC and
 sending it as a normal list post.
 
 Patrick is correct as to what happens, but it is a mystery to me why
 this is done. The AvoidDups handler makes a list of all explicit
 recipients of a message (addresses in To:, Cc:, Resent-To: and
 Resent-Cc:). It then goes through the message recipients (normally,
 the non-digest list members with delivery enabled) and any message
 recipient that is a list member and has DontReceiveDuplicates set is
 removed from the message recipients so that address doesn't receive a
 list message because it presumably receive a directly addressed
 message. So far, so good.
 
 But then, for reasons I don't understand, AvoidDups then removes this
 address from the Cc: header, if that's where it was. It doesn't remove
 it if it is in To:, Resent-To: or Resent-Cc:. It just removes it from
 Cc:. It is not clear (to me at least) why.
 
 But the bottom line is any address in Cc: that would otherwise have
 received the post from the list and that has DontReceiveDuplicates set
 will not receive the post from the list (because it presumably
 received the Cc:) and will be removed from the Cc: header of the
 message sent from the list.
 
 Note that this does not affect digest members who are in Cc: because
 they will not be candidate recipients of the message.
 

let me get this straight. when somebody who is on the list, is also in the CC:
of the message, it wont get the mail from the list, only from the original
poster, right? that's what this DontReceiveDupes does.

but the other members of the list do get the mail. they should see in the Cc:
that one person, who didn't get it because of above condition. or am i wrong 
here?
--
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 CC lines

2006-05-18 Thread Imre Gergely

hi

i have some problems with a mailman list.
if i send from user A, to list L, and CC to B and C (where A,B,C are list
members on the same list), the mail i got back from the list (to user A) is
missing a CC address.
i mean when i look at the message (using firefox) there is only one user (B) in
the CC list, the other one is gone.

i don't know why this is. could somebody help me out?

i tried to send the same mail to another address too (like yahoo), with CC, and
it appears alright. so i don't think it's my MTA.

MTA: postfix-2.2.2, mailman: 2.1.5, distrib: Fedora Core 2

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