> I was told tonight that I have been sending dup emaisl to individuals.
> I wonder what can be the cause of this? I am using windows 7 64 bit
> and current version of Pmail.
Turn on session logging and the checkout the log to determine what you are actually sending. Go to File | Network configuration | General and turn on "Create Internet session logs (advanced diagnostic use only)"
Checking this control tells Pegasus Mail to create special log files that show the entire exchange of information between it and the servers it connects to. Each session will be created in a file called TCPxxxx.WPM in your home mailbox directory (the "xxxx" is replaced by four digits). Creating session logs will slow down the performance of your system somewhat, and you should be aware that any username and password information exchanged between Pegasus Mail and the server will be shown in the log, *even* if you use SSL to secure the connection. Session logs are primarily useful if you need to debug a problem between Pegasus Mail and one of the servers it connects to - you should enable the option only on instructions from a system administrator or from Pegasus Mail technical support. [ Technical note: this control has the same effect as using a "-Z 32" commandline switch when you run Pegasus Mail ]
You can now try again to send the mail and then look at the resulting TCP/IP debug file. Review of this file will tell you exactly what is going on between WinPMail and the server. You can send me a copy of the session log for analysis if you wish at the address below.
> I was told tonight that I have been sending dup emaisl to individuals.
>  I wonder what can be the cause of this?  I am using windows 7 64 bit
> and current version of Pmail.
Turn on session logging and the checkout the log to determine what you are actually sending.  Go to File | Network configuration | General and turn on "Create Internet session logs (advanced diagnostic use only)"  
Checking this control tells Pegasus Mail to create special log files that show the entire exchange of information between it and the servers it connects to. Each session will be created in a file called TCPxxxx.WPM in your home mailbox directory (the "xxxx" is replaced by four digits). Creating session logs will slow down the performance of your system somewhat, and you should be aware that any username and password information exchanged between Pegasus Mail and the server will be shown in the log, *even* if you use SSL to secure the connection. Session logs are primarily useful if you need to debug a problem between Pegasus Mail and one of the servers it connects to - you should enable the option only on instructions from a system administrator or from Pegasus Mail technical support. [ Technical note: this control has the same effect as using a "-Z 32" commandline switch when you run Pegasus Mail ]
You can now try again to send the mail and then look at the resulting TCP/IP debug file.  Review of this file will tell you exactly what is going on between WinPMail and the server. You can send me a copy of the session log for analysis if you wish at the address below.