Re: [Mailman-Users] Roadrunner/TWC blocking Emails

[Richard Shetron]

I'll agree and they don't always pay attention to their users.  I have 
road runner internet but separate email.


On 7/7/2019 1:59 AM, Stephen J. Turnbull wrote:

Hi Jayson,

Roadrunner has been problematic in this way for decades.  They don't
explain, they don't provide policy information or contact addresses,
and their staff have frequently been snotty about DoS'ing their own
customers.

You may have already seen this thread on the Spectrum forums.  I think
that help requests from RR users will be most likely to get them to
take action.  This suggests that there are channels available to
customers (apparently not very well publicized to RR users either!)

https://forums.timewarnercable.com/t5/Email/Listserve-messages-sent-to-my-RoadRunner-account-are-blocked/td-p/155952

  >     - Transcript of session follows -
  > ... while talking to dnvrco-cmedge01.email.rr.com.:
  > <<< 554 dnvrco-cmimta17 esmtp ESMTP server not available AUP#I-1000

  > Various attempts at Googling this error have lead me to believe that my
  > IP may have been blacklisted by RR/TWC for some reason.

Seems logical.  554 is an administrative denial, not a server issue,
and AUP is likely to abbreviate "Acceptable Use Policy".  As you say,
if you don't get to HELO it's an IP-based or reverse-DNS-based policy
of some kind.

  > Does anyone here know of an up-to-date link where I can find out if my
  > IP is blacklisted by them, submit a removal request, etc?

The only thing I can suggest is mail to postmaster.  (I seem to recall
that that address may have been non-functional at times, and it's
mentioned in the thread)

Steve

--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/guest2%40sgeinc.com


--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Funding Campaign for GNU Mailman

[Richard Shetron]

I'm on the MM3 mailing list.  Based on what I've been seeing without 
spending a lot of time researching things, MM# does not seem stable.  It 
seems somewhere in the alpha/beta range, but closer to alpha status. 
The problem does not seem to be with the MM3 code so much as it depends 
on a lot of other packages and they seem to be in somewhat of a state of 
flux causing MM3 to be temperamental and not always work right due to 
the changes in these packages.


It feels too much like the bleeding edge of technology to me at this time.

On 11/9/2017 6:51 PM, Abhilash Raj wrote:
[snip]
--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Removing archived spam

[Richard Shetron]

https://xkcd.com/927/

On 11/11/2017 2:04 PM, Dimitri Maziuk wrote:

On 2017-11-11 12:22, Phil Stracchino wrote:


Heh, I just looked at that myself.  How did such a useless tool ever
become standard?

[snip]
--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Recent phishing mails are targeting mailing-lists -- and do pass

[Richard Shetron]

Spamassassin produces a numeric rating for for an email based on 
multiple rules.  Legitimate email can easily get a rating of 3 or 4 
based on the way you have it configured.  I've seen double digit ratings 
as well.  If you check for a single digit, you may be filtering 
legitimate emails that have a low score.


On 9/26/2017 7:58 AM, Robert Heller wrote:
[snip]


I also use Spamassassin on my server, so having a rule like:

"X-Spam-Score: \d"

is also helpful at catching spam and phishing mail.


[snip]
--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Distributed mass subscribe attack?

[Richard Shetron]

On 8/18/2017 1:52 PM, Grant Taylor via Mailman-Users wrote:

On 08/18/2017 11:07 AM, Phil Stracchino wrote:

I second this.  It is a legitimate part of compliant email addresses, no
matter how many web stores seem to believe otherwise (or are merely
unaware of it).


I third this.

I love user+detail but HATE that poorly designed web forms balk at +, 
and have been forced to do something else for user+detail like 
functionality.


I also agree with allowing the +.  I run my own mail server and now that 
postfix allows defining more then one tag character, I've added _ so I 
can tag with both + and _.  The sites rejecting RFC compliant addresses 
are very annoying.

--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Send confirmation emails to user that sign up for my site

[Richard Shetron]

If the web backend can generate the code and email for the message and 
you are on a *nix system then all you have to do is:


cat  | sendmail -r  -s "" 

message can usually contain additional headers depending on the command 
line options.  message can be a canned message if you put the code in 
the subject.  You may need to make this a shell script or use some type 
of shell wrapper.


see man sendmail (even if you are not using sendmail, there is often a 
stub with other mailers to allow sending email with the sendmail command 
line interface for compatibility.


On 7/4/17 5:50 PM, kayla.manche...@devplateau.com wrote:
I have a site where users are able to sign up. When they sign up to the 
site, their information is stored in a database on the server.


What I want to do is send users that sign up an email for them to 
confirm the account they just made. The email would include a code and a 
link for the account verification page.


Is there anyway that I can link the database from my server to mailman 
so that mailman can send these emails out?

--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/guest2%40sgeinc.com



--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] list sponsorships

[Richard Shetron]

What I've always done is offered special pricing, usually at least 50% 
off for charitable 503(c) and other 'public service' type groups.  It 
more depended on the resources they required and the amount of hand holding.


On 5/15/17 3:13 PM, Chip Davis wrote:
All of the Mailman lists I host/admin are provided free of charge, as a 
value-add to the members of various non-profit groups.  Insofar as the 
actual costs of providing a discussion or announcement list are hard to 
tease out, the best I could do would be to apportion the total costs of 
the servers they are on across all the other services I get. The income 
would be nice to offset my expenses but administering it would be nearly 
as great as that of adminning the lists themselves. So I treat it as my 
contribution to good causes.


Also, I have a philosophical/ethical problem with charging for simply 
providing a FOSS service.  I know it's allowed but still...

[snip]
--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Web interface stopped working after ubuntu update

[Richard Shetron]

I had this problem during a ubuntu update.  IIRC:  I discovered that the 
update changed the user/group id's of mailman from mailman:www-data to 
list:list (or something like that) as it did a mailman update that 
messed up the id's.  It has been too long to remember the exact details. 
 The default ubuntu mailman install uses different permissions from a 
regular mailman install from the mailman tarball.  I may have removed 
and then reinstalled mailman from the tarball/source.  The ubuntu 
mailman package was pretty old, IIRC.


I remember systemd and apparmor breaking a running system and spending 
weeks fixing everything that was broken.  It broke enough stuff and 
caused enough problems that ubuntu has convinced me to find another *nix 
distribution or even switch to bsd to get away from the disaster that is 
systemd.


On 3/29/2017 3:31 PM, Nick Wyman wrote:

Mark,

Thank you for looking.


The error is "Operation not permitted". My best guess is this is
occurring at this point in the wrapper

#ifdef HAVE_SETREGID
 status = setregid(getegid(), -1);
 if (status)
 fatal(logident, SETREGID_FAILURE, "%s", strerror(errno));
#endif /* HAVE_SETREGID */


Indeed this is the case.  I recompiled the wrapper with this code block 
disabled and the web interface functioned again.

Note that the mailman user and group are "list" while apache runs as user and group 
"www-data".



Do other CGIs (e.g. admin, admindb, private, options) fail the same way.


Yes, all the cgi-bin executables return the same error message.



There should at least be something logged in /var/log/apache2/error.log
or wherever the error log is for the vhost. There is a 'syslog' call in
the wrapper, but it only writes the "Operation not permitted" message
that was displayed in the browser.

If you can find the exit status of the wrapper in the apache log, those
codes are defined as

/* Exit codes, so it's easier to distinguish what caused fatal errors when
  * looking at syslogs.
  */
#define GROUP_MISMATCH 2
#define SETREGID_FAILURE 3
#define EXECVE_FAILURE 4
#define MAIL_USAGE_ERROR 5
#define MAIL_ILLEGAL_COMMAND 6
#define ADDALIAS_USAGE_ERROR 7
#define GROUP_NAME_NOT_FOUND 8


I could not find this information in any log file.  However, via print 
instrumentation, I have reduced the problem to the setregid call.

I'm unable to explain why this command is suddenly failing.


--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/guest2%40sgeinc.com


--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman Hosting

[Richard Shetron]

Postfix is the same.  I had to install a greylisting package to add 
greylisting to postfix.


On 12/23/2016 9:50 AM, Odhiambo Washington wrote:


On 23 December 2016 at 17:36, Richard Shetron <gue...@sgeinc.com
<mailto:gue...@sgeinc.com>> wrote:

Maybe they were using some type of grey listing.

For those who don't know:
Grey listing is where the target MTA rejects with a retry error code
the email from a new source for some period of time.  Every site can
set their own delay.  Most spammers won't retry so it gets rid of a
lot of spam.  Real email servers will accept the retry error (4xx)
and retry after some prefigured time from a few seconds to an hour
or more.  The IP addresses are tracked and if retried after the time
limit are white listed for anywhere from a few hours to a month or more.


I know Exim will only treat a session as a failure if it gets 5xx. Does
Postfix do the same?


--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft."

--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman Hosting

[Richard Shetron]

Maybe they were using some type of grey listing.

For those who don't know:
Grey listing is where the target MTA rejects with a retry error code the 
email from a new source for some period of time.  Every site can set 
their own delay.  Most spammers won't retry so it gets rid of a lot of 
spam.  Real email servers will accept the retry error (4xx) and retry 
after some prefigured time from a few seconds to an hour or more.  The 
IP addresses are tracked and if retried after the time limit are white 
listed for anywhere from a few hours to a month or more.


On 12/23/2016 1:40 AM, Mark Dale wrote:

Thanks for the suggestion on the mailop list Jim.

Verizon began accepting mail again for lists on the European server
about 6 hours ago.

No light was shed as to why or what changed their view. Not only Verizon
but AT as well, at around the same time - a little puzzle that's
probably best left alone.

It may be that their default position is to block all list mail
regardless - until they get swamped with complaints.

I've subscribed to the mailop list as you suggest, and if I learn
anything relevant to this issue I'll post it back here.

Thanks,
Mark




 MailmanLists - hosted discussion lists
 Canberra, Australia
 Tel: +61 .2 61003121
 http://www.mailmanlists.net
===

On 22/12/16 16:15, Jim Popovitch wrote:

On Wed, Dec 21, 2016 at 11:42 PM, Mark Dale 
wrote:

...

All the DNS records (inc SPF, DKIM) are in place, the server is on no
RBLs,
con-current connections to the recieving mail servers is set at 2 in
Postfix. In short, all the right boxes are ticked as far as we can see.

Point noted about the time needed to build a good IP reputation. In
light of
that, we moved the list to our old established server in Europe. It
has a
SenderScore of 99, and of course all the same boxes are ticked. Verizon
still rejected list mail.

...




A good place to start is on the mailop list, explain your company and
sign-up practices/filtering, etc.  Be open and ask for specific reps
to contact you offline if necessary.  You may get some awesome help,
although this close to the holidays your message may not hit the right
people until next year.

https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


--
Mailman-Users mailing list Mailman-Users@python.org
https://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:
https://mail.python.org/mailman/options/mailman-users/guest2%40sgeinc.com


--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] distutils is not available or incomplete when ./configure mailman 2.1.23?

[Richard Shetron]

You can always search the cache with:
apt-cache search python
or
apt-cache search python-dev
to get less noise.

On 12/14/2016 2:58 PM, Caesar Samsi wrote:

Indeed it is but what tripped me up was it was not python-devel it is actually 
python-dev

Not quite a developer so didn’t think of trying -dev … :-)


On Dec 14, 2016, at 11:01 AM, Mark Sapiro  wrote:

On 12/14/2016 10:33 AM, Caesar Samsi wrote:

Ah, now it works. Would be great to see this info in the build & install
doc/wiki.



It's in the installation manual, section 15.1, as it said in the message
you received.



… checking that Python has a working distutils... configure: error:

* Distutils is not available or is incomplete for /usr/bin/python
* If you installed Python from RPM (or other package manager)
* be sure to install the -devel package, or install Python
* from source.  See sec. 15.1 of the Installation Manual for
* details



The manual is in various formats in the doc/ subdirectory of the
directory into which you unpacked and ran ./configure. I.e.,
doc/mailman-install/index.html, doc/mailman-install.dvi,
doc/mailman-install.pdf, doc/mailman-install.ps and doc/mailman-install.txt.

It is also online. See 
for the relevant section.

--
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
https://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: 
https://mail.python.org/mailman/options/mailman-users/guest2%40sgeinc.com


--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] illegible message in moderation approval queue

[Richard Shetron]

From a quick look, it looks like base64 encoding.  Invented back in the 
dialup/uucp days when transport was not always 8bit clean so things were 
encoded to make sure only transportable characters were used.


On 9/22/2016 9:58 PM, Matt Morgan wrote:

I have a message in a moderation queue. It's from a member (everyone is
moderated on this list) so I think it's not spam or other junk. But when I
click to review it, it's not legible. This is all I see in the message
excerpt:

IENvbnNkaXNsaXN0DQoNCrOqwMcgaVBob25lv6G8rSC6uLO/

I feel like I've seen other messages that look encoded/illegible in
moderation, though I don't have other examples right now. What can cause
this?

For what it's worth, the sender is a speaker of a language that uses a
different character set, so if that's possible cause, that might be the
reason here.

Thanks,
Matt
--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/guest2%40sgeinc.com


--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] cannot send mails to yahoo, hotmail and gmail

[Richard Shetron]

The problem is more likely in the MTA rather then mailman.  Have you 
checked the mailman logs?  Do you have access to the MTA logs?  Have you 
tried sending an email outside of mailman?


Do you know aht the MTA is?  common ones include postfix, sendmail, 
qmail, and exim.


On 9/18/2016 2:05 AM, Eko Budiharto wrote:

dear all,
I have a list using mailman. It cannot send mails to yahoo, hotmail and gmail. 
I check all setting in the mailman, but I still cannot find the problem yet. 
Please help me if someone who ever experience like this.

I am looking forward to a favorable reply from you. Thank you.

regards,
Eko
--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/guest2%40sgeinc.com


--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Which user is harvesting sender emails?

[Richard Shetron]

There is a LOT of broken software that will refuse rfc compliant email 
addresses as they do not properly follow the standards.  The + sign has 
been in use and part of the rfc's for at least 30 years.  I've found 
that using the underscore '_' will work when the plus '+' sign does not, 
however your mileage will vary.


What is even worse, you can create a +tag@ but later on 
the same companies software in a different part of the website will then 
refuse to accept the tagged address so even an initial acceptance can 
have problems elsewhere.


On 8/19/2016 10:21 AM, Bill Cole wrote:

On 18 Aug 2016, at 19:36, Mark Sapiro wrote:


Altering the From: based on recipient can be done by modifying the code.
Say you have a message "From: Ann User " and you want
to change that to "From: Ann User " where xxx is a
unique code for each recipient.



Please, don't anyone do that, ever. It's not just "risky," as noted in
earlier discussion, it would be positively abusive.

A less obvious approach would be to add an address IN A DOMAIN YOU
CONTROL in a X-[something] header (or perhaps a Cc header) that is
unique to each recipient so that when you get mail to that address,
you've identified your problem user.

HOWEVER, there is an angle to this problem that should be understood:
it's probably not being done by a human subscriber. One possibility is
that a subscriber has malware on their machine that is generating the
spam, so when you identify a subscriber who is your vector, you may only
be identifying someone which an insecure machine. Another possibility
(which would be untraceable and easy to automate on the spammer side) is
that someone other than a subscriber is harvesting addresses and
subjects from your web archive at mail-archive.com, where every message
has a button to "Reply via email" that kicks back a redirection to a
mailto: URL with the sender's address and Subject.
--
Mailman-Users mailing list Mailman-Users@python.org
https://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:
https://mail.python.org/mailman/options/mailman-users/guest2%40sgeinc.com


--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman 2's future (was Re: Filtering out Digest replies)

[Richard Shetron]

On 7/13/2016 12:16 PM, Barry Warsaw wrote:

On Jul 12, 2016, at 12:22 PM, Mark Sapiro wrote:

[snip end of life comments]

One thing that makes end of life either easier to handle or harder is:

1)  Documentation of the changes and the new system.

2)  Conversion aids.  At least a program to check a prior system and 
report all the problems in converting to the new system.  Best is a 
program that can do a full conversion from the old system to the new one 
with the minimal operator intervention.  Yes, I've done that, I worked 
for a company for 10 years and one of the standard things was converting 
new customers to our system, exporting data for those going away, and 
upgrading those on older versions to the newest version.


3)  Documentation.  I say this twice to emphasis it!


--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Our list serv host is threatening to shut us down for spam abuse

[Richard Shetron]

I had a customer with that problem.  We ended up using individual emails 
and adding the email address to the footer.  I don't remember the field, 
something user or user- something.  I had a program to scan those 
reports for the tag and provide the list of addresses to the list 
manager.  I think I ran it out of cron daily to scan the Maildir where 
those bounces/complaints ended up.


I had the list manager for those lists change to individual emails so 
that the email address could be added to the footer/signature as AOL and 
others seemed to never strip that part off.  AOL redacted the headers 
making them useless for determining the address to remove.


On 6/17/2016 4:21 PM, Andrew Hodgson wrote:

Hi,

I would work with the provider in this situation.  In my case I run several 
lists which are all opt-in, but people click on the report as spam button in 
Yahoo and AOL, causing issues.  I have an agreement with the hosting provider 
who run the network that if they get any complaints from AOL or Hotmail that 
come through this route, that they forward them onto me and I unsubscribe them 
from the list.  With AOL it is difficult as they remove the original email 
address who is complaining, Hotmail is OK and now Yahoo reports get sent to me 
directly.

I send the list traffic through specific servers so that it doesn't affect 
anything else.

Andrew.
--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/guest2%40sgeinc.com


--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] turn on tracing?

[Richard Shetron]

How do I find out what uid:gid the programs are running with?
Would I be better downloading a fresh copy of mailman and doing a 
reinstall over the broken copy?  The initial version was installed back 
in ubuntu 8.04 days when mailman wasn't a ubuntu package.  Since then 
for Ubuntu they changed some of the default groups for things, like 
mailing lists.


On 5/20/2016 11:47 AM, Mark Sapiro wrote:

On 05/20/2016 05:35 AM, Richard Shetron wrote:

How do I turn on tracing to find the source of this error.  The
interface worked until I told check_perms to fix permissions so I'm sure
there is a permission issue.  Also the qrunner won't run, which I also
suspect is a permission error.  My partner who did the install has
retired for medical reasons so I'm trying to learn how to do all sorts
of things in too little time :(  I tried to look in both the mailman
logs and the apache logs for errors and didn't find anything.

Bug in Mailman version 2.1.21rc2

We're sorry, we hit a bug!



There should be a traceback and other information about this error in
Mailman's error log. If it's not there, there is probably a permission
issue in writing the log.

You can at least temporarily ensure that Mailman's logs are writable by
anyone and see if that helps.

Also, you can edit $prefix/scripts/driver and at line 33 set

STEALTH_MODE = 0

and the traceback will be included on the "we hit a bug" page.

Also, if check_perms -f broke things, permissions must have been set in
some non-standard way to begin with. See the FAQ article at
<https://wiki.list.org/x/4030645>.


--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] turn on tracing?

[Richard Shetron]

How do I turn on tracing to find the source of this error.  The 
interface worked until I told check_perms to fix permissions so I'm sure 
there is a permission issue.  Also the qrunner won't run, which I also 
suspect is a permission error.  My partner who did the install has 
retired for medical reasons so I'm trying to learn how to do all sorts 
of things in too little time :(  I tried to look in both the mailman 
logs and the apache logs for errors and didn't find anything.


Bug in Mailman version 2.1.21rc2

We're sorry, we hit a bug!

Please inform the webmaster for this site of this problem. Printing of 
traceback and other system information has been explicitly inhibited, 
but the webmaster can find this information in the Mailman error logs.

--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] best way to reconfirm a list

[Richard Shetron]

That is correct.  The lists are current news announcements so only the
list owner posts to the list.  The sample headers I got look legit as
far as I can tell.  They redacted all the email/destination information
that would id the receiving system/email.

The original lists are old enough to not have been confirmed.  The goal
would be to send a confirmation email to everyone on the list and
unsubscribe anyone who does not re-confirm within a reasonable time, say
1 week.

On 5/6/2014 12:59 AM, Peter Shute wrote:
 Keith Bierman wrote:

 ​But since the OP said
 .  New
 subscribers are asked to subscribe to a yahoo group instead.

 I assumed it was really Yahoo (perhaps under a mask as mail 
 provider for some other named service, ala comcast ;) who 
 was doing the blacklisting...
 who else would be recommending yahoo groups as an alternative?
 
 I took that to mean that these lists are no longer accepting new members, and 
 that prospective members are being advised to join some particular yahoo 
 groups instead. I.e. they're gradually migrating to yahoo groups.
 
 Peter Shute
 --
 Mailman-Users mailing list Mailman-Users@python.org
 https://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: 
 https://mail.python.org/mailman/options/mailman-users/guest2%40sgeinc.com
 
--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] best way to reconfirm a list

[Richard Shetron]

I looked through the list admin manual and didn't see anything about
reconfirming a list.  Is there an easy way to have mailman reconfirm a list?

I have a list that has been in use for 5+years and all of a sudden maps
is saying I'm hitting a spam trap.  The list has not been added to in at
least 3+years.  Actually I have 2 lists that maps claims is hitting spam
traps, but neither list has been added to in at least 3+ years.  New
subscribers are asked to subscribe to a yahoo group instead.
--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Upgrade 2.1.14 to 2.1.17 on Ubuntu Question

[Richard Shetron]

I've searched the list and found enough related posts that this looks
like it should be simple just reinstall, hopefully with the original
PREFIX settings and probably diff the old and new mm_cfg.py files just
to catch all the changes/new features/etc.

I have visual problems so my eyes often go fuzzy if I do too much
computer work at one time.

However I find there may be a complication from a problem made from the
initial install of 2.1.14.

The initial install was done as user mailman, group mailman.  When I
reboot the server it seems to set mailman to user list, group list and I
have to go an fix permissions and ownership back to mailman:mailman.

If I install 2.1.17 over 2.1.14 and use list:list for user:group will
this fix the 'problem'?  Are there any gotchas I should be aware of?
I've found that at least with the current install (not done by me) that
fixing all the bin/checkperm problems will actually break mailman on the
server ;)

If relevant we are using postfix.

I was thinking of upgrading to MM3, but I don't see any final release
version and no software to upgrade from 2.1.x to 3.x.

Thanks in advance.

Rick Shetron
--
Mailman-Users mailing list Mailman-Users@python.org
https://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: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Hello all - mailman down after power failure and hard shutdown

[Richard Shetron]

I'd suggest trying ps -auxww|grep mailman to seem if any mailman 
processes are running, this assumes mailman runs as its own user id. 
Some installs use the username list or lists instead of mailman.


If nothing show up then I'd check:

1)  /etc/postfix/*.cf and /etc/postfix/transport and diff them with an 
older copy to make sure they haven't changed.


2)  check /var/lib/mailman/qfiles/maildir
The actual location may depend on your version and installation 
options.

If mailman is NOT running then the cur subdir should be empty.
I've found mailman will not restart if there is anything in the 
directory cur.  I'd check the files, if any, in both new and cur and tmp 
just to see what's there.

--
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] SMTP problem after recovering from disk full, clues?

[Richard Shetron]

I've noticed that if mailman is stopped/crashes/system reboot/etc. and 
there is anything in mailman/qfiles/maildir/cur that stuff seems to just 
hang in mailman until you stop mailman, clear this directory, and then 
restart mailman.  May not be your problem but try checking it.


you might also want to run the various check/test programs in 
mailman/bin such as check_db and check_perms.


On 5/20/2013 1:45 AM, David Josephson wrote:

A very old and well-used list has been fine for years on this box,
running Mailman 2.1.10 on Red Hat 7.2. The disk got full and everything
crashed. I was able to clear out a couple GB of space and get all
services running again, but now mailman will not send any messages,
either to the list admins or to members. Just before it died completely,
admins got a We're sorry, we hit a bug email.

Incoming spam is properly discarded and logged in /logs/vette. Incoming
posts show up in /logs/post showing 250 failures (there are 698 members
on the list). The web interface seems to be functioning properly.

/logs/smtp-failure shows
Low level smtp error: (-2, 'Name or service not known'), msgid: ...
and then

May 19 22:02:15 2013 (16851) Low level smtp error: please run connect()
first, msgid: ...

and then listings of each of the addresses where delivery was attempted,
each with delivery to xx@yy failed with code -1: (-2, 'Name or service
not known')

Nothing has changed with /etc/smrsh or sendmail, I can send and receive
mail with mutt just fine.

When I reinstalled mailman and sent it a test post, I got the group
mismatch error reminder in the returned mail message that I needed to
run configure with --with-mail-gid=mail, which I did, now test messages
to lists don't bounce back to the sender, they just don't get out of the
server.

Following some of the FAQs I've looked with dumpdb and find no obviously
corrupt .pck files. I moved ~mailman/lists and ~mailman/archives off
somewhere else, reinstalled the same version, brought those directories
back to ~mailman, and get the same behavior.

What am I missing?

--
David Josephson
--
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/guest2%40sgeinc.com


--
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] Domain not found problems

[Richard Shetron]

I'm having problems with DOMAIN not found errors.  Is there anyway to 
edit/remove them from the qfiles/out .pck files?  They don't seem to be 
getting purged by mailman and hang around way too long.


I'm using postfix and mailman 2.1.12 under ubuntu 8.04.

I found item 4.20 in the FAQ, but I'm not sure if it would work and 
still working on learning postfix as my normal admin is ill.  I'd only 
want it to work for mailman and not for other users regarding this problem.


I'm disabled due to vision problems so I did look through the archives 
until my eyes went buggy.


Thanks
--
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] Fw: Mass Mail

[Richard Shetron]

I can't say what others do, but we carefully vet people before setting 
up a list for someone.  One of my email addresses is on every list we 
host so I get a copy of everything sent.  I use thunderbird and have it 
filter all the mailing list traffic to a separate mailbox.  Once the 
list if properly vetted I tend to ignore the list unless I get a 
complaint.  I can then look at the last few sendings to see what was sent.


Occasionally a list member will have their computer compromised and emit 
spam.  If necessary, the user can be blocked until their computer is fixed.


Some lists use moderators so every posting to the list must be approved.

As I have root access to all the systems involved I will occasionally do 
a 'tail -f mail.log' to see how mail is flowing.  Sometimes it is too 
fast to see, but you can usually tell if most of the status messages are 
250 (message sent) or 4xx or 5xx.  Sometimes I'll just grep the log for 
specific responses.



On 4/30/2013 7:03 AM, Javad Hoseini-Nopendar wrote:



Thank you dear Mark, Steven, Adam and Richard for your helpful answers.
Now I have another question. Many of the hosting servers in my country Iran,
disable the mailing list service for all their users (unless the users of
Private Servers). If you talk to them and swear an oath not to send spam, or
if you become contented with paying extra charge, again they don't accept to
activate the mailing list service for shared hosts, because if I start
sending spam, their IP will go into the black list of Gmail and Yahoo and
all the websites on that hosting service will be blocked by Yahoo and Gmail
anti-spam filters. What do the hosting companies of other countries do in
order to prevent spamming by the users of their mailing lists? Do they
deactivate the mailing lists too, or have ways to supervise the websites and
prevent them from spamming? -

Original Message -
From: Stephen J. Turnbull step...@xemacs.org
To: Richard Damon rich...@damon-family.org
Cc: mailman-users@python.org
Sent: Tuesday, April 30, 2013 10:09 AM
Subject: Re: [Mailman-Users] Mass Mail


Richard Damon writes:

   There is a fourth case, Host Provider sends the emails then sends you a
   bill for the overage at the rate specified in the contract. This could
   be very expensive for going that much over limit.

All I can say is, ouch!  :-(

--
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/javad%40irannopendar.com

--
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/guest2%40sgeinc.com


--
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] Mass Mail

[Richard Shetron]

On 4/29/2013 6:44 AM, Adam McGreggor wrote:
[snip]


+1. Even 5000 seems to be the threshold these days, for unknown
netblocks.


Each has their own limit and sometimes it is based on history, sometimes 
on number reported as spam.  You can send 100k emails and if 1000 are 
reported as spam you can get blocked or even 100 at times.  Every 
provider is different.


I don't have it handy, but there was a list of some of the major 
provider's bulk sender sign up pages.  I had it bookmarked until a 
browser crash lost the bookmark for me.



--
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 continues to deliver to deleted list

[Richard Shetron]

On 11/5/2012 8:02 PM, Mark Sapiro wrote:

Josh Berkus wrote:


Folks,

I deleted a mailing list using rmlist.  However, mailman continues to
send out messages to the recipients on this list, and I can't seem to
make it stop.  There's ~~ 3000 pending deliveries, so I'd really rather
that they not go out.

For now mailman is shut down.  How do I clean out its pending messages
queue entirely?



First of all, if the list is gone, i.e. there is no lists/LISTNAME/
directory in Mailman's hierarchy, no currently queued messages will be
processed. Outgoing runner or some other runner may pick up queue
entries for this list, but the list won't be there, so the queued
message will be shunted with an error log message 'Dequeuing message
destined for missing list: LISTNAME'. Therefore, you can just restart
Mailman and any messages in Mailman's queues from the affected list
will just wind up in the shunt queue and won't be processed.

Thus, any 'pending' deliveries which will go out have already been
delivered from Mailman to the MTA, and stopping them has to be done in
the MTA (unless that's moot at this point).


I have a shell script that I use to remove email from the postfix queue 
based on some unique text string.  This is only for postfix and is kinda 
crude, but it works ;)


It should run on any *nix system.


--
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] mailman running very slow

[Richard Shetron]

Yes I've tried to research via google, etc.  I've run through the page at:
http://wiki.list.org/display/DOC/4.78+Troubleshooting-+No+mail+going+out+to+lists+members

I'm running ubuntu with mailman 2.1.14 and things seem to be taking 
forever.  Until a few days ago things were running fine.  There have 
been no config/system changes.


One of the things I'm seeing is is the smtp log file:

Oct 23 13:42:13 2012 (19673) 
7.0.1.0.0.20121016133607.0469b...@marchreport.com smtp to 
marchreport_daily_alert_ctc10 for 2 recips, completed in 168.029 seconds


That seem to be a very long time for processing a list.

Also mailing from a week ago are starting to come through, but I thought 
I'd removed all of them from both the mailq and from mailman.  I thought 
I new how to cancel/remove older mailings, but it seems not.  How do you 
cancel old mailings?  I've cleared the postfix queue and I thought I'd 
cleared the mailman qfiles.


I'm also occasionally getting the following error in the smtp-failure log:

Oct 24 06:00:01 2012 (29638) Low level smtp error: (4, 'Interrupted 
system call'), msgid:7.0.1.0.0.20121016133607.0469b...@marchreport.com


We're using ubuntu with postfix.

python processes:

mailman   4576  0.0  0.0   9608  4792 ?Ss   06:00   0:00 
/usr/bin/python /var/lib/mailman/bin/mailmanctl -s start
mailman   4577  0.0  0.0   9552  6456 ?S06:00   0:00 
/usr/bin/python /var/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s
mailman   4578  0.0  0.1  17420 14696 ?S06:00   0:01 
/usr/bin/python /var/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s
mailman   4579  0.0  0.0   9528  6436 ?S06:00   0:00 
/usr/bin/python /var/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s
mailman   4580  0.0  0.0   9544  6444 ?S06:00   0:00 
/usr/bin/python /var/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s
mailman   4581  0.0  0.0   9520  6488 ?S06:00   0:00 
/usr/bin/python /var/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s
mailman   4582  0.2  0.1  14628 11964 ?S06:00   0:25 
/usr/bin/python /var/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s
mailman   4583  0.0  0.1  12332  9688 ?S06:00   0:00 
/usr/bin/python /var/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s
mailman   4584  0.0  0.0   9512  6448 ?S06:00   0:00 
/usr/bin/python /var/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s
mailman   4585  0.0  0.0   9728  6904 ?S06:00   0:08 
/usr/bin/python /var/lib/mailman/bin/qrunner --runner=MaildirRunner:0:1 -s



another error in smtp-failure:

Oct 24 09:37:18 2012 (4582) All recipients refused: {'mmm5...@aol.com': 
(503, '5.5.1 Error: nested MAIL command')}, msgid: 
7.0.1.0.0.20121016133607.0469b...@marchreport.com


The SMTP settings in mm_cfg.py:

MAILMAN_SITE_LIST = 'mailman'
SMTPPORT = 587
#SMTPHOST = 'mail.marchreport.com'  Just did this change from name to ip
SMTPHOST = '71.244.124.123'

postfix listens on 587:
master.cf:587  inet  n   -   n   -   120   smtpd
--
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] meaning of data in mailman smtp file

[Richard Shetron]

What does this line really mean and why does it take so long to run?

Oct 23 06:03:01 2012 (1870) 
7.0.1.0.0.20121016133607.0469b...@marchreport.com
smtp to marchreport_daily_alert_ctc10 for 2 recips, completed in 168.022 
seconds


Thanks
--
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 running very slow

[Richard Shetron]

I played with some settings and did some restarts and things look better:

Oct 24 17:13:22 2012 (5464) 
7.0.1.0.0.20121023125107.046bd...@marchreport.com smtp to 
marchreport_daily_alert_ctc01 for 3379 recips, completed in 151.441 seconds
Oct 24 17:16:11 2012 (5464) 
7.0.1.0.0.20121023125107.046bd...@marchreport.com smtp to 
marchreport_daily_alert_cta31 for 3826 recips, completed in 169.111 seconds
Oct 24 17:25:44 2012 (5464) 
7.0.1.0.0.20121023125107.046bd...@marchreport.com smtp to 
marchreport_daily_alert_ctc02 for 7202 recips, completed in 572.629 seconds
Oct 24 17:29:32 2012 (5464) 
7.0.1.0.0.20121023125107.046bd...@marchreport.com smtp to 
marchreport_daily_alert_ctc03 for 3694 recips, completed in 227.642 seconds


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