Re: qconfirm-0.12.0 available

On Mon, Dec 01, 2003 at 11:53:00AM +0100, Gerrit Pape wrote:
> On Sun, Nov 30, 2003 at 01:48:18PM -0600, Gary wrote:
> > As far as I can tell, there is a downside of this is that qconfirm-inject
> > changes the envelope sender.  I belong to several e-groups that utilize
> > ezmlm and this would not work out, as I now use a subscribed envelope
> > address for those lists, and with qconfirm-inject, the envelope address
> > would change, so it would not work out. I also currently use a
> > non-existant Message-ID subdomain that would be picked up by qconfirm-mid.
> 
> Yes, I know about these ``subscribers only'' mailing list.  But I never
> really understood why they force you to use your subscription address as
> envelope sender when sending to the list.  Current standards don't force
> you.  Running qconfirm on such lists would add value.  Non-subscribers
> would not just get a bounce, they would get a bounce (confirmation
> request), and with the bounce the possibility to have the message
> delivered to the list nonetheless, simply by replying.  The new qconfirm
> version even would to this automatically, it already should work fine
> with this list.
> 
> > Can't do this now, if I set qconfirm up with these features.. I think
> > these new features would be only good for lists like qmail or djbdns that
> > require no subscription address.
> 
> The new features are optional, you don't need to use them.

And, as I just discovered, you can disable them in mutt on a per-message basis.
For example, if this is in your .muttrc file:

send-hook .                          'set sendmail="/command/qconfirm-inject"'
send-hook '~t [email protected]'     'set sendmail="/var/qmail/bin/qmail-inject"'

then the qconfirm-inject stuff will be used for every recipient except the
bincimap mailing list. You can also set the envelope sender the same way, so
everything will be handled automatically when you send to one of these lists.

Chris