<p>Thanks, Jerry, for the quick reply (via email). Forcing the server address for all outgoing mail got checked at some point. (Tools/Options/Outgoing mail)</p><p> Back in business.</p><p>Really appreciate this forum and the great support it offers.</p><p> </p>

<p>Not sure if the subject line is the correct description of the problem  but here's the situation -</p><p> Running Pmail as a mail server over our household LAN with the following command line switches: </p><p>C:\PMAIL\Programs\winpm-32.exe -A -E server.txt</p><p>Got two users defined, me and wife. This has been operational for several years and serves our needs quite well. My machine has the only Internet connection in the house, wife's machine is on the LAN with her own install of PMail accessing her mailbox on my machine, all directories and pointers, etc., have been functioning fine. Always in the past if I wanted to send wife an email I simply used her user name and the message would go direct to her mailbox without going out to the server then back again.</p><p>I <i>think</i> that makes sense.</p><p>Now all of a sudden when I send wife a message it gets placed in the email queue and of course bounces since it's not a fully resolved email address. That is, it's addressed to "wife" and not "wife@mydomainname". This in turn fouls up the filtering rule that snatches any incoming messages addressed to wife@mydomainname and forwards them to wife, the local user name on our system.</p><p>I've gone through all the options, tools, settings I can find and can't see anything that would specify how mail sent to local users should be treated aside from 'regular' mail. Besides, I haven't made any changes to PMail's settings in a long time.  What am I overlooking?</p><p>Thanks for any advice...</p><p> </p>