G. Pape
qconfirm

qconfirm - configuration


Configure qconfirm for mailing lists
Configure qconfirm for a public mailbox
Configure qconfirm for sending mail

qconfirm protecting a mailing list

To setup qconfirm to protect a mailing list that is handled through a dot-qmail file, create a qconfirm directory for this list by running the qconfirm-conf program as the user that is running the list. E.g., if the user floyd runs the ezmlm mailing list floyd-list@list.smarden.org in the directory ~floyd/list/, do
  # su - floyd
  $ qconfirm-conf ~floyd/list/qconfirm
The output of the qconfirm-conf program tells you to add a line to the top of your dot-qmail file. Add this line to the top of the dot-qmail file that handles messages to the mailing lists (e.g. ~floyd/.qmail-list):
  $ echo '|qconfirm-check -d./list/qconfirm' >.qmail-list'{new}'
  $ cat .qmail-list >>.qmail-list'{new}'
  $ mv .qmail-list'{new}' .qmail-list
By default qconfirm runs in sender mode. That means that every sender needs to confirm the delivery of the first message she sends to the mailing list. After this confirmation all subsequent messages from this sender are allowed without confirmation.

You can configure qconfirm to automatically allow mails from subscribers without any confirmation at all, please see the faq. Such a configuration is similar to a subscribers-only mailing list, but with the advantage that non-subscribers can post if they go through the confirmation process once, no action from the list owner is required. They can add themselves to the list of senders that are allowed to send mail to the mailing list without confirmation on their own.

qconfirm can also be told to request confirmation for the delivery of each single message sent to the mailing list, without exception. Please see the faq.

You should consider adding the -n option to qconfirm-check, to prevent delivery acknowledgements from being sent.

qconfirm directories can be shared across dot-qmail files of the same user. You should not mix message mode and sender mode in the same qconfirm directory.


qconfirm protecting a public mailbox

To setup qconfirm to protect a public mailbox, create a ~/.qconfirm directory by running the qconfirm-conf program as the user that owns the mailbox:
  $ qconfirm-conf ~/.qconfirm
The output of the qconfirm-conf program tells you to add a line to the top of your dot-qmail file, add the line to the dot-qmail file that handles the mailbox you want to protect. Here is an example on how to do so:
  $ echo '|qconfirm-check -d./.qconfirm' >.qmail'{new}'
  $ cat .qmail >>.qmail'{new}'
  $ mv .qmail'{new}' .qmail
If you did not have a dot-qmail file before, make sure to also add a line specifying delivery to your normal mailbox (e.g. ./Maildir/).

See here if the public mail address is handled through qmail's virtualdomains.

If you use the mailbox for normal mail conversation, particularly, if you expect replies to mails that you have sent to be delivered to this mailbox, you should consider to tell qconfirm to check the headers of mails for known references, to have those mails delivered without confirmation. To do so, you need to know the format of the Message-IDs of your outgoing mail, and tell qconfirm-check to run qconfirm-check-mid. See the man page for details, here's an example:

  $ head -1 .qmail
  |qconfirm-check -d./.qconfirm qconfirm-check-mid -a '@mid.smarden.org'
This is done automatically if you use qconfirm for sending mail messages also.

qconfirm directories can be shared across dot-qmail files of the same user. You should not mix message mode and sender mode in the same qconfirm directory.


qconfirm for sending mail messages

To setup qconfirm for sending mail, modify the ~/.qconfirm directory by running the qconfirm-conf program with the -i option as the user that owns the mailbox. E.g., if the user floyd runs qconfirm to protect the public mail address <floyd@smarden.org> through the qconfirm directory ~floyd/.qconfirm, and the mail address is handled through ~floyd/.qmail, do as user floyd:
  $ qconfirm-conf -i ~/.qconfirm ~/.qmail floyd smarden.org ./Maildir/
Now floyd can use qconfirm-inject instead of qmail-inject to send mail messages from floyd@smarden.org. Delivery notifications are automatically validated, delivery confirmation requests automatically confirmed, and valid notifications delivered to the mailbox ~floyd/Maildir/.

If the user floyd runs qconfirm to protect the public mail address <floyd@example.org>, and the domain example.org is handled through qmail's virtualdomains with the entry

  example.org:floyd-example
mail messages to <floyd@example.org> are processed through the dot-qmail file ~floyd/.qmail-example-floyd, and floyd needs to run
  $ qconfirm-conf -i ~/.qconfirm ~/.qmail-example-floyd floyd example.org

Gerrit Pape <pape@smarden.org>
$Id: configuration.html,v 1.8 2003/11/27 14:10:27 pape Exp $