SBS2003 Exchange SMTP Connector and SSL

[mrce...@gmail.com]

Hello,

I'm been using the SMTP connector to forward all mail through my ISP's
mail servers for the past few years. This has worked great for me as
I am on a dynamic IP and sending mail directly from my server caused
most of my mail to get stopped by anti-spam filters.

Unfortunately, AT&T recently sent me an email stating that they will
be requiring SSL for all POP and SMTP connections starting in August.

I've searched for solutions on how to enable SSL with the connector,
but have come up empty.

Does anyone know of a way to continue to be able to forward my mail
through an SSL connection to my ISP like I have been for years w/ the
connector? Are there any third party solutions? Or will I need to
purchase in a static IP in order to continue to use my Exchange
server?

Thanks for any help,
Mike

[Dan Walker]

Mike,

Third party email solutions are my preference, TZO http://www.tzo.com),
DYNDns. (http://www.dyndns.com/) I use TZO. and have had no problems.

Another solution can be found in KB Articles 265293, 312411 and 274842.
The last article explains how to change listening port on the exchange
server, possibility port 443, your ISP will tell you.

TZO mail fowarding is my solution, although I have worked with a company
that successfully employed the SMTP Connector method.

Either way presents no great obstacles.

Dan

<mrce...@gmail.com> wrote in message
news:1178488035.4...@n59g2000hsh.googlegroups.com...

[mrce...@gmail.com]

Hello again,

Thanks for the info Dan.

I currently use No-IP.com for my dynamic DNS. They have something
called Alternate-port SMTP (http://www.no-ip.com/services/managed_mail/
outbound_port_25_unblock.html). Is this like what you use through
tzo.com? From no-ip's explaination, does it apear their service could
be a solution? I submitted a ticket for some more information from
them.

I took a look at those KB articles, but none of them seem to address
my issue. Most of it seems to pertain to Exchange's SMTP Server. As
you may or may not know, the Exchange SMTP Connector allows the
Exchange server to send all email to another SMTP server for delivery
as if it were an email client, versus sending the email directly to
the receiving email server. You supply a SMTP server and login
credentials just like you do when setting up a SMTP/POP account in
Outlook or any other email client. The advantage of this is that the
destination email servers will see my ISPs SMTP server as the sending
email server, and not my server which is on a dynamic IP block (which
is an anti-spam trigger). Do ya know what I'm sayin'?

So regardless of how I setup Exchange's SMTP server, I do not believe
it will change how the SMTP Connector communicates with my ISPs SMTP
server. I basically need the options that are in Outlook regarding
incoming and outgoing port numbers and SSL, but they apparently aren't
there.

Any other suggestions? Anyone? I don't suppose there are any plans
for a new and improved Exchange SMTP Conenctor anytime soon...

Thanks again,
Mike

[rju166]

MS basically sold you and me up the river. They have an SMTP connector that
doesn't work and they won't update it. And if you use the recommended SMTP
server it gets blocked by anti-spammers. So what are you supposed to do?

Yes, I'm pissed off about this. You would think MS would back up its own
customers. You would think using MS products would be a guarantee that the
product works. But apparently not.

<mrce...@gmail.com> wrote in message
news:1178584386.7...@l77g2000hsb.googlegroups.com...