Email from Webserver: Page 2 - Enhance Control Panel

Email from Webserver

xyzulu

adham I don’t have any enhance servers with email role or a smart host set. All Wordpress emails go via postmark with the “from” email being forced to a domain that is a sender signature domain in Postmark.

adham

xyzulu I followed your advice and I'm doing that now 🙂 thank you!

8Dweb

Adam I was reading through all forum posts to find this. I knew I had read it at some point. We do not want any local MTA on our web servers, for any reason. Everything must flow through either the cluster SMTP servers or smarthosts (if required by our customers).

I would, as others have suggested, make this something that can be toggled from Settings | Email - something like "Disable MTA for web servers" or if it needs to be a setting on individual servers, have that option under settings for each server in the servers area of the UI.

XN-Matt

Very much agree. This should have been given as an option, not removal of a feature without any consideration from those now expecting it to work in a certain way.

lxix

Is it posible to revert to the original email handling setup by modifying the postfix configuration? I’d like to avoid sending emails directly from the local MTA on my web servers. Thanks!

Adam

lxix Is it posible to revert to the original email handling setup by modifying the postfix configuration? I’d like to avoid sending emails directly from the local MTA on my web servers. Thanks!

You could create an email account on the email server (maybe on a generic domain) and set it as a smart host on the web server.

XN-Matt

Not at the moment.

XN-Matt

This suggestion is not workable where you block outbound SMTP from the website container, as realistically, everyone should do.

I've raised a ticket on this but it appears this change without any prior notice or consultation has actually broken email.

If you use Cloudflare and your mail is on a different server to your the website, customers will find their mail fails all SPF checks.

The a classification does not match because it now points to Cloudflare and the mx record does not match because it is a different IP. So the SPF record has no reference to the webserver sending email.

Enhance need to make sure that if you're going to set things one way of work, you don't then change this overnight, without any warning or consultation and by doing so, actually break websites in the process that were working perfectly before.

gmakhs

XN-Matt mate enhance is not production ready, we all need to embrace that, and be patient .

Communication have been a major issue on the V12 update too, it doesn't suprise me is an issue on other sectors also .

XN-Matt

You miss the point.

It did work, but they changed the way it worked without notice and thus they created a problem which didn’t exist and have not fixed or reverted it.

gmakhs

XN-Matt Not production ready not only as a product but also as a team, mistakes are bound to happen, also bad communication

Rich

gmakhs I have it in production use for my business and a charity and it's been fine for over a year and half. Enhance is used buy some companies that have 100's of servers. Adam refers to it as production ready and I don't disagree... lacking features isn't the same as not being production ready. Sure there are changes/challenges to deal with.

Wither it's production ready for your use case is entirely up to you. It is safe in the wild and doing what it's design to do.

@XN-Matt Yes this wasn't a good one, and app servers need to be able to limit from allowing PHP mail. I've recently finally switched to a smart host and now I wish I could block all php mail, that said php mail IS blocked now anyway by the smart rely as it lacks sufficient SPF headers, but still.

Right now I am currently testing out adding a server wide php.ini directive:
disable_functions = mail
An end user can undo/modify it on the CP. (It's to stop bots.)
I don't think it works, even after container and webserver resets I seem to be able to send mail via php. 😐

« Previous Page