> I am about to implement an exim configuration whereby mail
> tagged as spam by our gateways (not exim) is
> frozen in the queues for later delivery. I intend to
> deliver it at night. I use the queue_only option to
> put all mail into the queue in any case, and I have
> qrunners which perform actual delivery. The spam
> mail will be frozen by a global filter.
We have a similar situation by prefering non-spam messages over spam during
LMTP delivery to Cyrus which could be very slow for 45000+ users. Therefore
exim freezes the spam and has some queue delivery processes started with -q
and some with -qff. Option queue_run_in_order is also enabled. Works very
well.
> Obviously, the size of the mail queue is about to get
> real large. I anticipate having 20K to 100K messages
> in the queue. I am running the split_queue_directory option.
Occasionally our queue grows up to 50K messages. NagiosGrapher (which we
use to monitor and visualize the size of the queue) showed that the
absolute maximum is 105K messages so far. Exim can handle it without
a problem on our HP DL380. Due to the two different queue runners, non-spam
mails still gets delivered fast and only mails sorted out as spam have some
delay before delivered into the spam-folders of our users - nothing to
worry about.
As Philip wrote: large queues will slow down exim but even 100K is below
the level to think about workarounds like moving messages out of the queue
or delivering via batched SMTP.
Heiko
Heiko Schlichting | Freie Universität Berlin
heiko@??? | Zentraleinrichtung für Datenverarbeitung (ZEDAT)
Telefon +49 30 838-54327 | Fabeckstraße 32
Telefax +49 30 838454327 | 14195 Berlin
