Re: [Mailman-Users] Basic bounce processing question

[Mark Sapiro]

Michael Kabot wrote:

>Follow up question on the below suggestion.
>
>In this configuration if a user replies, they will be replying to the
>-bounces address which will then send email to the Admin - not the entire
>list?


Not if their MUA does what it is supposed to do. Replies should go to
the From: overridden by Reply-To:, not to the Sender:.

This is no different than the ordinary case where the -bounces address
is used for automated bounce processing.


>How do I configure the list to use the "basename", without the -bounces, in
>the Sender: field?


If you really want to, 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] Basic bounce processing question

[Michael Kabot]

Follow up question on the below suggestion.

In this configuration if a user replies, they will be replying to the
-bounces address which will then send email to the Admin - not the entire
list?

How do I configure the list to use the "basename", without the -bounces, in
the Sender: field?

Thanks,

Mike

| -Original Message-
| From: Mark Sapiro [mailto:[EMAIL PROTECTED]
| Sent: Friday, November 16, 2007 11:31 AM
| To: [EMAIL PROTECTED]; Mailman-Users@python.org
| Subject: Re: [Mailman-Users] Basic bounce processing question
| 
| Michael Kabot wrote:
| >
| >Is there anyway to turn the bounce processing score feature off,
| prevent
| >bounces from going back to list members, but still have bounce
| messages go
| >the list owner?
| 
| 
| You do this in the MTA. If the MTA has an alias like:
| 
| listname-bounces: "|/path/to/mail/mailman bounces listname"
| 
| You change it to
| 
| listname-bounces: "|/path/to/mail/mailman owner listname"
| 
| If the MTA uses some other kind of routing for Mailman, you do the
| equivalent thing.
| 
| Note that bounces from RFC compliant MTAs will always be returned to
| the listname-bounces address (the envelope sender). That address is
| also put in Sender: and Errors-To: headers in the outgoing mail to
| help non-compliant MTAs get it right. Still, there are non-compliant
| MTAs that will return bounces to the From: or other header address.
| There's nothing Mailman can do about that.
| 
| --
| 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] aliasing for another domain

[Brad Knowles]

On 12/12/07, Paul wrote:

>  My idea is like like this.  I've tested it and it seems to work fine, but
>  am wondering if there is a more correct way.
>
>  * Make an mx record at "newdomain.com", such as "list.newdomain.com", and
>  give the new mx record the "mydomain" IP address.
>
>  * Add "list.newdomain.com" in my mx virtual domain table.
>
>  * Add all mailman's aliases in my mx's virtual table.

Depending on your MTA and how the aliases are generated for 
integration with your MTA, this step may not be necessary.

If you're going to have all the same lists with the same names in 
both domains, then you don't need to have virtual domain support 
within Mailman, just have the MTA recognize "list.newdomain.com" as a 
name that it should treat as "local".  At that point, the same system 
aliases for the old domain will now function for 
"list.newdomain.com", and you shouldn't need to do anything else with 
the aliases.

>  Is there an easier way to alias all of mailman's aliases, such as for
>  admin, bounces, confirm, join, leave, owner, request, subscribe,
>  unsubscribe?

If you're going to use the virtual alias table interface, then I 
don't see an easier way around this problem.  If you use local 
aliases instead (which only have a "local" address portion leaving 
off the host/domain part), then you should be fine.

-- 
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] Auto-Discard Sender Filter

[Brad Knowles]

On 12/12/07, Henry wrote:

>  I've talked to the list admins and they have all claimed that they did
>  not place these e-mail addresses there nor do they know how they got
>  there in the first place. Is there some sort of automatic "feature" in
>  Mailman that would be adding these e-mail addresses without manual
>  intervention? My first inclination after looking through the online
>  documentation and from using Mailman for the last few years was that
>  someone simply added these e-mail addresses manually by mistake and
>  either forgot about it or just didn't care to admit to doing it.

When you first pull up the moderation queue for a mailing list, 
anything that is held gives you at least one set of options you can 
take (allow, reject, discard, etc...) but if the post came from a 
non-member you get an additional set of options you can take 
(including putting the sender address on the auto-discard list, the 
auto-accept list, etc...).

This is the only other way I know of to "automatically" put addresses 
on one of the per-list whitelists or blacklists.

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

[Mailman-Users] aliasing for another domain

[Paul]

I have been hosting a some mailman list for years now, and now we are
looking into getting the list from [EMAIL PROTECTED] to
[EMAIL PROTECTED]

Here are some specifics:
The new domain already has a mail server and hosting web pages.

My idea is like like this.  I've tested it and it seems to work fine, but
am wondering if there is a more correct way.

* Make an mx record at "newdomain.com", such as "list.newdomain.com", and
give the new mx record the "mydomain" IP address.

* Add "list.newdomain.com" in my mx virtual domain table.

* Add all mailman's aliases in my mx's virtual table.

* Change the "Host name this list prefers for email" line in the "general
options page" to "list.newdomain.com".

My questions are:

Is there an easier way to alias all of mailman's aliases, such as for
admin, bounces, confirm, join, leave, owner, request, subscribe,
unsubscribe?

Also, the web interface will still be at "mydomain.com", which should not
be a problem, I guess a cname could be done for "list.newdomain.com", but
then I don't want to have that much control over that subdomain, just mx
for it.

--
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] Bounce management and uncaught bounce notifications

[Stephen J. Turnbull]

[EMAIL PROTECTED] writes:

 > Q1Why are they called 'uncaught' ... ?

This is pretty standard jargon.  There are low level routines, each of
which traps the errors it expects.  Some trap mice, some trap bears,
some trap bacteria.

Every once in a while, something unimaginable like the Loch Ness
Monster comes along and eludes all the traps.  So Mailman sets up a
moat around the castle in a high level routine, and it is the high-
level routine that eventually catches the tricky ones swimming in the
moat, and throws them in the dungeon because it has nothing useful to
do with them.  Then it calls the Sherriff (that's you!) to decide what
to do with them.

So "uncaught" is elliptical: it means "uncaught by one of the handlers
for errors we are prepared to handle sanely."

>From the "aren't you glad you asked?" department.

--
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] listinfo_url and optionsurl alternatives?

[Mark Sapiro]

Michael Grueter wrote:
>
>On Dec 10, 2007, at 1:10 PM, Mark Sapiro wrote:
>
>> If you have the appropriate add_virtualhost() directives in mm_cfg.py
>> for this host and you have run fix_url if necessary to give the list
>> the correct web_page_url attribute, you should get the URL's you want
>> from the default template.
>>
>> See some of the articles returned by
>> > query=web_page_url&querytype=simple&casefold=yes&req=search>.
>
>Hi Mark,
>
>Thanks for the info. I was able to play with the variables you  
>mentioned and it works. So as far as correctly configuring Mailman is  
>concerned, are you saying that I should not have to edit  
>subscribeack.txt in order for the "host name this list prefers for  
>email" to show up instead of the generic mail server host name?


For purposes of discussion, let's say the "host name this list prefers
for email" is example.com.

Then, what I am saying is that if the URLs for your list's web pages
should be of the form http://example.com/mailman/..., the list's
hidden web_page_url attribute should be 'http://example.com/mailman/'
and then %(listinfo_url)s will produce
http://example.com/mailman/listinfo/listname and %(optionsurl)s will
produce http://example.com/mailman/options/listname/username%40domain


Now there are several ways to accomplish this, but first you should have

add_virtualhost('example.com', 'example.com')

in mm_cfg.py. Then you can run

bin/withlist -r -r fix_url listname -u example.com

to fix the list.


>I'm running Mac OS X Server 10.4.10 and there is a GUI admin tool for  
>configuring mailing lists. This is what I used to setup my mailing  
>list. Maybe it is not configuring things properly. Are you familiar  
>with this tool?


No, although I know that some people who run Apple's Mac OS X Server
Mailman forgo Apples GUI and use Mailman's web admin interface instead.

-- 
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] Implicit destination

[Mark Sapiro]

Barry Finkel wrote:

>Steve Burling wrote:
>>>
>>>But as near as I can tell, she *is* putting the list address in the To: 
>>>field, it's just been munged (presumably by Micro$oft LookOut) to have 
>>>quotes in funny places.  Here's what the To: field looks like from the 
>>>listname.mbox file (edited to protect the innocent):
>>>
>>>To: "[EMAIL PROTECTED]" <'[EMAIL PROTECTED]'>
>>>
>>>Are those unnecessary single quotes inside the "<...>" confusing Mailman? 
>
>And Mark Sapiro replied:
>
>>Python's email.Utils.parseaddr() returns the single quotes as part of
>>the address.
>>
>>I hate to be in a position of defending LookOut, but are you sure she
>>doesn't have the quoted address in her address book entry?
>>
>>If this can't be fixed at her end, you could put the quoted address in
>>the list's acceptable_aliases.
>
>>From my reading of RFC2821, 
>
> <'[EMAIL PROTECTED]'>
>
>is invalid.  Here is how I parse it, followed by the RFC 2821
>definitions:


It is clearly invalid, no argument about that, but the question was
what to do about it.


>To: "[EMAIL PROTECTED]" <'[EMAIL PROTECTED]'>
>To: [display-name] angle-addr
>To: [display-name] "<" addr-spec ">"
>To: [display-name] "<" local-part "@" domain ">"
>
>to  =   "To:" address-list CRLF
>address-list=   (address *("," address)) / obs-addr-list
>address =   mailbox / group
>mailbox =   name-addr / addr-spec
>name-addr   =   [display-name] angle-addr
>display-name=   phrase
>angle-addr  =   [CFWS] "<" addr-spec ">" [CFWS] / obs-angle-addr
>addr-spec   =   local-part "@" domain
>local-part  =   dot-atom / quoted-string / obs-local-part
>obs-addr-list   =   1*([address] [CFWS] "," [CFWS]) [address]
>obs-angle-addr  =   [CFWS] "<" [obs-route] addr-spec ">" [CFWS]
>
>Note that 
>
> addr-spec
>
>does not have apostrophes at each end.


BTW, only the edu' part is invalid as only letters, digits and
non-leading hyphens can appear in the dot-separated pieces of domain,
but the 'list part is a legal local-part.


-- 
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] Auto-Discard Sender Filter

[Mark Sapiro]

Charles Marcus wrote:

>On 12/12/2007, Mark Sapiro ([EMAIL PROTECTED]) wrote:
>> There is also an option in the admindb interface to add the sender of
>> a held non-member post to one of the *_these_nonmembers filters when
>> handling the post. This may explain how the addresses got in the
>> OP's list without the admin's remembering putting them there.
>
>Yeah, thats the one I was thinking of... but the funny thing is, I just 
>tested this and I don't see that option when I go to deal with the 
>post... is there a way to disable these so you don't see them at all?


The option is only there for posts from non-members. Posts from members
held for moderation or other reasons will not have that option because
it doesn't make sense for them.

-- 
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] Auto-Discard Sender Filter

[Charles Marcus]

On 12/12/2007, Mark Sapiro ([EMAIL PROTECTED]) wrote:
> There is also an option in the admindb interface to add the sender of
> a held non-member post to one of the *_these_nonmembers filters when
> handling the post. This may explain how the addresses got in the
> OP's list without the admin's remembering putting them there.

Yeah, thats the one I was thinking of... but the funny thing is, I just 
tested this and I don't see that option when I go to deal with the 
post... is there a way to disable these so you don't see them at all?

-- 

Best regards,

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

Re: [Mailman-Users] listinfo_url and optionsurl alternatives?

[Michael Grueter]

On Dec 10, 2007, at 1:10 PM, Mark Sapiro wrote:

> Michael Grueter wrote:
>
>> The subscribeack.txt template file uses two variables that I would
>> like to change:
>>
>> 1) %(listinfo_url)s produces the following URL:
>>
>> http://hostname/mailman/listinfo/listname
>>
>> where hostname is the generic host name for the mail server.
>>
>> 2) %(optionsurl)s produces a similar URL with the same generic  
>> hostname:
>>
>> http://hostname/mailman/options/listname/username%40domain
>>
>> Instead, I would like Mailman to use the custom "host name this list
>> prefers for email" as entered in the General Options page of the
>> Administration web page. What variables would I use to do this?
>
> %(host_name)s is exactly that.
>
> If you want to make a url, you would need something like
>
> http://%(host_name)s/mailman/listinfo/listname
>
> or
>
> http://%(host_name)s/mailman/options/listname/%(user)s
>
> although if that's what you're trying to do, your Mailman and/or your
> list is not properly configured.
>
> If you have the appropriate add_virtualhost() directives in mm_cfg.py
> for this host and you have run fix_url if necessary to give the list
> the correct web_page_url attribute, you should get the URL's you want
> from the default template.
>
> See some of the articles returned by
>  query=web_page_url&querytype=simple&casefold=yes&req=search>.

Hi Mark,

Thanks for the info. I was able to play with the variables you  
mentioned and it works. So as far as correctly configuring Mailman is  
concerned, are you saying that I should not have to edit  
subscribeack.txt in order for the "host name this list prefers for  
email" to show up instead of the generic mail server host name?

I'm running Mac OS X Server 10.4.10 and there is a GUI admin tool for  
configuring mailing lists. This is what I used to setup my mailing  
list. Maybe it is not configuring things properly. Are you familiar  
with this tool?

Thanks,

- Mike
--
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] Auto-Discard Sender Filter

[Mark Sapiro]

Charles Marcus wrote:

>Mark Sapiro, on 12/12/2007 4:06 PM, said the following:
>> Henry wrote:
>>> My first inclination after looking through the online
>>> documentation and from using Mailman for the last few years was that
>>> someone simply added these e-mail addresses manually by mistake and
>>> either forgot about it or just didn't care to admit to doing it.
>>> Basically I just wanted to make sure there wasn't anything I've missed
>>> and this was in fact just user error and some feature you can
>>> enable/disable through the admin options.
>
>> When a list is created, the *_these_nonmember fields are empty. There
>> is no feature/option/configuration setting to make them otherwise by
>> default.
>
>Seems like I recall seeing an option to 'discard messages from this 
>poster' when handling some administrative holds at some time, but I 
>don't see it now...


Privacy options...->Sender filters->discard_these_nonmembers.

There is also an option in the admindb interface to add the sender of a
held non-member post to one of the *_these_nonmembers filters when
handling the post. This may explain how the addresses got in the OP's
list without the admin's remembering putting them there.

-- 
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] Auto-Discard Sender Filter

[Charles Marcus]

Mark Sapiro, on 12/12/2007 4:06 PM, said the following:
> Henry wrote:
>> My first inclination after looking through the online
>> documentation and from using Mailman for the last few years was that
>> someone simply added these e-mail addresses manually by mistake and
>> either forgot about it or just didn't care to admit to doing it.
>> Basically I just wanted to make sure there wasn't anything I've missed
>> and this was in fact just user error and some feature you can
>> enable/disable through the admin options.

> When a list is created, the *_these_nonmember fields are empty. There
> is no feature/option/configuration setting to make them otherwise by
> default.

Seems like I recall seeing an option to 'discard messages from this 
poster' when handling some administrative holds at some time, but I 
don't see it now...

-- 

Best regards,

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

Re: [Mailman-Users] Auto-Discard Sender Filter

[Mark Sapiro]

Henry wrote:
>
>My first inclination after looking through the online
>documentation and from using Mailman for the last few years was that
>someone simply added these e-mail addresses manually by mistake and
>either forgot about it or just didn't care to admit to doing it.
>Basically I just wanted to make sure there wasn't anything I've missed
>and this was in fact just user error and some feature you can
>enable/disable through the admin options.


When a list is created, the *_these_nonmember fields are empty. There
is no feature/option/configuration setting to make them otherwise by
default.

-- 
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] Extracting e-mail addresses from a dead machine

[Mark Sapiro]

Dragon wrote:

>Mark Sapiro sent the message below at 07:48 12/12/2007:
>
>>If you did have access to a Mailman installation, you could run
>>Mailman's bin/dumpdb against the config.pck which would produce output
>>easier to deal with, or you could create a lists// directory
>>in that installation, put the config.pck in it and run
>>"bin/list_members -f -p "
> End original message. -
>
>Is it really necessary to have a fully functioning Mailman 
>installation to do this?
>
>Would it not be sufficient to have Python installed, a copy of the 
>dumpdb script and the config.pck file?


Nope. There are two issues. The first is that there are imports of
Mailman modules in dumpdb. The 'import paths' which among other things
inserts the path to mailman in sys.path so that Mailman modules can be
imported needs to be removed if there is no paths module or path to
the Mailman installation. There is also a 'from Mailman.i18n import _'
which can be replaced with

def _(s):
return s

If you do those things, the dumpdb script will run, but then you will
likely encounter the second issue. The config.pck probably contains
instances of the _BounceInfo class defined in Mailman/Bouncer.py. If
so, the unpickling needs to import that module to understand the
_BounceInfo class instances. So you need that module plus everything
it imports, etc.

I.e. you need pretty much a whole Mailman installation.

-- 
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] Implicit destination

[Barry Finkel]

Steve Burling wrote:
>>
>>But as near as I can tell, she *is* putting the list address in the To: 
>>field, it's just been munged (presumably by Micro$oft LookOut) to have 
>>quotes in funny places.  Here's what the To: field looks like from the 
>>listname.mbox file (edited to protect the innocent):
>>
>>To: "[EMAIL PROTECTED]" <'[EMAIL PROTECTED]'>
>>
>>Are those unnecessary single quotes inside the "<...>" confusing Mailman? 

And Mark Sapiro replied:

>Python's email.Utils.parseaddr() returns the single quotes as part of
>the address.
>
>I hate to be in a position of defending LookOut, but are you sure she
>doesn't have the quoted address in her address book entry?
>
>If this can't be fixed at her end, you could put the quoted address in
>the list's acceptable_aliases.

>From my reading of RFC2821, 

 <'[EMAIL PROTECTED]'>

is invalid.  Here is how I parse it, followed by the RFC 2821
definitions:

To: "[EMAIL PROTECTED]" <'[EMAIL PROTECTED]'>
To: [display-name] angle-addr
To: [display-name] "<" addr-spec ">"
To: [display-name] "<" local-part "@" domain ">"

to  =   "To:" address-list CRLF
address-list=   (address *("," address)) / obs-addr-list
address =   mailbox / group
mailbox =   name-addr / addr-spec
name-addr   =   [display-name] angle-addr
display-name=   phrase
angle-addr  =   [CFWS] "<" addr-spec ">" [CFWS] / obs-angle-addr
addr-spec   =   local-part "@" domain
local-part  =   dot-atom / quoted-string / obs-local-part
obs-addr-list   =   1*([address] [CFWS] "," [CFWS]) [address]
obs-angle-addr  =   [CFWS] "<" [obs-route] addr-spec ">" [CFWS]

Note that 

 addr-spec

does not have apostrophes at each end.
--
Barry S. Finkel
Computing and Information Systems Division
Argonne National Laboratory  Phone:+1 (630) 252-7277
9700 South Cass Avenue   Facsimile:+1 (630) 252-4601
Building 222, Room D209  Internet: [EMAIL PROTECTED]
Argonne, IL   60439-4828 IBMMAIL:  I1004994

--
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] Extracting e-mail addresses from a dead machine

[Dragon]

Mark Sapiro sent the message below at 07:48 12/12/2007:
>Visvanath Ratnaweera wrote:
> >
> >I have the data backup from a dead machine. The list is not moved
> >to a new server (yet). Therefore I have no running system of Mailman.
> >
> >Is there a way of extracting the e-mail addresses from this (data)
> >backup?



>If you did have access to a Mailman installation, you could run
>Mailman's bin/dumpdb against the config.pck which would produce output
>easier to deal with, or you could create a lists// directory
>in that installation, put the config.pck in it and run
>"bin/list_members -f -p "
 End original message. -

Is it really necessary to have a fully functioning Mailman 
installation to do this?

Would it not be sufficient to have Python installed, a copy of the 
dumpdb script and the config.pck file?





Dragon

~~~
  Venimus, Saltavimus, Bibimus (et naribus canium capti sumus)
~~~

--
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] Extracting e-mail addresses from a dead machine

[Visvanath Ratnaweera]

Hi Mark

Ref: Mark Sapiro <[EMAIL PROTECTED]> 12.12.2007 18:16

I'm impressed by the support one gets in this list!

> Visvanath Ratnaweera wrote:
> >
> >I have the data backup from a dead machine. The list is not moved
> >to a new server (yet). Therefore I have no running system of Mailman.
> >
> >Is there a way of extracting the e-mail addresses from this (data)
> >backup?
> 
> 
> The addresses are in Mailman's lists//config.pck file on the
> backup.  All the good ways of getting them require access to a Mailman
> installation somewhere. Since you don't have that, you are left with
> running 'strings config.pck' and sifting through the output for the
> addresses.

That defeats the original purpose. Until I get the list running
there was an urgent mail to be sent - only in case if there is a
trivial solution.
 
> If you did have access to a Mailman installation, you could run
> Mailman's bin/dumpdb against the config.pck which would produce output
> easier to deal with, or you could create a lists// directory
> in that installation, put the config.pck in it and run
> "bin/list_members -f -p "

I think better get the list working before the next "urgency" ;-(
Will come back if there is a need. Thanks a lot!

Visvanath
--
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] Auto-Discard Sender Filter

[Henry]

Hello All,

One of our Mailman mailing lists appears to have several e-mail
addresses listed under the sender filter section:

"List of non-member addresses whose postings will be automatically discarded"

I've talked to the list admins and they have all claimed that they did
not place these e-mail addresses there nor do they know how they got
there in the first place. Is there some sort of automatic "feature" in
Mailman that would be adding these e-mail addresses without manual
intervention? My first inclination after looking through the online
documentation and from using Mailman for the last few years was that
someone simply added these e-mail addresses manually by mistake and
either forgot about it or just didn't care to admit to doing it.
Basically I just wanted to make sure there wasn't anything I've missed
and this was in fact just user error and some feature you can
enable/disable through the admin options.

Anyone's input will be much appreciated. Thanks!

-- 
Henry Chang
henhowc at ucla.edu
University of California, Los Angeles
--
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] PHP Script for search archive

[Brian Carpenter]

All you do is just follow the on screen instructions. You will need to make 
sure you create a database and a database user that is setup to access the 
database. You will need the following information to properly setup sphyder:

database name:
database username:
database password:

You can download the script at the following location:

http://www.emwd.com/download/searchable_archives.tar.bz2

If anyone improves it then please let me know.

Regards,
Brian
--
EMWD.com -  'Powered by Techies'


-Original Message-
From: Ivan Van Laningham [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, December 12, 2007 11:19 AM
To: Brian Carpenter; mailman-users@python.org
Subject: Re: [Mailman-Users] PHP Script for search archive

Hi All--
Me!  Me!  Me!

;-)  I'm interested, very!

As part of my dedicated server from GoDaddy, which uses Plesk for an 
admin interface, a mysql DB is pre-installed.  How difficult is it for a 
DB neophyte to integrate with an existing setup like that?

Metta,
Ivan

Brian Carpenter wrote:
> We have come up with a php script that provides a search function for 
> mailman. It uses the sphyder search engine and requires a mysql database. The 
> script comes with an installation feature that will automatically install 
> sphyder and do the initial indexing of the archive. It works with both 
> private and public archives. You will need a member subscription to the list 
> in question if the archives are private. Once the installation is done then 
> all that is needed is to run a cron job that indexes new posts into the mysql 
> database.
> The limitations to this script is that it requires a mysql db and can only be 
> installed on a list by list basis. Also the search page is NOT integrated 
> with archives. It is setup as a separate page outside of the mailing list 
> archives however that has not been an issue with our clients. It can probably 
> be integrated easy enough into your archives if you want.
> If there is enough interest in this then I will make it a free download and 
> perhaps someone can create a FAQ entry to the download. Just let me know.
> Regards,Brian--EMWD.com -  'Powered by 
> Techies'
> -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> On Behalf Of Peter EdleySent: Wednesday, December 12, 2007 10:15 AMTo: [EMAIL 
> PROTECTED]: Re: [Mailman-Users] PHP Script for search archive
> Not sure if there where any replies to this off list if so could youplease 
> repost to the list since this is somthing I would be interestedin.
> 
> On Tue, 2007-12-11 at 12:24 -0300, Hermes PHP wrote:> Hi,> >  > > Does anyone 
> know of any script in PHP that look inside archives of the list?> >  > > The 
> archives of the list are private.> >  > > > > Solution in phyton or perl not 
> serve to me, has to be in PHP> >  > > > > Att,> > 'É um orgulho ter você como 
> nosso cliente'> >  > Hermes Alves> Gerente TI>  > 
> ArgoHost.net> Hospedagem Web com Facilidade>  
> http://www.argohost.net/> http://www.argohost.net> Suporte 
> Telefônico: (85) 3264 9944 / (11) 4063 4844 R. 102> E-mail:  
> mailto:[EMAIL PROTECTED]>> [EMAIL PROTECTED]> >  > > > > 
> --> 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/peter%40cww.org.uk> > Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
> --Mailman-Users mailing 
> [EMAIL PROTECTED]://mail.python.org/mailman/listinfo/mailman-usersMailman 
> FAQ: http://www.python.org/cgi-bin/faqw-mm.pySearchable Archives: 
> http://www.mail-archive.com/mailman-users%40python.org/Unsubscribe: 
> http://mail.python.org/mailman/options/mailman-users/brian%40emwd.com
> Security Policy: 
> http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
> --Mailman-Users mailing 
> [EMAIL PROTECTED]://mail.python.org/mailman/listinfo/mailman-usersMailman 
> FAQ: http://www.python.org/cgi-bin/faqw-mm.pySearchable Archives: 
> http://www.mail-archive.com/mailman-users%40python.org/Unsubscribe: 
> http://mail.python.org/mailman/options/mailman-users/ivanlan%40pauahtun.org
> Security Policy: 
> http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
> 

-- 
Ivan Van Laningham
God N Locomotive Works
http://www.pauahtun.org/
http://www.python.org/workshops/1998-11/proceedings/papers/laningham/laningham.html
Army Signal Corps:  Cu Chi, Class of '70
Author:  Teach Yourself Python in 24 Hours

--
Mailman-Users mailing list
Mailman-User

Re: [Mailman-Users] Implicit destination

[Mark Sapiro]

Steve Burling wrote:
>
>But as near as I can tell, she *is* putting the list address in the To: 
>field, it's just been munged (presumably by Micro$oft LookOut) to have 
>quotes in funny places.  Here's what the To: field looks like from the 
>listname.mbox file (edited to protect the innocent):
>
>To: "[EMAIL PROTECTED]" <'[EMAIL PROTECTED]'>
>
>Are those unnecessary single quotes inside the "<...>" confusing Mailman? 


Python's email.Utils.parseaddr() returns the single quotes as part of
the address.

I hate to be in a position of defending LookOut, but are you sure she
doesn't have the quoted address in her address book entry?

If this can't be fixed at her end, you could put the quoted address in
the list's acceptable_aliases.

-- 
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] PHP Script for search archive

[Richard Pyne]

Definitely interested.

Thanks.

--Richard

On 12 Dec 2007 at 10:54, Brian Carpenter wrote:

> We have come up with a php script that provides a search function for 
> mailman. It uses the sphyder search engine and requires a mysql database. The 
> script comes with an installation feature that will automatically install 
> sphyder and do the initial indexing of the archive. It works with both 
> private and public archives. You will need a member subscription to the list 
> in question if the archives are private. Once the installation is done then 
> all that is needed is to run a cron job that indexes new posts into the mysql 
> database.
> 
> The limitations to this script is that it requires a mysql db and can only be 
> installed on a list by list basis. Also the search page is NOT integrated 
> with archives. It is setup as a separate page outside of the mailing list 
> archives however that has not been an issue with our clients. It can probably 
> be integrated easy enough into your archives if you want.
> 
> If there is enough interest in this then I will make it a free download and 
> perhaps someone can create a FAQ entry to the download. Just let me know.
> 
> Regards,
> Brian
> --
> EMWD.com -  'Powered by Techies'
> 
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Edley
> Sent: Wednesday, December 12, 2007 10:15 AM
> To: mailman-users@python.org
> Subject: Re: [Mailman-Users] PHP Script for search archive
> 
> Not sure if there where any replies to this off list if so could you
> please repost to the list since this is somthing I would be interested
> in.
> 
> 
> On Tue, 2007-12-11 at 12:24 -0300, Hermes PHP wrote:
> > Hi,
> > 
> >  
> > 
> > Does anyone know of any script in PHP that look inside archives of the list?
> > 
> >  
> > 
> > The archives of the list are private.
> > 
> >  
> > 
> > 
> > 
> > Solution in phyton or perl not serve to me, has to be in PHP
> > 
> >  
> > 
> > 
> > 
> > Att,
> > 
> > 'É um orgulho ter você como nosso cliente'
> > 
> >  
> > Hermes Alves
> > Gerente TI
> >  
> > ArgoHost.net
> > Hospedagem Web com Facilidade
> >  http://www.argohost.net/> http://www.argohost.net
> > Suporte Telefônico: (85) 3264 9944 / (11) 4063 4844 R. 102
> > E-mail:  mailto:[EMAIL PROTECTED]>
> > [EMAIL PROTECTED]
> > 
> >  
> > 
> > 
> > 
> > --
> > 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/peter%40cww.org.uk
> > 
> > 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/brian%40emwd.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/rpyne%40kinfolk.org
> 
> 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] Implicit destination

[Steve Burling]

One of our lists has someone post to it whose mail is held, with the error:

Blind carbon copies or other implicit destinations are not allowed. Try
reposting your message by explicitly including the list address in the
To: or Cc: fields.

But as near as I can tell, she *is* putting the list address in the To: 
field, it's just been munged (presumably by Micro$oft LookOut) to have 
quotes in funny places.  Here's what the To: field looks like from the 
listname.mbox file (edited to protect the innocent):

To: "[EMAIL PROTECTED]" <'[EMAIL PROTECTED]'>

Are those unnecessary single quotes inside the "<...>" confusing Mailman? 
Or am I missing something really obvious?

-- 
Steve Burling
University of Michigan, ICPSRVoice: +1 734 615.3779
330 Packard Street   FAX:   +1 734 647.8700
Ann Arbor, MI 48104-2910
--
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] Bounce management and uncaught bounce notifications

[Mark Sapiro]

[EMAIL PROTECTED] wrote:
>
>Q1Why are they called 'uncaught' since they have clearly been sent to a 
>Mailman address, and then neatly packaged up by Mailman and sent to me as list 
>and/or site admin? Are they really just 'unrecognizable' possible bounces (as 
>it says in the body of the Mailman email), or am I missing something?


No, you aren't missing anything. If
bounce_unrecognized_goes_to_list_owner is Yes, any message received at
the listname-bounces address which is not recognized by Mailman as a
DSN is forwarded to the list owner as an unrecognized bounce since at
that point, Mailman doesn't know if it was an actual undeliverable
mail DSN or something else.


>Q2.Have these responses also been sent to the sender of the message to 
>which they are responses?  
>(I don't see how they can have been, as there's nothing in most of the headers 
>relating to the original message)


No, they are only sent to the list owners and only if
bounce_unrecognized_goes_to_list_owner is Yes.


>Q3Are these responses causing the bounce count for the users to be 
>increased?
>(Again, I don't think that this can be the case, because they come back from a 
>different address at the same domain, except possibly for the rare occasion 
>where an out-of-office response comes back from an individual mailbox which is 
>on my list)


No. If Mailman could detect that it was an actual DSN regarding
non-delevery to a list member, then it wouldn't be 'unrecognized'.


>Q4How can I inspect users' bounce counts?


Go to the admin membership list and click the user's name to go to the
user's options page. If the user has a non-zero bounce score, that
will be reported near the top of the options page.

Or, if you have access, look in Mailman's bounce log.


>Q5A small number of mailboxes were automatically set to nomail because of 
>bouncing due to errors on my part (NB these were NOT the ones generating 
>uncaught bounce messages). Mailman's behaviour in this case was reasonable, 
>except (here's the important part) it did NOT send me a message about the 
>suspension. But I have bounce_notify_owner_on_disable set to Yes and 
>bounce_notify_owner_on_unsubscribe_set to Yes. (The same thing used to happen 
>on the antique Mailman installation, but at least there I would get 
>notifications most of the time). Where should I look to find out why these 
>notifications are not reaching me? 


Look in Mailman's bounce log to find the "disabling" entries. Then look
in Mailman's smtp log for entries at that time with message id's of
the form <[EMAIL PROTECTED]>. nn is a sequence
number and t.ttt is a time in seconds since the epoch.

There should be one message with sequence number x and two more with
sequence number x+1. The first is the message to the user. The second
is the message to listname-owner and the third is the resend of the
listname-owner message to the actual owner addresses. If you see
these, Mailman sent the notices. Beyond that, you have to look in your
MTA's logs.


>Q6Again with regard to Q5: 
>I've checked my aliases file and it looks OK. Exactly which role in 
>-@mydomain.net should the notifications be coming to?


They go to list-owner and are then resent to the list's owner (and
moderator) addresses.


>My main concern is actually Q5, because at present it looks like I need to 
>audit all my mailing lists (more frequently than used to be the case) to check 
>whether users are being dropped without me being notified. But I'd like to 
>understand the other stuff too.


The listname-owner address needs to work. You can test it by just
mailing to listname-owner to see if you receive the mail. The fact
that you receive some notices is not definitive. Some owner notices
are relayed through listname-owner and some are sent to the owners
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] PHP Script for search archive

[Mohamed CHAARI]

Brian Carpenter wrote:
> We have come up with a php script that provides a search function for 
> mailman. It uses the sphyder search engine and requires a mysql database. The 
> script comes with an installation feature that will automatically install 
> sphyder and do the initial indexing of the archive. It works with both 
> private and public archives. You will need a member subscription to the list 
> in question if the archives are private. Once the installation is done then 
> all that is needed is to run a cron job that indexes new posts into the mysql 
> database.
> 
> The limitations to this script is that it requires a mysql db and can only be 
> installed on a list by list basis. Also the search page is NOT integrated 
> with archives. It is setup as a separate page outside of the mailing list 
> archives however that has not been an issue with our clients. It can probably 
> be integrated easy enough into your archives if you want.
> 
> If there is enough interest in this then I will make it a free download and 
> perhaps someone can create a FAQ entry to the download. Just let me know.
> 
> Regards,
> Brian

Hello Brian,

I'm very interested in your solution.
Is it possible to use it ?

Thank you


-- 
---
--Mohamed CHAARI   (mailto:[EMAIL PROTECTED])
--
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] PHP Script for search archive

[Ivan Van Laningham]

Hi All--
Me!  Me!  Me!

;-)  I'm interested, very!

As part of my dedicated server from GoDaddy, which uses Plesk for an 
admin interface, a mysql DB is pre-installed.  How difficult is it for a 
DB neophyte to integrate with an existing setup like that?

Metta,
Ivan

Brian Carpenter wrote:
> We have come up with a php script that provides a search function for 
> mailman. It uses the sphyder search engine and requires a mysql database. The 
> script comes with an installation feature that will automatically install 
> sphyder and do the initial indexing of the archive. It works with both 
> private and public archives. You will need a member subscription to the list 
> in question if the archives are private. Once the installation is done then 
> all that is needed is to run a cron job that indexes new posts into the mysql 
> database.
> The limitations to this script is that it requires a mysql db and can only be 
> installed on a list by list basis. Also the search page is NOT integrated 
> with archives. It is setup as a separate page outside of the mailing list 
> archives however that has not been an issue with our clients. It can probably 
> be integrated easy enough into your archives if you want.
> If there is enough interest in this then I will make it a free download and 
> perhaps someone can create a FAQ entry to the download. Just let me know.
> Regards,Brian--EMWD.com -  'Powered by 
> Techies'
> -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> On Behalf Of Peter EdleySent: Wednesday, December 12, 2007 10:15 AMTo: [EMAIL 
> PROTECTED]: Re: [Mailman-Users] PHP Script for search archive
> Not sure if there where any replies to this off list if so could youplease 
> repost to the list since this is somthing I would be interestedin.
> 
> On Tue, 2007-12-11 at 12:24 -0300, Hermes PHP wrote:> Hi,> >  > > Does anyone 
> know of any script in PHP that look inside archives of the list?> >  > > The 
> archives of the list are private.> >  > > > > Solution in phyton or perl not 
> serve to me, has to be in PHP> >  > > > > Att,> > 'É um orgulho ter você como 
> nosso cliente'> >  > Hermes Alves> Gerente TI>  > 
> ArgoHost.net> Hospedagem Web com Facilidade>  
> http://www.argohost.net/> http://www.argohost.net> Suporte 
> Telefônico: (85) 3264 9944 / (11) 4063 4844 R. 102> E-mail:  
> mailto:[EMAIL PROTECTED]>> [EMAIL PROTECTED]> >  > > > > 
> --> 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/peter%40cww.org.uk> > Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
> --Mailman-Users mailing 
> [EMAIL PROTECTED]://mail.python.org/mailman/listinfo/mailman-usersMailman 
> FAQ: http://www.python.org/cgi-bin/faqw-mm.pySearchable Archives: 
> http://www.mail-archive.com/mailman-users%40python.org/Unsubscribe: 
> http://mail.python.org/mailman/options/mailman-users/brian%40emwd.com
> Security Policy: 
> http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
> --Mailman-Users mailing 
> [EMAIL PROTECTED]://mail.python.org/mailman/listinfo/mailman-usersMailman 
> FAQ: http://www.python.org/cgi-bin/faqw-mm.pySearchable Archives: 
> http://www.mail-archive.com/mailman-users%40python.org/Unsubscribe: 
> http://mail.python.org/mailman/options/mailman-users/ivanlan%40pauahtun.org
> Security Policy: 
> http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
> 

-- 
Ivan Van Laningham
God N Locomotive Works
http://www.pauahtun.org/
http://www.python.org/workshops/1998-11/proceedings/papers/laningham/laningham.html
Army Signal Corps:  Cu Chi, Class of '70
Author:  Teach Yourself Python in 24 Hours

--
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] PHP Script for search archive

[Brian Carpenter]

We have come up with a php script that provides a search function for mailman. 
It uses the sphyder search engine and requires a mysql database. The script 
comes with an installation feature that will automatically install sphyder and 
do the initial indexing of the archive. It works with both private and public 
archives. You will need a member subscription to the list in question if the 
archives are private. Once the installation is done then all that is needed is 
to run a cron job that indexes new posts into the mysql database.

The limitations to this script is that it requires a mysql db and can only be 
installed on a list by list basis. Also the search page is NOT integrated with 
archives. It is setup as a separate page outside of the mailing list archives 
however that has not been an issue with our clients. It can probably be 
integrated easy enough into your archives if you want.

If there is enough interest in this then I will make it a free download and 
perhaps someone can create a FAQ entry to the download. Just let me know.

Regards,
Brian
--
EMWD.com -  'Powered by Techies'

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Edley
Sent: Wednesday, December 12, 2007 10:15 AM
To: mailman-users@python.org
Subject: Re: [Mailman-Users] PHP Script for search archive

Not sure if there where any replies to this off list if so could you
please repost to the list since this is somthing I would be interested
in.


On Tue, 2007-12-11 at 12:24 -0300, Hermes PHP wrote:
> Hi,
> 
>  
> 
> Does anyone know of any script in PHP that look inside archives of the list?
> 
>  
> 
> The archives of the list are private.
> 
>  
> 
> 
> 
> Solution in phyton or perl not serve to me, has to be in PHP
> 
>  
> 
> 
> 
> Att,
> 
> 'É um orgulho ter você como nosso cliente'
> 
>  
> Hermes Alves
> Gerente TI
>  
> ArgoHost.net
> Hospedagem Web com Facilidade
>  http://www.argohost.net/> http://www.argohost.net
> Suporte Telefônico: (85) 3264 9944 / (11) 4063 4844 R. 102
> E-mail:  mailto:[EMAIL PROTECTED]>
> [EMAIL PROTECTED]
> 
>  
> 
> 
> 
> --
> 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/peter%40cww.org.uk
> 
> 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/brian%40emwd.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] Extracting e-mail addresses from a dead machine

[Mark Sapiro]

Visvanath Ratnaweera wrote:
>
>I have the data backup from a dead machine. The list is not moved
>to a new server (yet). Therefore I have no running system of Mailman.
>
>Is there a way of extracting the e-mail addresses from this (data)
>backup?


The addresses are in Mailman's lists//config.pck file on the
backup.  All the good ways of getting them require access to a Mailman
installation somewhere. Since you don't have that, you are left with
running 'strings config.pck' and sifting through the output for the
addresses.

If you did have access to a Mailman installation, you could run
Mailman's bin/dumpdb against the config.pck which would produce output
easier to deal with, or you could create a lists// directory
in that installation, put the config.pck in it and run
"bin/list_members -f -p "

-- 
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] PHP Script for search archive

[Peter Edley]

Not sure if there where any replies to this off list if so could you
please repost to the list since this is somthing I would be interested
in.


On Tue, 2007-12-11 at 12:24 -0300, Hermes PHP wrote:
> Hi,
> 
>  
> 
> Does anyone know of any script in PHP that look inside archives of the list?
> 
>  
> 
> The archives of the list are private.
> 
>  
> 
> 
> 
> Solution in phyton or perl not serve to me, has to be in PHP
> 
>  
> 
> 
> 
> Att,
> 
> 'É um orgulho ter você como nosso cliente'
> 
>  
> Hermes Alves
> Gerente TI
>  
> ArgoHost.net
> Hospedagem Web com Facilidade
>  http://www.argohost.net/> http://www.argohost.net
> Suporte Telefônico: (85) 3264 9944 / (11) 4063 4844 R. 102
> E-mail:  mailto:[EMAIL PROTECTED]>
> [EMAIL PROTECTED]
> 
>  
> 
> 
> 
> --
> 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/peter%40cww.org.uk
> 
> 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] Bounce management and uncaught bounce notifications

[[EMAIL PROTECTED]]

Hi

I've just upgraded to Mailman 2.1.9 from a much earlier installation.
One of the new features that puzzles me is the 'uncaught bounce notification'. 
I get these for out-of-office responses and for auto-replies. 

The auto-replies come from some artificial mailbox address.

The out-of-office responses will come either from an address on my list, or, 
where the address on my list is itself the address of a list on the remote 
system, from an individual address on the remote list. A few are addressed to 
[EMAIL PROTECTED] (as they used to be) and the majority to [EMAIL 
PROTECTED]

I have some questions:

Q1Why are they called 'uncaught' since they have clearly been sent to a 
Mailman address, and then neatly packaged up by Mailman and sent to me as list 
and/or site admin? Are they really just 'unrecognizable' possible bounces (as 
it says in the body of the Mailman email), or am I missing something?

Q2.Have these responses also been sent to the sender of the message to 
which they are responses?  
(I don't see how they can have been, as there's nothing in most of the headers 
relating to the original message)

Q3Are these responses causing the bounce count for the users to be 
increased?
(Again, I don't think that this can be the case, because they come back from a 
different address at the same domain, except possibly for the rare occasion 
where an out-of-office response comes back from an individual mailbox which is 
on my list)

Q4How can I inspect users' bounce counts?

Q5A small number of mailboxes were automatically set to nomail because of 
bouncing due to errors on my part (NB these were NOT the ones generating 
uncaught bounce messages). Mailman's behaviour in this case was reasonable, 
except (here's the important part) it did NOT send me a message about the 
suspension. But I have bounce_notify_owner_on_disable set to Yes and 
bounce_notify_owner_on_unsubscribe_set to Yes. (The same thing used to happen 
on the antique Mailman installation, but at least there I would get 
notifications most of the time). Where should I look to find out why these 
notifications are not reaching me? 

Q6Again with regard to Q5: 
I've checked my aliases file and it looks OK. Exactly which role in 
-@mydomain.net should the notifications be coming to?

My main concern is actually Q5, because at present it looks like I need to 
audit all my mailing lists (more frequently than used to be the case) to check 
whether users are being dropped without me being notified. But I'd like to 
understand the other stuff too.

Rod


--
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] Extracting e-mail addresses from a dead machine

[Visvanath Ratnaweera]

Hi all

This could also be a FAQ, sorry but I couldn't find the answer.

I have the data backup from a dead machine. The list is not moved
to a new server (yet). Therefore I have no running system of Mailman.

Is there a way of extracting the e-mail addresses from this (data)
backup?

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