Forum Discussion
messg spam from my office email to yahoo
when i send a mesg from my office to yahoo , the message enter to inbox folder , then after 1min or 2min , the message fall to junk folder , can someone help me with this , or explain to me what goi...
Unfortentually we didn't go with sendgrid.
They flagged my signup as suspicious, and after wasting 2 days with their support, and them coming back with, "Please provide your LinkedIn info to verify your identity" made me just switch to proofpoint. SMTP2GO was another option, and they "said" you can use their API with O365, their documentation was very generic, and just went over the API on their side without vetting any configuration with O365. I don't think the rep fully understood what I was trying to accomplish since why would anyone normally would want to send all their email out O365 through a SMTP relay service.
Just switched mail flow to proofpoint not too long ago for our client. Here what was found.
Sending from our mailbox in the customer's domain, that we previously stated not as spam in our att mailbox, ended up in the spam folder.
Sending email from a new or a mailbox we haven't tested with in the past, from the customer domain, does not end up in the spam folder to our att test mailbox.
We created a new mailbox at aol.com
Found that all emails went through without issues.
Coworker's yahoo mailbox also received the messages without issues from the customer's domain. At first it did end up in the spam, but appeared to clear up without his interaction with the second email. At this time I also stopped DKIM signing from Microsoft, and did it directly from proofpoint.
Had the CEO of the client email those three mailboxes, all went through, nothing ended up in spam.
(not related but for the lulz)
Emailed from my AOL test box and to my att test one, and vice versa. both ended up in spam lol
I don't have the complete warm and fuzzies considering how mail I once flagged as not spam, ended back up in the spam box. I'll take this improvement through. Will have to monitor it over the next few days.
Why do I think this isn't a Microsoft problem?
Because the client also uses a 3rd party website used for volunteer signup.
While I do have to address this with the end-user who manages it. While the From domain, sends out with the website's domain name, the reply to is set to the customer's domain. This voulentier sign up a website also doesn't support DKIM, thus I see the fails in my DMARC reports for DKIM from yahoo.com, and co.
But yet.. all of that mail goes through and gets to yahoo.com's inbox, even though its failing DKIM. I only have DMARC in reporting mode at this time until I can clean it up.
So scottchester it seems like we were able to get around this problem using a spam filtering service that can filter/relay outbound. While more costly than a SMTP relay service, I at least have emails that would of ended up in the spam folder, in the inbox now.
Though while I don't think it would be the case here. Are all of you that are having issues signing DKIM outbound from O365? As at first, I figured I was going to have mix results with this until I removed DKIM signing on microsoft's side and just had Proofpoint doing it. It actually made a difference. Could be nothing and just things straightening its self out from the changeover, as I can't see why a DKIM signature from Microsoft in the message headers would trip yahoo mail services to flag it as spam..
But at this point, if mail gets to the inbox for yahoo mailservices domains. I really don't care what it was lol
They flagged my signup as suspicious, and after wasting 2 days with their support, and them coming back with, "Please provide your LinkedIn info to verify your identity" made me just switch to proofpoint. SMTP2GO was another option, and they "said" you can use their API with O365, their documentation was very generic, and just went over the API on their side without vetting any configuration with O365. I don't think the rep fully understood what I was trying to accomplish since why would anyone normally would want to send all their email out O365 through a SMTP relay service.
Just switched mail flow to proofpoint not too long ago for our client. Here what was found.
Sending from our mailbox in the customer's domain, that we previously stated not as spam in our att mailbox, ended up in the spam folder.
Sending email from a new or a mailbox we haven't tested with in the past, from the customer domain, does not end up in the spam folder to our att test mailbox.
We created a new mailbox at aol.com
Found that all emails went through without issues.
Coworker's yahoo mailbox also received the messages without issues from the customer's domain. At first it did end up in the spam, but appeared to clear up without his interaction with the second email. At this time I also stopped DKIM signing from Microsoft, and did it directly from proofpoint.
Had the CEO of the client email those three mailboxes, all went through, nothing ended up in spam.
(not related but for the lulz)
Emailed from my AOL test box and to my att test one, and vice versa. both ended up in spam lol
I don't have the complete warm and fuzzies considering how mail I once flagged as not spam, ended back up in the spam box. I'll take this improvement through. Will have to monitor it over the next few days.
Why do I think this isn't a Microsoft problem?
Because the client also uses a 3rd party website used for volunteer signup.
While I do have to address this with the end-user who manages it. While the From domain, sends out with the website's domain name, the reply to is set to the customer's domain. This voulentier sign up a website also doesn't support DKIM, thus I see the fails in my DMARC reports for DKIM from yahoo.com, and co.
But yet.. all of that mail goes through and gets to yahoo.com's inbox, even though its failing DKIM. I only have DMARC in reporting mode at this time until I can clean it up.
So scottchester it seems like we were able to get around this problem using a spam filtering service that can filter/relay outbound. While more costly than a SMTP relay service, I at least have emails that would of ended up in the spam folder, in the inbox now.
Though while I don't think it would be the case here. Are all of you that are having issues signing DKIM outbound from O365? As at first, I figured I was going to have mix results with this until I removed DKIM signing on microsoft's side and just had Proofpoint doing it. It actually made a difference. Could be nothing and just things straightening its self out from the changeover, as I can't see why a DKIM signature from Microsoft in the message headers would trip yahoo mail services to flag it as spam..
But at this point, if mail gets to the inbox for yahoo mailservices domains. I really don't care what it was lol
NLart glad to see you found a workaround.
My first thought is that the IP of your website must be better than Microsoft's, but that's an interesting data point about emailing from att to yahoo and it ending up in the spam.
It seems like probably yahoo and microsoft both have something they could learn here. I kept thinking MS reputation was the issue since that's the clear error we get when some emails fail to charter.net.
Our emails going through smtp2go are dkim signed from both MS and smtp2go and making it into the inbox. I didn't test not signing messages from Microsoft.
I'm with you, I'm kind of over troubleshooting this problem when no one at Microsoft or Yahoo seems to care. It's unfortunate!
My first thought is that the IP of your website must be better than Microsoft's, but that's an interesting data point about emailing from att to yahoo and it ending up in the spam.
It seems like probably yahoo and microsoft both have something they could learn here. I kept thinking MS reputation was the issue since that's the clear error we get when some emails fail to charter.net.
Our emails going through smtp2go are dkim signed from both MS and smtp2go and making it into the inbox. I didn't test not signing messages from Microsoft.
I'm with you, I'm kind of over troubleshooting this problem when no one at Microsoft or Yahoo seems to care. It's unfortunate!