whitelist
Patrick Ben Koetter
p at sys4.de
Mon Jul 15 14:46:08 CEST 2019
Dino,
* Dino Edwards <dino.edwards at mydirectmail.net>:
> >P.S.
> >Any pre-queue process will introduce a noticable delay. This is imposed by
> >the scan process itself. It is the same delay you have in post-queue – its
> >just that now you get to "see" in SMTP sessions. Clients won't bother. The
> >typical client timeout is 600 second. That's ten minutes a >client will
> >wait for your amavis setup to get the job done. If it hasn't finished by
> >then you have a problem – no matter if you are using a pre- or a post-queue
> >setup.
>
> If this setup introduces “noticable” delays for up to 10 minutes, I see that
> as a problem. My customers will see that as a problem also. I was constantly
> being asked why does it take so long for emails to arrive and gmail doesn’t
> take that long etc… when I was using graylisting. So you must have really
> understanding customers.
you misunderstood me.
The delay is always there. It doesn't matter if you use a post-queue or
pre-queue setup. The delay is caused by any scanning/filtering that takes
place. The only difference between a pre-queue and a post-queue setup is that
you get to "see" (read: notice) it, when you e.g. telnet to your mail platform
and send a message. In such cases you will notice a delay after you've send
the message and before the server accepts or rejects the message. You don't
get to see that delay in a post-queue setup, because you don't observe the
session with e.g. a telnet client. But it is there. It's the regular scanning
time.
Your customers will not notice a delay on inbound mail if you switch from a
post-queue to a pre-queue setup, because the time to filter the message
remains the same.
*If* you run a pre-queue setup on SMTP submission, your customers *will* not a
delay, because the will notice that their MUA seems to *hang* while it
submits the message.
Use pre-queue for MTA to MTA traffic and post-queue for MUA to MTA traffic and
you get the best of both worlds.
p at rick
--
[*] sys4 AG
https://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG,80333 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief
Aufsichtsratsvorsitzender: Florian Kirstein
More information about the amavis-users
mailing list