Virus scanner blocking/messing up traffic?

[m.goode]

Originally Posted by Silver Bullet

Is the Spam Filter still scanning your POP mail while using the non-standard port?

Sorry, Actually it does not scan the 109 port, but we are still getting the benefit of tar pitting and the 110 port is still being scanned.

[darklogic]

Just want to start off by saying sorry in the length of this post.
I'm running a POP3 server and when trying to receive e-mails from outside of the network over an IPSec tunnel or a FQDM POP3 will error out if you have SPAM, Phishing, and Virus blocker turned on, but if you do a PPTP into the internal network which will give you a internal IP of that network and force all traffic through the PPTP VPN, the POP3 will pass and e-mails come right into your inbox without any issues. After almost 6 months ago on a post with this issue, still no fix I see. One other note, this issue remains on any e-mail client, not just Thunderbird.

Most threats to a network come from e-mail and browsing the web right!!! Well how can I be affective with the Untangle system if I must disable 3 mods which include SPAM filtering, Phishing filtering, and Virus filtering just to be able to get e-mail remotely from the network? I can't go around and change standard ports on over 300 machines. This is just not practical. I know I may sound irritated, but only because this was brought up by others and myself months ago on this thread and others. I stopped receiving any responses on that issue. Now I see the same issue popping up in new threads. Plus I addressed this issue in beta testing and still no response. Beta2 5.1 and still no fix.

I persist with this issue only because I cannot find really any other issues with the Untangle system other than in the reports and that is a plus, but this issue has been a drag for way to long. I have used other systems to protect our e-mail until Untangle gets a resolution for this, the question is when? Clark Connect does not have as many features as Untangle, but still uses the spam assassin engine and ClamAV. I have to run Untangle in transparent mode behind a Clark Connect system that does proxy filtering for our incoming SMTP due to not being able to have Untangles filters enabled. And yes I have tried many solutions for front end firewalls such as, Monowall, PFsense, Smoothwall, Endian, MFN2, Sonicwall, Cisco PIX 506E, ISA2006, and Vyatta. Oh and I tried having Untangle as a standalone firewall. I just want to know if this issue is going to be fixed anytime soon. I can see you ignoring this post only because of my tone, but others have this issue as well, so I’m not just complaining over nothing.

[ThisMedved]

I found this thread looking for other Thunderbird causes for my Mail trouble.
Bug http://bugzilla.untangle.com/show_bug.cgi?id=3210 for YUM has been closed as duplicate for http://bugzilla.untangle.com/show_bug.cgi?id=2524 also resolved.

Is another bug open for the POP retrieval issue or is more information needed?

I have changed Thunderbird settings to download headers and leave on server until deleted by the mail client. This is allowing me to narrow down which Untangle module causes Thunderbird to fail. Thunderbird continues to fail downloading many e-mail bodies.

Downloads have been successful with only Virus scanning enabled.

Downloads from the same POP server with Outlook are successful.

Any advice would be appreciated.

[XeOn]

I know this is old, but I have the same problem with Untangle 5.2 and Thunderbird/Eudora.
Outlook express works fine, but then again outlok express chooses different port if 110 doesn't work.
Switching off Spam Blocker & Virus Blocker or Phish Blocker works and all our emails are received. Switching to SSL port (995) also works, but none of these fixes actually works in real life, since it doesn't scans emails.

Any thoughts?

Thanks!

[sky-knight]

Ever consider that Thunderbird might be the problem? I have random pop retrieval issues with every mail client in existence... Outlook (express), Thunderbird, Pine, Entourage, etc...

They all have one thing in common, a usually spam e-mail is sitting on the server and something about it causes the POP session to puke and clients complain of duplicated e-mails. The only solution I've ever found is to delete the message using a webmail client and try again. Also, mail clients configured to leave messages on the server for any length of time seem more prone to this failure, as they invariably leave stuff on the server they really shouldn't and things get out of sync.

I haven't seen anything in UT 5.1, 5.2, 5.2.1 that would indicate the pop3 proxy being anymore bug/failure prone than most AV companies local pop3 proxies. Which incidentally, they are in the mix too causing more problems. The long and short is the more software you get involved with any given process the more likely it is that something will go wrong. The only way you can narrow this down and pin it on UT is get a message that won't download and use Telnet to manually retrieve it...

If you can do this with a packet capture running even better, it will be required to lock down the bug and fix it.