Re: Exchange 03 send problem
- From: "kj" <KevinJ.SBS@xxxxxxxxxxxxxxxxxx>
- Date: Tue, 26 Jun 2007 10:24:11 -0700
Lanwench [MVP - Exchange] wrote:
Frank McCallister SBS MVP <anonymous> wrote:
Mailhop Outbound from Dyndns.com will allow you to send on port 2525
if you can receive on port 25. To Test have someone NOT on Bellsouth
(maybe a cable customer) Telnet yourip 25 and see if they connect.
I have used Dyndns for 4 years on port 2525 and never had a message
bounce due to problems on my end.
I can vouch for 'em too. I love dyndns.
All in favor say "ey"
"EY"!
<mrhanman@xxxxxxxxx> wrote in message
news:1182810295.304599.284040@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
thanks for your response. however, authenticating did not solve the
problem. bellsouth's mail servers use anonymous access for users of
their service. also, when i switched it back to anonymous, i can no
longer send email to users at @bellsouth.net
On Jun 25, 4:30 pm, "Lanwench [MVP - Exchange]"
<lanwe...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
mrhan...@xxxxxxxxx wrote:
I've set up a SBS 03 server for a client who has bellsouth
residential (i suggested that they upgraded to business) DSL
service. bellsouth does not allow mail servers on their netowork
(at least no outgoing mail servers) so i have the SMTP connector
set to forward all mail through mail.bellsouth.net. my problem is
that they can only send to email addresses at bellsouth i.e.
@bellsouth.net. all other emails bounce back almost immediately
with this error:
Your message did not reach some or all of the intended recipients.
Subject: test
Sent: 6/25/2007 2:20 PM
The following recipient(s) could not be reached:
x...@xxxxxxxxxxxxxxxxx on 6/25/2007 2:20 PM
There was a SMTP communication problem with the
recipient's email server. Please contact your system
administrator. <server.shexxxxxxorykennels.local #5.5.0
smtp;550 relaying mail to mcxxxxxxxxech.net is not allowed>
You need to authenticate to the SMTP server - find the SBS SMTP
connector in
Exchange system manager, go to its properties/advanced/outbound
security and
enter the valid username/pw there.
i have a POP connector set to fetch their current email from their
bellsouth.net email,
Not related....
and it comes through fine. btw, those are the
email addresses i tested sending to. i know that they are not
going to be able to receive emails on this server until they
upgrade to business DSL (bellsouth blocks port 25), but they
should still be able to send, right? i could be wrong, but if
they can send to x...@xxxxxxxxxxxxx, shouldn't they be able to
send to x...@xxxxxxxxx?
Not unless you're allowed to relay through it - and you will
probably have
to authenticate to the SMTP server to do that.
thanks for your help
--
/kj
.
- Follow-Ups:
- Re: Exchange 03 send problem
- From: Lanwench [MVP - Exchange]
- Re: Exchange 03 send problem
- References:
- Exchange 03 send problem
- From: mrhanman
- Re: Exchange 03 send problem
- From: Lanwench [MVP - Exchange]
- Re: Exchange 03 send problem
- From: mrhanman@xxxxxxxxx
- Re: Exchange 03 send problem
- From: Frank McCallister SBS MVP
- Re: Exchange 03 send problem
- From: Lanwench [MVP - Exchange]
- Exchange 03 send problem
- Prev by Date: Re: GPO causing client security logs to fill?
- Next by Date: Re: Blocking Windows Live Messenger
- Previous by thread: Re: Exchange 03 send problem
- Next by thread: Re: Exchange 03 send problem
- Index(es):
Relevant Pages
|
Loading