Re: qconfirm feature request

> Hmm, qconfirm-inject overrides the return path itself to properly handle
> delivery notification, what should it do if the -f option is given?
> Simply accept this sender, at the cost of not processing delivery
> notifications through qconfirm-notice?

 Oh. I see. Sorry about that, I was tired yesterday. ;)
 Let me explain where my request is coming from.

 After 2 years of laziness, I've eventually decided that properly
configuring qconfirm would take less time than manually deleting all
the spam I get (which is now _very much_).
 The thing is, I have a multi-address, multi-folder setup with a
couple bazillion .qmail files; each folder must be configured
separately. For instance, the [email protected] address must
have this mailing-list whitelisted - and maybe your sender addresses
too ;) - and request confirmation for any other sender. Other
addresses will have a different configuration, with a different
whitelist.

 This means I have to configure as many qconfirm directories as I
have folders. It works, but it requires careful juggling with
qconfirm options, and overriding defaults practically everywhere.

 When I'm in a folder, I want my From: line to be the relevant
address, and I also want the Return-Path to be the same address
(so when I get a bounce, it goes into the proper folder).
 Before setting up qconfirm, I used Mutt's folder-hook command to
set up the proper injection line, i.e. something like

folder-hook somefolder set sendmail="qmail-inject -fsomesender"

 Now that I'm using qconfirm-inject as the injection program, I need
an equivalent option to do the same. But I had overlooked the fact
that qconfirm-inject itself modifies the sender.

 After taking a look at the qconfirm-inject documentation, I understand
that the correct solution to my need is to use the QNOTICE_USER
configuration file. Since I have a different qconfirm directory for
each different folder, I can have a different QNOTICE_USER too.
 Problem solved.

 Actually, it _would_ be possible to implement a -f option to
qconfirm-inject.
 Parse the argument, extract a user and a host, which will override
QNOTICE_USER and QNOTICE_HOST. The final Return-Path will be
user-$QNOTICE_EXT-qnoticehash@host.
 But it requires some parsing. It's perfectly reasonable for an
injection program to parse, but it's a bit too complex for me to
write the patch on the spot. I'll leave it to you ;)

 Thanks for hearing my ramblings.

-- 
 Laurent