This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

POP3 (4.021) All messages quarantined !

Since the upgrade to 4.021, all pop3 messages are quarantined by Astaro. The following messsage is forwarded to the recipient :

The VirusScanner has found a virus in your mail. The scanning report follows:

Failed to scan file: /tmp/wool/3419/03419-1077201081-00005/textfile0
This mail is quarantined and can be seen in the Proxy Content Manager on your firewall

Instead of the infected email this message has been sent to you.

Any clue on what is happening and how I can correct this ?

Thanks.

This thread was automatically locked due to age.

Parents

0 William Warren over 21 years ago

I jsut noticed that as well....i ahve 6 messages from two of my security mailing lists that have no atachments but get the same error...any ideas? I have shutdown pop3 a/v until this gets figured out.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 William Warren over 21 years ago

I jsut noticed that as well....i ahve 6 messages from two of my security mailing lists that have no atachments but get the same error...any ideas? I have shutdown pop3 a/v until this gets figured out.
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 Xeno over 21 years ago in reply to William Warren

Hi,
I was not able to reproduce that. I am using 4.021. Everything works fine. Could you post your pop3-configuration?

Xeno
Cancel
Vote Up 0 Vote Down

Cancel
0 William Warren over 21 years ago in reply to Xeno

Private_Networks_-_RFC1918 Any delete

worked fine until .021...
Cancel
Vote Up 0 Vote Down

Cancel
0 fxdsuperglide over 21 years ago in reply to William Warren

I also have POP3 Proxy running and I am getting no problems and I just updated to 4.021 I cannot duplicate it either..
Cancel
Vote Up 0 Vote Down

Cancel
0 William Warren over 21 years ago in reply to fxdsuperglide

well i tried something i do when ASL decides to act stupid...i tried a standard reboot....that did not fix the problem...so i let it come back up..after it was finished booting..i pulled the plug..then let it come back up..problem solved(sometimes windows techniques work on linux rofl)
Cancel
Vote Up 0 Vote Down

Cancel
0 pgervaix over 21 years ago in reply to Xeno

I solved the problem with my system.

In my configuration no proxied networks were defined and virus protection was on. With version 4.020 messages were still scanned even if nothing was entered in the proxied network, so I never bothered. When I updated to version 4.021 all messages were blocked. As soon as I entered something in the proxied networks, everything was fine.
Cancel
Vote Up 0 Vote Down

Cancel