cabot-20040212.tar.gz ? (was: Re: Patch for #4502 and #4503)

[Laurent Fousse]

--xgyAXRrhYN0wYx8y
Content-Type: multipart/mixed; boundary="7AUc2qLy4jB3hD7Z"
Content-Disposition: inline


--7AUc2qLy4jB3hD7Z
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

Le Thu, Feb 12, 2004 at 05:05:52PM +0100, Peter Palfrader =E9crivait:
> On Thu, 12 Feb 2004, Laurent Fousse wrote:
> > I've read the howto, it gives detailed instructions but it is, err...
> > complicated. I didn't setup a dedicated cabot user on my system, is
> > that really needed ?
>=20
> No it's not.  The howto shows one possible way.

That's good because I don't do it this way. Documentation on how I do
it is attached. Please Peter and Joost comment on this before I add
it to the cvs.

> PS: I've cut the Cc considerable.  We all are on cabot-devel@lists.n.o.

Thought so.

Cheers,

Laurent.

--7AUc2qLy4jB3hD7Z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="cabot-doc.pod"
Content-Transfer-Encoding: quoted-printable


=3Dpod

=3Dhead1 A guide to cabot as a local user


This manual explains you to set up cabot as a local user, without the
need for a system B<cabot> user.

=3Dhead1 Requirements

You need to set several email addresses in your cabot configuration
file for cabot to work properly. This manual assumes you receive your
mail directly to john@example.com and your MTA lets you add arbitrary
suffixes to your local part, for example "john-whatever@example.com".
If your MTA is exim you may want to have a look at the
B<local_part_suffix> and B<local_part_suffix_optional> variables.

=3Dhead1 Cabot configuration

The first step is to write your personal cabot configuration file in
~/.cabotrc. Most variables are self explanatory and here are some
guidelines for a complete automation of the process:

=3Dover 4

=3Ditem BCCmail

This is an address where you want to get a copy of all email sent by
cabot. Though not strictly necessary it may be useful when your
correspondent loses its challenge email. I suggest something of the
line of B<john-ca-out@example.com>.

=3Ditem bot

This is the addresse of the bot. It is the address where the challenge
replies are sent; you could chose something like
B<john-cabot@example.com>.

=3Dback

=3Dhead1 Integration with procmail

Challenge replies should be fed to ca-recv(1), so the following
procmail recipe achieves this :

 :0
 * ^To: john-cabot\@example\.com
 |/usr/bin/ca-recv
=20
If you would like to keep a copy of challenge replies, you can try the
following instead :

 :0c
 * ^To: john-cabot\@example\.com
 challenges/

 :0A
 |/usr/bin/ca-recv

Outgoing challenges may be kept in a separate mailbox as well:

 :0
 * ^To: john-ca-out\@example\.com
 cabot/

=3Dhead1 Integration with .forward files

The idea is the same as with procmail rules : put=20

 |/usr/bin/ca-recv

in a file named ~/.forward-john-cabot. You get the idea.

--7AUc2qLy4jB3hD7Z--

--xgyAXRrhYN0wYx8y
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAK/okRoAVF6FpbSsRAnsHAKCR6H5yqn8fTvviJA4IInc+bs2lxgCdHDFR
CBY7TMlQ22iNrw9jKdY7+jM=
=AU51
-----END PGP SIGNATURE-----

--xgyAXRrhYN0wYx8y--