On Fri, 23 Jun 2006, Chris Lightfoot wrote:
> On Fri, Jun 23, 2006 at 02:46:12AM +0200, Eduardo Díaz Comellas wrote:
> [...]
> >
> > Is this possible today? Any chance to get it implemented? Any help to
> > implement it?
>
> Switch off exim's own queue runners, and use an ACL to stick the
> priorities in a header in the mail (erasing any such that already
> exists).
You could just use an acl_m* variable, since these are stored in the queue
files and don't require fiddling with the header.
> Then write a program which iterates over the queue files, reading the
> headers (-H files) to obtain the priorities and then sorting the list of
> message-IDs in order;
You can almost use exipick to do this, except that it can't sort the
output in the way you want. But if you only have a couple of priority
levels then this isn't a problem: just run an exipick for each priority
level in turn.
> Is this wise, though? In your scheme low-priority mails could be queued
> indefinitely behind higher-priority ones, and delayed for an arbitrarily
> long time, which sounds undesirable.
It may be OK to try delivering the low priority messages at slack times,
e.g. overnight.
Tony.
--
<fanf@???> <dot@???>
http://dotat.at/ ${sg{\N${sg{\
N\}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}\
\N}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}
