Thanks for that info Martin, I should have guessed the info originated from the SMTP server based on the reference number quoted. I finally found the errors by resending and using Internet Session log . The reference number then jumped out with the preceding line containing the address in error. FYI, the errors were 1: a comma after the .com and 2: ".." (2 dots) between the server name and com
I also noted that the personal name (in quotes) included with each address is NOT transmitted by Pegasus to the SMTP server based on the log entries and on observation of an email received from the lists. Only the email address itself (between the < > is sent. However I will continue to add them as some of the weird addresses people use don't make it easy to identify the address outside the email process itself. I use an automated spreadsheet to add the info and to allow me to count the number of emails per list to stay within the number per list server limits. (There are other clients that will do this automagically but I prefer Pegasus!!!)
The errors originated the the spreadsheet and data base sent to me by the database person each time I have to do a mailing (about 1700 persons and using 17 lists due to the maximums addresses per list imposed by the smtp server - (a spam avoidance measure)!!!)
I have been lucky in finding this type of error before, not so much this time, but I now have another tool in my arsenal for tracking them down.....
Thanks again
Stuart
(Montreal/Naples FL)
<p>Thanks for that info Martin, I should have guessed the info originated from the SMTP server based on the reference number quoted. I finally found the errors by resending and using Internet Session log . The reference number then jumped out with the preceding line containing the address in error. FYI, the errors were&nbsp; 1: a comma after the .com and &nbsp; 2: ".."&nbsp; (2 dots) between the server name and com</p><p>I also noted that the personal name (in quotes) included with each address is NOT transmitted by Pegasus to the SMTP server based on the log entries and on observation of an email received from the lists. Only the email address itself (between the &lt;&nbsp;&nbsp;&nbsp; &gt; is sent. However I will continue to add them as some of the weird addresses people use don't make it easy to identify the address outside the email process itself. I use an automated spreadsheet to add the info and to allow me to count the number of emails per list to stay within the&nbsp; number per list server limits. (There are other clients that will do this automagically but I prefer Pegasus!!!)
</p><p>&nbsp;</p><p>&nbsp;The errors originated the the spreadsheet and data base sent to me by the database person each time I have to do a mailing (about 1700 persons and using 17 lists due to the maximums addresses per list&nbsp; imposed by the smtp server - (a spam avoidance measure)!!!)
</p><p>I have been lucky in finding this type of error before, not so much this time, but I now have another tool in my arsenal&nbsp; for tracking them down.....</p><p>&nbsp;Thanks again
</p><p>Stuart</p><p>&nbsp;(Montreal/Naples FL)
</p>