handling cabot mail messages (was: Re: cabot debian package)

[Joost van Baal]

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

On Wed, Feb 11, 2004 at 12:40:00PM +0100, Laurent Fousse wrote:
>=20
> I've added a 3 lines procmail
> recipe to README.Debian. This could be added to the upstream tarball
> indeed.

Please commit it to CVS.

> Le Wed, Feb 11, 2004 at 10:52:41AM +0100, Joost van Baal =E9crivait:
> > Sample ~/.forward or ~/.courier would be nice too: I believe
> > you don't need procmail or maildrop to use cabot.
>=20
> I don't use .forward files as they are less powerful than procmail,
> but anything than can pipe a mail through a command is good.=20

I like to use address extensions.  E.g. use laurent-cabot@komite.net for
you cabot stuff, and handle the cabot mail via ~laurent/.forward-cabot
(or .forward+cabot , depending on your MTA.)  The .forward-foo file just
has to contain the pipe.  Nice thing is that you don't need external
software parsing the message: less errorprone.

> I'll have
> a look at exim's documentation for .forward files because :
>=20
> $ man forward
> No manual entry for forward

Hm, ye, exim ships documentation in info files.  Have done some
searching, but couldn't find anything on .forward file support in Exim.
It should be there somewhere, though...

Bye,

Joost


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

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

iD8DBQFAK6chBgac8paUV/ARAr9WAJ96OHeLd6HMKHgXuezHXE0vDzk8jwCfRHdd
aSYjNHo1qeffq4XDDqmcuqg=
=yYaq
-----END PGP SIGNATURE-----

--XZq0mbLCR4KNTYFe--