Messed up Mailserver
 

Hi,

I tried to do some updating of my spamassisan clamav. This didn't go well, as I got error messages so I wanted to stop with it.

I followed guidelines which I found in the howto section, http://www.howtoforge.com/postfix_an..._clamav_ubuntu

But as I already had a wrking postfix with virtual users setup I didn;t start from the top. I was actually only interested in updating spam and clamav.
BUt got into troubles

I would like to resolve it that my postfix will work again (no accounts are capable of receiving mail at this moment.

Telnet localhost 25 followed by the command ehlo localhost gives me a connection refused message.

My mail.warn file gives this error
Feb 29 11:55:58 mussorubuntu postfix/master[8248]: warning: process /usr/lib/postfix/smtpd pid 8675 exit status 1
Feb 29 11:55:58 mussorubuntu postfix/master[8248]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling

My maillog gives following messages:
Feb 29 11:56:59 mussorubuntu postfix/master[8248]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Feb 29 11:57:59 mussorubuntu postfix/smtpd[8714]: fatal: open database /etc/postfix/sender_access.db: No such file or directory
Feb 29 11:58:00 mussorubuntu postfix/master[8248]: warning: process /usr/lib/postfix/smtpd pid 8714 exit status 1
Feb 29 11:58:00 mussorubuntu postfix/master[8248]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling

How should I repair this??
Thanks
Harry

Create the file /etc/postfix/sender_access then run this command

That was easy, great thanks.

any advice how to do clamav and spamassisan

Whats the problem with those ? Am sure you can continue following the howto for that.

I ran into problems updating clamav.

But I'll try again starting from paragraph 4.1 from this Howto

What were the problems maybe i can help ?

THe howto told me to update clamav, I did with apt-get install command, but it keep on telling me it was outdated when I needed to configure clamav (with freshclam)

That means the repo has not been upgraded to the latest clamav that is available upstream. There is no need to panic.