Symantec Email Proxy Error 1003,11
Updated: 02 Mar 2009 | 17 comments
Occcasionally, I have a user who receives a pop-up warning about Proxy Error 1003,11 (Your email message was unable to be sent because your mail server rejected the message). The latest such message a user reported also said "250 its ok for <email address of recipient>". That particular message still went through, but sometimes messages don't go through, although they appear to be sent and the message is moved to the user's "Sent" folder.
This is using POP mail, no Exchange server involved. Happens with Outlook 2003 and 2007.
I can't figure a way to prevent the 1003,11 message, or to ensure that the client is always able to send mail. In SEPM, I have disabled email scanning and Outlook protection, but the problem still exists with certain clients. It is possible that attachments may be involved, but I'm not sure if this is true in every case.
We have been using Endpoint Security 11 with about 25 clients for about a month now. Previously, we had been running Symantec Antivirus Corporate Edition, but even as long as a year ago, the problem would occasionally appear.
Discussion Filed Under:
Comments
I am having the same issue does anyone have a resolution.
Apparently no one does. This issue has been going on for years and I've never seen a real answer.
Symantec will say that it's your mail host's fault, that their product is just "relaying the error message". Yet you can't contact your mail host and expect them to fix anything, because they'll tell you it's Symantec's fault and they don't support your software.
Obviously it is an issue, obviously there's a common cause, and obviously there should be a way to fix it. With Endpoint Protection, you can't just "turn off" outgoing email scanning by itself, it's all or nothing. And even if you turn off email scanning COMPLETELY, the issue can still happen. Frankly, I'm getting tired of end users asking about it, and it's things like this that make me want to abandon the product altogether. Very frustrating. I suspect it has something to do with the way Symantec is interpreting the responses from the mail server, or perhaps it's a particular mail server response that is being (mis)interpreted to generate the error on the client side. Or perhaps it's a timeout issue. I don't know. In many cases, the messages still send despite the error. There should be a way to supress these messages if nothing else.
Symantec needs to provide a solution to this problem and not just excuses.
While actually solving the problem would be preferred, I would be somewhat content in the interim if they would give us the ability to go into the configuration settings and turn off checking for outcoming mail but leave it on for incoming mail.
I been having the same issue with Endpoint Security 11. Clients are running Outlook 2002. Message shows up at random. I click the message away and then the users resend the message and it gets sent fine. I read on this forum about changing the outgoing port number to a random non standard port would fix the issue, but the problem still exists.
We recently upgraded to Symantec Endpoint Protection and are having the same issues. For that matter, we have had the same issues after upgrading previous versions of Symantec. The problem is that it is so random. It has happened to me sending mail to internal and external e-mail addresses, with and without attachments. I have even had an e-mail train with the same subject where some go through fine and some get the error. One of the problems is that the messages show up in the sent items, even if they did not go through. It makes it harder to backtrack and re-send the right messages.
Another issue is that the hyperlink on the error message points to a Symantec page with instructions on options we do not have. It sends me here
But I do not have an option to turn off outbound e-mail scanning.
I hope this gets resolved.
I had the same problem and solved it with this free program.
http://www.superantispyware.com/
Solution?
I had the same error 1003,11. It only happend very ocasionally. Disabling email scanning made no difference. The rest of my error said 554, Sorry message looks like spam or phish to me (OP).
Turned out it was my mail server that was the problem. I had to add our internal mail addresses to our whitelist on our spam filter. This solved the problem. Just wanted to add this in case someone else has a similar problem.
Email Proxy Error.
Dear All,
Our also facing the same issue specifically when the email message is sent we get the pop up stating :
"Your email message was unable to be sent because your mail server rejected the message"
this error was seen even since the SAVCE and now in SEP. And the the solution provided by Symantec was to disable the Email Scanning. I hope in SEP atleast there is some different solution.
when this solution was given to the customer they say then which why should symantec provide the Email Sacnner and what if the mail is infected with virus.
Request you all please update me in case anyone is having solution for this.
Regards,
Ranjit
how can we fix this problem?
i have same problem in one client. there is no solition?
Please Help
Best Regards
Everything works better when everything works together.
hi, we faced same issue,
hi,
we faced same issue, however scanning the computer in safe mode with the latest RR resolved the issue. We found couple of threats on that system.
You may try scanning the computer after updating with the latest definition.
Cheers
Pete!
Cheers!
Pete
Help Link: http://www.symantec.com/business/support/overview.jsp?pid=54619
thank you for answer
Thank you for answer. This client is in another city. i shutdown it. and i said my friend and he will do full system scan tomorrow. If it will be solved only scan i will write again. Does symantec have a removal tool for spyware? and i asked to myself this client have last virus definition but how can be infected? and why SEP cannot fix this problem? Should we buy another program from Symantec about spyware?
Everything works better when everything works together.
hi, this is based on my
hi,
this is based on my experience. The system point at that moment were not known to us, hence cannot say why it could not detect. We ran RR on the computer.
Pete!
Cheers!
Pete
Help Link: http://www.symantec.com/business/support/overview.jsp?pid=54619
error massage
threre is some problem in anti visus of symantec of massage error please soloution
I also having same issue How
I also having same issue How to troubleshoot this error......?
How to resolve this
Can anybody suggest me to resolve this issue
am getting this popup continuously. My desktop is filling with this popup
for temperoraly am able to stop this by end tasking but it is comming again.
Hi
try this
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2010011410001948
If this Info helps to resolve the issue please Mark as Solution
Thanks
Hi
Also
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2009031811513448
If this Info helps to resolve the issue please Mark as Solution
Thanks
Would you like to reply?
Login or Register to post your comment.