Email query
-
Yeah, they also say:
Limitations of direct send
Your messages will be subject to antispam checks.
Sent mail might be disrupted if your IP addresses are blocked by a spam list.
Office 365 uses throttling policies to protect the performance of the service.I'm making the assumption that IP address isn't blocked by a spam list and that throttling policies won't feature. Normal antispam checks can be mitigated by whitelisting the domain and adding an SPF record.
-
@Carnival-Boy said in Email query:
Yeah, they also say:
Limitations of direct send
Your messages will be subject to antispam checks.
Sent mail might be disrupted if your IP addresses are blocked by a spam list.
Office 365 uses throttling policies to protect the performance of the service.I'm making the assumption that IP address isn't blocked by a spam list and that throttling policies won't feature. Normal antispam checks can be mitigated by whitelisting the domain and adding an SPF record.
But all of that could be ignored if the crazy application just supported modern email technologies, i.e. username/password for SMTP
-
@Carnival-Boy said in Email query:
Yeah, they also say:
Limitations of direct send
Your messages will be subject to antispam checks.
Sent mail might be disrupted if your IP addresses are blocked by a spam list.
Office 365 uses throttling policies to protect the performance of the service.I'm making the assumption that IP address isn't blocked by a spam list and that throttling policies won't feature. Normal antispam checks can be mitigated by whitelisting the domain and adding an SPF record.
You cannot whitelist the domain. it is already your domain. That is how direct send works.. It will still block it if they want.
-
Then use a different domain, as I suggested earlier. Or whitelist by IP address. Which is really more or less the same as your instructions for creating a connector. You're just allowing non authenticated connections to bypass any filters.
I'm not suggesting Direct Send as a solution, by the way. I'm just questioning why it would fail.
-
@Carnival-Boy different domain can help. But requires buying and maintaining another domain and records. Might be cheaper than a hosted relay but not than a local one.
-
A domain is about 10 bucks a year!
-
@Carnival-Boy said in Email query:
A domain is about 10 bucks a year!
Plus the management of it. and employee is only $10/hr, but the management and cube space and heating and cooling and benefits, etc, etc, etc... make that 10/hr person cost more like $40/hr.
-
@Carnival-Boy said in Email query:
A domain is about 10 bucks a year!
Well we pay more like $20 here. But it's less reliable, in my experience, and only supported by some systems. A relay is much more reliable and is $5/mo or $60/year. Three times the cost, if that is the only cost. But for the reliability and flexibility, I'd more likely go with the relay. And if you run the relay in house, it's free.
-
@scottalanmiller said in Email query:
And if you run the relay in house, it's free.
Hardly free. Roughly how much would you expect an MSP to charge to install, manage, support and patch an on-premise mail relay?
I'm still not sure about the purpose of using a relay. You still have to create a connector in O365 to accept mail from the relay. And you still need to put restrictions in, either by IP address or by a certificate on the relay. So what difference does a relay make compared with just having the application use the connector directly, as suggested by @JaredBusch? The relay seems redundant here.
-
@Carnival-Boy said in Email query:
@scottalanmiller said in Email query:
And if you run the relay in house, it's free.
Hardly free. Roughly how much would you expect an MSP to charge to install, manage, support and patch an on-premise mail relay?
I'm still not sure about the purpose of using a relay. You still have to create a connector in O365 to accept mail from the relay. And you still need to put restrictions in, either by IP address or by a certificate on the relay. So what difference does a relay make compared with just having the application use the connector directly, as suggested by @JaredBusch? The relay seems redundant here.
No you don't. The relay is modern so the relay itself will support logging in Via SMTP. The only reason we're adding a relay is because the software itself does not support this function natively.
-
Oh, ok. I was just following the instructions that @JaredBusch linked to about creating a connector. So you configure Postfix to login in to O365 with a username and password? Nothing needs to be done on O365? Is that simple to do?
-
@Carnival-Boy said in Email query:
Oh, ok. I was just following the instructions that @JaredBusch linked to about creating a connector. So you configure Postfix to login in to O365 with a username and password? Nothing needs to be done on O365? Is that simple to do?
I've never done it, so that part I have no idea.
-
It sounds fairly straightforward.
-
@Carnival-Boy said in Email query:
It sounds fairly straightforward.
It is fairly straightforward. But I would still do a relay and you authenticated email
-
@JaredBusch said in Email query:
@Carnival-Boy said in Email query:
It sounds fairly straightforward.
It is fairly straightforward. But I would still do a relay and you authenticated email
I talked to Jared offline about this.
His suggestion here is just what I said - Assuming the relay acts just like an email client, then you can skip the connector instructions above. The fact that the relay is authenticating allows it to send emails on behalf of the software in question as if it was any normal user.
-
I'm on the road in posing via Siri so you get what you get
-
@JaredBusch said in Email query:
I'm on the road in posing
I'm now picturing you getting photographed for Victoria's Secret on a highway somewhere.
-
@Carnival-Boy said in Email query:
@JaredBusch said in Email query:
I'm on the road in posing
I'm now picturing you getting photographed for Victoria's Secret on a highway somewhere.
I even shaved today!
-
