Re: ISP Blocked Port 25-SMTP Issue--HELP!

Is this a business class Verizon account as on residential service port 25
is typically blocked and your TOS doesn't allow you to run a mail or other
servers? POP3 is usually using port 110.

"PorBar" <> wrote in message
news:595021d9-7e3f-4736-8eb7-...
> We have SBS2000 with Exchange 2000 Server -we had no email issues
> until our ISP, Verizon, started blocking port 25. We use a smart host-
> AuthSMTP to send mail from our 3 domains. When Verizon blocked port
> 25, we could still receive mail with our POP3 Connector, but we could
> not send. Makes sense sense SMTP Connector uses port 25.
>
> So, per instructions from AuthSMTP, we changed the SMTP port to 2525.
> We could then send mail, however we could not longer receive. The mail
> comes into Exchange ok - we see messages in the POP3-Inforward folder
> - but does not get delivered to the Exchange Outlook clients until we
> change the port back to #25.
>
> 1. What is the relationship of the Exchange Delivery Service/POP3
> connector and port 25? We cannot find anywhere else to change port 25
> to port 2525.
>
> We think we need to setup either an additional SMTP connector, SMTP
> Virtual Server, or both. We attempted to start doing this and became
> confused/concerned as to which Exchange would use, etc.
>
> Thanks

I'll be short and sweet. Verizon is becoming more strict about enforcing
and *checking* traffic. We could help you create a second connector and
then Verizon will terminate your account for using it in a manner blatantly
forbidden in their TOS. That is a lot of work for nothing.

So, in short? I'd strongly urge you to stop trying to circumvent a
technical limitation as it'll be a stop-gap measure and could have drastic
ramifications on your business. Better to move to a business-class
connection now.

....and, as a complete tangent, ditch pop3. Once you have a good business
connection with port 25 unblocked, you can (and should) have email delivered
to your exchange server directly. The pop3 connector is not intended as a
long-term solution.

-Cliff


"PorBar" <> wrote in message
news:8bf59f01-268d-4525-8048-...
> On Oct 29, 1:54 pm, "SteveB" <newsgr...@public.lan> wrote:
>> Is this a business class Verizon account as on residential service port
>> 25
>> is typically blocked and your TOS doesn't allow you to run a mail or
>> other
>> servers? POP3 is usually using port 110.
>>
>> "PorBar" <compsos...@gmail.com> wrote in message
>>
>> news:595021d9-7e3f-4736-8eb7-...
>>
>> > We have SBS2000 with Exchange 2000 Server -we had no email issues
>> > until our ISP, Verizon, started blocking port 25. We use a smart host-
>> > AuthSMTP to send mail from our 3 domains. When Verizon blocked port
>> > 25, we could still receive mail with our POP3 Connector, but we could
>> > not send. Makes sense sense SMTP Connector uses port 25.
>>
>> > So, per instructions from AuthSMTP, we changed the SMTP port to 2525.
>> > We could then send mail, however we could not longer receive. The mail
>> > comes into Exchange ok - we see messages in the POP3-Inforward folder
>> > - but does not get delivered to the Exchange Outlook clients until we
>> > change the port back to #25.
>>
>> > 1. What is the relationship of the Exchange Delivery Service/POP3
>> > connector and port 25? We cannot find anywhere else to change port 25
>> > to port 2525.
>>
>> > We think we need to setup either an additional SMTP connector, SMTP
>> > Virtual Server, or both. We attempted to start doing this and became
>> > confused/concerned as to which Exchange would use, etc.
>>
>> > Thanks
>
> This is a residential service, business service not offered here by
> Verizon. Port 25 just started being blocked by Verizon this week. Yes
> POP uses port 110 and the mail does come into the Exchange Server. It
> just will not go to the Outlook clients.
>
> Since we have 3 company domain names, we have always used AuthSMTP as
> smarthost with the default SMTP connection settings to send mail.
>
> The problem seems to be that the Exchange Delivery Service listens on
> port 25??? We need it to listen on port 2525 for POP3 mail to go to
> clients --guessing here?

Cliff while I agree with you the OP said Verizon doesn't offer business
class service at his location. I think he needs to look at other
alternatives such as business class cable or even some T1 provider.

"Cliff Galiher" <> wrote in message
news:...
> I'll be short and sweet. Verizon is becoming more strict about enforcing
> and *checking* traffic. We could help you create a second connector and
> then Verizon will terminate your account for using it in a manner
> blatantly forbidden in their TOS. That is a lot of work for nothing.
>
> So, in short? I'd strongly urge you to stop trying to circumvent a
> technical limitation as it'll be a stop-gap measure and could have drastic
> ramifications on your business. Better to move to a business-class
> connection now.
>
> ...and, as a complete tangent, ditch pop3. Once you have a good business
> connection with port 25 unblocked, you can (and should) have email
> delivered to your exchange server directly. The pop3 connector is not
> intended as a long-term solution.
>
> -Cliff
>
>
> "PorBar" <> wrote in message
> news:8bf59f01-268d-4525-8048-...
>> On Oct 29, 1:54 pm, "SteveB" <newsgr...@public.lan> wrote:
>>> Is this a business class Verizon account as on residential service port
>>> 25
>>> is typically blocked and your TOS doesn't allow you to run a mail or
>>> other
>>> servers? POP3 is usually using port 110.
>>>
>>> "PorBar" <compsos...@gmail.com> wrote in message
>>>
>>> news:595021d9-7e3f-4736-8eb7-...
>>>
>>> > We have SBS2000 with Exchange 2000 Server -we had no email issues
>>> > until our ISP, Verizon, started blocking port 25. We use a smart host-
>>> > AuthSMTP to send mail from our 3 domains. When Verizon blocked port
>>> > 25, we could still receive mail with our POP3 Connector, but we could
>>> > not send. Makes sense sense SMTP Connector uses port 25.
>>>
>>> > So, per instructions from AuthSMTP, we changed the SMTP port to 2525.
>>> > We could then send mail, however we could not longer receive. The mail
>>> > comes into Exchange ok - we see messages in the POP3-Inforward folder
>>> > - but does not get delivered to the Exchange Outlook clients until we
>>> > change the port back to #25.
>>>
>>> > 1. What is the relationship of the Exchange Delivery Service/POP3
>>> > connector and port 25? We cannot find anywhere else to change port 25
>>> > to port 2525.
>>>
>>> > We think we need to setup either an additional SMTP connector, SMTP
>>> > Virtual Server, or both. We attempted to start doing this and became
>>> > confused/concerned as to which Exchange would use, etc.
>>>
>>> > Thanks
>>
>> This is a residential service, business service not offered here by
>> Verizon. Port 25 just started being blocked by Verizon this week. Yes
>> POP uses port 110 and the mail does come into the Exchange Server. It
>> just will not go to the Outlook clients.
>>
>> Since we have 3 company domain names, we have always used AuthSMTP as
>> smarthost with the default SMTP connection settings to send mail.
>>
>> The problem seems to be that the Exchange Delivery Service listens on
>> port 25??? We need it to listen on port 2525 for POP3 mail to go to
>> clients --guessing here?
>

Steve,

I saw that and my post never referred to staying with Verizon. I was
just making it *VERY* clear that Verizon not offering business connections
is not a valid excuse to break their ToS. Long term, that'll cause more
harm than good and put the business at bigger risk.

-Cliff


"SteveB" <> wrote in message
news:##...
> Cliff while I agree with you the OP said Verizon doesn't offer business
> class service at his location. I think he needs to look at other
> alternatives such as business class cable or even some T1 provider.
>
> "Cliff Galiher" <> wrote in message
> news:...
>> I'll be short and sweet. Verizon is becoming more strict about enforcing
>> and *checking* traffic. We could help you create a second connector and
>> then Verizon will terminate your account for using it in a manner
>> blatantly forbidden in their TOS. That is a lot of work for nothing.
>>
>> So, in short? I'd strongly urge you to stop trying to circumvent a
>> technical limitation as it'll be a stop-gap measure and could have
>> drastic ramifications on your business. Better to move to a
>> business-class connection now.
>>
>> ...and, as a complete tangent, ditch pop3. Once you have a good business
>> connection with port 25 unblocked, you can (and should) have email
>> delivered to your exchange server directly. The pop3 connector is not
>> intended as a long-term solution.
>>
>> -Cliff
>>
>>
>> "PorBar" <> wrote in message
>> news:8bf59f01-268d-4525-8048-...
>>> On Oct 29, 1:54 pm, "SteveB" <newsgr...@public.lan> wrote:
>>>> Is this a business class Verizon account as on residential service port
>>>> 25
>>>> is typically blocked and your TOS doesn't allow you to run a mail or
>>>> other
>>>> servers? POP3 is usually using port 110.
>>>>
>>>> "PorBar" <compsos...@gmail.com> wrote in message
>>>>
>>>> news:595021d9-7e3f-4736-8eb7-...
>>>>
>>>> > We have SBS2000 with Exchange 2000 Server -we had no email issues
>>>> > until our ISP, Verizon, started blocking port 25. We use a smart
>>>> > host-
>>>> > AuthSMTP to send mail from our 3 domains. When Verizon blocked port
>>>> > 25, we could still receive mail with our POP3 Connector, but we could
>>>> > not send. Makes sense sense SMTP Connector uses port 25.
>>>>
>>>> > So, per instructions from AuthSMTP, we changed the SMTP port to 2525.
>>>> > We could then send mail, however we could not longer receive. The
>>>> > mail
>>>> > comes into Exchange ok - we see messages in the POP3-Inforward folder
>>>> > - but does not get delivered to the Exchange Outlook clients until we
>>>> > change the port back to #25.
>>>>
>>>> > 1. What is the relationship of the Exchange Delivery Service/POP3
>>>> > connector and port 25? We cannot find anywhere else to change port
>>>> > 25
>>>> > to port 2525.
>>>>
>>>> > We think we need to setup either an additional SMTP connector, SMTP
>>>> > Virtual Server, or both. We attempted to start doing this and became
>>>> > confused/concerned as to which Exchange would use, etc.
>>>>
>>>> > Thanks
>>>
>>> This is a residential service, business service not offered here by
>>> Verizon. Port 25 just started being blocked by Verizon this week. Yes
>>> POP uses port 110 and the mail does come into the Exchange Server. It
>>> just will not go to the Outlook clients.
>>>
>>> Since we have 3 company domain names, we have always used AuthSMTP as
>>> smarthost with the default SMTP connection settings to send mail.
>>>
>>> The problem seems to be that the Exchange Delivery Service listens on
>>> port 25??? We need it to listen on port 2525 for POP3 mail to go to
>>> clients --guessing here?
>>
>
>

I'm startled--I had thought Verizon offered business service over their
whole territory--they don't charge much, if anything more than the
residential fees. We have fixed IP which they DO charge a good bit more
for, but we don't have port 25 blocked. OTOH, our service was down for much
of 4 working days while they figured out how to configure their routers to
allow for that.

"PorBar" <> wrote in message
news:8bf59f01-268d-4525-8048-...
> On Oct 29, 1:54 pm, "SteveB" <newsgr...@public.lan> wrote:
>> Is this a business class Verizon account as on residential service port
>> 25
>> is typically blocked and your TOS doesn't allow you to run a mail or
>> other
>> servers? POP3 is usually using port 110.
>>
>> "PorBar" <compsos...@gmail.com> wrote in message
>>
>> news:595021d9-7e3f-4736-8eb7-...
>>
>> > We have SBS2000 with Exchange 2000 Server -we had no email issues
>> > until our ISP, Verizon, started blocking port 25. We use a smart host-
>> > AuthSMTP to send mail from our 3 domains. When Verizon blocked port
>> > 25, we could still receive mail with our POP3 Connector, but we could
>> > not send. Makes sense sense SMTP Connector uses port 25.
>>
>> > So, per instructions from AuthSMTP, we changed the SMTP port to 2525.
>> > We could then send mail, however we could not longer receive. The mail
>> > comes into Exchange ok - we see messages in the POP3-Inforward folder
>> > - but does not get delivered to the Exchange Outlook clients until we
>> > change the port back to #25.
>>
>> > 1. What is the relationship of the Exchange Delivery Service/POP3
>> > connector and port 25? We cannot find anywhere else to change port 25
>> > to port 2525.
>>
>> > We think we need to setup either an additional SMTP connector, SMTP
>> > Virtual Server, or both. We attempted to start doing this and became
>> > confused/concerned as to which Exchange would use, etc.
>>
>> > Thanks
>
> This is a residential service, business service not offered here by
> Verizon. Port 25 just started being blocked by Verizon this week. Yes
> POP uses port 110 and the mail does come into the Exchange Server. It
> just will not go to the Outlook clients.
>
> Since we have 3 company domain names, we have always used AuthSMTP as
> smarthost with the default SMTP connection settings to send mail.
>
> The problem seems to be that the Exchange Delivery Service listens on
> port 25??? We need it to listen on port 2525 for POP3 mail to go to
> clients --guessing here?