pop3 timed out

[bench]

One of my clients is reporting that outlook gives an error when checking for e-mail. The error says that the operation timed out waiting for a response from the receiving(pop) server. It's the first time I've seen this happen with gatekeeper and I don't know why it's doing it.

Another client is also reporting that outlook begans to download the e-mails then stops and quits. It does not download anything. I have checked the users folder in the proxy server and he does have over 15 messages of various sizes, one of 2.2 MB.

What could be causing this to happen? How can I prevent it? My client is driving crazy demanding for this not to happen but I don't know where to start. You prompt help would be greatly appreciate it.

Also, I continue to see that other servers are relaying their messages through wingate, mostly from russia. I have open relay checking and about 6 ordb sites to check against but I can't stop the relaying from those servers. Is there any way possible to stop them???

[Nev]

One of my clients is reporting that outlook gives an error when checking for e-mail.

Hi Bench,

Have you looked here --> http://forums.qbik.com/viewtopic.php?t=3195 which hopefully will have some clues!
Otherwise, turn on debug logging for the POP3 Server and wait for the error, which could be posted here in the forum.

Maybe it could look similar to this post --> http://forums.qbik.com/viewtopic.php?t=3567 !

Also, I continue to see that other servers are relaying their messages through wingate,

Now can't help much here, so you have the SMTP server bound to an external adaptor for a reason, maybe the mail server document could be useful or applying authentication to users trying to access the service would be my best guesses here.

Report back and someone will take it further.

[bench]

We had no choice but to switch back to argosoft due to the great deal of problems gatekeeper has. The lack of technical support makes even harder to solve the problems has they are happening for the client.

For unknown reasons wingate mail server would not send to certain domains after having sent to those domains during the first 4 days of operation. Wingate also rejected certain incoming e-mails from users in the same domain. Wingate would not deliver e-mails in users mailboxes, my guess here is because of the infected e-mails. Wingate provides no documentation on how to link antivirus software, symantec for example, to the mail server so it checks e-mails as they come in or go out.

Symantec corporate edition did catch some viruses,mostly in wingate cache, and some in users inbox but I could not delete them because wingate would not allow it.

Last, wingate provides no documentation on how to best setup mail server to block spam or stop spam messages relaying.

We will only use wingate to restrict access for users but no longer as the mail server as it lacks functionality and support.

[jamesc]

Sorry to hear about your email blues; just read it. I just did a search of our support system and cannot find a reference to your email address. Did you create a support ticket for this issue?

[MattP]

Hi Bench,

Do you have your SMTP debug logs showing the mail failures?

Regarding the relaying problem, do you have the allow relay box checked in the receiving menu of the WinGate mail server?

WinGate does not provide plug-in support for Symantec, if you want to link an AV to WinGate you'll need to purchase the Kaspersky AntiVirus for WinGate plug-in, this will then scan your mail (and internet traffic) as it comes into the WinGate server.

Did you read our mail server setup document? You can download it from here, http://www334.pair.com/qbiknz/documents ... ations.pdf