Re: [Mailman-Users] mailman 2.1.14 stops sending mail

[Mark Sapiro]

On 4/11/2013 9:07 AM, Millsap, James wrote:
> Unfortunately It is difficult as this machine is critical to our
operations, I don't have a whole lot of time to troubleshoot, before I
must have it up and running. It usually takes around two days for this
issue to come up. -TERM will kill it, no need to use --KILL. This is
built from source so no redhat packages. This is what I have in the
qrunner log.
> 
[...]
> Apr 10 10:01:08 2013 (17611) OutgoingRunner qrunner caught SIGTERM.  Stopping.
[...]
> Apr 10 10:01:08 2013 (17604) Master watcher caught SIGTERM.  Exiting.
[...]
> Apr 10 10:01:37 2013 (17604) Master watcher caught SIGTERM.  Exiting.
> Apr 10 10:01:37 2013 (17611) OutgoingRunner qrunner caught SIGTERM.  Stopping.
> Apr 10 10:01:37 2013 (17611) OutgoingRunner qrunner exiting.
> Apr 10 10:01:38 2013 (17604) Master qrunner detected subprocess exit
> (pid: 17611, sig: None, sts: 15, class: OutgoingRunner, slice: 1/1)
[...]


Interesting that OutgoingRunner wouldn't exit until SIGTERMed a second
time. It seems highly likely that it is waiting on something 'not
interruptable' and this is why it stops processing in the first place
and is reluctant to die.

The real question is what's it waiting on and why? Without the answer or
some more clue to this, I don't know what.

Check the MTA logs from the time OutgoingRunner 'hung' and the time it
was SIGTERMed. Also consider enabling smtplib debug logging (see
).

-- 
Mark Sapiro 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://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] receive your own posts problem

[Stephen J. Turnbull]

William Bagwell writes:

 > So if a list adds a footer to the body of a message (many do) then that 
 > implies that the Message-ID /should/ be changed.

No.  As the section you quoted later shows, that is a "syntactic
difference" and clearly *not* a reason for changing the Message-ID.

 > Obviously Mailman does not want to break threading for no good
 > reason. However fighting Gmail's annoying feature with a less
 > annoying kludge is a good enough reason in my book.

I didn't say that individual site managers couldn't do this.  I think
it's a bad idea for Mailman to provide the feature.  I'll probably
lose, just like we've lost on Reply-To munging.  Note that it's a
10-line or so Handler, which you place near the CookHeaders Handler.

I realize that having Mailman provide the option is the most
convenient way to handle the issue, and if individual senders consider
that the message in their Sent folder, the copy that they receive via
self-cc, and the copy they receive via the list are different, then
they are arguably within the RFC to have the Message-IDs changed.  I
think that's a misinterpretation of the RFC, but I doubt even the RFC
authors have thought carefully about Gmail's perverse behavior in this
context.

Note that there are already ways for senders to handle the issue.  For
example, have Mailman ACK your posts, which tells you Mailman has
received and distributed the post.  Accept that sometimes you're
boring and nobody replies -- if they do, Gmail does display your sent
posts as part of the "conversation", which should be fine.

Of course, this is a little painful for the sender.  But that's as it
should be, since "We know you DO have a choice of airlines, and we
thank you for traveling with United today."  If you don't like the
inflight meal, pay for business class.  Get another MUA.

 > If the sender ticks the box telling Mailman to change the
 > Message-ID then they get to take the heat.

No, the sender gets exactly what she wants, and is very unlikely to
take any heat.  Mailman will get to take the heat when their non-list
correspondents complain, usually directly to list owners rather than
to senders, and occasionally to Mailman-Users.  You understand the
consequences of that choice, but in my experience most users won't,
and will impose problems on third parties without hesitation.

This feature, like Reply-To munging, is an invitation to smoking in
the elevators.

 > Other settings have brief descriptions / warnings so a sentence
 > warning about breaking threading

It doesn't break threading, except for the sender (that's exactly what
they want), and Cc/Bcc-only recipients (who don't deserve this).  In
fact, according to your argument claiming the feature conforms to RFC,
it doesn't break threading at all, since only the message distributed
via the list is part of the list thread.  The other message generated
by the proposed feature is in a separate subthread.

 > and the other issues you raise would not be out of place.

"If you enable this feature without complaining vigorously and
periodically to Gmail, then you are a selfish antisocial wretch" 
would do in my book. ;-)

An alternative to telling them they're being selfish would be to
automatically enable ACK on people who enable Message-ID munging to
remind them of the trouble they may be imposing on others, and give
them an incentive to stop it.

Yet another alternative would be to reject list posts that contain
CCs.  Then *all* problems are restricted to the sender and Bcc
recipients (but they're unusual as far as I know), because nobody else
ever sees the original Message-ID.
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] accessing relay mailman server from itsown network

[Mark Sapiro]

Anne Wainwright wrote:
>
>Actually there were 5 'absolute=1' entries in admindb.py and changing
>them all has resolved the issue of pending moderator request, but the
>list archives remains absolute.


Current Mailman has only 4. The change between 2.1.14 and 2.1.15 to add
the logout button inserted this one

# Now print the results and we're done.  Short circuit for when
there
# are no pending requests, but be sure to save the results!
admindburl = mlist.GetScriptURL('admindb', absolute=1)
if not mlist.NumRequestsPending():

and removed these two

doc.AddItem(_('There are no pending requests.'))
doc.AddItem(' ')
doc.AddItem(Link(mlist.GetScriptURL('admindb', absolute=1),
 _('Click here to reload this page.')))
doc.AddItem(mlist.GetMailmanFooter())
print doc.Format()
mlist.Save()
return

admindburl = mlist.GetScriptURL('admindb', absolute=1)
form = Form(admindburl)
# Add the instructions template

In any case, you want to remove ', absolute=1' from the two or its one
replacement.

That leaves these three:

in main()

# Add a link back to the overview, if we're not viewing the
overview!
adminurl = mlist.GetScriptURL('admin', absolute=1)

in handle_no_list()

url = Utils.ScriptURL('admin', absolute=1)
link = Link(url, _('list of available mailing lists.')).Format()
doc.AddItem(_('You must specify a list name.  Here is the
%(link)s'))

and in show_helds_overview)_

# Add the by-sender overview tables
admindburl = mlist.GetScriptURL('admindb', absolute=1)

The last of these should definitely be changed. The other two are
actually links back to the admin (not admindb) overview page. The one
in main() is a link to the admin overview for the host of the list
that we're currently processing in the admindb page, but the one in
handle_no_list() is different because there is no list. Depending of
site configuration, the host in this URL if absolute may be the web
host of the current page, or it may be DEFAULT_URL_HOST. This could
cause problems with a relative URL if the absolute one should go to
DEFAULT_URL_HOST.

So I would say in your case, you can probably safely remove them all,
but in terms of what I might do for a bug and fix, I may not do the
one in handle_no_list().

As far as the archive URL is concerned, this is generated differently
as it has to take into account whether the archives are public or
private and the setting for PUBLIC_ARCHIVE_URL and it's always
absolute.

-- 
Mark Sapiro 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://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Running an External Command on Subscribe

[Mark Sapiro]

Dennis Putnam wrote:
>
>Is there some place (log) I can monitor to detect a new subscriber for a
>particular list?


Mailman's 'subscribe' log.

-- 
Mark Sapiro 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://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] receive your own posts problem

[William Bagwell]

On Thursday 11 April 2013, Stephen J. Turnbull wrote:
> No, by definition it's a nasty feature, as it involves nonconformance
> to RFC 5322.

How so? I see two places in section 3.6.4. that suggest otherwise.
" A message
   identifier pertains to exactly one version of a particular message;
   subsequent revisions to the message each receive new message
   identifiers."

So if a list adds a footer to the body of a message (many do) then that 
implies that the Message-ID /should/ be changed. Obviously Mailman does not 
want to break threading for no good reason. However fighting Gmail's 
annoying feature with a less annoying kludge is a good enough reason in my 
book.

Just below, same section 3.6.4., top of page 25, "In all
  cases, it is the meaning that the sender of the message wishes to
  convey (i.e., whether this is the same message or a different
  message) that determines whether or not the "Message-ID:" field
  changes, not any particular syntactic difference that appears (or
  does not appear) in the message."

If the sender ticks the box telling Mailman to change the Message-ID then 
they get to take the heat. Other settings have brief descriptions / warnings 
so a sentence warning about breaking threading and the other issues you 
raise would not be out of place.
-- 
William
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Running an External Command on Subscribe

[Dennis Putnam]

Is there some place (log) I can monitor to detect a new subscriber for a
particular list?

On 4/11/2013 2:04 PM, Mark Sapiro wrote:
> Dennis Putnam wrote:
>> Is there a way to have an external command executed when a subscribe
>> request is received (both web and email)?
>
> Not without code modification.
>




signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Running an External Command on Subscribe

[Mark Sapiro]

Dennis Putnam wrote:
>
>Is there a way to have an external command executed when a subscribe
>request is received (both web and email)?


Not without code modification.

-- 
Mark Sapiro 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://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Making a Mailman legacy archive searchable?

[Barry Warsaw]

On Apr 12, 2013, at 01:06 AM, Stephen J. Turnbull wrote:

>FreeWAIS (oldie but still goodie), Namazu, and Xapian come to mind.
>They all require some effort on the part of the user, though.  I don't
>know of anything that you can trivially install (eg, from RPM or
>.deb).

Whoosh is technology I'm looking at for Mailman 3.

https://pypi.python.org/pypi/Whoosh/2.4.1

-Barry
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] receive your own posts problem

[Stephen J. Turnbull]

William Bagwell writes:

 > As long as it defaults off and is user selectable I think this would be a 
 > nice feature.

No, by definition it's a nasty feature, as it involves nonconformance
to RFC 5322.

 > Suggested similar in the past... It will break threading for those
 > of us who want full Usenet style indented threading. Doubt that
 > those who read mail in a web browser or read and delete will
 > notice.

They will if they're CC'd and try to search archives by Message-ID, or
if they have a deduplicator running locally.
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] receive your own posts problem

[William Bagwell]

On Thursday 11 April 2013, Joseph Brennan wrote:
> The solution, or workaround I would say, is to change the Message-ID.
> Possibly, a milter could do this on the way in on the Mailman host. Maybe
> add a fixed string to what's already there.
>
> However this might have some impact on non Gmail users that does not come
> to mind immediately, so I am NOT saying to do this.

As long as it defaults off and is user selectable I think this would be a 
nice feature. Suggested similar in the past... It will break threading for 
those of us who want full Usenet style indented threading. Doubt that those 
who read mail in a web browser or read and delete will notice.
-- 
William
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Making a Mailman legacy archive searchable?

[Mark Sapiro]

David Roth wrote:
>>
>> Working out-of-the-box is always nice, but I wasn't expecting it entirely.
>Anyone happen to have a URL to someone doing searchable Mailman archives,
>just so I could see what others have done as an example? Thanks!


See the FAQ at .

I use ht://dig. See the link at the bottom of the FAQ.

It's not a very good example, most of my lists have private arrchives,
but see  for an example of
what it looks like.

-- 
Mark Sapiro 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://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] mailman 2.1.14 stops sending mail

[Millsap, James]

Unfortunately It is difficult as this machine is critical to our operations, I 
don't have a whole lot of time to troubleshoot, before I must have it up and 
running. It usually takes around two days for this issue to come up.  -TERM 
will kill it, no need to use --KILL. This is built from source so no redhat 
packages.   This is what I have in the qrunner log. 

Apr 10 10:01:08 2013 (17606) ArchRunner qrunner caught SIGTERM.  Stopping.
Apr 10 10:01:08 2013 (17606) ArchRunner qrunner exiting.
Apr 10 10:01:08 2013 (17611) OutgoingRunner qrunner caught SIGTERM.  Stopping.
Apr 10 10:01:08 2013 (17612) VirginRunner qrunner caught SIGTERM.  Stopping.
Apr 10 10:01:08 2013 (17612) VirginRunner qrunner exiting.
Apr 10 10:01:08 2013 (17607) BounceRunner qrunner caught SIGTERM.  Stopping.
Apr 10 10:01:08 2013 (17608) CommandRunner qrunner caught SIGTERM.  Stopping.
Apr 10 10:01:08 2013 (17608) CommandRunner qrunner exiting.
Apr 10 10:01:08 2013 (17609) IncomingRunner qrunner caught SIGTERM.  Stopping.
Apr 10 10:01:08 2013 (17609) IncomingRunner qrunner exiting.
Apr 10 10:01:08 2013 (17610) NewsRunner qrunner caught SIGTERM.  Stopping.
Apr 10 10:01:08 2013 (17610) NewsRunner qrunner exiting.
Apr 10 10:01:08 2013 (17613) RetryRunner qrunner caught SIGTERM.  Stopping.
Apr 10 10:01:08 2013 (17613) RetryRunner qrunner exiting.
Apr 10 10:01:08 2013 (17604) Master watcher caught SIGTERM.  Exiting.
Apr 10 10:01:08 2013 (17604) Master qrunner detected subprocess exit
(pid: 17606, sig: None, sts: 15, class: ArchRunner, slice: 1/1)
Apr 10 10:01:08 2013 (17604) Master qrunner detected subprocess exit
(pid: 17608, sig: None, sts: 15, class: CommandRunner, slice: 1/1)
Apr 10 10:01:08 2013 (17604) Master qrunner detected subprocess exit
(pid: 17609, sig: None, sts: 15, class: IncomingRunner, slice: 1/1)
Apr 10 10:01:08 2013 (17604) Master qrunner detected subprocess exit
(pid: 17610, sig: None, sts: 15, class: NewsRunner, slice: 1/1)
Apr 10 10:01:08 2013 (17604) Master qrunner detected subprocess exit
(pid: 17612, sig: None, sts: 15, class: VirginRunner, slice: 1/1)
Apr 10 10:01:08 2013 (17604) Master qrunner detected subprocess exit
(pid: 17613, sig: None, sts: 15, class: RetryRunner, slice: 1/1)
Apr 10 10:01:08 2013 (17607) BounceRunner qrunner exiting.
Apr 10 10:01:08 2013 (17604) Master qrunner detected subprocess exit
(pid: 17607, sig: None, sts: 15, class: BounceRunner, slice: 1/1)
Apr 10 10:01:37 2013 (17611) OutgoingRunner qrunner caught SIGTERM.  Stopping.
Apr 10 10:01:37 2013 (17604) Master watcher caught SIGTERM.  Exiting.
Apr 10 10:01:37 2013 (17611) OutgoingRunner qrunner caught SIGTERM.  Stopping.
Apr 10 10:01:37 2013 (17611) OutgoingRunner qrunner exiting.
Apr 10 10:01:38 2013 (17604) Master qrunner detected subprocess exit
(pid: 17611, sig: None, sts: 15, class: OutgoingRunner, slice: 1/1)
Apr 10 10:01:58 2013 (15858) CommandRunner qrunner started.
Apr 10 10:01:59 2013 (15859) IncomingRunner qrunner started.
Apr 10 10:01:59 2013 (15856) ArchRunner qrunner started.
Apr 10 10:01:59 2013 (15857) BounceRunner qrunner started.
Apr 10 10:01:59 2013 (15862) VirginRunner qrunner started.
Apr 10 10:01:59 2013 (15860) NewsRunner qrunner started.
Apr 10 10:01:59 2013 (15863) RetryRunner qrunner started.
Apr 10 10:01:59 2013 (15861) OutgoingRunner qrunner started.

-Original Message-
From: Mark Sapiro [mailto:m...@msapiro.net] 
Sent: Wednesday, April 10, 2013 3:59 PM
To: Millsap, James
Cc: mailman-users@python.org
Subject: Re: [Mailman-Users] mailman 2.1.14 stops sending mail

On 4/10/2013 8:43 AM, Millsap, James wrote:
> 
> mailman  15854 1  0 10:01 ?00:00:00 /usr/bin/python 
> /usr/local/mailman/bin/mailmanctl -s start
> mailman  15861 15854  0 10:01 ?00:00:06 /usr/bin/python 
> /usr/local/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
> 
> I have to kill the outgoingrunner specifically.  The only thing I see in the 
> logs is a lack of logging.  It has been running with stunning reliability on 
> this machine for the last few years, so I am not sure what is going on.  
> Perhaps one of redhat's patches killed it.


Can you kill -TERM it or do you need to kill -KILL it?

Are you sure there's nothing relevant in Mailman's qrunner log 
(/var/log/mailman/qrunner if a rhel packaged Mailman)? Is there a current .bak 
file in the out queue (/var/spool/mailman/out/)

What does 'lsof' show for the process? You might be able to get something 
useful from 'gdb' or maybe see something like 
.

If I had to guess, I'd guess it gets hung waiting for an SMTP response from the 
MTA.

-- 
Mark Sapiro 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://wiki.list.org/x/AgA3
Securi

Re: [Mailman-Users] Making a Mailman legacy archive searchable?

[jdd]

Le 11/04/2013 18:14, David Roth a écrit :


Anyone happen to have a URL to someone doing searchable Mailman archives,
just so I could see what others have done as an example? Thanks!


if the archive is public, a simple google site:XXX link should do the 
trick


jdd


--
http://www.dodin.org
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Making a Mailman legacy archive searchable?

[David Roth]

On Thu, Apr 11, 2013 at 12:06 PM, Stephen J. Turnbull wrote:

> David Roth writes:
>
>  > Is there anything open-source to make a Mailman legacy archive
> searchable?
>
> FreeWAIS (oldie but still goodie), Namazu, and Xapian come to mind.
> They all require some effort on the part of the user, though.  I don't
> know of anything that you can trivially install (eg, from RPM or
> .deb).
>
>
> Working out-of-the-box is always nice, but I wasn't expecting it entirely.
Anyone happen to have a URL to someone doing searchable Mailman archives,
just so I could see what others have done as an example? Thanks!

David Roth
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Making a Mailman legacy archive searchable?

[Stephen J. Turnbull]

David Roth writes:

 > Is there anything open-source to make a Mailman legacy archive searchable?

FreeWAIS (oldie but still goodie), Namazu, and Xapian come to mind.
They all require some effort on the part of the user, though.  I don't
know of anything that you can trivially install (eg, from RPM or
.deb).


--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] receive your own posts problem

[Joseph Brennan]

I think he is saying that his mailing list subscribers subscribed to
gmail do not receive a copy of they own mail.

fir this we do not have any solution :-)



The solution, or workaround I would say, is to change the Message-ID. 
Possibly, a milter could do this on the way in on the Mailman host. Maybe 
add a fixed string to what's already there.


However this might have some impact on non Gmail users that does not come 
to mind immediately, so I am NOT saying to do this.


Joseph Brennan
Columbia University Information Technology


--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Making a Mailman legacy archive searchable?

[David Roth]

Is there anything open-source to make a Mailman legacy archive searchable?
What would be useful is a way for visitors to a website to be able to
search the Mailman archives using a keyword and have it display those mail
messages. I'm also thinking of having a tag cloud made up of the most
commonly used words from the given Mailman archive. So when one of those
tag cloud words is clicked on it lists as an index those messages. Any
suggestions? Thanks!

David Roth
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] receive your own posts problem

[jdd]

Le 11/04/2013 17:14, Mark Sapiro a écrit :

Neil Anuskiewicz wrote:


I do have a second gmail just for checking my own posts! The thing is this
is an informal list that I setup as a favor for a small organization. A
number of the list members have gmail so I'm not concerned about this for
me but for the subscribers. I'm the list admin so I want to make the
experience as pleasant as possible for my subscribers. Unfortunately, it's
probably not realistic for people to drop their gmail accounts.



Are you saying you don't receive the post at your second gmail account
either? If so, that is a different issue than the one in the FAQ we've
been referring to. See the FAQ at .

I think he is saying that his mailing list subscribers subscribed to 
gmail do not receive a copy of they own mail.


fir this we do not have any solution :-)

jdd

--
http://www.dodin.org
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] receive your own posts problem

[Mark Sapiro]

Neil Anuskiewicz wrote:

>I do have a second gmail just for checking my own posts! The thing is this
>is an informal list that I setup as a favor for a small organization. A
>number of the list members have gmail so I'm not concerned about this for
>me but for the subscribers. I'm the list admin so I want to make the
>experience as pleasant as possible for my subscribers. Unfortunately, it's
>probably not realistic for people to drop their gmail accounts.


Are you saying you don't receive the post at your second gmail account
either? If so, that is a different issue than the one in the FAQ we've
been referring to. See the FAQ at .

-- 
Mark Sapiro 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://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] accessing relay mailman server from its own network

[Anne Wainwright]

Mark, hello,

Actually there were 5 'absolute=1' entries in admindb.py and changing
them all has resolved the issue of pending moderator request, but the
list archives remains absolute.

Awaiting your official confirmation on which entries to change.

Anne

On Thu, Apr 11, 2013 at 02:25:10PM +0200, Anne Wainwright wrote:
> Hello, Mark,
> 
> This action solved the stated problem but now I note that the same
> situation pertains in "Tend to pending moderator requests" where
> held messages cannot be read or actioned.
> 
> Also "Go to list archives". (we do not have this running). The other two
> links are fine.
> 
> I see three more 'absolute=1' entries in admindb.py - shall I change all
> three?
> 
> regards
> Anne
> 
> 
> On Wed, Apr 10, 2013 at 03:00:50PM -0700, Mark Sapiro wrote:
> > Mark Sapiro wrote:
> > >
> > >What we need to do is figure out why those few URLs on the Membership
> > >List page are absolute. It may be a bug. I'll look at that.
> > 
> > 
> > There are two places in Mailman/Cgi/admin.py where it requests absolute
> > URLs. The relevant code bits are
> > 
> > def membership_options(mlist, subcat, cgidata, doc, form):
> > # Show the main stuff
> > adminurl = mlist.GetScriptURL('admin', absolute=1)
> > ...
> > 
> > and
> > 
> > def password_inputs(mlist):
> > adminurl = mlist.GetScriptURL('admin', absolute=1)
> > 
> > The first of these affects the 'letter/digit' links on the membership
> > ant the action for the Search, Submit Your Changes and Set buttons,
> > and the second affects (I think) only the link to the general options
> > section on the Passwords page.
> > 
> > I see no reason why these need to be absolute URLs. You could just
> > change the two mlist.GetScriptURL lines to
> > 
> > adminurl = mlist.GetScriptURL('admin')
> > 
> > and I think that would fix it. If you wouldn't mind trying this and
> > reporting, I'd appreciate it and if it seems OK, I'll file a bug and
> > change it for 2.1.16.
> > 
> > There may be some http/https issue around this, but offhand, I can't
> > think why.
> > 
> > -- 
> > Mark Sapiro 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://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> http://mail.python.org/mailman/options/mailman-users/anotheranne%40fables.co.za
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] accessing relay mailman server from its ownnetwork

[Anne Wainwright]

Hello, Mark,

This action solved the stated problem but now I note that the same
situation pertains in "Tend to pending moderator requests" where
held messages cannot be read or actioned.

Also "Go to list archives". (we do not have this running). The other two
links are fine.

I see three more 'absolute=1' entries in admindb.py - shall I change all
three?

regards
Anne


On Wed, Apr 10, 2013 at 03:00:50PM -0700, Mark Sapiro wrote:
> Mark Sapiro wrote:
> >
> >What we need to do is figure out why those few URLs on the Membership
> >List page are absolute. It may be a bug. I'll look at that.
> 
> 
> There are two places in Mailman/Cgi/admin.py where it requests absolute
> URLs. The relevant code bits are
> 
> def membership_options(mlist, subcat, cgidata, doc, form):
> # Show the main stuff
> adminurl = mlist.GetScriptURL('admin', absolute=1)
> ...
> 
> and
> 
> def password_inputs(mlist):
> adminurl = mlist.GetScriptURL('admin', absolute=1)
> 
> The first of these affects the 'letter/digit' links on the membership
> ant the action for the Search, Submit Your Changes and Set buttons,
> and the second affects (I think) only the link to the general options
> section on the Passwords page.
> 
> I see no reason why these need to be absolute URLs. You could just
> change the two mlist.GetScriptURL lines to
> 
> adminurl = mlist.GetScriptURL('admin')
> 
> and I think that would fix it. If you wouldn't mind trying this and
> reporting, I'd appreciate it and if it seems OK, I'll file a bug and
> change it for 2.1.16.
> 
> There may be some http/https issue around this, but offhand, I can't
> think why.
> 
> -- 
> Mark Sapiro 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://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Running an External Command on Subscribe

[Dennis Putnam]

Is there a way to have an external command executed when a subscribe
request is received (both web and email)? If so, how and how do I pass
the requestor's address to it? Thanks.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] receive your own posts problem

[Stephen J. Turnbull]

Neil Anuskiewicz writes:

 > You guys are saying that I could contact Google and actually have some
 > influence? Have a lot of other people brought up the issue with
 > them?

No, that was ironic.  A lot of people (including several on this list)
have contacted them and asked them to make it possible to receive your
own sent mail, but they are unwilling to change this for some reason.
As far as I know their stubborn refusal has never received adequate
explanation.
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org