Re: Why is e-mail being rejected when sending to an external domai
- From: "Ace Fekay [MVP]" <PleaseAskMe@xxxxxxxxxxxxxx>
- Date: Fri, 1 Jun 2007 06:57:51 -0400
In news:86903E3A-871B-432A-AB19-5B0BE3B9E1F1@xxxxxxxxxxxxx,
AD <AD@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Our user is using Exchange and the client is Outlook 2003. We
recently switched our Exchange server to a colo so the IP for our
mail server has changed. It's not a POP or IMAP account. It's an
SMTP account. No it does not allow relaying. It's closed off to
open relaying. The user at our company used to be able to send to
the user at the external domain; however, since we moved changed the
public IP to our mail server the user at our company has been unable
to send messages to the external user. I'm assuming this is some
sort of DNS issue somewhere, but I can't figure out what it would be
or where to start looking.
"it is usually an error where the client is trying to send it out
directly using SMTP and is trying to relay."
How would I be able to find out if this is the problem? I'm not a DNS
expert and I'm very new to it so I'm not sure where I would start
looking. Would it be under properties of the SMTP virtual server?
If Outlook is configured as an SMTP account, then you've actually configured
Outlook for either POP or IMAP. If the users have all their folders, then
it's IMAP, otherwise if just the inbox, it's POP. POP3 and IMAP4 are
'retrieval' protocols. SMTP is a sending protocol. Both types actually use
SMTP to send mail. Therefore to me it is a RELAY problem. Set the users in
the POP or IMAP properties to authenticate when sending mail. By default
Exchange will allow to relay mail if authenticated.
Ace
.
- Prev by Date: Re: add server to dns
- Next by Date: Re: Can anyone help me with this?
- Previous by thread: Re: add server to dns
- Next by thread: Re: Virtual hosting...
- Index(es):
Relevant Pages
|
Loading