Re: [Mailman-Users] Importing Eudora email box into archives

[Mark Sapiro]

BG Mahesh wrote:
>
>Cool, I will try it out. How to preserve the attachments?

This is a problem.

I looked more closely at a Eudora .mbx file and I see that the MIME
structure of the messages is not preserved. The messages are
'flattened' - the outer Content-Type: header is preserved, but all
boundaries and part headers are removed and non-text attachments are
stored aside with a pointer left in the message.

Thus, the messages in the Eudora .mbx file are vaguely similar to
messages that have been scrubbed by Mailman's Scrubber.py module,
except the Content-Type: of the Eudora message is no longer correct
which will probably confuse the Mailman bin/arch process.

Thus, converting the Eudora .mbx will probably require a fairly
involved script. I'm not aware of an existing one.

-- 
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] Importing Eudora email box into archives

[Mark Sapiro]

BG Mahesh wrote:
>
>I have the archives of a mailing list in my Eudora mailbox [with
>attachments]. Is there anyway I could import it into Mailman archives?

bin/arch will probably do it.

I would do the following steps. First

bin/cleanarch < eudora.mbx > temp.mbox

Then it depends on whether or not there are existing Mailman archives
for the list, and if so, whether it is important to preserve the
existing message numbers in this archive. Basically, you want to
concatenate the existing archives/private/listname.mbox/listname.mbox
file if any and the temp.mbox created above.

If preserving message numbers is not a priority, it is best to do

cat temp.mbox archives/private/listname.mbox/listname.mbox > temp2.mbox
cp temp2.mbox archives/private/listname.mbox/listname.mbox

which will leave archives/private/listname.mbox/listname.mbox in
cronological sequence, but if you want to preserve message numbers,
you need to add temp.mbox to the end.

In either case, you then do

bin/arch --wipe listname

to totally rebuild the Pipermail archive from the default
archives/private/listname.mbox/listname.mbox.

You could just do the first step above and then do

bin/arch listname temp.mbox

To add the messages in temp.mbox to the existing listname Pipermail
archive, but then you have the archive split between two mbox files
which makes searching and subsequent rebuilding awkward.

-- 
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] Importing Eudora email box into archives

[BG Mahesh]

hi

I have the archives of a mailing list in my Eudora mailbox [with
attachments]. Is there anyway I could import it into Mailman archives?

--
--
B.G. Mahesh
--
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] 550 Recipient Address Rejected Error

[Mark Sapiro]

Phelps Williams wrote:
>
>I created the /etc/postfix/transport file just for this purpose, as in it
>was not in existence before.  As you might expect there is not a
>/etc/postfix/transport.db file.  Is this generated a certain way.


You need to do the postfix command

postmap /etc/postfix/transport

in order to generate the /etc/postfix/transport.db file.


-- 
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] Problem w/ alias

[noc ops]

Mark Sapiro wrote:
> noc ops wrote:
> 
>>In order to bypass my MX record, I like to point my mailman directly to
>>to e-mail server's ip address (10.0.0.10). See below cust and paste.
>>
>>
>>Is this correct? Please advice.
> 
> 
> 
> I don't know about the postfix stuff
-
no worries...I'll ping the list about postfix MX related question.


> 
> 
> 
>>/etc/mailman/mm_cfg.py
>>
>>#-
>># Default domain for email addresses of newly created MLs
>>DEFAULT_EMAIL_HOST = '10.0.0.10'
> 
> 
> 
> This is almost certainly wrong. This should be the domain that users
> address their list mail to. Unless you actually want Mailman mail to
> be addressed to e.g., [EMAIL PROTECTED], you don't want this.

Yeah I figured this the minute I saw my /var/log/mail.log complaining
about illegal address systax as you indicated. I've changed it since then.



regards,
/virendra

> 
--
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] Problem w/ alias

[Mark Sapiro]

noc ops wrote:
>
>In order to bypass my MX record, I like to point my mailman directly to
>to e-mail server's ip address (10.0.0.10). See below cust and paste.
>
>
>Is this correct? Please advice.


I don't know about the postfix stuff


>/etc/mailman/mm_cfg.py
>
>#-
># Default domain for email addresses of newly created MLs
>DEFAULT_EMAIL_HOST = '10.0.0.10'


This is almost certainly wrong. This should be the domain that users
address their list mail to. Unless you actually want Mailman mail to
be addressed to e.g., [EMAIL PROTECTED], you don't want 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=show&file=faq01.027.htp

Re: [Mailman-Users] Problem w/ alias

[noc ops]

Mark Sapiro wrote:
> noc ops wrote:
> 
>>What's interesting is, under 'Privacy Options'-->'Recipient filters' the
>>"Ceiling on acceptable number of recipients for a posting" was set to
>>10. So I've set this to 0 to see what happens.
> 
> 
> This has nothing to do with your issue. It is the number of explicit
> addresses in To: and Cc: headers of the message *to* the list which
> will cause the post to be held for moderator approval because of "too
> many recipients".
-
ok.

> 
> As Patrick said in reply to your followup, you now need to look to your
> MTA logs, but it is curious that your bounce log is empty. Is
> bounce_processing set off for this list?
-
I'm trying to bypass my spam filter and go directly to my e-mail server
to see if it could be causing issues.

In order to bypass my MX record, I like to point my mailman directly to
to e-mail server's ip address (10.0.0.10). See below cust and paste.


Is this correct? Please advice.



etc/postfix/main.cf

myhostname = mailman.domain.com
alias_maps = hash:/etc/aliases
##alias_maps = hash:/etc/postfix/aliases, hash:/var/lib/mailman/data/aliases
alias_database = hash:/etc/aliases
##alias_database = hash:/etc/postfix/aliases
myorigin = /etc/mailname
mydestination = mailman.domain.com, localhost.domain.com, , localhost
relayhost =  10.0.0.10
mynetworks = 127.0.0.0/8
mailbox_command = procmail -a "$EXTENSION"
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all


/etc/mailman/mm_cfg.py

#-
# Default domain for email addresses of newly created MLs
DEFAULT_EMAIL_HOST = '10.0.0.10'
#-
# Default host for web interface of newly created MLs
DEFAULT_URL_HOST   = 'mailman.domain.com'
#-



regards,
/virendra
--
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] Turn off wraping a line

[Mark Sapiro]

DongInn Kim wrote:
>
>Is there a simple configuration to turn off the functionality of
>wrapping a line in a mail?


If you're talking about 'header folding', then no, there is no option
to stop Mailman from doing this.

If you're talking about folding lines in the body of the message, I
don't know anywhere in Mailman where folding would be done except
maybe in content filtering html to plain text conversion. Folding is
more likely being done by the poster's MUA, the recipients MUA or if
the lines are really long by some MTA in the path to and from Mailman.
It's possible (I haven't looked into it) that Mailman folds really
long lines too. Note that by 'really long' I mean longer than the RFC
2821/2822 limit of 998 characters plus .

-- 
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] mailman and email harvesters

[Matthew Clarkson]

Mark Sapiro wrote:
> Matthew Clarkson wrote:
>
>   
>> We have switched half (about 15 so far) of our mailing lists from our 
>> majordomo server (with a hypermail based archiving system)  to our new 
>> mailman server.  I have just been notified by my boss that since the 
>> start of the switchover (3 weeks ago) he and a few other people have had 
>> a dramatic increase in spam based activity on their email accounts.
>> 
>
>
> Have they posted, or are they just members?
>
>   

They have all posted.

>> I 
>> checked to make sure my robots.txt on the webserver root was fine with 
>> the following entries
>>
>> User-agent: *
>> Disallow: /pipermail/
>> 
>
>
> Do you really think any spambot is going to honor a robots.txt file?
>
>   

I was aware that this is quite weak, but I knew that if I didn't mention 
it, it would have come up on the response to the initial email..

> If you have public archives, at a minimum you need
>
> ARCHIVER_OBSCURES_EMAILADDRS = Yes
>
> This is the default, but have you turned it off in mm_cfg.py? I'm not
> sure how effective the obfuscation is, but it's probably better than
> 'in the clear' addresses.
>
>   
This is set to obscure addresses (I have not changed any setting, either 
globally or list specific) to change this setting.
>> Also, I verified that all my lists private_roster settings were set to 
>> List members.
>>
>> Can anyone else think of, if it is mailman that is the culprit here, any 
>> settings or ways that email harvesters could grab email addresses from a 
>> mailman server?
>> 
>
>
> Can a spammer subscribe to your list and get the roster and then
> unsubscribe? I don't know if spammers are sophisticated enough to do
> this automatically, and I doubt they do it manually, but it is a
> possibility unless subscription requires approval or the roster is
> limited to admins.
>   
Yes, this could happen with most of our lists, but I would find it hard 
to believe (not that it is still not possible) that a spammer would 
spend his time on doing this for our relatively small (member wise) 
lists, especially as soon as we put our mailing lists up on mailman 
(less than a month ago),  this was the setting on our majordomo server 
for the last 3 years and we did not have this problem at all.

I mostly just wanted to verify with the original email I sent, that 
there wasn't a blatant setting I was overlooking which would lead to 
this.  I am thinking that it's not mailman, but probably another way 
that these harvesters are getting these email addresses.

Thank you very much for your insite and help into this Mark, I (and I'm 
sure many others) appreciate all the help you give this list.

--
Matthew Clarkson

--
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] Turn off wraping a line

[DongInn Kim]

Hi,

Is there a simple configuration to turn off the functionality of
wrapping a line in a mail?
I have mailman-2.1.6 installed on RHEL 4.
I apprecate your help in advance.

Regards,

-- DongInn
--
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 and email harvesters

[Mark Sapiro]

Matthew Clarkson wrote:

>We have switched half (about 15 so far) of our mailing lists from our 
>majordomo server (with a hypermail based archiving system)  to our new 
>mailman server.  I have just been notified by my boss that since the 
>start of the switchover (3 weeks ago) he and a few other people have had 
>a dramatic increase in spam based activity on their email accounts.


Have they posted, or are they just members?


>I 
>checked to make sure my robots.txt on the webserver root was fine with 
>the following entries
>
>User-agent: *
>Disallow: /pipermail/


Do you really think any spambot is going to honor a robots.txt file?

If you have public archives, at a minimum you need

ARCHIVER_OBSCURES_EMAILADDRS = Yes

This is the default, but have you turned it off in mm_cfg.py? I'm not
sure how effective the obfuscation is, but it's probably better than
'in the clear' addresses.


>Also, I verified that all my lists private_roster settings were set to 
>List members.
>
>Can anyone else think of, if it is mailman that is the culprit here, any 
>settings or ways that email harvesters could grab email addresses from a 
>mailman server?


Can a spammer subscribe to your list and get the roster and then
unsubscribe? I don't know if spammers are sophisticated enough to do
this automatically, and I doubt they do it manually, but it is a
possibility unless subscription requires approval or the roster is
limited to admins.

-- 
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] UnicodeError in admindb interface

[Mark Sapiro]

ts North wrote:

>I run several mailing lists under Mailman 2.1.6.   Recently 
> one of my mailing lists received 2 spam messages, I was able
> to delete one of them using the moderator admindb interface, but
> when I tried to delete the second message, I got the "hit a bug"
> page (traceback is listed below).
> 
> At that point I: ran check_db and check_perms, restarted the daemon,
> cleared out the locks.  No luck.


Restarting mailman shouldn't have been required. If you 'cleared locks'
you may now have multiple instances of the same qrunners running. This
needs to be addressed - see
.


> I found the heldmsg in data/ and deleted the message manually,
> which seems to have made matters worse.  Now when I access the 
> admindb web page for the mailing list, it throws the error right away before 
> displaying the admindb page (same traceback as before).  
> 
> I suspect I may have not deleted everything I need to delete.


That's right. You also need to delete the lists/listname/request.pck
that contains the request and points to the now non-existent heldmsg
file.

> I have
> considered upgrading to 2.1.7, but thought I should resolve this issue
> first.


I'm not sure if the underlying issue is fixed in 2.1.7 or not. At this
point, I would advise going to 2.1.8 (rc1 should be released this
weekend).

-- 
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] FAQ 6.9 on Debian Sarge

[Manlio Perillo]

Manlio Perillo ha scritto:
> [...]

> Mailman explicitly set the umask to 002 but postalias ignore it.
> Moreover in the manual page it is stated that, without the -p option,
> postalias should inherit file permission from the input file.
> 

I was wrong, it only inherits read access permission.
However I got an useful solution from one of postfix developers,
LaMont Jones:

Code not tested

# Mailman/MTA/Postfix.py
def _update_maps():
  # ...
  acmd = mm_cfg.POSTFIX_ALIAS_CMD + ' ' + ALIASFILE + \
 '&& chmod g+w ' + ALIASFILE
  # ...




Regards  Manlio Perillo

--
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 and email harvesters

[Matthew Clarkson]

We have switched half (about 15 so far) of our mailing lists from our 
majordomo server (with a hypermail based archiving system)  to our new 
mailman server.  I have just been notified by my boss that since the 
start of the switchover (3 weeks ago) he and a few other people have had 
a dramatic increase in spam based activity on their email accounts.  I 
checked to make sure my robots.txt on the webserver root was fine with 
the following entries

User-agent: *
Disallow: /pipermail/


Also, I verified that all my lists private_roster settings were set to 
List members.

Can anyone else think of, if it is mailman that is the culprit here, any 
settings or ways that email harvesters could grab email addresses from a 
mailman server?

--
Matthew Clarkson
--
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] Problem w/ alias

[Mark Sapiro]

noc ops wrote:
>
>What's interesting is, under 'Privacy Options'-->'Recipient filters' the
>"Ceiling on acceptable number of recipients for a posting" was set to
>10. So I've set this to 0 to see what happens.

This has nothing to do with your issue. It is the number of explicit
addresses in To: and Cc: headers of the message *to* the list which
will cause the post to be held for moderator approval because of "too
many recipients".

As Patrick said in reply to your followup, you now need to look to your
MTA logs, but it is curious that your bounce log is empty. Is
bounce_processing set off for this list?

-- 
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] Problem w/ alias

[Patrick Bogen]

On 3/31/06, noc ops <[EMAIL PROTECTED]> wrote:
> /var/log/mailman/smtp shows e-mails were delivered to all receipts
> within the alias.
>
You should check your MTA logs at this point to see why the messages
weren't delivered. Mailman handed them off properly- or at least
reported that it did.

--
- 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] Problem w/ alias

[noc ops]

noc ops wrote:
> Mark Sapiro wrote:
> 
>>noc ops wrote:
>>
>>
>>>For some unknown reason sending mail to this alias, not everyone (140
>>>users) on this list get messages. Few do and others don't?
>>>
>>>Is there a way to check for corruption? What should I be looking for?
>>>I'm kinda lost.
>>
>>
>>
>>Check Mailman's log files - particularly smtp, smtp-failure and bounce.
> 
> 
> I will check this in the morning and report back.
-
/var/log/mailman/smtp shows e-mails were delivered to all receipts
within the alias.

/var/log/smtp-failure and bounce is empty.


Is there anything that I'm may be overlooking?


regards,
/virendra


> 
> 
>>If the smtp log shows the post is sent to a smaller number than
>>expected, check the users settings in the membership list for 'nomail'
>>and maybe 'digest'. 
> 
> -
> Nope none of these are checked. I even subscribed/unsubscribed users
> from this alias with no avail. How do you fix the corruption issue.
> 
> 
> Also, are Topics defined for the list or were
> 
>>Topics ever defined? This can cause members to not get all messages.
> 
> -
> The topic filter is disabled.
> 
> 
> What's interesting is, under 'Privacy Options'-->'Recipient filters' the
> "Ceiling on acceptable number of recipients for a posting" was set to
> 10. So I've set this to 0 to see what happens.
> 
> 
> 
> 
> regards,
> /virendra
> 
> 
> --
> 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/aptgetd%40gmail.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

Re: [Mailman-Users] Creating my own confirm subscribe message

[Mark Sapiro]

Lasse Jensen wrote:
>
>I am new at using the Mailman and I am pretty impressed of all the
>possibilities. One thing I cant figure out though, is how to make my own
>"confirm subscribe"-message. I am sure its possible, but can't find out
>where to edit the automatic generated message?

See
.
The particular templates you want are subscribeack.txt and/or
verify.txt. Note that the subscribeack.txt template but not the
verify.txt template can be edited per list via the "Edit the public
HTML pages and text files" link on the admin web pages.

Also, on a different topic, you would do all of us who post to this
(mailman-users) list a favor if you would set your "Ikke til stede"
autoresponder to not respond to mail with a "Precedence: list" header,
or if you can't do that, disable delivery from this list before
turning on the autoresponder.

-- 
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] UnicodeError in admindb interface

[ts North]

I run several mailing lists under Mailman 2.1.6.   Recently 
 one of my mailing lists received 2 spam messages, I was able
 to delete one of them using the moderator admindb interface, but
 when I tried to delete the second message, I got the "hit a bug"
 page (traceback is listed below).
 
 At that point I: ran check_db and check_perms, restarted the daemon,
 cleared out the locks.  No luck.
 
 I found the heldmsg in data/ and deleted the message manually,
 which seems to have made matters worse.  Now when I access the 
 admindb web page for the mailing list, it throws the error right away before 
displaying the admindb page (same traceback as before).  
 
 I suspect I may have not deleted everything I need to delete.  I have
 considered upgrading to 2.1.7, but thought I should resolve this issue
 first.
 
 Any advice would be greatly appreciated, thanks,
 
 -Tom
 
 
 
 admin(24303): [- Traceback --] 
 admin(24303): Traceback (most recent call last):
 admin(24303):   File "/usr/local/mailman-2.1.6//scripts/driver", line 101, in 
 run_main
 admin(24303): main()
 admin(24303):   File "/usr/local/mailman-2.1.6/Mailman/Cgi/admindb.py", line 2
 34, in main
 admin(24303): num += show_helds_overview(mlist, form)
 admin(24303):   File "/usr/local/mailman-2.1.6/Mailman/Cgi/admindb.py", line 4
 85, in show_helds_overview
 admin(24303): mlist.HandleRequest(id, mm_cfg.DISCARD)
 admin(24303):   File "/usr/local/mailman-2.1.6/Mailman/ListAdmin.py", line 167
 , in HandleRequest
 admin(24303): forward, addr)
 admin(24303):   File "/usr/local/mailman-2.1.6/Mailman/ListAdmin.py", line 353
 , in __handlepost
 admin(24303): syslog('vette', note)
 admin(24303):   File "/usr/local/mailman-2.1.6/Mailman/Logging/Syslog.py", lin
 e 40, in write
 admin(24303): self.write_ex(kind, msg, args, kws)
 admin(24303):   File "/usr/local/mailman-2.1.6/Mailman/Logging/Syslog.py", lin
 e 58, in write_ex
 admin(24303): logf.write(msg + '\n')
 admin(24303):   File "/usr/local/mailman-2.1.6/Mailman/Logging/StampedLogger.p
 y", line 73, in write
 admin(24303): Logger.write(self, "%s %s" % (prefix, msg))
 admin(24303):   File "/usr/local/mailman-2.1.6/Mailman/Logging/Logger.py", lin
 e 91, in write
 admin(24303): f.write(msg)
 admin(24303): UnicodeError: ASCII encoding error: ordinal not in range(128)
 admin(24303): [- Python Information -] 
 admin(24303): sys.version =   2.2.3 (#1, Mar  9 2006, 18:16:14) 
 [GCC 3.2.3 20030502 (Red Hat Linux 3.2.3-53)] 
 admin(24303): sys.executable  =   /usr/bin/python 
 admin(24303): sys.prefix  =   /usr 
 admin(24303): sys.exec_prefix =   /usr 
 admin(24303): sys.path=   /usr 
 admin(24303): sys.platform=   linux2 
 admin(24303): [- Environment Variables -] 
 


-
Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.
--
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] Run mailman non-permanently?

[Patrick Bogen]

On 3/30/06, Friedemann Schorer <[EMAIL PROTECTED]> wrote:
> Hi Mark,
>
> > It is not necessary for Mailman to be running in order to accept
> > incoming Mailman mail. It will be passed to the mail/mailman wrapper
> > and queued whether or not Mailman is actually running. So, depending
> > on how much delay you can tolerate, you might be able to set up a cron
> > to start mailman say every 10 minutes and another to stop it say 1
> > minute later. You may need to experiment with this to insure that
> > queues don't get backlogged, but it might work.
It should be relatively trivial to check the status of the queues,
e.g. with some find magic. A wrapper script that (a) only runs mailman
if qfiles are present, and then (b) stops mailman some time after
there are no more qfiles might be a good way to accomplish this.

- 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] Creating my own confirm subscribe message

[Lasse Jensen]

Hi all
 
I am new at using the Mailman and I am pretty impressed of all the
possibilities. One thing I cant figure out though, is how to make my own
"confirm subscribe"-message. I am sure its possible, but can't find out
where to edit the automatic generated message?
 
All help will be deeply appreciated. 
 
Best regards

Lasse Jensen

 

---
Danish Red Cross Youth - Bragesgade 10, 2. sal
2200 København N - Tlf. 35 37 25 55 -   www.urk.dk
 
--
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