[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postfix-users
Subject:    Re: Email architecture
From:       Tom Marcoen <tom.marcoen () gmail ! com>
Date:       2018-07-17 14:38:18
Message-ID: CAJ-iVrNHNhYVDM9d4Zj67sYB5Q9ciOK0ccY5ex22Srw+Y9R4sQ () mail ! gmail ! com
[Download RAW message or body]

Hey Miles,

I agree, you can't forget about antispam and antivirus. I would run them on
the relay hosts in the DMZ, not on the internal mail servers. Though that
would be a tradeoff as well because then your internal emails between
employees won't get scanned anymore.

On Tue, 17 Jul 2018 at 16:32, Miles Fidelman <mfidelman@meetinghouse.net>
wrote:

> For what it's worth:
>
> Every time I have to (re)install a mail system, I google the combination
> of "postfix spamassassin amavis" and I find some good tutorials on step
> by step setup.  I seem to recall that one of the best was from one of
> the hosting providers.  (Can't forget the antispam and antivirus -
> they're the things that turn out to be the trickiest to wire in.
>
> Miles Fidelman
>
>
> On 7/17/18 6:20 AM, Tom Marcoen wrote:
> > Hey all,
> >
> > I was wondering if someone knows about a good tutorial or design
> > document describing how to setup postfix, dovecot (or something else)
> > and other tools to create a good and secure email architecture, i.e.
> >
> > -  how to configure postfix in a DMZ to relay incoming emails to a
> > dovecot (or similar) server.
> > - how to configure postifx in a secure network to receive emails from
> > users and forward it to a DMZ server
> > - how to configure a postfix server in a DMZ for outbound SMTP traffic.
> >
> > But also more in general, what are the best practices for designing an
> > email environment for a serious business?
> >
> > Best regards,
> > Tom
>
> --
> In theory, there is no difference between theory and practice.
> In practice, there is.  .... Yogi Berra
>
>

[Attachment #3 (text/html)]

<div dir="ltr">Hey Miles,<div><br></div><div>I agree, you can&#39;t forget about \
antispam and antivirus. I would run them on the relay hosts in the DMZ, not on the \
internal mail servers. Though that would be a tradeoff as well because then your \
internal emails between employees won&#39;t get scanned anymore.</div></div><br><div \
class="gmail_quote"><div dir="ltr">On Tue, 17 Jul 2018 at 16:32, Miles Fidelman \
&lt;<a href="mailto:mfidelman@meetinghouse.net">mfidelman@meetinghouse.net</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">For what it&#39;s worth:<br> <br>
Every time I have to (re)install a mail system, I google the combination <br>
of &quot;postfix spamassassin amavis&quot; and I find some good tutorials on step \
<br> by step setup.   I seem to recall that one of the best was from one of <br>
the hosting providers.   (Can&#39;t forget the antispam and antivirus - <br>
they&#39;re the things that turn out to be the trickiest to wire in.<br>
<br>
Miles Fidelman<br>
<br>
<br>
On 7/17/18 6:20 AM, Tom Marcoen wrote:<br>
&gt; Hey all,<br>
&gt;<br>
&gt; I was wondering if someone knows about a good tutorial or design <br>
&gt; document describing how to setup postfix, dovecot (or something else) <br>
&gt; and other tools to create a good and secure email architecture, i.e.<br>
&gt;<br>
&gt; -   how to configure postfix in a DMZ to relay incoming emails to a <br>
&gt; dovecot (or similar) server.<br>
&gt; - how to configure postifx in a secure network to receive emails from <br>
&gt; users and forward it to a DMZ server<br>
&gt; - how to configure a postfix server in a DMZ for outbound SMTP traffic.<br>
&gt;<br>
&gt; But also more in general, what are the best practices for designing an <br>
&gt; email environment for a serious business?<br>
&gt;<br>
&gt; Best regards,<br>
&gt; Tom<br>
<br>
-- <br>
In theory, there is no difference between theory and practice.<br>
In practice, there is.   .... Yogi Berra<br>
<br>
</blockquote></div>



[prev in list] [next in list] [prev in thread] [next in thread]