[quote user="Spiderlegs"]

Correct for the old SMTP.  And, yes...the POP is 110.  

[/quote]

Suggest that you try using Port 995 with SSL for POP.

Reminded when SBCGlobal changed over to SSL.  A few months before they sent out notices with the new setup information. One day I got a panic call from an Outlook Express user because she could no longer send/receive mail.  Turns out she thought the notices were from scammers so she ignored them.

KSQR

Recently I find that sending mail from version 4.7 (Windows Pro 7, 64-bit) will not deliver to addressees with yahoo or msn extensions on their address.  This had been working for as long as I can remember.  But in the last 2 weeks it has ceased to be functional.  I tested to a yahoo address today via my ISP's proprietary e-mail program and it works fine; so it is not my ISP, and it is not my computer.  And it would not be yahoo's or msn's filtering process, as these proprietary ISP e-mails are delivered no problem.  I also re-loaded Pegasus 4.7 to see if a clean load would fix the problem.  It has not.  Hotmail, cox.net, gmail...everybody else works.  What's going on?

[quote user="Spiderlegs"]Recently I find that sending mail from version 4.7 (Windows Pro 7, 64-bit) will not deliver to addressees with yahoo or msn extensions on their address.  This had been working for as long as I can remember.  But in the last 2 weeks it has ceased to be functional.  I tested to a yahoo address today via my ISP's proprietary e-mail program and it works fine; so it is not my ISP, and it is not my computer.  And it would not be yahoo's or msn's filtering process, as these proprietary ISP e-mails are delivered no problem.  I also re-loaded Pegasus 4.7 to see if a clean load would fix the problem.  It has not.  Hotmail, cox.net, gmail...everybody else works.  What's going on?
[/quote]

Suggest creating an SMTP log file so that you can look for anything abnormal.  To do this is to go to File | Network
configuration | General and turn on "Create Internet session logs (advanced diagnostic use only)"  Another way is to run
Pegasus Mail with a "-Z 32" command line switch.

Pegasus Mail will create log files that show the *entire* exchange of information between it and the mail server in files
in the TCPlog directory in your home mailbox directory; suggest that you only send a small test message.  An SMTP session is
recorded in a file with an *.SMTP extension; for a POP the file extension is .POP.  File names include date and time information.

NOTE: Username and password information exchanged between Pegasus Mail and the server will be shown in the log file.

KSQR

I have done what you suggest and see the results.  What should I be looking for that would indicate Pegasus is not actually delivering to those yahoo or msn addresses?

Thank you!

Spiderlegs

You will only see that the transaction was normal or otherwise. If the message was sent normally it suggests that the problem lies elsewhere.

You can post the log here if you wish, but delete your username and password before doing so. Be aware that these might be Base64 encoded and not immediately apparent.

Here are the files (logs):

 14:19:54.902: --- 14 Feb 2015, 14:19:54.902 ---
14:19:54.902: Connect to 'SMTP.newmex.com', timeout 30 seconds.
14:19:55.994: >> 220 rio.newmex.com ESMTP Postfix<cr><lf>
14:19:55.994: << EHLO [192.168.0.2]<cr><lf>
14:19:56.119: >> 250-rio.newmex.com<cr><lf>
14:19:56.119: >> 250-PIPELINING<cr><lf>
14:19:56.119: >> 250-SIZE 65536000<cr><lf>
14:19:56.119: >> 250-VRFY<cr><lf>
14:19:56.119: >> 250-ETRN<cr><lf>
14:19:56.119: >> 250-ENHANCEDSTATUSCODES<cr><lf>
14:19:56.119: >> 250-8BITMIME<cr><lf>
14:19:56.119: >> 250 DSN<cr><lf>
14:19:56.119: << MAIL FROM:<*******@newmex.com> SIZE=484<cr><lf>
14:19:56.197: >> 250 2.1.0 Ok<cr><lf>
14:19:56.197: << RCPT TO:<artistjesse@yahoo.com><cr><lf>
14:19:56.259: >> 250 2.1.5 Ok<cr><lf>
14:19:56.259: << DATA<cr><lf>
14:19:56.306: >> 354 End data with <CR><LF>.<CR><LF><cr><lf>
14:19:56.322: << From: *******@newmex.com<cr><lf>
14:19:56.322: << To: artistjesse@yahoo.com<cr><lf>
14:19:56.322: << Date: Sat, 14 Feb 2015 14:19:54 -0700<cr><lf>
14:19:56.322: << MIME-Version: 1.0<cr><lf>
14:19:56.322: << Subject: another test<cr><lf>
14:19:56.322: << Message-ID: <54DFBBFA.11701.E50532@gallard.newmex.com><cr><lf>
14:19:56.322: << Return-receipt-to: *******@newmex.com<cr><lf>
14:19:56.322: << Priority: normal<cr><lf>
14:19:56.322: << X-mailer: Pegasus Mail for Windows (4.70)<cr><lf>
14:19:56.322: << Content-type: text/plain; charset=US-ASCII<cr><lf>
14:19:56.322: << Content-transfer-encoding: 7BIT<cr><lf>
14:19:56.322: << Content-description: Mail message body<cr><lf>
14:19:56.322: << <cr><lf>
14:19:56.322: << Hi Stevie...<cr><lf>
14:19:56.322: << <cr><lf>
14:19:56.322: << Trying something else.<cr><lf>
14:19:56.322: << <cr><lf>
14:19:56.322: << Ken<cr><lf>
14:19:56.322: << <cr><lf>
14:19:56.322: << .<cr><lf>
14:19:56.478: >> 250 2.0.0 Ok: queued as BFCE6B403B0<cr><lf>
14:19:56.493: << QUIT<cr><lf>
14:19:56.540: >> 221 2.0.0 Bye<cr><lf>
14:19:56.540: --- Connection closed normally at 14 Feb 2015, 14:19:56.540. ---
14:19:56.540:

And the other one (POP):

14:19:59.707: --- 14 Feb 2015, 14:19:59.707 ---
14:19:59.707: Connect to 'mail.newmex.com', timeout 30 seconds.
14:20:00.752: >> +OK MagicMail ready.<cr><lf>
14:20:00.752: << USER *******<cr><lf>
14:20:00.799: >> +OK<cr><lf>
14:20:00.799: << PASS *******<cr><lf>
14:20:00.893: >> +OK Logged in.<cr><lf>
14:20:00.893: << STAT<cr><lf>
14:20:00.939: >> +OK 0 0<cr><lf>
14:20:00.939: << QUIT<cr><lf>
14:20:01.002: >> +OK Logging out.<cr><lf>
14:20:01.002: --- Connection closed normally at 14 Feb 2015, 14:20:01.002. ---
14:20:01.002:

Thanks for helping...

Spiderlegs

I'm not an expert with TCP logs but the SMTP log looks OK to me.

Unless someone else has another idea or can identify a problem I suggest you refer the log to the ISP for comment.

It appears that the message has gone missing somewhere between it and the intended receiver, possibly into a spamtrap.

[quote user="Spiderlegs"]

Here are the files (logs):

14:19:54.902: --- 14 Feb 2015, 14:19:54.902 ---
14:19:54.902: Connect to 'SMTP.newmex.com', timeout 30 seconds.
14:19:55.994: >> 220 rio.newmex.com ESMTP Postfix<cr><lf>  

[/quote]

I would expect to see that you have an SSL or an SSL/TLS session was established, e.g.

18:19:41.697: [*] SSL/TLS session established

Suggest checking your SMTP configuration to make sure that you are using either Port 465 or 587 and that the security settings match.

KSQR

I'm not sure why that would be. The server hasn't listed it as an option and regardless of that, appears to have accepted the message. (250.2.0.0)

You guys are certainly more knowledgeable than I.  I will check with our ISP folks on Monday morning; hopefully they can decipher something.  Thanks for taking a look at this.

Cheers,

Spiderlegs

[quote user="Spiderlegs"]

You guys are certainly more knowledgeable than I.  I will check with our ISP folks on Monday morning; hopefully they can decipher something.  Thanks for taking a look at this.

[/quote]

Excerpt from: http://www.taosnet.com/help/dir/2

"Mail Servers - When configuring your email program to check mail, in addition to your User name and Password, you will need to specify the following mail servers inside your email program.

    Incoming Mail Server: mail.newmex.com - SSL/TLS is supported and recommended on the default ports.

    Secure Outgoing Mail Server: mail.newmex.com - This server has an outgoing size limit of 8Mbytes per email; set the email program to use port 587 with your normal TaosNet username and password. This is necessary so that certain systems, DSL in particular, that block the use of the default port of 25 can be bypassed. We recommend enabling TLS/STARTTLS for secure encrypted communication."

Try using mail.newmex.com instead of smtp.newmex.com

KSQR
 

The problem does not appear to relate to communication with the server and the use of TLS/STARTTLS or otherwise is (ostensibly} not an issue.

The question is why certain messages reach their intended destinations and some do not, and in particular why the subject message was accepted by the server but not delivered.

That said, if the changes being made by Taosnet as outlined by KSQR are applicable to your situation, there is good reason to try the new SMTP server to see if that makes any difference.

It is possible that the problems you are experiencing are transitional.

Many thanks, guys, for taking an interest in this and looking this over.  I will try your suggestions.

Thank you again...

Spiderlegs

KSQR was on the right track.  Changing the name of the server and upgrading the port passes my outgoing mail through a more current server allowing yahoo and msn to read the incoming messages with greater confidence.  As a result, this problem now appears to be fixed.

Thanks for your great suggestions.

Spiderlegs

[quote user="Spiderlegs"]

Changing the name of the server and upgrading the port passes my outgoing mail through a more current server allowing yahoo and msn to read the incoming messages with greater confidence.

[/quote]

Sounds like ISP speak for "your messages are no longer being rejected or dumped into a spam trap for no good reason."

[quote user="Spiderlegs"]

KSQR was on the right track.  Changing the name of the server and upgrading the port passes my outgoing mail through a more current server allowing yahoo and msn to read the incoming messages with greater confidence. 

 [/quote]

For SMTP were you using Port 25 before?  For POP are you using Port 110, Port 995, or other?

KSQR

The log suggests port 25 for SMTP. Rio.newmex.com offers STARTTLS on port 587 and that does not appear.

Correct for the old SMTP.  And, yes...the POP is 110.  Getting answers today from friends with yahoo addresses just like normal.  As well as all others.

Spiderlegs