DELIVERY Failure - SMTP Protocol Returned a Permanent Error

Hi,

When I try to send emails out to certain places I get Mail Router Errors for some of them. The errors are either:

Error transferring to MX.COGECO.CA; SMTP Protocol Returned a Permanent Error 501 #5.1.3 Invalid character (‘%’) in username.

OR

Error transferring to lhedge01.SJHC.LONDON.ON.CA; SMTP Protocol Returned a Permanent Error 501 Syntax error in command parameter(s) Invalid address

I think this is because it gets mailed out as

Name/DomainName%DomainName@example.com

instead of:

Name/DomainName@example.com OR Name@example.com

Is there a setting in the Current Server or Message Settings Document that would get rid of the “%DomainName” part? Right now some emails go through with the current setting but others are rejected by the recipient’s mail server because of the above. Any help would be appreciated. Thanks.

Jason

Subject: DELIVERY Failure - SMTP Protocol Returned a Permanent Error

Do you have a Global Domain Document? If so, check out the Conversions Tab.

If you make a change to this document, you’ll have to restart the Router task before the change takes effect.

HTH.

Gregg

Subject: RE: DELIVERY Failure - SMTP Protocol Returned a Permanent Error

Thanks for the suggestion. It pointed me in the right direction. As I didn’t have a Global Domain document and didn’t want to take the chance of creating anything new without fully understanding it, on Configuration - Messaging - Configurations - click on the appropriate server configuration document - MIME - Conversion Options - Outbound → Lookup Internet address for all Notes addresses when Internet address is not defined in document: → EnableAlso had to make sure person had Internet Address in the Domain Directory.

That seemed to have done the trick.

Subject: RE: DELIVERY Failure - SMTP Protocol Returned a Permanent Error

Are there other settings somewhere that a person should check? We are receiving this now on 6.5.5 release.

Subject: RE: DELIVERY Failure - SMTP Protocol Returned a Permanent Error

Did you ever get a solution to this? We are also having a problem. Thanks