Re: I need a better understanding of SBS Internet Email Smarthost, pop3 etc



I am ok with calling your mail from the ISP with the Exchange Pop3 connector
if that is the only way you are going to get it, but you have a bigger
problem with sending mail. As I understand this, you essentially have no
"smart host", and can't send via SMTP - DNS because of your dynamic ip
address.

I am even ok with your not using exchange and just using OL or OLE or
Windows Mail and not even installing Exchange on your SBS. If you are a one
person company you won't notice the difference.

Your problem seems to be that you want all the cake, and you want to eat the
cake, and you still want to have all the cake. You want to use a service
that prohibits the kind of activity you are proposing to do/generate, and be
devious and find a "work around". Well, I don't think you can. What you
can do, and this might be the only way, is to get one of the dynamic to
static services and take your chances. Unless you plan to mass email, I
don't think Verizon will really care if you send out 10 messages per day
using SMTP / DNS.

And if you do get warned / caught / banned, it will be because you are
attempting to do something you said you would not do when you signed the
terms of service agreement.

Others may have different advice, but there is no "get out of jail free"
card in this game.

--
Larry

Please post the resolution to
your issue so that all can benefit.


"Roveer" <roveer@xxxxxxxxx> wrote in message
news:25aa86f8-d129-47f7-a28b-babf0007413b@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I just configured my SBS box (not yet in production) to send/receive
email via pop3 accounts that I have hosted at my domain name
registrar. I decided to do this for a number of reasons. I'm going
to list the reasons and I'd like to see if there are better ways of
doing this.


1. I need name@xxxxxxxxxxxx not verizon.com etc.
2. ISP is Verizon FIOS that will not allow hosting on a residential
service
3. IP is Dynamic, Static is business class (see below)
4. I've "heard" there are blacklists for residential IP addr's that
would cause trouble with mail delivery

As a result I got a bunch of mailboxes from Network Solutions
(actually a web hosting package which had 500 mailboxes and a couple
of gigs of web space). I'll either move my website in the future or
just use the on-line space for backup either way on a 5 year
agreement it was very inexpensive (375 bucks total)

I set up SBS to send/receive mail through these pop3 accounts using
the required port 2525 so there's no blocking issues. I'm told by NS
that I can add SSL that would give even better security since I've
always been a bit peeved about most everything going clear text for
SMTP.

Now, I've posted a few times for help and I've been getting a lot of
replies that they don't know why I'm even trying to do this. This
brings me to believe I've done something terribly wrong, that's why
I'm posting for your comments.

My decision to do this was based on the following:

1. Verizon doesn't want most hosting exchange in their network.
Eventually they might boot me if they were to
look at the traffic
2. Who's going to let me "relay" through their SMTP, AND host my
domain name at their SMTP (this is where I
think I might have gone wrong. I keep hearing about using DYDNS
to forward. And if there is such a service, how reliable is it? My e-
mail is small business, but it's still important. Dont' want to find
that a company stopped a "free service" Don't think Network Solutions
is going anywhere.

3. If I went to Business class FIOS it would cost a whole bunch more
for half the speed and break all my bundle pricing (do you know how
long it took me to finally get it straightened out with Verizon, some
of you probably do)

So help me understand if I've done something wrong. Like I mentioned
before, nothing is in production yet, NS has 30 day money back on the
web hosting so I'm not really out anything if I decide to go another
direction. Based on all the reading I've done, and some discussion it
seemed like the way to go, but I'm all ears for the discussion.

Thanks and I look forward to the replies.




.



Relevant Pages

  • Re: Exchange emails not visible at client computer
    ... pop3 is for incoming mail only, you don't use it for outgoing mail. ... So we use their pipex smtp settings to send mail. ... So without exchange in the frame, we have two accounts setup that are used ... see the mails disappearing from the pop3 server as i collect them. ...
    (microsoft.public.windows.server.sbs)
  • RE: POP3 Connector: Multiple Accounts to one Exchange Mailbox
    ... This issue may occur when the Windows Small Business Server 2003 Connector ... You may experience this issue when you configure a POP3 ... account with a domain that is outside your Exchange organization. ... SMTP address in the Exchange default recipient policy. ...
    (microsoft.public.windows.server.sbs)
  • Re: Problems with BCC in SBS-Exchange 2003
    ... Looks like a weekend at work switching our Pop to SMTP ... The final answer is that when the POP3 protocol is used for multiple ... this type of header. ... I gave up on the Exchange POP3 connector within ...
    (microsoft.public.windows.server.sbs)
  • Re: POP3 email without the connector
    ... When you join these pcs to the domain all outlook settings will be gone, ... POP3 is not for a business environment, doesn't support BCC, clear text passwords over internet and if implement exchange IMF pop3 isn't supported. ... SMTP is the business solution, or 3rd party pop3, GFI Mailessentials or popbeamer. ...
    (microsoft.public.windows.server.sbs)
  • RE: Cant send or receive e-mail to POP3 users on same domain--HELP!
    ... Run the CEICW and go through the Internet and firewall option. ... If you choose to forward emails to the ISP's email server (smart ... Connector for POP3 Mailboxes' option, ... The Mailbox type is User Mailbox, and select the appropriate Exchange ...
    (microsoft.public.windows.server.sbs)