NTLWorld SMTP Problem-E-mail outage??
 

Hi

I use outlook express and can receive mail fine on all my accounts but
am unable to send on any via the smtp.ntlworld.com server.
So I can get mail through the pop3 but nothing through the smtp

NTL support couldnt help and the "service status" is not very informative

Error message as follows:

An unknown error has occurred. Subject 'Re: test fron ntl', Account: 'Carpman NI', Server: 'smtp.ntlworld.com', Protocol: SMTP, Server Response: '452 Message rejected', Port: 25, Secure(SSL): No, Server Error: 452, Error Number: 0x800CCC6C

Tried everything I know(been using this stuff for about 3years without any major problems)disabled all my virus and firewall stuff,reset router n times and topbox n times?

Could be something subtle at the PC end(ie through updates?) but I am pretty sure the problem is at the NTL end of things?

I can access/send fine through the NTL website or mail2web etc but no joy using outlook or outlook express.

Thanks in advance for any help

Chris

Re: NTLWorld SMTP Problem-E-mail outage??
 

Have you checked your settings in Outlook Express/ Outlook? Sometimes if your email address and the reply to addresses do not match you get a server error.
Also make sure you are clean of virus, spyware and trojans as that error can occur if the email servers think you are trying to relay spam or have a trojan that is trying to send spam.
It could also be that the email server is down again.

Re: NTLWorld SMTP Problem-E-mail outage??
 

I'm getting the same problems (on two different computers), and have been since early yesterday. Same error message. I downloaded a free SMTP server to run on my laptop, and my mail is being sent via that, NOT NTL.
I believe that one or more email servers is/are banjaxed. :mad:

Re: NTLWorld SMTP Problem-E-mail outage??
 

Wouldn't be the first time that NTL's mail servers have hit issues ;)

Re: NTLWorld SMTP Problem-E-mail outage??
 

Hi Chris,

You've already posted about this issue here: http://www.cableforum.co.uk/board/sh...577#post488577

There's no need for duplicate threads, so I'll close this one & let the other run.