D
DanBeadle
I have Outlook 2003 with SP2 installed. I use it to get mail from a local
exchange server. I also access 2 pop3 accounts with it.
Recently, without changes on my end, I have been getting an error message on
replying to mail from either Pop3 account:
"503 This mail server requires authentication when attempting to
send to a non-local e-mail address. Please check your mail client settings or
contact your administrator to verify that the domain or address is defined
for this server."
I had the account set up with "Outbound Server requires Authentication".
The outbound server is correct.
I looked at the trace of the SMTP session. It is starting up the session
with the pop3 server (at my domain). Instead of using my server login in,
which is in the format of (e-mail address removed), it uses my machine name,
dan2 as the EHLO user. It doesn't seem to issue user/pw logon.
I tried clicking the button - log on to pop3 server before sending. The
behavior doesn't seem to be any different when viewed with a network analyser.
I tried outlook express on a Server2000 product and it does work just fine -
logging into pop3 first, then sending.
My failing desktop also uses Symantec Antivirus and email scanning is turned
on.
Like I say, it was working. So this could be a result of changes on the
outsourced pop3 server, or to auto-updates applied by either MS or Symantec.
Any suggestions would be appreciated.
Dan
exchange server. I also access 2 pop3 accounts with it.
Recently, without changes on my end, I have been getting an error message on
replying to mail from either Pop3 account:
"503 This mail server requires authentication when attempting to
send to a non-local e-mail address. Please check your mail client settings or
contact your administrator to verify that the domain or address is defined
for this server."
I had the account set up with "Outbound Server requires Authentication".
The outbound server is correct.
I looked at the trace of the SMTP session. It is starting up the session
with the pop3 server (at my domain). Instead of using my server login in,
which is in the format of (e-mail address removed), it uses my machine name,
dan2 as the EHLO user. It doesn't seem to issue user/pw logon.
I tried clicking the button - log on to pop3 server before sending. The
behavior doesn't seem to be any different when viewed with a network analyser.
I tried outlook express on a Server2000 product and it does work just fine -
logging into pop3 first, then sending.
My failing desktop also uses Symantec Antivirus and email scanning is turned
on.
Like I say, it was working. So this could be a result of changes on the
outsourced pop3 server, or to auto-updates applied by either MS or Symantec.
Any suggestions would be appreciated.
Dan