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 on that system can not find the package. I have not found the actual comment in the mail.log file and what I found on http://www.mikecappella.com/logwatch/faq.html#connectionoverload, logwatch generated that text, not Postfix so I am in the wrong place with my question. If the site is correct, this is not to much of an issue after all. It seems to be more of a vague indication message. There have been suggestions about changing the smptd_timeout to a larger value. I have not found smtpd_timeout in my master.cf file. It looks like the message from logwatch is telling me that there were a large number of unresolved connections, ie no ip address given before the disconnect occurred. Side note on this. I installed logwatch on Ubuntu 7.10 and given the info on the site, the postfix-logwatch module I am using is dated. The message verbiage was changed to include the phrase "Possible connection overload". Given that knowledge, I can live with this error.
Guy On Tue, Jan 13, 2009 at 11:13 AM, Noel Jones <njo...@megan.vbhcs.org> 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 so it has me a bit curious. >> > > Cool, considering the current postfix-logwatch version is 1.37.08. > > http://www.mikecappella.com/logwatch/ > > Maybe your postfix-logwatch module needs updating. > > 73, > > -- > Noel Jones > -- 73 Guy Story KC5GOI kc5...@gmail.com
