On 02/28/2016 03:32 PM, Mark Sapiro wrote:
>
> I am pleased to announce the release of Mailman 2.1.21.
It always happens. The only question is how. The thing is discovery of a
bug immediately after a release. This time the how was my PGP signature
being broken in the outgoing messages from 2 of
On 02/29/2016 12:48 PM, Keith Seyffarth wrote:
>
> I haven't had any problems with my many low-volume lists correctly
> removing dead addresses - as long as the receiving MTA is not configured
> to not bounce undeliverable mail properly...
It depends on the list and settings. The defaults are
>> Shouldn't mailman (or any good mailing list server) be automatically
>> removing bouncing addresses?
>
>
> Mailman is very good at this IF it is properly configured. There are
> list settings under control of the list admin. The defaults are
> reasonable for lists that moderate to high traffic
On 02/29/2016 07:44 AM, Keith Seyffarth wrote:
>
> Shouldn't mailman (or any good mailing list server) be automatically
> removing bouncing addresses?
Mailman is very good at this IF it is properly configured. There are
list settings under control of the list admin. The defaults are
reasonable
[changed the subject, I don't intend to carry this topic any further]
On 2/28/2016 11:28 PM, Ruben Safir wrote:
On 02/29/2016 02:12 AM, Carl Zwanzig wrote:
Oh, and -nothing- involved in email handling is "real time", which has a
fairly specific meaning in computing.
Use whatever terminology
On 2/28/2016 11:19 PM, Mark Sapiro wrote:
On 02/28/2016 10:51 PM, Ruben Safir wrote:
smtpd_recipient_restrictions = check_client_access
hash:/etc/postfix/helo_client_exceptions check_sender_access
hash:/etc/postfix/sender_checks, reject_invalid_hostname,
[...]
This is almost certainly your
On 02/29/2016 10:44 AM, Keith Seyffarth wrote:
> how many honeypots are out there flagging this sender as a bad
> sender and harming the listserv, or possibly the whole domain or IP as
> being a problem sender?
there are no honey pots. Most of the email addresses have been on the
lists for a
> I would run through the logs to find all the domains that are timing out on
> dns, then mark the recipients on those domains as "no mail". After that, see
> how delivery goes for the rest of them. Besides, why keep users on the list
> than don't exist or actually get delivery?
Shouldn't
On 02/29/2016 04:19 AM, Stephen J. Turnbull wrote:
> > From looking at your Postfix logs, it looks as though you have a major
> > DNS problem. I suggest that you install bind and set up a caching DNS
> > server on the same box that is running Mailman.
>
> Good idea, but I suspect that
Thanks for the suggestions, Hank!
Hank van Cleef writes:
> From looking at your Postfix logs, it looks as though you have a major
> DNS problem. I suggest that you install bind and set up a caching DNS
> server on the same box that is running Mailman.
Good idea, but I suspect that wouldn't
Mark Sapiro writes:
> This is almost certainly your problem. All those [RBL] checks take
> time, especially if DNS is slow.
Also, several of the checks (RBL and otherwise) seem to be in there
repeatedly. ISTR that Postfix does the checks in the order specified,
so they might be done multiple
Mark Sapiro writes:
> This is almost certainly your problem. All those [RBL] checks take
> time, especially if DNS is slow.
Also, several of the checks (RBL and otherwise) seem to be in there
repeatedly. ISTR that Postfix does the checks in the order specified,
so they might be done multiple
On 02/29/2016 03:08 AM, Hank van Cleef wrote:
> a. What is your computer hardware?
fit/pc2 Intel Atom with a gig of ram and 2 gigs of swap on a tetrabyte
- /proc/cpuinfo -
processor : 0
vendor_id : GenuineIntel
cpu family: 6
model : 28
model name:
The esteemed Ruben Safir has said:
>
> On 02/28/2016 03:57 PM, Tanstaafl wrote:
> > On 2/28/2016 1:19 PM, Stephen J. Turnbull wrote:
> >> If that doesn't make it obvious what you need to do, you might want to
> >> tell us something about your configuration and use case. What
14 matches
Mail list logo