From: Pandu Poluan <pandu@poluan.info>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] Mailscanner or amavisd-new
Date: Mon, 28 Nov 2011 21:31:59 +0700 [thread overview]
Message-ID: <CAA2qdGWcDQBALPMEM6k50tuJBs0homTXZDCOmYk3OQ-Zxce+3Q@mail.gmail.com> (raw)
In-Reply-To: <CAHJT52-TBRAeaM1ifrhTMOyoSWbwcmQjCw6wpZH9sN_a4pwu6A@mail.gmail.com>
On Mon, Nov 28, 2011 at 20:44, Mișu Moldovan <dumol@gnome.org> wrote:
> On Mon, Nov 28, 2011 at 14:04, Pandu Poluan <pandu@poluan.info> wrote:
> [snip]
>>
>> I think it's Postfix's README:
>>
>> http://www.postfix.org/SMTPD_PROXY_README.html
>>
>> That said, the above page explicitly warns about the possibility of server
>> deadlock. Since this is meant to be the corporate mail gateway, I prefer the
>> after-queue methods.
>
> Ah, I see... I know that README and it is basically right. However,
> even with after-queue scanning you will run into the same class of
> problems and you'll have to put limits for the number of threads for
> antispam scanning etc.
>
> The main difference, speed-wise, is that with after-queue scanning the
> MTA will accept and queue new mail much faster. But the delivery will
> still be delayed until scanning finishes. In case of a massive flood
> of mails or a malfunction of the filters, both the sender and the
> receiver will be unaware of the delay.
>
> But if you put the limits right in the before-queue antispam scanning,
> there will be no delays that the sender or receiver are unaware of. In
> case of a massive flood of mails, the sender's MTA will keep retrying
> until reaching the limit (eg. 4 hours) when it will inform the sender
> that it cannot deliver and it is still retrying. So the sender will
> know that he/she must try to reach that person using other channels of
> communication.
>
Hmmm... you do have a point.
I'm going to study MIMEDefang.
Rgds,
--
FdS Pandu E Poluan
~ IT Optimizer ~
• LOPSA Member #15248
• Blog : http://pepoluan.tumblr.com
• Linked-In : http://id.linkedin.com/in/pepoluan
next prev parent reply other threads:[~2011-11-28 14:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 6:02 [gentoo-server] Mailscanner or amavisd-new Pandu Poluan
2011-11-28 6:23 ` Matt Thode
2011-11-28 6:40 ` Pandu Poluan
2011-11-28 9:14 ` Alessandro Ratti
2011-11-28 10:25 ` Mișu Moldovan
2011-11-28 11:09 ` Alessandro Ratti
2011-11-28 11:15 ` Mișu Moldovan
2011-11-28 11:28 ` Hannes Erven
2011-11-28 11:46 ` Mișu Moldovan
2011-11-28 12:04 ` Pandu Poluan
2011-11-28 13:44 ` Mișu Moldovan
2011-11-28 14:31 ` Pandu Poluan [this message]
2011-11-28 15:49 ` Pandu Poluan
2011-11-28 16:32 ` Mișu Moldovan
2011-11-28 16:50 ` Pandu Poluan
2011-11-28 18:27 ` Mișu Moldovan
2011-11-29 12:11 ` J. Roeleveld
2011-11-29 13:22 ` Vinícius Ferrão
2011-11-29 13:36 ` Pandu Poluan
2011-11-29 14:08 ` J. Roeleveld
2011-11-29 14:20 ` Pandu Poluan
2011-11-29 14:04 ` J. Roeleveld
2011-11-29 18:02 ` Mișu Moldovan
2011-11-30 7:38 ` J. Roeleveld
2011-11-30 8:02 ` Pandu Poluan
2011-11-29 18:26 ` kashani
2011-11-29 18:48 ` Pandu Poluan
2011-11-30 7:44 ` J. Roeleveld
2011-11-29 14:22 ` Alessandro Storti Gajani
2011-11-30 7:35 ` J. Roeleveld
2011-11-30 9:46 ` Mișu Moldovan
2011-11-28 12:26 ` [gentoo-server] " Pandu Poluan
2011-11-28 15:22 ` [gentoo-server] " Eduardo Schoedler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA2qdGWcDQBALPMEM6k50tuJBs0homTXZDCOmYk3OQ-Zxce+3Q@mail.gmail.com \
--to=pandu@poluan.info \
--cc=gentoo-server@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox