Critical Errors in the Event Logs?

[undrop79]

We have a Dell Server running W2003 SBS.

Ever since this has been installed at our site, I have always received the same errors in our daily "Server Perfomance Report" which I get emailed with every morning.

At first I though it was because we had a crappy Home Office DSL router which kept disconnecting and reconnecting all the time because it couldn't cope with the number of requests it was getting at one given time.

This has now been replaced by a Cisco 877 DSL router which is working fine and doesnt get disconnected from the internet at all, but I am still getting the same errors?? (The same error gets logged aroung 600 times a day!)

The erors are all to do with the Pop3 Connector.

These were yesterdays errors (total of 454):

96 Total Occurences for each of the following:
1019 - The message download process finished with one or more errors.

1023 - The downloading process for mailbox <user5519 [pop.1and1.co.uk]> was ended with one or more errors.

1029 - Access was denied to the mailbox <pop.1and1.co.uk> logging on as <user5519>. Verify the password for the mailbox account, and try again.

1036 - An error occurred during a POP3 transaction to server <pop.1and1.co.uk [user5519]>. The error is 0 (The operation completed successfully. ).

9 Total Occurences for each of the following:
1053 - The delivery process for message <id: {32F38259-7523-418E-915B-1074EDD1A792}> finished with one or more errors.

1056 - The message <id:{32F38259-7523-418E-915B-1074EDD1A792}> can not be delivered. The error code is: -2147220979.

Can anyone tell me why this may be happening every day??

[Vectorman211]

Are you intentionally running a public POP3 server by chance? Looks to me that someone is attempting to retrieve e-mail as "user 5519". If you are not intentionally running a public POP3 server you should block port 110 on your router access control list. In fact, all inbound ports should be blocked unless you specifically run a service that you want to have accessed outside your LAN.

[undrop79]

Users are able to access their Pop3 mailboxes by using Outlook Web Access. This is a feature I would like to keep.

Is this what you mean by a public POP3 server?

[Vectorman211]

I just got done answering your post on your exchange server lol. I see now what your problem is. You are using exhange to download messages from your external mail server to local exchange MBs. That error is being generated because user5519's credentials are being rejected by your external mail server which I assume is the <pop.1and1.co.uk> address.

OWA (Outlook Web Access) is not POP3 it is HTTP (Web). I would strongly advise against allowing it to be used outside your internal network unless it is served via SSL (HTTPS) as serving in plain text would be detrimental to your account and e-mail security.

[undrop79]

I know! I posted the majority of these messages a while back and nobody replied to them. Now suddenly, you're managing to work you way through... Funny.

Anyway, I can't beleive how I didn't figure this one out for myself. If I'd of just checked to see who user5519 was in our network, I would have solved the problem straight away. It was an employee who left the company. Since they left, I changed the mailbox from my external hosting company to a forwarding account to another mailbox within the company, leaving user5519 mailbox absolete, hence the reason for the POP3 service not being able to access it and coming up with the errors... doh!

Our OWA us served via HTTPS so hopefully this is ok!

Thanks again!!!!

[Vectorman211]

Believe me pal, I've had worse brain farts :D. Sounds like you're all set with OWA as well.

EDIT:
You may want to just double check when you get home that you physically can not access OWA via HTTP, it should not be an option to use HTTPS.

[undrop79]

Thanks for the advice. Will check this when I get home.