Re: [Mailman-Users] Mail Processing Problem?

[Brad Knowles]

On 1/9/08, Dennis Putnam wrote:

>  It seems that is not what it is using for the RCPT TO.

RCPT TO is a recipient address.  Look through the list of subscribers 
for your list and make sure that they are all correctly formed and 
valid domains.

-- 
Brad Knowles <[EMAIL PROTECTED]>
LinkedIn Profile: 
--
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] spamassassin and mailman

[Brad Knowles]

On 1/9/08, Noah wrote:

>  many of our list moderators are receiving quite a bit of moderated
>  messages that is spam.  Sometimes 20 to 40 or even more times a day.  I
>  am wondering if there is a way to send all list mail through SA rules
>  and then trash the mail that is a specific score so it never even gets
>  moderated.  Any clues on how to accomplish this?

This kind of stuff needs to be done in the MTA, not Mailman.

That said, search the FAQ Wizard at 
 for "spam".

-- 
Brad Knowles <[EMAIL PROTECTED]>
LinkedIn Profile: 
--
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] Slow or Missed mails

[Brad Knowles]

On 1/9/08, Abdul Javid wrote:

>  I noticed the mail processing is slow and sometimes they are notprocessed
>  at all

Search the Mailman FAQ Wizard at 
 for words like 
"performance" and "troubleshoot".

-- 
Brad Knowles <[EMAIL PROTECTED]>
LinkedIn Profile: 
--
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] mailman logs - how to check if all members recievedmail

[Mark Sapiro]

Abdul Javid wrote:

>  Is there a way to check if the mail has be sent to all members in mailing 
> list


First, figure out how many recipients there should be. Get the possible
recipients with

  bin/list_members --regular --nomail=enabled listname | wc -l

Then figure out how many of those won't receive this post - the poster
if the poster has "Receive your own posts to the list?" set to No and
any list members directly addressed in To: or Cc: that have "Avoid
duplicate copies of messages?" set to Yes - and subtract from the
possible recipients.

Then go to Mailman's smtp log and find the message like:

Jan 10 13:03:41 2008 (368)  smtp to listname for nnn
recips, completed in t.ttt seconds

and verify that nnn is the expected number.

You can also check Mailman's smtp-failure and bounce logs for failed
deliveries and bounces reported to Mailman.

Beyond that, you have to ask the outgoing MTA.

-- 
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] UTF-8 question

[Eva Isaksson]

Mark Sapiro:
> I'm not certain about all of this, but there are places including
> Scrubber (removing attachments and flattening a message to plain text)
> and adding msg_header and msg_footer where the character set of a
> message can be coerced.

Yes, this seems to be the case. Our lists typically have umlaut
characters in their descriptions. Here's an example:

List-Id: =?utf-8?q?Vihreiden_vaikuttajien_sis=C3=A4inen_keskustelulista?=

Using a test list, I was able to find out that a list that has
only us-ascii in its headers and msg_footer will keep the original
charset untouched. As soon as any of those has any utf-8 stuff
in it, it causes a forced charset=utf-8.

I had spent more than a week trying to figure this out, 
so it's good to find out why this happens.

- Eva
-- 
 Eva Isaksson * [EMAIL PROTECTED] * [EMAIL PROTECTED]
 http://www.helsinki.fi/~eisaksso/
--
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] Mail Processing Problem?

[Mark Sapiro]

Dennis Putnam wrote:
>
>No. I do not have a static IP or a registered domain, which is why all
>mail from this server has to go through my ISP's server. However,
>non-mailman mail is sent just fine. If it is indeed the "MAIL FROM"
>then why would my changes in mm_cfg.py, not have fixed it? On the
>other hand, why would it complain about 'RCPT TO' rather then 'MAIL
>FROM'?


The changes you made in mm_cfg.py

DEFAULT_REPLY_GOES_TO_LIST = 2
REPLY_TO_ADDRESS = ''

have nothing to do with this issue. First, they only set defaults for
new lists. They have no effect on existing lists. Second, they only
have to do with a Reply-To: header in outgiong list posts which has
absolutely nothing to do with your problem.


>On the
>other hand, why would it complain about 'RCPT TO' rather then 'MAIL
>FROM'?


Lots of reasons. It could be a relaying issue which can't be detected
until the MTA knows the destination, or it could just be that the MTA
is configured to do the FROM domain check at RCPT time in the SMTP
transaction.

What is the exact reject response from the MTA?

What is the difference between 'non-Mailman' mail that works and
Mailman mail that doesn't. Does the non-Mailman mail come from a
different envelope from domain? Does non-Mailman mail use SMTP-AUTH to
authenticate to the ISP?

-- 
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] mailman logs - how to check if all members recieved mail

[Abdul Javid]

Hi
  Is there a way to check if the mail has be sent to all members in mailing list
   
  thanks in advance for your replies 
   
  Abdul 

   
-
Never miss a thing.   Make Yahoo your homepage.
--
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] Mail Processing Problem?

[Dennis Putnam]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Thanks for the reply.

No. I do not have a static IP or a registered domain, which is why all
mail from this server has to go through my ISP's server. However,
non-mailman mail is sent just fine. If it is indeed the "MAIL FROM"
then why would my changes in mm_cfg.py, not have fixed it? On the
other hand, why would it complain about 'RCPT TO' rather then 'MAIL
FROM'?

At 02:38 PM 1/10/2008, you wrote:

RCPT TO is the SMTP command for specifying the recipient(s) of the
message. These will be the addresses of the list members or the
owner/moderator or other recipient of a Mailman generated notice.

I do not thing that is what the ISP's MTA is complaining about. I
thing
it returns whatever reject status it is returning in response to a
RCPT TO command, but that doesn't mean it is complaining about the
recipient address.

I believe what it doesn't like is the MAIL FROM address - i.e. the
[EMAIL PROTECTED] address. Is your list's host_name in DNS?

- --
Mark Sapiro <[EMAIL PROTECTED]>The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (MingW32)

iD8DBQFHhpgQ/fiWYqZ2tVQRAiOiAKCZt1L6wcPut5WyOTGxYGvSoUT73QCeOYFD
l48NO6KUihIevmqal//eeMU=
=G09E
-END PGP SIGNATURE-


--
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] UTF-8 question

[Mark Sapiro]

Eva Isaksson wrote:
>
>The changes made for utf-8 included:
>- changing the template files and the Finnish translation file
>into utf-8 with iconv.
>- fixing the mm_cfg.py by making DEFAULT_CHARSET = 'UTF-8'
>and copying the relevant litany of LC_DESCRIPTIONS from
>Defaults.py into mm_cfg.py and setting Finnish into utf-8.


You really only needed to copy the one add_language() that you changed
(and also leave off the _() around the name) as in

add_language('fi', 'Finnish', 'utf-8')

>Now, the problem that keeps puzzling me:
>
>1. Before the change, mails with charset=iso-8859-1 and
>charset=utf-8 were being distributed with the charset
>untouched. I figured out as this is how it should be - right?


Yes, but not necessarily in all cases.


>2. As our server hosts a lot of lists (almost 400 of them)
>I decided to try utf-8 out on a smaller scale first, on an 
>Ubuntu server, running only a couple of lists with its standard 
>mailman package, version 2.1.5. The utf-8 change was a success. 
>The webpages and archive were all okay, and the charset of 
>mails was untouched too.
>
>3. As things looked promising, I decided to proceed with our
>real list server. The result: 
>Web pages, archive, all okay, now in utf-8.
>Mails... all of them in utf-8. And I mean ALL mails.
>
>My question: was this to be expected? Is everything meant
>to be in utf-8 from now on, including the forcing of
>charset=utf-8 into all list mail headers? And why didn't this 
>happen neither with the iso-8859-1 settings, nor with the
>Ubuntu server?


I'm not certain about all of this, but there are places including
Scrubber (removing attachments and flattening a message to plain text)
and adding msg_header and msg_footer where the character set of a
message can be coerced.

I did do a very simple test, and I don't see the problem.

Can you post an example of a test message as sent to a list and the
corresponding message as received from the list with the character set
coerced to UTF-8?


-- 
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] Some detail questions about migrating lists

[Mark Sapiro]

Frank Griffin wrote:
>
>According to the UPGRADE document, file formats have changed as have
>actual files (some new, some gone).  What triggers the 2.1 version to do
>the necessary conversions ?  Is it just finding files of the old version
>and recognizing them as such ?


Yes, as far as the old config.db to new config.pck conversion is
concerned.

As far as other files such as the pending database and qfiles are
concerned, these will be converted by bin/update if you are upgrading
an installation, but if you are simply moving lists from an old to a
new installation, it is best to deal with pending requests and queued
messages on the old system and blow off anything that is left. There
is no automated way of converting these in the new installation.


>Does the last_mailman_version in the
>data directory trigger this ?


No. last_mailman_version tells bin/update whether it needs to do
anything. This comes into play when installing an upgrade, but when
moving an old list's config.(db|pck) into an existing installation, it
is the DATA_FILE_VERSION in the config file itself that triggers the
update.


>There are various minor concerns, such as file permissions, aliases,
>redoing public archive symlinks, and so forth.  This made me wonder if
>it would be easier/possible to run bin/newlist for each existing 2.0
>list in the 2.1.9 system, and *then* bring over the data, lists, and
>archives/private directories.  Advisable ?


No. This is absolutely wrong. If you create the list on the new system
first, Mailman will always see that list's config.pck and will never
look at the config.db that you move over.

My advice is:

Do not create the lists on the new host.

Do not move anything from the data/ directory.

Move only the config.db from the lists// directories.

Move the archives/private/ tree.

Run bin/list_lists which will instantiate every list and convert every
old config.db to a new config.pck.

Run bin/genaliases to create/update aliases.

After conversion, remove the config.db files as if you don't, a
possible future problem in reading the config.pck and config.pck.last
files could cause Mailman to fall back to the then outdated config.db.

Public archive symlinks will be created automatically the first time a
list's configuration is saved. The bin/list_lists accessing and
converting of the config.db files won't do this, but a list post or
accessing the admin web interface for a list will.

-- 
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] Moderation Bit Problem

[Mark Sapiro]

Kathy Gee wrote:
>
>When the moderation bit for a member is turned on, that member gets an
>error message when trying to post a message.  The error message says
>"Your message could not be processed because of an internal error
>(software problem).  We are very sorry.  The system administrator has
>been notified of the problem."  I'm sure this message is pretty generic
>therefore not much help.  The message is no where to be found in any log
>that I can see and it never gets to the "tend to pending moderator
>requests" mode.


First thing to check is the list's Privacy options...->Sender filters
member_moderation_action and member_moderation_notice.

The only way I know that Mailman could be doing this is if that message
is set as member_moderation_notice, and member_moderation_action is
set to Reject.

Assuming that is not the reason, and that posts from unmoderated
members are processed normally, what are the full headers of this
message? Is there anything in Mailman's error log or othher logs with
a timestamp within a second or so of when this message is sent?

-- 
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] Mail Processing Problem?

[Mark Sapiro]

Dennis Putnam wrote:
>
>I'll give that a try. In the mean time maybe it is not what I thought
>based on your explanation. The specific error from my ISP complains
>about a missing DNS entry for RCPT TO. How do I set mailman to place
>the correct RCPT TO information in the headers for my SMTP server. I
>tried setting:
>
>DEFAULT_REPLY_GOES_TO_LIST = 2
>REPLY_TO_ADDRESS = ''
>
>It seems that is not what it is using for the RCPT TO.


RCPT TO is the SMTP command for specifying the recipient(s) of the
message. These will be the addresses of the list members or the
owner/moderator or other recipient of a Mailman generated notice.

I do not thing that is what the ISP's MTA is complaining about. I thing
it returns whatever reject status it is returning in response to a
RCPT TO command, but that doesn't mean it is complaining about the
recipient address.

I believe what it doesn't like is the MAIL FROM address - i.e. the
[EMAIL PROTECTED] address. Is your list's host_name in DNS?

-- 
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] Some detail questions about migrating lists

[Frank Griffin]

Hi all,

I need to migrate lists from an *old* Slackware system running MM 2.0
(0x20f0) to a new system where MM is installed via RPM (2.1.9).

I've read the posts linked to by the FAQ, and the basic procedure is to
copy the data, lists, and archives directories and run withlist
fix_url.  But I have a couple of minor questions:

According to the UPGRADE document, file formats have changed as have
actual files (some new, some gone).  What triggers the 2.1 version to do
the necessary conversions ?  Is it just finding files of the old version
and recognizing them as such ?  Does the last_mailman_version in the
data directory trigger this ?

There are various minor concerns, such as file permissions, aliases,
redoing public archive symlinks, and so forth.  This made me wonder if
it would be easier/possible to run bin/newlist for each existing 2.0
list in the 2.1.9 system, and *then* bring over the data, lists, and
archives/private directories.  Advisable ?

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