0 pts.
 smtp and external application
Hello, one of our customers tried without luck to send an email using a dot.NET application and Domino SMTP service; unfortunately I don't have the detail of application, but I know that the sender and the recipient are both internal user; the error is: "554 Mail from myuser@mydomain.com rejected for policy reasons". Thank You in advance for any suggestions, Regards, Maurizio

Software/Hardware used:
ASKED: October 3, 2006  10:08 AM
UPDATED: October 5, 2006  4:01 AM

Answer Wiki:
The domino server routing the email has a policy restriction set to not allow email from this domain. See the Domino Admin Help to find the appropriate fields and have the domain that should be allowed to send email through the domino server added to the appropriate field. This needs to be done by the Domino administrator.
Last Wiki Answer Submitted:  October 3, 2006  11:15 am  by  Maggs   0 pts.
All Answer Wiki Contributors:  Maggs   0 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _


 

Thank You Maggs!

The domain is normally used to send external email from lotus client, but this is not a “normal” send, because it is made by an external Dot.NET application… is it necessary to authorize the IP client?

Regards,

Maurizio

 0 pts.

 

Yes you might have to whitelist specific IP as authorized senders. Or you might have to create DNS records. Look in authorized relay servers too. Other possibilities are that SMTP server to server traffic is expected to be authenticated (username/password) or come encrypted over SSL, especially if you have a SMTP gateway or appliance server that normal prescreens all the email raw off the Internet before passing it on the main server.

There are in fact several ways a sophisticated email server or its add ons can restrict who can pretend to be a real smtp server and not just a spammer’s zombie machine.

 0 pts.

 

Yes you might have to whitelist specific IP as authorized senders. Or you might have to create DNS email records. Look in authorized relay servers too. Other possibilities are that SMTP server to server traffic is expected to be authenticated (username/password) or come encrypted over SSL, especially if you have a SMTP gateway or appliance server that normal prescreens all the email raw off the Internet before passing it on the main server.

There are in fact several ways a sophisticated email server or its add ons can restrict who can pretend to be a real smtp server and not just a spammer’s zombie machine.

 0 pts.

 

Thank You Mortree,
do you suggest to use:

“Allow messages only from the following internet hosts to be sent to external internet domains”

“Exclude these connecting hosts from anti-relay checks”

or “authentication” ?

Best Regards

Maurizio

 0 pts.