Marketing Campaign E-mail and Office365 - Check My Logic, Please
- 
 @NetworkNerd said in Marketing Campaign E-mail and Office365 - Check My Logic, Please: Would adding users with internal e-mail addresses to Safe Senders allow the messages to come through the filter to internal recipients as expected? That's kind of like an individualized whitelist in the O365 world, right? I would expect so, yes. 
- 
 That makes sense, the email is coming as if it was from that server because it believes that it itself is the master of the domain. 
- 
 You can also create a transport rule that will bypass all the spam filtering heuristics and whatnot. 
- 
 @NetworkNerd said in Marketing Campaign E-mail and Office365 - Check My Logic, Please: Would adding users with internal e-mail addresses to Safe Senders allow the messages to come through the filter to internal recipients as expected? That's kind of like an individualized whitelist in the O365 world, right? I wouldn't do this. A lot of spammers put the from and to address the same for this reason. If you whitelist all your internal addresses, I would think you would get a lot of spam. 
- 
 @Kelly said in Marketing Campaign E-mail and Office365 - Check My Logic, Please: You can also create a transport rule that will bypass all the spam filtering heuristics and whatnot. Nothing gets around 100% of the rules from what I was reading on this two years ago. 
- 
 I would need to see the ehaders, but I send email from a postfix relay with a valid return on my Office 365 server to other Office 365 users all the time and nothing is junked. The only thing I did was to add the WAN IP of the location with the Postfix server as a new connector trusted by IP. 
- 
 @Mike-Davis said in Marketing Campaign E-mail and Office365 - Check My Logic, Please: @NetworkNerd said in Marketing Campaign E-mail and Office365 - Check My Logic, Please: Would adding users with internal e-mail addresses to Safe Senders allow the messages to come through the filter to internal recipients as expected? That's kind of like an individualized whitelist in the O365 world, right? I wouldn't do this. A lot of spammers put the from and to address the same for this reason. If you whitelist all your internal addresses, I would think you would get a lot of spam. I agree this is not a good way to go and that the chances for spam go way up. In this case we're talking about 10 different internal addresses. 
- 
 @JaredBusch said in Marketing Campaign E-mail and Office365 - Check My Logic, Please: I would need to see the ehaders, but I send email from a postfix relay with a valid return on my Office 365 server to other Office 365 users all the time and nothing is junked. The only thing I did was to add the WAN IP of the location with the Postfix server as a new connector trusted by IP. ^^^ This ^^^ I did that for postfix and haven't had any spam flagging issues. 
- 
 @JaredBusch said in Marketing Campaign E-mail and Office365 - Check My Logic, Please: I would need to see the ehaders, but I send email from a postfix relay with a valid return on my Office 365 server to other Office 365 users all the time and nothing is junked. The only thing I did was to add the WAN IP of the location with the Postfix server as a new connector trusted by IP. Very similar to what you mention here, I think this is it - https://support.e2ma.net/Resource_Center/Account_how-to/how-to-whitelist-emma. 
- 
 @NetworkNerd said in Marketing Campaign E-mail and Office365 - Check My Logic, Please: @JaredBusch said in Marketing Campaign E-mail and Office365 - Check My Logic, Please: I would need to see the ehaders, but I send email from a postfix relay with a valid return on my Office 365 server to other Office 365 users all the time and nothing is junked. The only thing I did was to add the WAN IP of the location with the Postfix server as a new connector trusted by IP. Very similar to what you mention here, I think this is it - https://support.e2ma.net/Resource_Center/Account_how-to/how-to-whitelist-emma. Not exactly. That is whitelisting entire IP blocks. 





