[BlueOnyx:04977] Re: disable all email

[Darrell D. Mobley]

> -----Original Message-----
> From: blueonyx-bounces at blueonyx.it [mailto:blueonyx-bounces at blueonyx.it]
> On Behalf Of Michael Stauber
> Sent: Wednesday, July 07, 2010 5:30 AM
> To: BlueOnyx General Mailing List
> Subject: [BlueOnyx:04972] Re: disable all email
> 
> Yes, because /etc/mail/local-host-names is the wrong place for that.
> 
> When you tick the box for "disable all email" for a site, then the
> following lines gets added to /etc/mail/access:
> 
> ### Start Block Email for Virtual Site: site4.smd.net ###
> www.site-in-question.com           ERROR:5.1.1:550 User unknown
> ### END Block Email for Virtual Site: site4.smd.net ###
> 
> That'll then make sure that all email to that site is rejected with a
> "User unknown" message.

Your response snipped an important part of Bret's post, which is the last
part of the following sentence starting with "so that forms...":

"The server should be set up to NOT recieve email for those domains by
removing or commenting out the entries in local-host-names so that forms or
other system generated emails will be sent to the dns resolved mx record for
that domain."

His comments indicate that by not removing the domain in question from the
local-host-names file for sites that have email disabled in the GUI, email
generated by website forms or system-generated email would never make it to
the proper email server for the domain in question.

Does email generated at the system level or email generated by someone
submitting a website form for a given domain get routed correctly in the
situation you described?  If I have elected to separate my email solution
from my website, email generated by my website should still be able to make
its way to me.