SMTP protocol errors

HCL Domino Domino Forum
1

I’m getting the following errors on some mail sent outside the organization. It seems like this is intermittent and is not for all outgoing mail. Any idea if this is a server setting on our end or is it the receiving site?

SMTP Protocol Returned a Permanent Error 550 relaying to email_address_from_here@removed.com prohibited by administrator

Error transferring to CONNECTIONS.COM; SMTP Protocol Returned a Permanent Error 553 sorry, that domain isn’t in my list of allowed rcpthosts (#5.7.1)

Error transferring to HOTELFLAMINGO.COM; SMTP Protocol Returned a Permanent Error 530 authentication required for relay (#5.7.1)

Error transferring to YUKONCOMMUNICATIONS.NET; SMTP Protocol Returned a Permanent Error 550 relaying to semail_address_from_here@removed.com prohibited by administrator

Error transferring to VILLASCARIBE.COM; SMTP Protocol Returned a Permanent Error 550 client.

2

Subject: SMTP troubleshooting & RFC code reference

You have several DIFFERENT error messages going on here, so let’s look at them one at a time.And I’m going to start by pointing you at a valuable resource - a list of RFC error codes and their meanings. That’s those codes “553” and “5.7.1” that are in the error messages.

http://www.faqs.org/rfcs/rfc3463.html

relaying to prohibited by administrator - This is on Domino’s side. Somewhere in your configuration, you’ve blocked sending to this address or domain. Check your Messaging Configuration documents, RouterSMTP tab, Restrictions and Controls tab, SMTP Outbound tab. Look at the field labelled “Deny messages to recipients in the following Internet domains or hostnames:”.

Permanent Error 553 sorry, that domain isn’t in my list of allowed rcpthosts (#5.7.1)

  • check the RFC codes, and you’ll find that “5.5.3” indicates “too many recipients” and 5.7.1 Delivery not authorized, message refused

  • So this message was refused by the recipient server because there were too many recipients. They probably enabled something to block large numbers of recipients to prevent spam.

Permanent Error 530 authentication required for relay (#5.7.1)

  • X.3.0 Other or undefined mail system status: The destination system exists and normally accepts mail, but something about the system has caused the generation of this DSN.

  • and 5.7.1 Delivery not authorized, message refused

So this one they aren’t really giving you much info, other than something on the recipient’s system caused it to refuse the message. I would try again another day, hoping it was a bad configuration on their side and they will correct it. Otherwise, you’ll have to get in touch with someone at that company and get their email administrator involved.

Permanent Error 550 client.

  •   X.5.0   Other or undefined protocol status Something was wrong with the protocol necessary to deliver the message to the next hop and the problem cannot be well expressed with any of the other provided detail codes.

  • Again, not a very helpful message, and I would try again another day, hoping it was a bad configuration on their side and they will correct it. Otherwise, you’ll have to get in touch with someone at that company and get their email administrator involved.

Only the first one is something you have set on the Domino server. The rest are the recipient server rejecting your messages for various reasons.

3

Subject: SMTP Protocol errors

Please see comments within your suggestions. Thank you very much for your help! I wanted to mention that I have DDM running and I am seeing some of the following error messages. Could this be DNS issues?

Mail from Diveres/DRS to destination [$retry gci.net.s6a1.psmtp.com] has exceeded its retry limit.

Router: No messages transferred to RUCECI.COM (host mail2.RUCECI.COM) via SMTP: Remote system no longer responding

You have several DIFFERENT error messages going on here, so let’s look at them one at a time.

And I’m going to start by pointing you at a valuable resource - a list of RFC error codes and their meanings. That’s those codes “553” and “5.7.1” that are in the error messages.

http://www.faqs.org/rfcs/rfc3463.html

relaying to prohibited by administrator - This is on Domino’s side. Somewhere in your configuration, you’ve blocked sending to this address or domain. Check your Messaging Configuration documents, RouterSMTP tab, Restrictions and Controls tab, SMTP Outbound tab. Look at the field labelled “Deny messages to recipients in the following Internet domains or hostnames:”.

I checked this setting and the value is blank. This is the field:

Deny messages to recipients in the following Internet domains or hostnames:

Could there be any other settings to check that would cause this error?

Permanent Error 553 sorry, that domain isn’t in my list of allowed rcpthosts (#5.7.1)

  • check the RFC codes, and you’ll find that “5.5.3” indicates “too many recipients” and 5.7.1 Delivery not authorized, message refused

  • So this message was refused by the recipient server because there were too many recipients. They probably enabled something to block large numbers of recipients to prevent spam.

The message that kicked back was addressed to a single indivdual and we don’t generate a large number of messages to these domains that would cause the recipienet mail system to think we are spammers.

Permanent Error 530 authentication required for relay (#5.7.1)

  • X.3.0 Other or undefined mail system status: The destination system exists and normally accepts mail, but something about the system has caused the generation of this DSN.

  • and 5.7.1 Delivery not authorized, message refused

So this one they aren’t really giving you much info, other than something on the recipient’s system caused it to refuse the message. I would try again another day, hoping it was a bad configuration on their side and they will correct it. Otherwise, you’ll have to get in touch with someone at that company and get their email administrator involved.

Permanent Error 550 client.

  • X.5.0 Other or undefined protocol status Something was wrong with the protocol necessary to deliver the message to the next hop and the problem cannot be well expressed with any of the other provided detail codes.

  • Again, not a very helpful message, and I would try again another day, hoping it was a bad configuration on their side and they will correct it. Otherwise, you’ll have to get in touch with someone at that company and get their email administrator involved.

Only the first one is something you have set on the Domino server. The rest are the recipient server rejecting your messages for various reasons.

4

Subject: SMTP Protocol errors

RE: >>>>>>> I checked this setting and the value is blank. This is the field: / Deny messages to recipients in the following Internet domains or hostnames: / Could there be any other settings to check that would cause this error? ** Just about anything on that same tab, or in the server rules, as these are the places where you set policies on outbound messages. Also, if you change anything in the config, restart the router task to be sure the changes are obeyed.

RE: - check the RFC codes, and you’ll find that “5.5.3” indicates “too many recipients” and 5.7.1 Delivery not authorized, message refused / - So this message was refused by the recipient server because there were too many recipients. They probably enabled something to block large numbers of recipients to prevent spam. / >>>>>>> The message that kicked back was addressed to a single indivdual and we don’t generate a large number of messages to these domains that would cause the recipienet mail system to think we are spammers.

** Then the recipient’s server is giving you the wrong information for WHY it was rejected. But it was rejected on their end, and you’ll have to get them involved to get it fixed.