• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

ISP Blocked Port 25-SMTP Issue--HELP!

P

PorBar

#1
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
 
S

SteveB

#2
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" <compsosinc@newsgroup> wrote in message
news:595021d9-7e3f-4736-8eb7-b8bd627d2674@newsgroup

> 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
 
P

PorBar

#3
On Oct 29, 1:54 pm, "SteveB" <newsgr...@newsgroup> 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...@newsgroup> wrote in message
>
> news:595021d9-7e3f-4736-8eb7-b8bd627d2674@newsgroup
>

> > 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?
 
C

Cliff Galiher

#4
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" <compsosinc@newsgroup> wrote in message
news:8bf59f01-268d-4525-8048-7c5cee2ea368@newsgroup

> On Oct 29, 1:54 pm, "SteveB" <newsgr...@newsgroup> 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...@newsgroup> wrote in message
>>
>> news:595021d9-7e3f-4736-8eb7-b8bd627d2674@newsgroup
>>

>> > 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?
 
S

SteveB

#5
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" <cgaliher@newsgroup> wrote in message
news:uk1VBzQWKHA.504@newsgroup

> 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" <compsosinc@newsgroup> wrote in message
> news:8bf59f01-268d-4525-8048-7c5cee2ea368@newsgroup

>> On Oct 29, 1:54 pm, "SteveB" <newsgr...@newsgroup> 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...@newsgroup> wrote in message
>>>
>>> news:595021d9-7e3f-4736-8eb7-b8bd627d2674@newsgroup
>>>
>>> > 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?
>
 
C

Cris Hanna [SBS - MVP]

#6
I agree with Cliff and Steve that using residential class service in a business scenario, while a cheaper alternative, is going to continue to provide headaches. As a quick fix while waiting to find a new business class provider, to resolve your issue, you many wish to re-run the CEICW wizard and re-plug in the necessary mods

--
Cris Hanna [SBS - MVP] (since 1997)
Co-Contributor, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small...bs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"SteveB" <newsgroup@newsgroup> wrote in message news:%23%23VzhNSWKHA.3404@newsgroup
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" <cgaliher@newsgroup> wrote in message
news:uk1VBzQWKHA.504@newsgroup

> 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" <compsosinc@newsgroup> wrote in message
> news:8bf59f01-268d-4525-8048-7c5cee2ea368@newsgroup

>> On Oct 29, 1:54 pm, "SteveB" <newsgr...@newsgroup> 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...@newsgroup> wrote in message
>>>
>>> news:595021d9-7e3f-4736-8eb7-b8bd627d2674@newsgroup
>>>
>>> > 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?
>
 
C

Cliff Galiher

#7
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" <newsgroup@newsgroup> wrote in message
news:##VzhNSWKHA.3404@newsgroup

> 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" <cgaliher@newsgroup> wrote in message
> news:uk1VBzQWKHA.504@newsgroup

>> 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" <compsosinc@newsgroup> wrote in message
>> news:8bf59f01-268d-4525-8048-7c5cee2ea368@newsgroup

>>> On Oct 29, 1:54 pm, "SteveB" <newsgr...@newsgroup> 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...@newsgroup> wrote in message
>>>>
>>>> news:595021d9-7e3f-4736-8eb7-b8bd627d2674@newsgroup
>>>>
>>>> > 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?
>>
>
>
 
B

Bill Sanderson

#8
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" <compsosinc@newsgroup> wrote in message
news:8bf59f01-268d-4525-8048-7c5cee2ea368@newsgroup

> On Oct 29, 1:54 pm, "SteveB" <newsgr...@newsgroup> 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...@newsgroup> wrote in message
>>
>> news:595021d9-7e3f-4736-8eb7-b8bd627d2674@newsgroup
>>

>> > 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?
 
P

PorBar

#9
On Oct 30, 10:29 pm, "Bill Sanderson"
<bill_sander...@newsgroup> wrote:

> 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 formuch
> of 4 working days while they figured out how to configure their routers to
> allow for that.
>
> "PorBar" <compsos...@newsgroup> wrote in message
>
> news:8bf59f01-268d-4525-8048-7c5cee2ea368@newsgroup
>

> > On Oct 29, 1:54 pm, "SteveB" <newsgr...@newsgroup> 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...@newsgroup> wrote in message
>

> >>news:595021d9-7e3f-4736-8eb7-b8bd627d2674@newsgroup
>

> >> > 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.
> >

> > 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?
Just a farmer here int he sticks with no option but DSL, Found out how
to solve in Exchange SMTP Connector.
 
K

Ken Gordon

#10
Virtual SMTP Server

Loa Corporation offers a virtual SMTP server that should work here. It appears to your client as an SMTP server running locally on 127.0.0.1. See us at http://www.loapowertools.com.



PorBar wrote:

ISP Blocked Port 25-SMTP Issue--HELP!
30-Oct-09

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

Previous Posts In This Thread:

EggHeadCafe - Software Developer Portal of Choice
Custom configuration Data from DataSets: Less is More
http://www.eggheadcafe.com/tutorial...d-329a2cdc9f44/custom-configuration-data.aspx