Re: Exchange smarthost for SBC ADSL users
- From: "Justin - synacs" <jcbrown@xxxxxxxxx>
- Date: 18 Aug 2006 12:05:17 -0700
1.
I haven't looked at their phone bill, but it seems like residential
grade service at their business address. I agree a static IP would be
ideal, and that's probably what we'll end up doing, set them up the
right way. This client is "on a budget" but so is everybody, right?
2.
I thought No IP was in fact a Dynamic DNS service. Maybe I'm wrong
there. The reason for the second connector is that I didn't want the
smarthost to dictate the maximum recipients figure, which is I believe
around 30 at the present. That's when they send from Outlook directly
to the ISP SMTP server.
I used their original username/password in attempting the smarthost
connector. The SBC mail server allows us to login as
"company@xxxxxxxxxxxxx" and send e-mails as "user@xxxxxxxxxxx", and I
was trying to extend that functionality to the connector.
Cris Hanna (SBS-MVP) wrote:
you should be looking at a couple of options
1. Moving to a static IP. Would I be correct in assuming you are using SBC's residential DSL service for your SBS network?? If thats the case are you aware that you are probably in violation of their terms of service? Most Cable/DSL providers specifically prohibit running email and webservers on their networks.
2. Look at a true Dynamic DNS solution. TZO.org or DynDNS.org. That way you can have the correct DNS records
Without seeing the specific's of your setup, There may be issues with the second connector or the first and second may not be interacting correctly...not sure.
Why not send everything through one connector?
Are you trying to use multiple user names and passwords for the smarthost?
--
Cris Hanna [SBS-MVP]
--------------------------------------
Please do not respond directly to me, but only post in the newsgroup so all can take advantage
"Justin - synacs" <jcbrown@xxxxxxxxx> wrote in message news:1155919201.781140.277860@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for your reply, Cris.
The dynamic IP address prevents us from using PTR and SPF records.
Unless there is a 3rd party solution to this. We did use a 3rd party
(No IP) that resolves a generic company.no-ip.com host name to the
public IP address, and then we have a CNAME/alias that resolves
internal.company.com to company.no-ip.com. This makes RWW available
consistently, which is great.
About the smarthost, yes I used their username@xxxxxxxxxxxxx and
password via basic authentication. I re-entered that several times,
thinking I must have mistyped the password. The same logon works in
Outlook, with standard port 25 and no SPA/TLS.
Cris Hanna (SBS-MVP) wrote:
> what prevents you from creating the PTR/Reverse DNS and SPF records
>
> Are you saying that SBC Global is the smart host? Are you supplying the user name and password for the account being used to send mail out?
>
> --
> Cris Hanna [SBS-MVP]
> --------------------------------------
> Please do not respond directly to me, but only post in the newsgroup so all can take advantage
> "Justin - synacs" <jcbrown@xxxxxxxxx> wrote in message news:1155916716.784888.302770@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> The SMTP server in question is the one used in Outlook, in order to get
> outgoing mail from the sender to the recipient.
>
> This same server, when entered as a smart host, does not forward mail
> to its recipient. It appears to blackhole every e-mail, as the messages
> leave the Outlook client and wind up in Sent Items. They also appear to
> leave the Exchange server, as they can't be found in the Message
> Tracking Center in ESM. However, no matter what the domain, they are
> not delivered to the external recipient. No Non-Delivery Report is seen
> by the sender.
>
> Has anyone made the smarthost work on SBC? Routing via DNS works for
> some domains, but since we can't implemenet a PTR record, they are
> bound to have problems with AOL and comcast addresses. Not to mention
> sbcglobal.
>
> ------=_NextPart_000_07BC_01C6C2B6.13916550
> Content-Type: text/html; charset=iso-8859-1
> Content-Transfer-Encoding: quoted-printable
> X-Google-AttachSize: 2159
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
> <META content="MSHTML 6.00.2900.2963" name=GENERATOR>
> <STYLE></STYLE>
> </HEAD>
> <BODY bgColor=#ffffff>
> <DIV><FONT face=Arial size=2>what prevents you from creating the PTR/Reverse DNS
> and SPF records</FONT></DIV>
> <DIV><FONT face=Arial size=2></FONT> </DIV>
> <DIV><FONT face=Arial size=2>Are you saying that SBC Global is the smart
> host? Are you supplying the user name and password for the account
> being used to send mail out?</FONT></DIV>
> <DIV><BR>-- <BR>Cris Hanna
> [SBS-MVP]<BR>--------------------------------------<BR>Please do not respond
> directly to me, but only post in the newsgroup so all can take advantage</DIV>
> <BLOCKQUOTE
> style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Justin - synacs" <<A
> href="mailto:jcbrown@xxxxxxxxx";>jcbrown@xxxxxxxxx</A>> wrote in message <A
> href="news:1155916716.784888.302770@xxxxxxxxxxxxxxxxxxxxxxxxxxxx";>news:1155916716.784888.302770@xxxxxxxxxxxxxxxxxxxxxxxxxxxx</A>...</DIV>The
> SMTP server in question is the one used in Outlook, in order to
> get<BR>outgoing mail from the sender to the recipient.<BR><BR>This same
> server, when entered as a smart host, does not forward mail<BR>to its
> recipient. It appears to blackhole every e-mail, as the messages<BR>leave the
> Outlook client and wind up in Sent Items. They also appear to<BR>leave the
> Exchange server, as they can't be found in the Message<BR>Tracking Center in
> ESM. However, no matter what the domain, they are<BR>not delivered to the
> external recipient. No Non-Delivery Report is seen<BR>by the
> sender.<BR><BR>Has anyone made the smarthost work on SBC? Routing via DNS
> works for<BR>some domains, but since we can't implemenet a PTR record, they
> are<BR>bound to have problems with AOL and comcast addresses. Not to
> mention<BR>sbcglobal.<BR></BLOCKQUOTE></BODY></HTML>
>
> ------=_NextPart_000_07BC_01C6C2B6.13916550--
------=_NextPart_000_08B9_01C6C2C6.1F91F490
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Google-AttachSize: 8605
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2963" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>you should be looking at a couple of
options</FONT></DIV>
<DIV><FONT face=Arial size=2>1. Moving to a static IP. Would I be
correct in assuming you are using SBC's residential DSL service for your SBS
network?? If thats the case are you aware that you are probably in
violation of their terms of service? Most Cable/DSL providers
specifically prohibit running email and webservers on their
networks.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>2. Look at a true Dynamic DNS solution.
TZO.org or DynDNS.org. That way you can
have the correct DNS records</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Without seeing the specific's of your setup, There
may be issues with the second connector or the first and second may not be
interacting correctly...not sure.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Why not send everything through one
connector?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Are you trying to use multiple user names and
passwords for the smarthost?</FONT></DIV>
<DIV><BR>-- <BR>Cris Hanna
[SBS-MVP]<BR>--------------------------------------<BR>Please do not respond
directly to me, but only post in the newsgroup so all can take advantage</DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Justin - synacs" <<A
href="mailto:jcbrown@xxxxxxxxx";>jcbrown@xxxxxxxxx</A>> wrote in message <A
href="news:1155919201.781140.277860@xxxxxxxxxxxxxxxxxxxxxxxxxxxx";>news:1155919201.781140.277860@xxxxxxxxxxxxxxxxxxxxxxxxxxxx</A>...</DIV>Thanks
for your reply, Cris.<BR><BR>The dynamic IP address prevents us from using PTR
and SPF records.<BR>Unless there is a 3rd party solution to this. We did
use a 3rd party<BR>(No IP) that resolves a generic company.no-ip.com host name
to the<BR>public IP address, and then we have a CNAME/alias that
resolves<BR>internal.company.com to company.no-ip.com. This makes RWW
available<BR>consistently, which is great.<BR><BR>About the smarthost, yes I
used their <A href="mailto:username@xxxxxxxxxxxxx";>username@xxxxxxxxxxxxx</A>
and<BR>password via basic authentication. I re-entered that several
times,<BR>thinking I must have mistyped the password. The same logon works
in<BR>Outlook, with standard port 25 and no
SPA/TLS.<BR><BR><BR><BR><BR><BR>Cris Hanna (SBS-MVP) wrote:<BR>> what
prevents you from creating the PTR/Reverse DNS and SPF records<BR>><BR>>
Are you saying that SBC Global is the smart host? Are you
supplying the user name and password for the account being used to send mail
out?<BR>><BR>> --<BR>> Cris Hanna [SBS-MVP]<BR>>
--------------------------------------<BR>> Please do not respond directly
to me, but only post in the newsgroup so all can take
advantage<BR>> "Justin - synacs" <<A
href="mailto:jcbrown@xxxxxxxxx";>jcbrown@xxxxxxxxx</A>> wrote in message <A
href="news:1155916716.784888.302770@xxxxxxxxxxxxxxxxxxxxxxxxxxxx";>news:1155916716.784888.302770@xxxxxxxxxxxxxxxxxxxxxxxxxxxx</A>...<BR>>
The SMTP server in question is the one used in Outlook, in order to
get<BR>> outgoing mail from the sender to the
recipient.<BR>><BR>> This same server, when entered as a
smart host, does not forward mail<BR>> to its recipient. It
appears to blackhole every e-mail, as the messages<BR>> leave
the Outlook client and wind up in Sent Items. They also appear
to<BR>> leave the Exchange server, as they can't be found in
the Message<BR>> Tracking Center in ESM. However, no matter
what the domain, they are<BR>> not delivered to the external
recipient. No Non-Delivery Report is seen<BR>> by the
sender.<BR>><BR>> Has anyone made the smarthost work on SBC?
Routing via DNS works for<BR>> some domains, but since we can't
implemenet a PTR record, they are<BR>> bound to have problems
with AOL and comcast addresses. Not to mention<BR>>
sbcglobal.<BR>><BR>> ------=_NextPart_000_07BC_01C6C2B6.13916550<BR>>
Content-Type: text/html; charset=iso-8859-1<BR>> Content-Transfer-Encoding:
quoted-printable<BR>> X-Google-AttachSize: 2159<BR>><BR>>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><BR>>
<HTML><HEAD><BR>> <META http-equiv=Content-Type
content="text/html; charset=iso-8859-1"><BR>> <META content="MSHTML
6.00.2900.2963" name=GENERATOR><BR>> <STYLE></STYLE><BR>>
</HEAD><BR>> <BODY bgColor=#ffffff><BR>> <DIV><FONT
face=Arial size=2>what prevents you from creating the PTR/Reverse
DNS<BR>> and SPF records</FONT></DIV><BR>>
<DIV><FONT face=Arial
size=2></FONT>&nbsp;</DIV><BR>> <DIV><FONT
face=Arial size=2>Are you saying that SBC Global is the smart<BR>>
host?&nbsp;&nbsp; Are you supplying the user name and password for the
account<BR>> being used to send mail out?</FONT></DIV><BR>>
<DIV><BR>-- <BR>Cris Hanna<BR>>
[SBS-MVP]<BR>--------------------------------------<BR>Please do
not respond<BR>> directly to me, but only post in the newsgroup so all can
take advantage</DIV><BR>> <BLOCKQUOTE<BR>>
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT:
#000000 2px solid; MARGIN-RIGHT: 0px"><BR>>
<DIV>"Justin - synacs" &lt;<A<BR>> href="<A
href='mailto:jcbrown@xxxxxxxxx";>jcbrown@xxxxxxxxx</A>&gt'>mailto:jcbrown@xxxxxxxxx">jcbrown@xxxxxxxxx</A>&gt</A>;
wrote in message <A<BR>> href="<A
href='news:1155916716.784888.302770@xxxxxxxxxxxxxxxxxxxxxxxxxxxx";>news:1155916716.784888.302770@xxxxxxxxxxxxxxxxxxxxxxxxxxxx</A>...</DIV>The'>news:1155916716.784888.302770@xxxxxxxxxxxxxxxxxxxxxxxxxxxx">news:1155916716.784888.302770@xxxxxxxxxxxxxxxxxxxxxxxxxxxx</A>...</DIV>The</A><BR>>
SMTP server in question is the one used in Outlook, in order
to<BR>> get<BR>outgoing mail from the sender to the
recipient.<BR><BR>This same<BR>> server, when
entered as a smart host, does not forward mail<BR>to
its<BR>> recipient. It appears to blackhole every e-mail, as
the messages<BR>leave the<BR>> Outlook client and wind up
in Sent Items. They also appear to<BR>leave the<BR>>
Exchange server, as they can't be found in the Message<BR>Tracking
Center in<BR>> ESM. However, no matter what the domain, they
are<BR>not delivered to the<BR>> external recipient. No
Non-Delivery Report is seen<BR>by the<BR>>
sender.<BR><BR>Has anyone made the smarthost work on SBC? Routing
via DNS<BR>> works for<BR>some domains, but since we
can't implemenet a PTR record, they<BR>> are<BR>bound to
have problems with AOL and comcast addresses. Not to<BR>>
mention<BR>sbcglobal.<BR></BLOCKQUOTE></BODY></HTML><BR>>
<BR>>
------=_NextPart_000_07BC_01C6C2B6.13916550--<BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_08B9_01C6C2C6.1F91F490--
.
- Follow-Ups:
- Re: Exchange smarthost for SBC ADSL users
- From: Owen Williams [SBS MVP]
- Re: Exchange smarthost for SBC ADSL users
- From: Cris Hanna \(SBS-MVP\)
- Re: Exchange smarthost for SBC ADSL users
- References:
- Exchange smarthost for SBC ADSL users
- From: Justin - synacs
- Re: Exchange smarthost for SBC ADSL users
- From: Cris Hanna \(SBS-MVP\)
- Re: Exchange smarthost for SBC ADSL users
- From: Justin - synacs
- Re: Exchange smarthost for SBC ADSL users
- From: Cris Hanna \(SBS-MVP\)
- Exchange smarthost for SBC ADSL users
- Prev by Date: Re: SBS - Exchnage over RPC
- Next by Date: Re: SCSI Question
- Previous by thread: Re: Exchange smarthost for SBC ADSL users
- Next by thread: Re: Exchange smarthost for SBC ADSL users
- Index(es):
Relevant Pages
|
