I received a error in my log watch report that I have not seen before and
just wanted to get a idea of what I am seeing. Based on a match from a
Google search back in 2004 it looks like a dirty disconnect could cause the
error message below. I snagged the entries in the log file for the spot of
t
> People seem to be logging in and out. Seems normal for a mailserver,
> > if you ask me.
> >
>
> too many users with 'a' as first letter, and machine is in the US while
> OP is in UK. so either OP munged things, or his server is under attack.
>
> anyway, as you said, not a postfix issue.
>
>
--
73
Guy Story KC5GOI
kc5...@gmail.com
On Tue, Jan 13, 2009 at 11:38 AM, Guy Story KC5GOI wrote:
> Noel, just before I saw your post I realized I had confused the two. My
> mistake or is it I can see into the future? :) I have the current Logwatch,
> not the postfix-logwatch module.An apt-get -install -s postfix-logwatch
rror.
Guy
On Tue, Jan 13, 2009 at 11:13 AM, Noel Jones wrote:
> Guy Story KC5GOI wrote:
>
>>
>>Maybe your postfix-logwatch module needs updating.
>>
>>
>> 7.3.6 is the version I installed via apt two weeks ago. It is the first
>> time I saw this
I removed dsbl just now. I have not been able to locate the message in the
log that triggered it yet. I will keep looking, got side tracked by a
support call.
On Tue, Jan 13, 2009 at 10:56 AM, Noel Jones wrote:
> Guy Story KC5GOI wrote:
>
>> I received the following error for th
I received the following error for the first time yesterday in my logwatch
report. It was in the Postfix section.
1 *Warning: Pre-queue content-filter connection overload
--
1 After CONNECT
1 unknown unknown
I have read ove
