Jump to content

Update Thurs 3/22 - #1


Recommended Posts

We are aware of the following two issues and are working on them:

1) POP is generating unknown error:10 errors

2) mx.spamcop.net is not working; mx2.spamcop.net is working and well configured sending servers should always fall back to the secondary MX entry if the higher priority MX is not working.

Link to comment
Share on other sites

We are aware of the following two issues and are working on them:

1) POP is generating unknown error:10 errors

2) mx.spamcop.net is not working; mx2.spamcop.net is working and well configured sending servers should always fall back to the secondary MX entry if the higher priority MX is not working.

Have you any estimate for how long it's likely to take to fix the POP issue? It's been broken for well over 24h now.

Thanks,

Chris

Link to comment
Share on other sites

I sure wish I knew the answer :-(

Mines never stopped?

settings POP

Username login

password

pop.spamcop.net

port 110

Send

smtp.cesmail.net

psword same as POP

port 587

Link to comment
Share on other sites

Petzl, that's not the same POP that they were talking about here. There were problems with the automated POP retrieval that the SC email server does to retrieve messages from third-party systems, not with the ability to POP mail from SC to a local email client.

DT

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...