[IMGate] Re: strange postfix startup message

[Bob McGregor]

ok, that got rid of the errors on the postfix start.
however, I still have no /var/log/maillog

I did move it from /var/log/maillog to /usr/bob/maillog this morning while =
i was digging out of our problem... did that break something.

Insidently, the problem this morning was that we had an infected computer =
in our network that found our imgate box and was spewing like crazy. We =
run declude on the imail box but nothing on our imgate box and config our =
clients to use imail. The infected computer must have finally hit the IP =
of our imgate to start the flood.

if anyone runs similar to this, make sure your internal clients cannot use =
port 25 on your imgate box or you could end up like we did tough lesson=
.



On Friday, December 17, 2004 10:22 AM, Len Conrad [EMAIL PROTECTED] =
wrote:

postfix check
   -- redisplays the same errors for postdrop and postqueue
postfix upgrade
   -- is not a valid command, upgrade does not list

my mistake, in the src directly, after compiling,

make upgrade

Len

[IMGate] Re: strange postfix startup message

[Len Conrad]

however, I still have no /var/log/maillog

in fbsd, syslogd will not create files, only write to files.

man touch

Insidently, the problem this morning was that we had an infected computer =
in our network that found our imgate box and was spewing like crazy. We =
run declude on the imail box but nothing on our imgate box and config our =
clients to use imail. The infected computer must have finally hit the IP =
of our imgate to start the flood.

You should have had (trusted) mynetworks = restricted to only Imail IP 
and other PCs you have complete control over.

policies that trust IPs, esp subscriber/PC IPs, is dangerous and should be 
tightly restricted.

Len