Qmail 451 mail server temporarily rejected message (#4.3.0)

[tantons]

Hello,

I posted this in an old thread but was not sure if it is active anymore!
I am getting an error every time a message is sent to a domain on the Interworx box. I have tried with My clamav service is running and not. Everything that gets sent to this server is rejected with this responce being sent to the sending server- 451 mail server temporarily rejected message (#4.3.0)
as well as this line after the following line- 1 1104 00:00:00 ERROR OXU03130
I have searched and have found nothing that will fix this problem. It can send find and any message that is sent to another domain on the same server is recieved fine. But anything that comes from the outside is rejected with this message.

Any help would be greatly appreciated!!!
I have reinstalled simscan restarted qmail tried with an without spam turned on. The firewall is open.

A side not does anyone know of a good list server that works well with Interworks.
I would like to add that I am very impressed with the responce I have gotten when I needed help. This is one of the reasons I was trying to find another salution to the email software I was using. I paid for support but it was almost impossible to get a responce and when it did come it was always wait until the next release to get a function that I had already paid for. You may not have all the features right now but I would rather have your support over there features that half the time don't work anyway.

Thanks
Todd

[tantons]

Hello again,
I tried sending an email using outlook with an account on the server and I get this error when it tries to send - qmail 451 unable to exec qq (#4.3.0)
I can not connect to the pop3 server as well.

Any help at this point would be great

Thanks

[rone]

Hi Tantons,

If you pay for support then open a ticket for it. The response of the Interworx team is always fast and they sure will help you.
Goto: https://www.interworx.com/support/helpdesk/ to create a ticket.

[IWorx-Paul]

If it's not a case of ClamAV being down which it sounds like it's not, we would have to login to the box and check it out, so rone's suggestion of opening a support ticket is probably best.

Paul

[tantons]

Sorry I didn't mean their support!!! It was support from another software cmpany I was speaking of! Interworx support has been very good!!!

[pascal]

Hi,

Did you resolve the problem ?

Pascal

[tantons]

Hey Pascal, I sent a support ticket. there are looking at it now. I didn't see that you had replyed until now!

As I don't have alot of knowledge about Linux, I don't want to send a support ticket every time I have a problem. As the problem might be me. I want to rule that out first. jajaja

Thanks

[EverythingWeb]

This issue appeared in the last few hours for us. Not even our dedicated Spam Appliance was able to pass mail through, and its deferred queue stacked up.

We disabled the ClamAV/Anti-Spam on the (Iworx) server and flushed the defferred queue on our Spam appliance and all mails came through. We are investigating what is/has caused this.

[pascal]

This issue appeared too this night !

Only for one old server (not the cluster one) !

delivery 204: deferral: xx.110.xx.145_failed_after_I_sent_the_message./Remote_host_said:_451_mail_server_temporarily_reje cted_message_(#4.3.0)/

The best should to open a ticket !

Pascal

[pascal]

The clamd seems to be the problem !

In /var/log/smtp/current I see a lot of simscan clamd error

Also if I look a the clamav page on nodeworx, the virus definitions file seems to be empty

main.cvd 31 Dec 2006 13

[EverythingWeb]

Yes you are right Pascal. I'll be submitting a ticket in a bit - or maybe Iworx can respond here for everyone's benefit :)

[pascal]

In fact it has been some soft updates



1. clamav.x86_64 0:0.90-100.rhe4x os
applied
2. perl-Mail-SPF-Query.x86_64 0:1.999.1-101.rhe4x os
applied
3. perl-Net-CIDR-Lite.x86_64 0:0.20-101.rhe4x os
applied
4. perl-Sys-Hostname-Long.x86_64 0:1.4-101.rhe4x os
applied
5. proftpd.x86_64 0:1.3.0a-104.rhe4x os
applied
6. spamassassin.x86_64 0:3.1.8-200.rhe4x os
applied

I have opened a support ticket !

[pascal]

What is that as soon as there is a

freshclam


There is these logs


# freshclam
ClamAV update process started at Sat Feb 24 17:15:15 2007
main.cvd is up to date (version: 42, sigs: 83951, f-level: 10, builder: tkojm)
Downloading daily-2642.cdiff [100%]
daily.cvd updated (version: 2642, sigs: 10362, f-level: 13, builder: ccordes)
Database updated (94313 signatures) from database.clamav.net (IP: 195.214.240.53)
Clamd successfully notified about the update.


Then all definitions disepears

Pascal

[IWorx-Socheat]

Hi guys,

CentOS released an update to SpamAssassin recently, and we upgraded our packages to match. We're aware of the current situation, and are looking in to it. We'll have an update for everyone shortly.

Thanks,
Socheat

[pascal]

Thanks Socheat

And good luck

Pascal

[EverythingWeb]

Fedora 3 & 4 here Socheat, unless its a sweeping package and distro doesn't make any difference.

Thanks for the update - most appreciated :)

[IWorx-Paul]

Hi guys,

Apparnetly something changed in the new ClamAV version that was resulting in clamav not being able to read the directory's owned by the simscan user, even though it clearly should, and has in previous versions.

Run
yum update

on your boxes, that will pull down a newly updated simscan RPM that should work around the new clamav behavior.

Paul

[pascal]

The problem is resolved !

Interworx has done a new version of simscan, which will be automaticly installed if you have the software updates set to ON !

Thanks a ton to them

Pascal

[pascal]

Arff sorry guys

I still was at the end of the 1st page !

[tantons]

I started having this problem again! Clamav won't even start, and every message sent to the server is rejected! what changed between last weekend and this weekend? was there another update?

Todd

[IWorx-Paul]

The last update was on Monday, nothing has changed since then. I'd check /var/log/clamav/clamd.log file for errors when trying to start clamd.

I'd also run
yum update

to make sure you've got the most recent update installed.

Paul

[tantons]

The last entry in the log is for Sat Feb 24th! I haven't changed anything in the system. and it is not loging anything when I try to start. Iworx just says faild to start!

I have run yum update several times and it only say nothing to update! I have even tried a restart of the system today.

So that means it hasn't allowed any incoming messages since last saturday! I am glad I havn't put anything of importance on this system!!

Do I need to file another ticket?

Thanks
Todd

[IWorx-Paul]

Yes, you should open a ticket.