Emails send from rails with O365 being rejected as spam
I have a Rails 5 app deployed on Heroku. I'm using devise for email and have setup everything correctly to send password reset emails. This works perfectly in my dev environment. However, when I send from production I get an error in my 0365 inbox that says:
Generating server: CO2PR13MB0140.namprd13.prod.outlook.com
myemail@gmail.com
Remote Server returned '550 5.7.708 Service unavailable. Access denied, traffic
not accepted from this IP. For more information please go to
http://go.microsoft.com/fwlink/?LinkId=526653 AS(8561)
[CO2PR13MB0124.namprd13.prod.outlook.com]'
Original message headers:
Received: from CO2PR13MB0140.namprd13.prod.outlook.com
([fe80::c872:9c6:9d6a:8b3]) by CO2PR13MB0140.namprd13.prod.outlook.com
([fe80::c872:9c6:9d6a:8b3%4]) with mapi id 15.20.1339.019; Wed, 14 Nov 2018
02:42:20 +0000
MIME-Version: 1.0
Content-Type: text/plain
Date: Wed, 14 Nov 2018 02:42:20 +0000
Message-ID:
<5beb8b87e888a_42b06292aba70609bd@01184e4c-2116-478b-a773-fcc26ac206aa.mail>
Subject: Reset password instructions
In looking into this, and talking to support, it appears that the it's being rejected because a third party server is (my app on Heroku I'm assuming) is trying to send out the email with 0365 settings.
Here are my development.rb settings that work perfectly:
# Don't care if the mailer can't send.
config.action_mailer.raise_delivery_errors = true
config.action_mailer.perform_caching = true
config.action_mailer.default_url_options = :host => 'localhost:3000'
config.action_mailer.delivery_method = :smtp
config.action_mailer.smtp_settings =
:address => 'smtp.office365.com',
:port => '587',
:authentication => :login,
:user_name => ENV['365_USERNAME'],
:password => ENV['365_PASSWORD'],
:domain => 'mysite.com',
:enable_starttls_auto => true
Here are my production.rb settings that cause O365 to reject the email. I've tried playing with these quite a bit. And I've ensured that the "from" email matches the login email. i.e. I'm not trying to send from no-reply@mysite.com or similar.
config.action_mailer.raise_delivery_errors = true
config.action_mailer.perform_caching = false
config.action_mailer.default_url_options = :host => 'www.mysite.com'
config.action_mailer.delivery_method = :smtp
config.action_mailer.smtp_settings =
:address => 'smtp.office365.com',
:port => '587',
:authentication => :login,
:user_name => ENV['365_USERNAME'],
:password => ENV['365_PASSWORD'],
:domain => 'mysite.com',
:enable_starttls_auto => true
From discussions with support. I may need to add an SPF TXT record to allow emails to be sent from a remote server. The problem is, I have no idea what to add to the SPF record. My current spf record is:
v=spf1 include:spf.protection.outlook.com -all
ruby-on-rails email heroku spf
add a comment |
I have a Rails 5 app deployed on Heroku. I'm using devise for email and have setup everything correctly to send password reset emails. This works perfectly in my dev environment. However, when I send from production I get an error in my 0365 inbox that says:
Generating server: CO2PR13MB0140.namprd13.prod.outlook.com
myemail@gmail.com
Remote Server returned '550 5.7.708 Service unavailable. Access denied, traffic
not accepted from this IP. For more information please go to
http://go.microsoft.com/fwlink/?LinkId=526653 AS(8561)
[CO2PR13MB0124.namprd13.prod.outlook.com]'
Original message headers:
Received: from CO2PR13MB0140.namprd13.prod.outlook.com
([fe80::c872:9c6:9d6a:8b3]) by CO2PR13MB0140.namprd13.prod.outlook.com
([fe80::c872:9c6:9d6a:8b3%4]) with mapi id 15.20.1339.019; Wed, 14 Nov 2018
02:42:20 +0000
MIME-Version: 1.0
Content-Type: text/plain
Date: Wed, 14 Nov 2018 02:42:20 +0000
Message-ID:
<5beb8b87e888a_42b06292aba70609bd@01184e4c-2116-478b-a773-fcc26ac206aa.mail>
Subject: Reset password instructions
In looking into this, and talking to support, it appears that the it's being rejected because a third party server is (my app on Heroku I'm assuming) is trying to send out the email with 0365 settings.
Here are my development.rb settings that work perfectly:
# Don't care if the mailer can't send.
config.action_mailer.raise_delivery_errors = true
config.action_mailer.perform_caching = true
config.action_mailer.default_url_options = :host => 'localhost:3000'
config.action_mailer.delivery_method = :smtp
config.action_mailer.smtp_settings =
:address => 'smtp.office365.com',
:port => '587',
:authentication => :login,
:user_name => ENV['365_USERNAME'],
:password => ENV['365_PASSWORD'],
:domain => 'mysite.com',
:enable_starttls_auto => true
Here are my production.rb settings that cause O365 to reject the email. I've tried playing with these quite a bit. And I've ensured that the "from" email matches the login email. i.e. I'm not trying to send from no-reply@mysite.com or similar.
config.action_mailer.raise_delivery_errors = true
config.action_mailer.perform_caching = false
config.action_mailer.default_url_options = :host => 'www.mysite.com'
config.action_mailer.delivery_method = :smtp
config.action_mailer.smtp_settings =
:address => 'smtp.office365.com',
:port => '587',
:authentication => :login,
:user_name => ENV['365_USERNAME'],
:password => ENV['365_PASSWORD'],
:domain => 'mysite.com',
:enable_starttls_auto => true
From discussions with support. I may need to add an SPF TXT record to allow emails to be sent from a remote server. The problem is, I have no idea what to add to the SPF record. My current spf record is:
v=spf1 include:spf.protection.outlook.com -all
ruby-on-rails email heroku spf
add a comment |
I have a Rails 5 app deployed on Heroku. I'm using devise for email and have setup everything correctly to send password reset emails. This works perfectly in my dev environment. However, when I send from production I get an error in my 0365 inbox that says:
Generating server: CO2PR13MB0140.namprd13.prod.outlook.com
myemail@gmail.com
Remote Server returned '550 5.7.708 Service unavailable. Access denied, traffic
not accepted from this IP. For more information please go to
http://go.microsoft.com/fwlink/?LinkId=526653 AS(8561)
[CO2PR13MB0124.namprd13.prod.outlook.com]'
Original message headers:
Received: from CO2PR13MB0140.namprd13.prod.outlook.com
([fe80::c872:9c6:9d6a:8b3]) by CO2PR13MB0140.namprd13.prod.outlook.com
([fe80::c872:9c6:9d6a:8b3%4]) with mapi id 15.20.1339.019; Wed, 14 Nov 2018
02:42:20 +0000
MIME-Version: 1.0
Content-Type: text/plain
Date: Wed, 14 Nov 2018 02:42:20 +0000
Message-ID:
<5beb8b87e888a_42b06292aba70609bd@01184e4c-2116-478b-a773-fcc26ac206aa.mail>
Subject: Reset password instructions
In looking into this, and talking to support, it appears that the it's being rejected because a third party server is (my app on Heroku I'm assuming) is trying to send out the email with 0365 settings.
Here are my development.rb settings that work perfectly:
# Don't care if the mailer can't send.
config.action_mailer.raise_delivery_errors = true
config.action_mailer.perform_caching = true
config.action_mailer.default_url_options = :host => 'localhost:3000'
config.action_mailer.delivery_method = :smtp
config.action_mailer.smtp_settings =
:address => 'smtp.office365.com',
:port => '587',
:authentication => :login,
:user_name => ENV['365_USERNAME'],
:password => ENV['365_PASSWORD'],
:domain => 'mysite.com',
:enable_starttls_auto => true
Here are my production.rb settings that cause O365 to reject the email. I've tried playing with these quite a bit. And I've ensured that the "from" email matches the login email. i.e. I'm not trying to send from no-reply@mysite.com or similar.
config.action_mailer.raise_delivery_errors = true
config.action_mailer.perform_caching = false
config.action_mailer.default_url_options = :host => 'www.mysite.com'
config.action_mailer.delivery_method = :smtp
config.action_mailer.smtp_settings =
:address => 'smtp.office365.com',
:port => '587',
:authentication => :login,
:user_name => ENV['365_USERNAME'],
:password => ENV['365_PASSWORD'],
:domain => 'mysite.com',
:enable_starttls_auto => true
From discussions with support. I may need to add an SPF TXT record to allow emails to be sent from a remote server. The problem is, I have no idea what to add to the SPF record. My current spf record is:
v=spf1 include:spf.protection.outlook.com -all
ruby-on-rails email heroku spf
I have a Rails 5 app deployed on Heroku. I'm using devise for email and have setup everything correctly to send password reset emails. This works perfectly in my dev environment. However, when I send from production I get an error in my 0365 inbox that says:
Generating server: CO2PR13MB0140.namprd13.prod.outlook.com
myemail@gmail.com
Remote Server returned '550 5.7.708 Service unavailable. Access denied, traffic
not accepted from this IP. For more information please go to
http://go.microsoft.com/fwlink/?LinkId=526653 AS(8561)
[CO2PR13MB0124.namprd13.prod.outlook.com]'
Original message headers:
Received: from CO2PR13MB0140.namprd13.prod.outlook.com
([fe80::c872:9c6:9d6a:8b3]) by CO2PR13MB0140.namprd13.prod.outlook.com
([fe80::c872:9c6:9d6a:8b3%4]) with mapi id 15.20.1339.019; Wed, 14 Nov 2018
02:42:20 +0000
MIME-Version: 1.0
Content-Type: text/plain
Date: Wed, 14 Nov 2018 02:42:20 +0000
Message-ID:
<5beb8b87e888a_42b06292aba70609bd@01184e4c-2116-478b-a773-fcc26ac206aa.mail>
Subject: Reset password instructions
In looking into this, and talking to support, it appears that the it's being rejected because a third party server is (my app on Heroku I'm assuming) is trying to send out the email with 0365 settings.
Here are my development.rb settings that work perfectly:
# Don't care if the mailer can't send.
config.action_mailer.raise_delivery_errors = true
config.action_mailer.perform_caching = true
config.action_mailer.default_url_options = :host => 'localhost:3000'
config.action_mailer.delivery_method = :smtp
config.action_mailer.smtp_settings =
:address => 'smtp.office365.com',
:port => '587',
:authentication => :login,
:user_name => ENV['365_USERNAME'],
:password => ENV['365_PASSWORD'],
:domain => 'mysite.com',
:enable_starttls_auto => true
Here are my production.rb settings that cause O365 to reject the email. I've tried playing with these quite a bit. And I've ensured that the "from" email matches the login email. i.e. I'm not trying to send from no-reply@mysite.com or similar.
config.action_mailer.raise_delivery_errors = true
config.action_mailer.perform_caching = false
config.action_mailer.default_url_options = :host => 'www.mysite.com'
config.action_mailer.delivery_method = :smtp
config.action_mailer.smtp_settings =
:address => 'smtp.office365.com',
:port => '587',
:authentication => :login,
:user_name => ENV['365_USERNAME'],
:password => ENV['365_PASSWORD'],
:domain => 'mysite.com',
:enable_starttls_auto => true
From discussions with support. I may need to add an SPF TXT record to allow emails to be sent from a remote server. The problem is, I have no idea what to add to the SPF record. My current spf record is:
v=spf1 include:spf.protection.outlook.com -all
ruby-on-rails email heroku spf
ruby-on-rails email heroku spf
asked Nov 14 '18 at 3:15
Dustin MaxeyDustin Maxey
8012
8012
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Their response just says they have blacklisted your IP, so it’s not down to your message content.
If you are sending from Heroku, you may need to list them in your SPF as well. Also ensure that your host name resolves backwards as well as forwards - that should be possible in Heroku’s control panel.
Once you’ve done that, check your SPF record gives a pass to your message source using kitterman.com or mxtoolbox testing services.
O365’s spam filter and blocking policy is pretty bad anyway, however I have had success in asking their support to remove blocks, though you need to persevere because they reject all such requests by default. This is poor service, but it’s still far better than you will get from gmail.
Thanks. I appreceiate the info and reply. I'm no expert at domain mgmt, so I have a couple, probably pretty basic, questions: 1) Can you elaborate on what you mean by "resolves backward and forwards"? 2) How would I "list Heroku in my SPF" Would I add heroku.com, the equivalent IP address, mysite.com, or something else?
– Dustin Maxey
Nov 14 '18 at 13:45
That's a DNS thing - if you look upyourhost.example.com
, you'll get an IP address - that's a forward lookup. If you then look up that IP (a reverse lookup), it should get back the same host name you started with. Setting that entry is normally done by your ISP, and they usually let you do it via a control panel. Before changing your live SPF record, stick your proposed values into Scott's site to check them.
– Synchro
Nov 14 '18 at 14:41
BTW, if you follow the link in the error message and look up the error code (5.7.708
), it says it's due to "The majority of traffic from this tenant has been detected as suspicious". There is also a document about their delisting portal.
– Synchro
Nov 14 '18 at 14:43
I did see that. I'm testing my devise authN setup in rails so sent a ton of PW reset requests to myself. I'm guessing that's what set it off. Oddly, I've done similar things before with the same rails/heroku setup and haven't run into this issue. I'll look into this more today. Thanks!
– Dustin Maxey
Nov 14 '18 at 15:46
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
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%2fstackoverflow.com%2fquestions%2f53292684%2femails-send-from-rails-with-o365-being-rejected-as-spam%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Their response just says they have blacklisted your IP, so it’s not down to your message content.
If you are sending from Heroku, you may need to list them in your SPF as well. Also ensure that your host name resolves backwards as well as forwards - that should be possible in Heroku’s control panel.
Once you’ve done that, check your SPF record gives a pass to your message source using kitterman.com or mxtoolbox testing services.
O365’s spam filter and blocking policy is pretty bad anyway, however I have had success in asking their support to remove blocks, though you need to persevere because they reject all such requests by default. This is poor service, but it’s still far better than you will get from gmail.
Thanks. I appreceiate the info and reply. I'm no expert at domain mgmt, so I have a couple, probably pretty basic, questions: 1) Can you elaborate on what you mean by "resolves backward and forwards"? 2) How would I "list Heroku in my SPF" Would I add heroku.com, the equivalent IP address, mysite.com, or something else?
– Dustin Maxey
Nov 14 '18 at 13:45
That's a DNS thing - if you look upyourhost.example.com
, you'll get an IP address - that's a forward lookup. If you then look up that IP (a reverse lookup), it should get back the same host name you started with. Setting that entry is normally done by your ISP, and they usually let you do it via a control panel. Before changing your live SPF record, stick your proposed values into Scott's site to check them.
– Synchro
Nov 14 '18 at 14:41
BTW, if you follow the link in the error message and look up the error code (5.7.708
), it says it's due to "The majority of traffic from this tenant has been detected as suspicious". There is also a document about their delisting portal.
– Synchro
Nov 14 '18 at 14:43
I did see that. I'm testing my devise authN setup in rails so sent a ton of PW reset requests to myself. I'm guessing that's what set it off. Oddly, I've done similar things before with the same rails/heroku setup and haven't run into this issue. I'll look into this more today. Thanks!
– Dustin Maxey
Nov 14 '18 at 15:46
add a comment |
Their response just says they have blacklisted your IP, so it’s not down to your message content.
If you are sending from Heroku, you may need to list them in your SPF as well. Also ensure that your host name resolves backwards as well as forwards - that should be possible in Heroku’s control panel.
Once you’ve done that, check your SPF record gives a pass to your message source using kitterman.com or mxtoolbox testing services.
O365’s spam filter and blocking policy is pretty bad anyway, however I have had success in asking their support to remove blocks, though you need to persevere because they reject all such requests by default. This is poor service, but it’s still far better than you will get from gmail.
Thanks. I appreceiate the info and reply. I'm no expert at domain mgmt, so I have a couple, probably pretty basic, questions: 1) Can you elaborate on what you mean by "resolves backward and forwards"? 2) How would I "list Heroku in my SPF" Would I add heroku.com, the equivalent IP address, mysite.com, or something else?
– Dustin Maxey
Nov 14 '18 at 13:45
That's a DNS thing - if you look upyourhost.example.com
, you'll get an IP address - that's a forward lookup. If you then look up that IP (a reverse lookup), it should get back the same host name you started with. Setting that entry is normally done by your ISP, and they usually let you do it via a control panel. Before changing your live SPF record, stick your proposed values into Scott's site to check them.
– Synchro
Nov 14 '18 at 14:41
BTW, if you follow the link in the error message and look up the error code (5.7.708
), it says it's due to "The majority of traffic from this tenant has been detected as suspicious". There is also a document about their delisting portal.
– Synchro
Nov 14 '18 at 14:43
I did see that. I'm testing my devise authN setup in rails so sent a ton of PW reset requests to myself. I'm guessing that's what set it off. Oddly, I've done similar things before with the same rails/heroku setup and haven't run into this issue. I'll look into this more today. Thanks!
– Dustin Maxey
Nov 14 '18 at 15:46
add a comment |
Their response just says they have blacklisted your IP, so it’s not down to your message content.
If you are sending from Heroku, you may need to list them in your SPF as well. Also ensure that your host name resolves backwards as well as forwards - that should be possible in Heroku’s control panel.
Once you’ve done that, check your SPF record gives a pass to your message source using kitterman.com or mxtoolbox testing services.
O365’s spam filter and blocking policy is pretty bad anyway, however I have had success in asking their support to remove blocks, though you need to persevere because they reject all such requests by default. This is poor service, but it’s still far better than you will get from gmail.
Their response just says they have blacklisted your IP, so it’s not down to your message content.
If you are sending from Heroku, you may need to list them in your SPF as well. Also ensure that your host name resolves backwards as well as forwards - that should be possible in Heroku’s control panel.
Once you’ve done that, check your SPF record gives a pass to your message source using kitterman.com or mxtoolbox testing services.
O365’s spam filter and blocking policy is pretty bad anyway, however I have had success in asking their support to remove blocks, though you need to persevere because they reject all such requests by default. This is poor service, but it’s still far better than you will get from gmail.
answered Nov 14 '18 at 8:32
SynchroSynchro
18.1k85271
18.1k85271
Thanks. I appreceiate the info and reply. I'm no expert at domain mgmt, so I have a couple, probably pretty basic, questions: 1) Can you elaborate on what you mean by "resolves backward and forwards"? 2) How would I "list Heroku in my SPF" Would I add heroku.com, the equivalent IP address, mysite.com, or something else?
– Dustin Maxey
Nov 14 '18 at 13:45
That's a DNS thing - if you look upyourhost.example.com
, you'll get an IP address - that's a forward lookup. If you then look up that IP (a reverse lookup), it should get back the same host name you started with. Setting that entry is normally done by your ISP, and they usually let you do it via a control panel. Before changing your live SPF record, stick your proposed values into Scott's site to check them.
– Synchro
Nov 14 '18 at 14:41
BTW, if you follow the link in the error message and look up the error code (5.7.708
), it says it's due to "The majority of traffic from this tenant has been detected as suspicious". There is also a document about their delisting portal.
– Synchro
Nov 14 '18 at 14:43
I did see that. I'm testing my devise authN setup in rails so sent a ton of PW reset requests to myself. I'm guessing that's what set it off. Oddly, I've done similar things before with the same rails/heroku setup and haven't run into this issue. I'll look into this more today. Thanks!
– Dustin Maxey
Nov 14 '18 at 15:46
add a comment |
Thanks. I appreceiate the info and reply. I'm no expert at domain mgmt, so I have a couple, probably pretty basic, questions: 1) Can you elaborate on what you mean by "resolves backward and forwards"? 2) How would I "list Heroku in my SPF" Would I add heroku.com, the equivalent IP address, mysite.com, or something else?
– Dustin Maxey
Nov 14 '18 at 13:45
That's a DNS thing - if you look upyourhost.example.com
, you'll get an IP address - that's a forward lookup. If you then look up that IP (a reverse lookup), it should get back the same host name you started with. Setting that entry is normally done by your ISP, and they usually let you do it via a control panel. Before changing your live SPF record, stick your proposed values into Scott's site to check them.
– Synchro
Nov 14 '18 at 14:41
BTW, if you follow the link in the error message and look up the error code (5.7.708
), it says it's due to "The majority of traffic from this tenant has been detected as suspicious". There is also a document about their delisting portal.
– Synchro
Nov 14 '18 at 14:43
I did see that. I'm testing my devise authN setup in rails so sent a ton of PW reset requests to myself. I'm guessing that's what set it off. Oddly, I've done similar things before with the same rails/heroku setup and haven't run into this issue. I'll look into this more today. Thanks!
– Dustin Maxey
Nov 14 '18 at 15:46
Thanks. I appreceiate the info and reply. I'm no expert at domain mgmt, so I have a couple, probably pretty basic, questions: 1) Can you elaborate on what you mean by "resolves backward and forwards"? 2) How would I "list Heroku in my SPF" Would I add heroku.com, the equivalent IP address, mysite.com, or something else?
– Dustin Maxey
Nov 14 '18 at 13:45
Thanks. I appreceiate the info and reply. I'm no expert at domain mgmt, so I have a couple, probably pretty basic, questions: 1) Can you elaborate on what you mean by "resolves backward and forwards"? 2) How would I "list Heroku in my SPF" Would I add heroku.com, the equivalent IP address, mysite.com, or something else?
– Dustin Maxey
Nov 14 '18 at 13:45
That's a DNS thing - if you look up
yourhost.example.com
, you'll get an IP address - that's a forward lookup. If you then look up that IP (a reverse lookup), it should get back the same host name you started with. Setting that entry is normally done by your ISP, and they usually let you do it via a control panel. Before changing your live SPF record, stick your proposed values into Scott's site to check them.– Synchro
Nov 14 '18 at 14:41
That's a DNS thing - if you look up
yourhost.example.com
, you'll get an IP address - that's a forward lookup. If you then look up that IP (a reverse lookup), it should get back the same host name you started with. Setting that entry is normally done by your ISP, and they usually let you do it via a control panel. Before changing your live SPF record, stick your proposed values into Scott's site to check them.– Synchro
Nov 14 '18 at 14:41
BTW, if you follow the link in the error message and look up the error code (
5.7.708
), it says it's due to "The majority of traffic from this tenant has been detected as suspicious". There is also a document about their delisting portal.– Synchro
Nov 14 '18 at 14:43
BTW, if you follow the link in the error message and look up the error code (
5.7.708
), it says it's due to "The majority of traffic from this tenant has been detected as suspicious". There is also a document about their delisting portal.– Synchro
Nov 14 '18 at 14:43
I did see that. I'm testing my devise authN setup in rails so sent a ton of PW reset requests to myself. I'm guessing that's what set it off. Oddly, I've done similar things before with the same rails/heroku setup and haven't run into this issue. I'll look into this more today. Thanks!
– Dustin Maxey
Nov 14 '18 at 15:46
I did see that. I'm testing my devise authN setup in rails so sent a ton of PW reset requests to myself. I'm guessing that's what set it off. Oddly, I've done similar things before with the same rails/heroku setup and haven't run into this issue. I'll look into this more today. Thanks!
– Dustin Maxey
Nov 14 '18 at 15:46
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f53292684%2femails-send-from-rails-with-o365-being-rejected-as-spam%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