On Sun, Feb 01, 2004 at 02:26:32AM +0100, Vincent Lefevre wrote:
> Well, looking at your scripts:
> you have won several Useless Use of Cat Awards
A bad habit of mine, I'm afraid...
> Or perhaps pigeons just like cats. :)
Many a true word is spoken in jest... Some pigeons enjoy teasing cats,
and
On 2004-01-31 23:51:55 +, Pigeon wrote:
> I don't think I'm trying to say "don't use procmail". Just that
> there's more than one way to skin a cat. Which is one of the things I
> like about Linux. I had the choice between "figure out procmail" and
> "use bash / ed / exim which I already know";
On Sat, Jan 31, 2004 at 12:45:04PM -0700, s. keeling wrote:
> Incoming from Pigeon:
> >
> > exim -bm. Useful if you want to avoid having to learn
> > Sanskrit^Wprocmail.
> >
> > For example, the following is what I use to strip the advertising from
> > Yahoo Groups mailing list traffic:
>
> Oh y
On 2004-01-31 18:43:10 +, Pigeon wrote:
> ...you mean that if you pipe a message through some external program
> you can't then feed the output of that program back into exim? It
> initially appears so, but it's straightforward to write a shellscript
> wrapper for the external program that adds
On 2004-01-30 22:18:58 -0500, Adam Aube wrote:
> Have you looked at maildrop?
I hesitated between maildrop and procmail and chose procmail propably
because I was already using it on another account. But maildrop is
installed on my machine. BTW, does anyone know when the new version
(1.6.3) will be
Incoming from Pigeon:
>
> exim -bm. Useful if you want to avoid having to learn
> Sanskrit^Wprocmail.
>
> For example, the following is what I use to strip the advertising from
> Yahoo Groups mailing list traffic:
Oh yes, that's far simpler than learning Sanskrit^Wprocmail. Yesiree,
Bob! You b
On Sat, Jan 31, 2004 at 01:09:21AM +0100, Vincent Lefevre wrote:
> * A result of a pipe can't be retrieved (and that's why the FAQ
> recommends to use procmail for such things).
...you mean that if you pipe a message through some external program
you can't then feed the output of that program ba
In article <[EMAIL PROTECTED]>,
Vincent Lefevre <[EMAIL PROTECTED]> wrote:
>On 2004-01-30 18:34:17 +, Miquel van Smoorenburg wrote:
>> See http://www.exim.org/ . Click on "Documentation and FAQs".
>
>There are several things I don't like:
You're probably right on most of those, exim filtering
Moin,
* Adam Aube wrote (2004-01-31 04:18):
>On Friday 30 January 2004 07:09 pm, Vincent Lefevre wrote:
>> However, procmail isn't perfect. The main problem is that it isn't
>> very powerful and may need other tools (mainly formail, but also
>> perl for the most complicated filters). A 100% perl-b
Hi,
* Vincent Lefevre wrote (2004-01-31 01:09):
>However, procmail isn't perfect. The main problem is that it isn't
>very powerful and may need other tools (mainly formail, but also
>perl for the most complicated filters). A 100% perl-based solution
>(with primitives for MIME decoding) would proba
On Friday 30 January 2004 07:09 pm, Vincent Lefevre wrote:
> However, procmail isn't perfect. The main problem is that it isn't
> very powerful and may need other tools (mainly formail, but also
> perl for the most complicated filters). A 100% perl-based solution
> (with primitives for MIME decodin
On 2004-01-30 18:34:17 +, Miquel van Smoorenburg wrote:
> See http://www.exim.org/ . Click on "Documentation and FAQs".
Thanks. The FAQ says to use procmail. :)
> The same documentation is available as a text file in
> /usr/share/doc/exim (spec.txt and filter.txt).
There are several things I
12 matches
Mail list logo
