On 17 Oct 2019, at 16:41, Steven Jones wrote:
ssh takes a long time to login but there is no load to cause this.
The first thing to suspect when logins take a long time with no tangible
loading issues (i/o, memory, and CPU all good) is DNS. If your resolver
is trying to query a
On 10/17/19 3:59 PM, Steven Jones wrote:
> thanks
>
> I am sort of suspecting postfix as /var/log/maillog is not being written to.
>
> meanwhile,
>
> /var/log/mailman/smtp has something odd. The time to send email varies
> between 0.017 and 180 seconds plus, and its getting worse,
>
>
thanks
I am sort of suspecting postfix as /var/log/maillog is not being written to.
meanwhile,
/var/log/mailman/smtp has something odd. The time to send email varies between
0.017 and 180 seconds plus, and its getting worse,
==
Oct 18 11:26:13 2019 (9398)
smtp to
On 10/17/19 1:41 PM, Steven Jones wrote:
> Hi,
>
> Yesterday we had a major network outage that lasted 2 hours+ This morning I
> find that the mailman server has "stopped working" I have restarted mailman
> and now the server but mailman is not processing any emails. The load in top
> is
Hi,
Yesterday we had a major network outage that lasted 2 hours+ This morning I
find that the mailman server has "stopped working" I have restarted mailman
and now the server but mailman is not processing any emails. The load in top
is 0.00 ~0.01 sort of thing, no no disk i/o, no action at
On 10/17/19 2:48 AM, Ralf Hildebrandt wrote:
>
> This was due to my non-default setting:
>
> confirm_delay_cleared = yes
>
> After sending a "your message is delayed" notification, inform the
> sender when the delay clears up. This can result in a sudden burst of
> notifications at the
On 10/17/19 2:38 AM, Tom Corcoran wrote:
> All my stuff is typically default and not set unless ye told me here. I
> double-checked and no rules in there
How do you know when a message is discarded? Do you get a message from
Mailman with Subject: Auto-discard notification with the message
Today I received a lot of unsubscription notifications for a certain
list.
I grew suspicious and had a closer look. I found that Postfix was
retrying the delivery for a lot of domains behind the same MX and was
(finally) reporting the delivery after a long time of queueing for
that MX host.
This
All my stuff is typically default and not set unless ye told me here. I
double-checked and no rules in there
On Wed, 16 Oct 2019 at 18:01, Mark Sapiro wrote:
> On October 16, 2019 9:16:14 AM PDT, Tom Corcoran
> wrote:
> >thanks, Mark,
> >
> >Content-Type: multipart/mixed;
> >
