Endpoint Protection Small Business Edition

 View Only
  • 1.  Email error: Your email message was unable to...

    Posted Jun 18, 2012 03:48 AM

    I recently changed email providers and suddenly I started receiving the following (very annoying!) message from Norton 360 when I sent out my statements to 500 customers:

    Email error

    Your email message was unable to be sent because the connectoin to your mail server was interrupted.  Please open your email client and re-send the message from the Sent Messages folder.

    My questions are:

    1. Is this correct - was the email not sent?  I don't see how as it is in my sent folder and I didn't receive a bounce notification.  It literally produced this error for every email that was sent

    2. If it is correct, what can i do about it.  I've been operating for 4 years with no problem until now?

    3. Can I turn this norton feature off?

     

    ps: I can't find norton 360 anywhere on the product list below - but I am using Norton 360

    Thanks

     

    Anton



  • 2.  RE: Email error: Your email message was unable to...

    Trusted Advisor
    Posted Jun 18, 2012 06:12 AM

    Hello,

    Since you are running Norton 360, I would request you to post this Comment on Norton Community:

    http://community.norton.com/t5/Norton-360/bd-p/Norton_360

    Hope that helps!!



  • 3.  RE: Email error: Your email message was unable to...

    Posted Jul 20, 2012 07:57 AM

    Goto Norton Community please.



  • 4.  RE: Email error: Your email message was unable to...

    Posted Jul 27, 2012 09:53 PM

    Follow mithun article plzzzzzzzz



  • 5.  RE: Email error: Your email message was unable to...

    Posted Aug 03, 2012 09:17 AM

    If subject lines and recipients are displayed, examine them to determine if mails were intentionally sent from the mail client.

    If not, isolate the computer from the network and follow best practice to determine if a currently undetected threat is operating on this computer. Checking what program is using common mail ports (performing anetstat -ao from the command line to learn what process is communicating on port 25) is often the best first step.