Community Discussions and Support
Can't send email due to SMTP/MHS address ambiguity

Okay, more data. Had the problem again this morning and did a little research. This time it occurred before I had downloaded any email. Found a reference suggesting adding IN: in front of the address to force this to be recognized as an internet (SMTP?) address. Tried that.

This got rid of the error message complaining about an SMTP/MHS ambiguity and replaced it with the following error message:

"No Internet Mail queue exists on this system. Internet mail messages cannot be sent."

Then I downloaded last night's accumulation of email and tried sending (to the Queue Manager) the outgoing message again. It went with no complaints.

Retrieved the message from the Queue Manager and removed the IN: from the address. Sent it back to the Queue Manager again. Again, no complaints.

Finally, sent the message, no complaints.

Odd....



<p>Okay, more data. Had the problem again this morning and did a little research. This time it occurred before I had downloaded any email. Found a reference suggesting adding IN: in front of the address to force this to be recognized as an internet (SMTP?) address. Tried that.</p><p>This got rid of the error message complaining about an SMTP/MHS ambiguity and replaced it with the following error message:</p><p>"No Internet Mail queue exists on this system. Internet mail messages cannot be sent."</p><p>Then I downloaded last night's accumulation of email and tried sending (to the Queue Manager) the outgoing message again. It went with no complaints.</p><p>Retrieved the message from the Queue Manager and removed the IN: from the address. Sent it back to the Queue Manager again. Again, no complaints.</p><p>Finally, sent the message, no complaints.</p><p>Odd....</p><p> </p><p> </p>

 Using PMail 4.52 (Win32).

When composing messages or replying to messages from known addressees I receive, intermittently, the following message:

"The address 'xxxxx@xxxxxxxxxx.com' could be either and SMTP or an MHS address. Please use an IN: or MHS: override on the address so WinPMail knows where to send it."

In "Internet Mail Options" for the email account, on the SMTP tab I have checked "Use instead to LAN mailer for internet mail" 

 Lee Miles

<p> Using PMail 4.52 (Win32).</p><p>When composing messages or replying to messages from known addressees I receive, intermittently, the following message: </p><p>"The address 'xxxxx@xxxxxxxxxx.com' could be either and SMTP or an MHS address. Please use an IN: or MHS: override on the address so WinPMail knows where to send it."</p><p>In "Internet Mail Options" for the email account, on the SMTP tab I have checked "Use instead to LAN mailer for internet mail"  </p><p> Lee Miles </p>

When composing messages or replying to messages from known addressees I receive, intermittently, the following message:

"The

address 'xxxxx@xxxxxxxxxx.com' could be either and SMTP or an MHS

address. Please use an IN: or MHS: override on the address so WinPMail

knows where to send it."

In "Internet Mail Options" for the email account, on the SMTP tab I have checked "Use instead to LAN mailer for internet mail" 

This error message says that you do not have a queue to send.  Sounds to me like you are using identities and at least one of the identities does not have a proper SMTP setup.  

<blockquote><p>When composing messages or replying to messages from known addressees I receive, intermittently, the following message: </p><p>"The address 'xxxxx@xxxxxxxxxx.com' could be either and SMTP or an MHS address. Please use an IN: or MHS: override on the address so WinPMail knows where to send it."</p><p>In "Internet Mail Options" for the email account, on the SMTP tab I have checked "Use instead to LAN mailer for internet mail"  </p></blockquote><p>This error message says that you do not have a queue to send.  Sounds to me like you are using identities and at least one of the identities does not have a proper SMTP setup.   </p>

Thanks for giving me a place to focus on.  I cleaned up and standardized my identities and I am 'back in business'.

Thanks for giving me a place to focus on.  I cleaned up and standardized my identities and I am 'back in business'.

After upgrading to Pegasus 4.63 recently, I've started having this problem, too.

Changing "Load Internet Services" to "Always" seems to have fixed this MOST of the time, but I still get this error occasionally. This is a problem only with sending mail, it doesn't affect receiving.

I'm running Windows XP, SP3 32 bit, Internet connection is via DSL. If I have this problem with one PC on this router, the others won't have it at the same time.

The last time this happened was a few days ago. I checked and Pegasus was still set to "Always." Closing and restarting Pegasus did not help. I changed Identies and tried sending from that one with the same negative result. But when I went back to my original, most commonly used Identity, things were back to their usual well-working normal.

This morning, as I was just finishing up my registration for this site and forums, I tried to check my settings again and noticed that under Tools, "Internet Options..." was greyed out. I've not seen this before, but I don't look there often. I changed Identies and found "Internet Options..." still greyed out. I sent a test message and it went okay. Some time later I checked, and found "Internet Options..." back to normal. At this point I don't know what, or if, something I did corrected it.

I don't recall ever having this problem before with earlier versions of Pegasus, but my memory here may be faulty.

This morning Pegasus is working fine, but there seems to be some sort of bug in version 4.63 that I thought was worth reporting.

thanks,


<p>After upgrading to Pegasus 4.63 recently, I've started having this problem, too.</p><p>Changing "Load Internet Services" to "Always" seems to have fixed this MOST of the time, but I still get this error occasionally. This is a problem only with sending mail, it doesn't affect receiving.</p><p>I'm running Windows XP, SP3 32 bit, Internet connection is via DSL. If I have this problem with one PC on this router, the others won't have it at the same time.</p><p>The last time this happened was a few days ago. I checked and Pegasus was still set to "Always." Closing and restarting Pegasus did not help. I changed Identies and tried sending from that one with the same negative result. But when I went back to my original, most commonly used Identity, things were back to their usual well-working normal.</p><p>This morning, as I was just finishing up my registration for this site and forums, I tried to check my settings again and noticed that under Tools, "Internet Options..." was greyed out. I've not seen this before, but I don't look there often. I changed Identies and found "Internet Options..." still greyed out. I sent a test message and it went okay. Some time later I checked, and found "Internet Options..." back to normal. At this point I don't know what, or if, something I did corrected it.</p><p>I don't recall ever having this problem before with earlier versions of Pegasus, but my memory here may be faulty.</p><p>This morning Pegasus is working fine, but there seems to be some sort of bug in version 4.63 that I thought was worth reporting.</p><p>thanks,</p><p> </p>

Your problem is most likely not in winpm-32 but is with winsock or loading or with connectivity at some  point between you and the mail server. At time of failure immediately close winpm-32 on that PC and then create session log or use -z 32 as part of command line to restart session and  immediately after failure go to home mail box location on drive and view the *.wpm log file to check for error or entry just prior to finish or termination of SMTP send function request.

When winsock is not found the internet options is greyed out and is again seen when there is good winsock and connection via tcp/ip. 

<p>Your problem is most likely not in winpm-32 but is with winsock or loading or with connectivity at some  point between you and the mail server. At time of failure immediately close winpm-32 on that PC and then create session log or use -z 32 as part of command line to restart session and  immediately after failure go to home mail box location on drive and view the *.wpm log file to check for error or entry just prior to finish or termination of SMTP send function request.</p><p>When winsock is not found the internet options is greyed out and is again seen when there is good winsock and connection via tcp/ip. </p>

What is actual command line or target line used to start winpm-32 on your machine? Does it include switches or none or -a for example? See Help, Commandline options.

What is actual command line or target line used to start winpm-32 on your machine? Does it include switches or none or -a for example? See Help, Commandline options.

Thanks for the response. I'll answer as best I can.

How would I create a session log?

If I add the -z 32 option to the command line, will it overwrite that log each time Pegasus starts up? If not, I'm afraid this will create a huge log rather quickly, that I'll have to clean up each time I start. This would not be a problem if Pegasus failed frequently, but so far, on this PC, the failure has happened only once out of several months of use. It NEVER happened under any of the previous versions of Pegasus.

A problem with TCP/IP or winsock seems unlikely since my brousers all work perfectly when Pegasus was unable to find a way to send mail. This gets into an area I'm not comfortable in, however, so I'm not sure about that.

I have several identities set up in my Pegasus installation. I have the Pegasus command line set up to put me into my most commonly used identity: winpm-32.exe -ID "nickname"

Let me know if you need more info.

thanks,


<p>Thanks for the response. I'll answer as best I can.</p><p>How would I create a session log?</p><p>If I add the -z 32 option to the command line, will it overwrite that log each time Pegasus starts up? If not, I'm afraid this will create a huge log rather quickly, that I'll have to clean up each time I start. This would not be a problem if Pegasus failed frequently, but so far, on this PC, the failure has happened only once out of several months of use. It NEVER happened under any of the previous versions of Pegasus.</p><p>A problem with TCP/IP or winsock seems unlikely since my brousers all work perfectly when Pegasus was unable to find a way to send mail. This gets into an area I'm not comfortable in, however, so I'm not sure about that.</p><p>I have several identities set up in my Pegasus installation. I have the Pegasus command line set up to put me into my most commonly used identity: winpm-32.exe -ID "nickname"</p><p>Let me know if you need more info.</p><p>thanks,</p><p> </p>

Well, the problem just happened again. I clicked "Send" twice, just to make sure, and each time I got the message that there was an SMTP/MHS address ambiguity, so the message could not be sent.

Remembering my previous solution, I changed to a different identity, clicked on Tools/Identities, looked at that window and then clicked "Done." Then I returned to my usual Identity and tried again. It worked.

Before this problem occurred, I had been able to retrieve mail, so it would seem that there was no problem with the TCP/IP stack.

Any more thoughts?

thanks,

<p>Well, the problem just happened again. I clicked "Send" twice, just to make sure, and each time I got the message that there was an SMTP/MHS address ambiguity, so the message could not be sent.</p><p>Remembering my previous solution, I changed to a different identity, clicked on Tools/Identities, looked at that window and then clicked "Done." Then I returned to my usual Identity and tried again. It worked.</p><p>Before this problem occurred, I had been able to retrieve mail, so it would seem that there was no problem with the TCP/IP stack.</p><p>Any more thoughts?</p><p>thanks,</p>

Okay, it's happening again. I can retrieve mail but I can't send it. I have a message composed, but when I click Send, I get the SMTP/MHS ambiguity message. I can't get the message to go into my outgoing queue.

So here's some additional info: When I click on Tools, "Internet Options..." is greyed out any time ANY outgoing message is the TOPMOST of my Pegasus windows. If I click on a different Pegasus window, bringing it to the top, Internet Options... is back in bold. I note that when a composed outgoing message is on top, the list (File, Edit, ...Help) gets one more element, becoming File, Edit,... Message, ... Help, but I have no idea if this is relevant.

Today, changing to an alternate Identity doesn't cure the problem. So far I've not been able to send any messages. This problem has persisted thru several restarts of Pegasus. After I post this message, I'll restart Windows.

It might be relevant for me to mention that I've moved my Pegasus mailbox folders to a non-default location, but I've done this for 15 years with no ill effects, and none of this changed when I upgraded to this latest version of Pegasus, which was when this problem started.

Oh yes, this is under Windows XP SP3, which I've been using for several years, with the same mailbox location, previous versions of Pegasus, and no problems.

OH, this just in: If I Save the outgoing message, then click File/Send Saved Messages, the Draft Manager comes up. From that window I can select the message I've just saved and click "Send Now", without actually opening that message. In that case, the message goes to my outgoing queue and from there I can send it with no complaints.

Any thoughts?


<p>Okay, it's happening again. I can retrieve mail but I can't send it. I have a message composed, but when I click Send, I get the SMTP/MHS ambiguity message. I can't get the message to go into my outgoing queue.</p><p>So here's some additional info: When I click on Tools, "Internet Options..." is greyed out any time ANY outgoing message is the TOPMOST of my Pegasus windows. If I click on a different Pegasus window, bringing it to the top, Internet Options... is back in bold. I note that when a composed outgoing message is on top, the list (File, Edit, ...Help) gets one more element, becoming File, Edit,... Message, ... Help, but I have no idea if this is relevant.</p><p>Today, changing to an alternate Identity doesn't cure the problem. So far I've not been able to send any messages. This problem has persisted thru several restarts of Pegasus. After I post this message, I'll restart Windows.</p><p>It might be relevant for me to mention that I've moved my Pegasus mailbox folders to a non-default location, but I've done this for 15 years with no ill effects, and none of this changed when I upgraded to this latest version of Pegasus, which was when this problem started.</p><p>Oh yes, this is under Windows XP SP3, which I've been using for several years, with the same mailbox location, previous versions of Pegasus, and no problems.</p><p>OH, this just in: If I Save the outgoing message, then click File/Send Saved Messages, the Draft Manager comes up. From that window I can select the message I've just saved and click "Send Now", without actually opening that message. In that case, the message goes to my outgoing queue and from there I can send it with no complaints.</p><p>Any thoughts?</p><p> </p>

Okay, on reboot, everything's back to normal. I still think this is a Pegasus problem, but it may have to do with the order that things start up. I have Pegasus set to startup automatically when I log in. So maybe I need to change that, although it worked for years this way.

Any more thoughts?


<p>Okay, on reboot, everything's back to normal. I still think this is a Pegasus problem, but it may have to do with the order that things start up. I have Pegasus set to startup automatically when I log in. So maybe I need to change that, although it worked for years this way.</p><p>Any more thoughts?</p><p> </p>

In going thru this process, I've also discovered that if I Save a message and then send it from the Draft Manager without opening it, it does not show up in the Copies to Self folder.

Sending a message this way manages to bypass the Copy to Self process. A minor flaw, unless you use the Draft Manager a lot. (I've never used it before....)


<p>In going thru this process, I've also discovered that if I Save a message and then send it from the Draft Manager without opening it, it does not show up in the Copies to Self folder.</p><p>Sending a message this way manages to bypass the Copy to Self process. A minor flaw, unless you use the Draft Manager a lot. (I've never used it before....)</p><p> </p>
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft