Glad the details helped!

I don't use Verizon as my primary email host, not because of security concerns but because their servers tend to be unreliable, and because the people running the servers don't seem very knowledgeable.   A couple of years ago, as part of an abortive anti-spam initiative, they turned off accepting email from ALL of Europe -- and kept it that way for weeks without notifying anyone!

I use gmail as my primary source, which does use SSL for both POP and smtp.  In addition, I have a backup copy of all my email, in case anything happens to my local store.  I could actually forward verizon mail to gmail, but I don't do it because the only mail I get on my verizon account is spam.

Gmail also has a superb Bayesian spam detector and I rarely see any leaking through. I get probably 50-100 spam a day and maybe 10 real email.  I never see the spam, so I don't worry about it. Gmail also has the advantage of having a good web mail interface so I can check my mail from any connected computer which allow access to gmail.

Pegasus works quite well with gmail, both directions, by the way.

Hi -

I am a private user in the United States, using Pegasus 4.41 on a machine
running Windows XP (sp3).  As of a few days ago I can no longer send email from Pegasus
via SMTP port 25, and 587 doesn't work either.  Any suggestions?

More details as follows:
My home ISP (Verizon) notified me a few days ago that it is implementing outbound port
25 blocking system-wide, and that anyone using an email client ("such as Outlook or Outlook Express") might need to change their SMTP settings to use port 587.  Although Verizon's website said this
implementation began in January 2009, I haven't had any problems in
the 10 months since then.  But the last few days I haven't been able
to send; so, I tried changing to 587.  That did not fix it.

I can still receive fine via Pegasus; and I can access the internet, and
send email via my email provider's web interface.  By the way my email provider is not the same as my ISP - I use a very small, local, web-based email provider.  My ISP, as mentioned above, is Verizon.

Verizon says it cannot help me - they say they only have tech support for
this problem for Outlook and Outlook Express.  They don't seem to know
Pegasus.  (I continue to be amazed at how many, not just people, but organizations - technology and communications companies, no less! - don't know about Pegasus.  I was introduced in the mid-90s, used every day through 2003, was forced away for a few years, and am happy to be back to Pegasus again for the last year or so.)  My email provider doesn't know either.

Anyway, if anyone has any suggestions for another SMTP port number
to use, or any other fix that would allow me to still use Pegasus to send,
I would be most appreciative to hear it!  Thank you very much.

> Verizon says it cannot help me - they say they only have tech support for this problem for Outlook and Outlook Express.  They don't seem to
> know Pegasus.  (I continue to be amazed at how many, not just people, but organizations - technology and communications companies, no less! -
> don't know about Pegasus.  I was introduced in the mid-90s, used every day through 2003, was forced away for a few years, and am happy to be
> back to Pegasus again for the last year or so.)  My email provider doesn't know either.

It does not matter if they know about Pegasus Mail, it does matter that they do not know how their system works.  All they need to tell you is what the names of the servers they use for POP3, SMTP (IMAP4) and how they are setup to work.

I check out the server outgoing.verizon.net using port 587 and got back this info.

220 vms173009.mailsrvcs.net -- Server ESMTP (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit))
ehlo thomas    (I entered this line)
250-vms173009.mailsrvcs.net
250-8BITMIME
250-PIPELINING
250-CHUNKING
250-DSN
250-ENHANCEDSTATUSCODES
250-EXPN
250-HELP
250-XADR
250-XSTA
250-XCIR
250-XGEN
250-XLOOP 55472F6906ECAA1C93DFBD9BA13A19EB
250-AUTH PLAIN LOGIN
250-AUTH=LOGIN
250-NO-SOLICITING
250 SIZE 20971520

You need to use ESMTP authorization.  David Harris has implemented ESMTP AUTH CRAM-MD5 for WinPMail.  It does a SMTP authentication in accordance with RFCs 2554 and 2195.  It will also do the LOGIN and the strange MS AUTH=LOGIN.

Go to Tools | Internet  options | (Sending) SMTP, edit the SMTP configuration, select the "Security" tab and then select the SMTP Authorization option as specified by your ISP.  Most require the the second or third SMTP Authorization option

[quote user="steveinpittsburgh"]By the way my email provider is not the same as my ISP - I use a very

small, local, web-based email provider.  My ISP, as mentioned above, is

Verizon
[/quote]

As Thomas says, it is nothing to do with Pegasus, or Outlook or whatever, it's just that the droids on the end of the phone don't have a flowchart for Pegasus and revert to the default answer "we can't help you" because they have no idea how the system works.

There are two options:

1. get Verizon to unblock your port 25 (yeah right!)

2. talk to your email provider and work around it.

Being a small provider you are more likely to get someone who knows how to breathe without instructions. [:)]

They may already have another port available, or may open one for you (and the rest of their customers afflicted by Verizon).

Sorry it's been a month and a half, but life keeps getting in the way. 

I still am not able to send. 

I did talk to my ISP (as suggested by dilberts_left_nut) - they had me try outbound port 2525, and I think a couple things too (this was a month ago, & unfortunately now I don't remember what).  None of that worked. 

Also talked to Verizon again (per Tom Stephenson) - Verizon gave me SMTP server host name, and username+password to log in to SMTP server (the "second SMTP Authorization option" as mentioned by Tom).  I put those in to the appropriate places in the dialog boxes under "Internet Options | Sending" but that has not worked either.  

I am not really a techie and have no clue what the rest of Tom's post was about - the lines following "check [ing the Verizon server] using port 587"; and what D Harris implemented, "RFC"s, etc.  However as best I can tell that was background info; the only action steps you meant for me to take were those after "Go to" in your last paragraph.  If I missed something please fill me in.

By the way, after entering the new server host, username & password info from Verizon, in addition to trying to send using port 2525, I went back & tried again with 587, 110, and 25.  None of those worked either.  

 On each of the four attempts I got a status message of "connecting to outgoing.verizon.net" which lasted for several seconds, and then a  "15: peer connect failure - the host has refused the connection".  At other times I have NOT gotten the "peer connect failure", instead I just get "no trace information available". 

I am feeling rather lost at this point; however, I hope I've included above enough information to allow someone to give further advice.  Thank you.

- Steve 

I don't know if this will help you  but I have Verizon as an ISP and by settings in Pegasus 4.51 are as follows in the Tools|internet options|sending(SMTP):

On the General tab:

Enter a name for this definition: Verizon

Service host: outgoing.verizon.net

TSP/IP Port 587   Timeout 30 seconds.

Then on the Security tab:

Use SSL/TLS :never radio button chosen.

All others unchecked Except

Login to the SMTP server using the following  details:

 Username: rdoherty2      Password: xxxx

The username/password pair MUST be the Verizon username and password, the same ones you use to login to Verizon Webmail, or to Verizon DSL (or FIOS).

This has worked for me since the changeover to Port 25 blocking .

The place where people most frequently make a mistake is in using the wrong username/password pair.  It must be the Verizon pair and not the other ISP's.

Hope this helps!

>>TSP/IP Port 587   Timeout 30 seconds. 

>>Then on the Security tab:

>>Use SSL/TLS :never radio button chosen.

I think that did it!  Beginning w/ a test c. 24 hours ago, it appears that I am sending again.  Since then I've successfully tested a couple more times, and even received replies to "real" emails that I tried sending.  I think it was the combination of port 587 and SSL/TLS that did it.  (I had tried 587 before; and I think I had tried SSL/TLS "never", with one of the other port numbers that had been suggested before; apparently though I had not tried "never" WITH 587.) 

I was actually correct from the start w/ the Verizon v. other ISP username and password, though thanks for pointing that out too.

Just one concern at this point:  am I significantly increasing security risks, of any type, by having SSL/TLS turned off?  I am concerned with this for both SMTP and POP3 though especially the latter.  Can anyone tell me:  Is 1) the concern justified, and 2) there anything that I can do to reduce risk (like perhaps turning SSL/TLS back on for POP3, and leaving it off only for SMTP?)

Thanks - for all suggestions to date, and (in advance) for any regarding the above.  

- Steve