thanks len,
I now have the maillog back. I restarted the syslogd process and it =
started logging.
I agree, that's the problem, I had my entire newtork in my mynetworks. I'=
ll make that change.=20
bob
On Friday, December 17, 2004 10:48 AM, Len Conrad <[EMAIL PROTECTED]> =
wrote:
>
>>however, I
>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
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 infecte
>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
thanks len,
postfix check
-- redisplays the same errors for postdrop and postqueue
postfix upgrade
-- is not a valid command, upgrade does not list
according to my mail.cf
the owner should be postfix
and group should be maildrop
on the ls -la postdrop the owner is root:maildrop
so I=20
postf
>However, I caused a couple issues:
>1. I movde the maillog to a different partition and now that postfix is =
>running, I have no maillog in the /var/log directory. It did not get =
>recreated. How do I get that back?
postfix check
and then if you can, re-run
postfix upgrade
which should fix
