Recipients Auto Rejecting Emails Sent With Exchange 2010 - Certificate Error Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Come Celebrate our 10 Year Anniversary!Exchange 2010 - Getting NDR's with Relaying Denied or Firewall ErrorAfter Certificate Update on Exchange 2003 -> Delivery has failed to these recipients or distribution listsError with smarthost forwarding mailExchange 2010 send from multiple domainsExchange 2010 - Failed DeliveryExchange 2010 “Cannot send on behalf of user”Bounce message from gsmtp - weird message pathWhere is the email bounce sent? To the @domain or to the IP that sent it?What type of email address should I recreate to prevent this NDR?Why are emails sent to me bouncing with incorrect MX records error message?
Using et al. for a last / senior author rather than for a first author
What happens to sewage if there is no river near by?
What does the "x" in "x86" represent?
List *all* the tuples!
When is phishing education going too far?
Why aren't air breathing engines used as small first stages
How to find all the available tools in macOS terminal?
Is a manifold-with-boundary with given interior and non-empty boundary essentially unique?
Dominant seventh chord in the major scale contains diminished triad of the seventh?
When -s is used with third person singular. What's its use in this context?
What are 'alternative tunings' of a guitar and why would you use them? Doesn't it make it more difficult to play?
Is there a "higher Segal conjecture"?
Is there a concise way to say "all of the X, one of each"?
How can I fade player when goes inside or outside of the area?
Why was the term "discrete" used in discrete logarithm?
Is there a service that would inform me whenever a new direct route is scheduled from a given airport?
What are the motives behind Cersei's orders given to Bronn?
How to recreate this effect in Photoshop?
How do I mention the quality of my school without bragging
Why does Python start at index -1 when indexing a list from the end?
Does accepting a pardon have any bearing on trying that person for the same crime in a sovereign jurisdiction?
What is the musical term for a note that continously plays through a melody?
Antler Helmet: Can it work?
Is there a Spanish version of "dot your i's and cross your t's" that includes the letter 'ñ'?
Recipients Auto Rejecting Emails Sent With Exchange 2010 - Certificate Error
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!Exchange 2010 - Getting NDR's with Relaying Denied or Firewall ErrorAfter Certificate Update on Exchange 2003 -> Delivery has failed to these recipients or distribution listsError with smarthost forwarding mailExchange 2010 send from multiple domainsExchange 2010 - Failed DeliveryExchange 2010 “Cannot send on behalf of user”Bounce message from gsmtp - weird message pathWhere is the email bounce sent? To the @domain or to the IP that sent it?What type of email address should I recreate to prevent this NDR?Why are emails sent to me bouncing with incorrect MX records error message?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
A strange problem recently developed with one of my Exchange 2010 servers. I have an exchange server setup as part of a Windows Small Business Server 2011 installation. The email for the domain was working perfectly for 4 or 5 months, and now with no change in configuration is having problems.
The inbound email still works great, but when an email is sent it occasionally bounces back with one of several error messages. It doesn't happen to all of the sent emails, just some of them. It appears as though mail sent to certain domains will always bounce, including mail sent to domains that used to work. It also seems like the error message is generated by the recipients receiving server. Here are some of the error messages that bounce back:
host123.SomeEmailHost.com rejected your message to the following e-mail
addresses: Someone LastName (aperson@adomain.com)
host123.SomeEmailHost.com gave this error: Verification failed for
The mail server could not deliver mail to
sender@sendingdomain.net. The account or domain may not exist, they may be
blacklisted, or missing the proper dns entries. Sender verify failed
A problem occurred during the delivery of this message to this e-mail
address. Try sending this message again. If the problem continues,
please contact your helpdesk.
Here is another message received when sending to a different domain:
mail12.anotherhost.com rejected your message to the following e-mail
addresses: someoneelse lastname (someoneelse@anotherdomain.com)
(someoneelse@anotherdomain.com) mail12.anotherhost.com gave this error:
sorry, that address is not in my list of allowed recipients; no valid
cert for gatewaying (#5.7.1)
A problem occurred during the delivery
of this message to this e-mail address. Try sending this message
again. If the problem continues, please contact your helpdesk.
I have tried researching these errors, but have not turned up anything that seems applicable to my server. Is it some sort of certificate error. I am using a self signed certificate on the server. If that is the problem, why did it just now start being a problem?
Any insight would be greatly appreciated.
email exchange-2010 email-server certificate email-bounces
asked Jun 14 '12 at 16:04
ThinkerIVThinkerIV
53127
add a comment |
A strange problem recently developed with one of my Exchange 2010 servers. I have an exchange server setup as part of a Windows Small Business Server 2011 installation. The email for the domain was working perfectly for 4 or 5 months, and now with no change in configuration is having problems.
The inbound email still works great, but when an email is sent it occasionally bounces back with one of several error messages. It doesn't happen to all of the sent emails, just some of them. It appears as though mail sent to certain domains will always bounce, including mail sent to domains that used to work. It also seems like the error message is generated by the recipients receiving server. Here are some of the error messages that bounce back:
host123.SomeEmailHost.com rejected your message to the following e-mail
addresses: Someone LastName (aperson@adomain.com)
host123.SomeEmailHost.com gave this error: Verification failed for
The mail server could not deliver mail to
sender@sendingdomain.net. The account or domain may not exist, they may be
blacklisted, or missing the proper dns entries. Sender verify failed
A problem occurred during the delivery of this message to this e-mail
address. Try sending this message again. If the problem continues,
please contact your helpdesk.
Here is another message received when sending to a different domain:
mail12.anotherhost.com rejected your message to the following e-mail
addresses: someoneelse lastname (someoneelse@anotherdomain.com)
(someoneelse@anotherdomain.com) mail12.anotherhost.com gave this error:
sorry, that address is not in my list of allowed recipients; no valid
cert for gatewaying (#5.7.1)
A problem occurred during the delivery
of this message to this e-mail address. Try sending this message
again. If the problem continues, please contact your helpdesk.
I have tried researching these errors, but have not turned up anything that seems applicable to my server. Is it some sort of certificate error. I am using a self signed certificate on the server. If that is the problem, why did it just now start being a problem?
Any insight would be greatly appreciated.
email exchange-2010 email-server certificate email-bounces
asked Jun 14 '12 at 16:04
ThinkerIVThinkerIV
53127
Do you have a PTR record configured for your outgoing IP for the Exchange server?
– Vick Vega
Oct 16 '15 at 14:50
add a comment |
A strange problem recently developed with one of my Exchange 2010 servers. I have an exchange server setup as part of a Windows Small Business Server 2011 installation. The email for the domain was working perfectly for 4 or 5 months, and now with no change in configuration is having problems.
The inbound email still works great, but when an email is sent it occasionally bounces back with one of several error messages. It doesn't happen to all of the sent emails, just some of them. It appears as though mail sent to certain domains will always bounce, including mail sent to domains that used to work. It also seems like the error message is generated by the recipients receiving server. Here are some of the error messages that bounce back:
host123.SomeEmailHost.com rejected your message to the following e-mail
addresses: Someone LastName (aperson@adomain.com)
host123.SomeEmailHost.com gave this error: Verification failed for
The mail server could not deliver mail to
sender@sendingdomain.net. The account or domain may not exist, they may be
blacklisted, or missing the proper dns entries. Sender verify failed
A problem occurred during the delivery of this message to this e-mail
address. Try sending this message again. If the problem continues,
please contact your helpdesk.
Here is another message received when sending to a different domain:
mail12.anotherhost.com rejected your message to the following e-mail
addresses: someoneelse lastname (someoneelse@anotherdomain.com)
(someoneelse@anotherdomain.com) mail12.anotherhost.com gave this error:
sorry, that address is not in my list of allowed recipients; no valid
cert for gatewaying (#5.7.1)
A problem occurred during the delivery
of this message to this e-mail address. Try sending this message
again. If the problem continues, please contact your helpdesk.
I have tried researching these errors, but have not turned up anything that seems applicable to my server. Is it some sort of certificate error. I am using a self signed certificate on the server. If that is the problem, why did it just now start being a problem?
Any insight would be greatly appreciated.
email exchange-2010 email-server certificate email-bounces
asked Jun 14 '12 at 16:04
ThinkerIVThinkerIV
53127
A strange problem recently developed with one of my Exchange 2010 servers. I have an exchange server setup as part of a Windows Small Business Server 2011 installation. The email for the domain was working perfectly for 4 or 5 months, and now with no change in configuration is having problems.
The inbound email still works great, but when an email is sent it occasionally bounces back with one of several error messages. It doesn't happen to all of the sent emails, just some of them. It appears as though mail sent to certain domains will always bounce, including mail sent to domains that used to work. It also seems like the error message is generated by the recipients receiving server. Here are some of the error messages that bounce back:
host123.SomeEmailHost.com rejected your message to the following e-mail
addresses: Someone LastName (aperson@adomain.com)
host123.SomeEmailHost.com gave this error: Verification failed for
The mail server could not deliver mail to
sender@sendingdomain.net. The account or domain may not exist, they may be
blacklisted, or missing the proper dns entries. Sender verify failed
A problem occurred during the delivery of this message to this e-mail
address. Try sending this message again. If the problem continues,
please contact your helpdesk.
Here is another message received when sending to a different domain:
mail12.anotherhost.com rejected your message to the following e-mail
addresses: someoneelse lastname (someoneelse@anotherdomain.com)
(someoneelse@anotherdomain.com) mail12.anotherhost.com gave this error:
sorry, that address is not in my list of allowed recipients; no valid
cert for gatewaying (#5.7.1)
A problem occurred during the delivery
of this message to this e-mail address. Try sending this message
again. If the problem continues, please contact your helpdesk.
I have tried researching these errors, but have not turned up anything that seems applicable to my server. Is it some sort of certificate error. I am using a self signed certificate on the server. If that is the problem, why did it just now start being a problem?
Any insight would be greatly appreciated.
email exchange-2010 email-server certificate email-bounces
email exchange-2010 email-server certificate email-bounces
asked Jun 14 '12 at 16:04
ThinkerIVThinkerIV
53127
asked Jun 14 '12 at 16:04
ThinkerIVThinkerIV
53127
asked Jun 14 '12 at 16:04
ThinkerIVThinkerIV
53127
asked Jun 14 '12 at 16:04
ThinkerIVThinkerIV
53127
asked Jun 14 '12 at 16:04
ThinkerIVThinkerIV
53127
53127
Do you have a PTR record configured for your outgoing IP for the Exchange server?
– Vick Vega
Oct 16 '15 at 14:50
add a comment |
Do you have a PTR record configured for your outgoing IP for the Exchange server?
– Vick Vega
Oct 16 '15 at 14:50
Do you have a PTR record configured for your outgoing IP for the Exchange server?
– Vick Vega
Oct 16 '15 at 14:50
Do you have a PTR record configured for your outgoing IP for the Exchange server?
– Vick Vega
Oct 16 '15 at 14:50
add a comment |
2 Answers
2
active
oldest
votes
Have you tested to see if you mail domain has been blacklisted? Another reason could be because the recipient is looking for a SPF dns entry for you domain. Have you created a SPF account?
answered Jun 20 '12 at 13:44
Jens KroghJens Krogh
161
I did a test to see if the domain is black listed. The test I ran checked in over 50 of the most popular black lists. It was not black listed in any of them. The domain does not have SPF records, I thought about it that that might be the problem. I will need to give that a try.
– ThinkerIV
Jun 26 '12 at 15:47
add a comment |
Recipient mail servers do a reverse DNS check to verify if the ip address from which the mail is being sent is authorised to do so. The recipient mail servers query the DNS to fetch the SPF and DKIM. These entries tell the recipient mail server the ip addresses that are authorised to send out email on behalf of the domain. Ideally creating a SPF for your domain should solve your problem.
If you have operated your email server without a SPF entry chances are that your ip has made it to one of the several blacklists. Use the mxlookup (google it please) and check the if the ip is listed and have your ip removed. The removal procedure is different for each of these lists.
answered Apr 15 '17 at 10:18
sridhar pandurangiahsridhar pandurangiah
4822823
You should laso consider creating a DKIM (Domain Keys Identified Email) record on your DNS. Some email servers look for DKIM.
– sridhar pandurangiah
Apr 21 '17 at 7:20
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f398812%2frecipients-auto-rejecting-emails-sent-with-exchange-2010-certificate-error%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Have you tested to see if you mail domain has been blacklisted? Another reason could be because the recipient is looking for a SPF dns entry for you domain. Have you created a SPF account?
answered Jun 20 '12 at 13:44
Jens KroghJens Krogh
161
I did a test to see if the domain is black listed. The test I ran checked in over 50 of the most popular black lists. It was not black listed in any of them. The domain does not have SPF records, I thought about it that that might be the problem. I will need to give that a try.
– ThinkerIV
Jun 26 '12 at 15:47
add a comment |
Have you tested to see if you mail domain has been blacklisted? Another reason could be because the recipient is looking for a SPF dns entry for you domain. Have you created a SPF account?
answered Jun 20 '12 at 13:44
Jens KroghJens Krogh
161
I did a test to see if the domain is black listed. The test I ran checked in over 50 of the most popular black lists. It was not black listed in any of them. The domain does not have SPF records, I thought about it that that might be the problem. I will need to give that a try.
– ThinkerIV
Jun 26 '12 at 15:47
add a comment |
Have you tested to see if you mail domain has been blacklisted? Another reason could be because the recipient is looking for a SPF dns entry for you domain. Have you created a SPF account?
answered Jun 20 '12 at 13:44
Jens KroghJens Krogh
161
Have you tested to see if you mail domain has been blacklisted? Another reason could be because the recipient is looking for a SPF dns entry for you domain. Have you created a SPF account?
answered Jun 20 '12 at 13:44
Jens KroghJens Krogh
161
answered Jun 20 '12 at 13:44
Jens KroghJens Krogh
161
answered Jun 20 '12 at 13:44
Jens KroghJens Krogh
161
answered Jun 20 '12 at 13:44
Jens KroghJens Krogh
161
161
I did a test to see if the domain is black listed. The test I ran checked in over 50 of the most popular black lists. It was not black listed in any of them. The domain does not have SPF records, I thought about it that that might be the problem. I will need to give that a try.
– ThinkerIV
Jun 26 '12 at 15:47
add a comment |
I did a test to see if the domain is black listed. The test I ran checked in over 50 of the most popular black lists. It was not black listed in any of them. The domain does not have SPF records, I thought about it that that might be the problem. I will need to give that a try.
– ThinkerIV
Jun 26 '12 at 15:47
I did a test to see if the domain is black listed. The test I ran checked in over 50 of the most popular black lists. It was not black listed in any of them. The domain does not have SPF records, I thought about it that that might be the problem. I will need to give that a try.
– ThinkerIV
Jun 26 '12 at 15:47
I did a test to see if the domain is black listed. The test I ran checked in over 50 of the most popular black lists. It was not black listed in any of them. The domain does not have SPF records, I thought about it that that might be the problem. I will need to give that a try.
– ThinkerIV
Jun 26 '12 at 15:47
add a comment |
Recipient mail servers do a reverse DNS check to verify if the ip address from which the mail is being sent is authorised to do so. The recipient mail servers query the DNS to fetch the SPF and DKIM. These entries tell the recipient mail server the ip addresses that are authorised to send out email on behalf of the domain. Ideally creating a SPF for your domain should solve your problem.
If you have operated your email server without a SPF entry chances are that your ip has made it to one of the several blacklists. Use the mxlookup (google it please) and check the if the ip is listed and have your ip removed. The removal procedure is different for each of these lists.
answered Apr 15 '17 at 10:18
sridhar pandurangiahsridhar pandurangiah
4822823
You should laso consider creating a DKIM (Domain Keys Identified Email) record on your DNS. Some email servers look for DKIM.
– sridhar pandurangiah
Apr 21 '17 at 7:20
add a comment |
Recipient mail servers do a reverse DNS check to verify if the ip address from which the mail is being sent is authorised to do so. The recipient mail servers query the DNS to fetch the SPF and DKIM. These entries tell the recipient mail server the ip addresses that are authorised to send out email on behalf of the domain. Ideally creating a SPF for your domain should solve your problem.
If you have operated your email server without a SPF entry chances are that your ip has made it to one of the several blacklists. Use the mxlookup (google it please) and check the if the ip is listed and have your ip removed. The removal procedure is different for each of these lists.
answered Apr 15 '17 at 10:18
sridhar pandurangiahsridhar pandurangiah
4822823
You should laso consider creating a DKIM (Domain Keys Identified Email) record on your DNS. Some email servers look for DKIM.
– sridhar pandurangiah
Apr 21 '17 at 7:20
add a comment |
Recipient mail servers do a reverse DNS check to verify if the ip address from which the mail is being sent is authorised to do so. The recipient mail servers query the DNS to fetch the SPF and DKIM. These entries tell the recipient mail server the ip addresses that are authorised to send out email on behalf of the domain. Ideally creating a SPF for your domain should solve your problem.
If you have operated your email server without a SPF entry chances are that your ip has made it to one of the several blacklists. Use the mxlookup (google it please) and check the if the ip is listed and have your ip removed. The removal procedure is different for each of these lists.
answered Apr 15 '17 at 10:18
sridhar pandurangiahsridhar pandurangiah
4822823
Recipient mail servers do a reverse DNS check to verify if the ip address from which the mail is being sent is authorised to do so. The recipient mail servers query the DNS to fetch the SPF and DKIM. These entries tell the recipient mail server the ip addresses that are authorised to send out email on behalf of the domain. Ideally creating a SPF for your domain should solve your problem.
If you have operated your email server without a SPF entry chances are that your ip has made it to one of the several blacklists. Use the mxlookup (google it please) and check the if the ip is listed and have your ip removed. The removal procedure is different for each of these lists.
answered Apr 15 '17 at 10:18
sridhar pandurangiahsridhar pandurangiah
4822823
answered Apr 15 '17 at 10:18
sridhar pandurangiahsridhar pandurangiah
4822823
answered Apr 15 '17 at 10:18
sridhar pandurangiahsridhar pandurangiah
4822823
answered Apr 15 '17 at 10:18
sridhar pandurangiahsridhar pandurangiah
4822823
4822823
You should laso consider creating a DKIM (Domain Keys Identified Email) record on your DNS. Some email servers look for DKIM.
– sridhar pandurangiah
Apr 21 '17 at 7:20
add a comment |
You should laso consider creating a DKIM (Domain Keys Identified Email) record on your DNS. Some email servers look for DKIM.
– sridhar pandurangiah
Apr 21 '17 at 7:20
You should laso consider creating a DKIM (Domain Keys Identified Email) record on your DNS. Some email servers look for DKIM.
– sridhar pandurangiah
Apr 21 '17 at 7:20
You should laso consider creating a DKIM (Domain Keys Identified Email) record on your DNS. Some email servers look for DKIM.
– sridhar pandurangiah
Apr 21 '17 at 7:20
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f398812%2frecipients-auto-rejecting-emails-sent-with-exchange-2010-certificate-error%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Do you have a PTR record configured for your outgoing IP for the Exchange server?
– Vick Vega
Oct 16 '15 at 14:50