On Sat, Nov 10, 2012 at 10:37:04PM +, Tony's unattended mail wrote:
However, I find dovecot deliver (which uses the sieve language
for filtering) to be much more readable/writable than procmail.
Sieve does not include regular expressions -- I shit you not.
Dovecote needs regular
/ Tony's unattended mail wrote on Sat 10.Nov'12 at 22:37:04 + /
However, I find dovecot deliver (which uses the sieve language
for filtering) to be much more readable/writable than procmail.
Sieve does not include regular expressions -- I shit you not.
Dovecote needs regular
Hi Will,
Thanks again for your ideas.
On 04/10/12 16:04, Will Fiveash wrote:
I use procmail and some shell scripts to basically do the same. Here is
my .procmail rule:
# Process killed threads, save killed threads in killedthreads mbox
:0:
* ? $HOME/bin/isthreadkilled
killedthreads
I
On Thu, Oct 11, 2012 at 10:12:16PM +0200, Alexis Letessier wrote:
Hi Will,
Thanks again for your ideas.
On 04/10/12 16:04, Will Fiveash wrote:
I use procmail and some shell scripts to basically do the same. Here is
my .procmail rule:
# Process killed threads, save killed threads
You're right Will,
I have used tr and sed expressions from Marco and only a part of your procmail
recipe (* ? script).
Thanks to you two then ;)
On 11/10/12 15:30, Will Fiveash wrote:
I don't see my script stuff in there so I'm thinking you probably need
to redirect your thanks to Marco. If
On Thu, Oct 11, 2012 22:43:39 PM +0200, Alexis Letessier wrote:
You're right Will,
I have used tr and sed expressions from Marco and only a part of
your procmail recipe (* ? script).
Thanks to you two then ;)
You're welcome! Glad the stuff was useful. For the record, the
procmail recipe
M. Fioretti wrote:
You're welcome! Glad the stuff was useful. For the record, the
procmail recipe in my blog post is NOT mine (as duly noted in the post
itself and/or in the code). Basically, I had the idea, then whined on
the procmail list about it until Sean Straw, procmail guru, became
On Thu, Oct 11, 2012 14:39:28 PM -0700, J Wermont wrote:
M. Fioretti wrote:
You're welcome! Glad the stuff was useful. For the record, the
procmail recipe in my blog post is NOT mine (as duly noted in the post
itself and/or in the code). Basically, I had the idea, then whined on
the
[ Will Fiveash wrote on Thu 4.Oct'12 at 16:04:47 -0500 ]
On Thu, Oct 04, 2012 at 10:54:39AM +0200, M. Fioretti wrote:
On Thu, October 4, 2012 10:47 am, Alexis Letessier wrote:
I use notmuch to index all my emails but i need some kind of database or
something to redirect threads
On Thu, October 4, 2012 10:47 am, Alexis Letessier wrote:
I use notmuch to index all my emails but i need some kind of database or
something to redirect threads that i already filtered out.
Is this a strange idea or should i change my workflow? Any ideas on how
this could be implemented?
I
Hi Marco,
Your two blog articles on the subject are really helpful.
I will try to adapt the procmail recipe to match message-id based on
notmuch search results in order to filter out unwanted threads:
~ % notmuch search --output=files 'id:14d85b32...@dem006.intra.tt' or
'id:ADFADSFADF'
On Thu, Oct 04, 2012 at 10:54:39AM +0200, M. Fioretti wrote:
On Thu, October 4, 2012 10:47 am, Alexis Letessier wrote:
I use notmuch to index all my emails but i need some kind of database or
something to redirect threads that i already filtered out.
Is this a strange idea or should i
On Fri, Aug 06, 2010 at 10:54:16PM +0200, Michelle Konzack wrote:
Hello Christian Ebert,
Am 2010-08-05 15:45:48, hacktest Du folgendes herunter:
As Erik is using Maildir even that wouldn't help much as the
messages would be delivered to Maildir/new/ .
And if he had looked into the
Hi Yue,
* Yue Wu vano...@gmail.com [06. Aug. 2010]:
On Thu, Aug 05, 2010 at 03:45:48PM +0100, Christian Ebert wrote:
* Erik Christiansen on Friday, August 06, 2010 at 00:38:37 +1000
On Thu, Aug 05, 2010 at 09:18:45PM +0800, Yue Wu wrote:
I don't only want to redeliver my emails, but also not
On Fri, Aug 06, 2010 at 10:48:05AM +0800, Yue Wu wrote:
In my case, after re-procmail, every email will be unread, I can't recorgnize
which are those I've read, I have to look those emails one by one and recall
if it's really read or unread by me.
In the script or procmail recipe that refiles
Hello Christian Ebert,
Am 2010-08-05 15:45:48, hacktest Du folgendes herunter:
As Erik is using Maildir even that wouldn't help much as the
messages would be delivered to Maildir/new/ .
And if he had looked into the archive of the procmail list, he would
know how to make files read. Including
Hello Yue Wu,
Am 2010-08-05 21:18:45, hacktest Du folgendes herunter:
for j in $(find $2 -type d | grep cur) ; do (
cd $j ;
for i in * ;
do cat $i | formail -ds procmail ;
done) ;
done
But after redeliverd, all emails are
* Yue Wu vano...@gmail.com [08-05-10 08:39]:
Sometimes I want to filter my emails with new rule of procmail, archived
list has the way to re-procmail, but all re-procmailed mails will be at
the new unread status. My question is, how to re-procmail without
changing the read/unread status
On Thu, Aug 05, 2010 at 08:50:22AM -0400, Patrick Shanahan wrote:
* Yue Wu vano...@gmail.com [08-05-10 08:39]:
Sometimes I want to filter my emails with new rule of procmail, archived
list has the way to re-procmail, but all re-procmailed mails will be at
the new unread status. My question
On Thu, Aug 05, 2010 at 09:18:45PM +0800, Yue Wu wrote:
I don't only want to redeliver my emails, but also not let all redelivered
mails become into the unread status. I'm using maildir format, and tried with
the following script:
for j in $(find $2 -type d | grep cur) ; do (
* Erik Christiansen on Friday, August 06, 2010 at 00:38:37 +1000
On Thu, Aug 05, 2010 at 09:18:45PM +0800, Yue Wu wrote:
I don't only want to redeliver my emails, but also not let all redelivered
mails become into the unread status. I'm using maildir format, and tried with
the following
On Thu, Aug 05, 2010 at 03:45:48PM +0100, Christian Ebert wrote:
* Erik Christiansen on Friday, August 06, 2010 at 00:38:37 +1000
On Thu, Aug 05, 2010 at 09:18:45PM +0800, Yue Wu wrote:
I don't only want to redeliver my emails, but also not let all redelivered
mails become into the unread
On Fri, Aug 06, 2010 at 08:34:01AM +0800, Yue Wu wrote:
Orgnizing all mails to be unread then mark the old ones to be read is
very tedious if mails is many.
Really?
How about T ~N ;N ?
Or in long form:
tag-pattern
pattern = new messages = ~N
tag-prefixtoggle-new
Optionally use ~O for old
pattern = new messages = ~N
tag-prefixtoggle-new
Optionally use ~O for old messages.
In my case, after re-procmail, every email will be unread, I can't recorgnize
which are those I've read, I have to look those emails one by one and recall
if it's really read or unread by me.
--
Regards,
Yue Wu
* Tim Johnson on Sunday, June 07, 2009 at 16:50:38 -0800
In the past, when I used mutt, I was using mbox type mailboxes.
Never had any problems with recipes like this:
## begin example
:0:
:0
with Maildir you don't need locking, but
* ^(From|Cc|To):.*gnome
/home/tim/Mail/Gnome
* Christian Ebert blacktr...@gmx.net [090607 17:11]:
:0
with Maildir you don't need locking, but
* ^(From|Cc|To):.*gnome
/home/tim/Mail/Gnome
/home/tim/Mail/Gnome/
^
the terminating directory slash.
You might want to poke around a bit in man 5 procmailrc for
On Mon, Jul 07, 2008 at 10:52:08PM -0700, Rem P Roberti wrote:
Never get mail as root. In fact never use root unless you really have
to, but that is a more general point.
Understood. But I thought this entry (root: rem) in my aliases file
would take care of that.
in root's crontab
On Mon, Jul 07, 2008 at 10:52:08PM -0700, Rem P Roberti wrote:
Never get mail as root. In fact never use root unless you really have
to, but that is a more general point.
Understood. But I thought this entry (root:rem) in my aliases file
would take care of that.
in
On Mon, Jul 07, 2008 at 10:52:08PM -0700, Rem P Roberti wrote:
Never get mail as root. In fact never use root unless you really have
to, but that is a more general point.
Understood. But I thought this entry (root: rem) in my aliases file
would take care of that.
On Mon, Jul 07, 2008 at 10:32:54PM -0700, Rem P Roberti wrote:
I have mutt installed on two other freebsd computers. I fetch pop mail
via getmail, and procmail puts things where they belong. I just
installed freebsd 7.0 on another computer with what I thought were the
exact same settings
I have mutt installed on two other freebsd computers. I fetch pop mail
via getmail, and procmail puts things where they belong. I just
installed freebsd 7.0 on another computer with what I thought were the
exact same settings for all of the mail programs involved. When I try
to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, December 10 at 08:23 PM, quoth Jamie Griffin:
I don't use local folders currently and manage my mail using imap
folders.
Cool, same here! I like being able to get access to all my email from
virtually anywhere.
I thought about
On Mon 10.Dec'07 at 14:51:02 -0600, Kyle Wheeler wrote:
On Monday, December 10 at 08:23 PM, quoth Jamie Griffin:
I don't use local folders currently and manage my mail using imap
folders.
Cool, same here! I like being able to get access to all my email from
virtually anywhere.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, December 10 at 09:15 PM, quoth Jamie Griffin:
Thanks Kyle
i will look at procmail and see what i can so. Any ideas on where i
could find some more infor about using procmail with imap folders?
The stuff i've looked at seems mostly
On Mon 10.Dec'07 at 15:37:00 -0600, Kyle Wheeler wrote:
On Monday, December 10 at 09:15 PM, quoth Jamie Griffin:
Thanks Kyle
i will look at procmail and see what i can so. Any ideas on where i
could find some more infor about using procmail with imap folders?
The stuff i've looked at
Am 2007-10-09 16:06:31, schrieb Rem P Roberti:
Back at it (Kyle, are you out there?). I've been trying to set up
individual mailboxes for folks I receive mail from frequently. I
create the mailbox in .muttrc (mailboxes $HOME/Mail/user), and then a recipe
like this in
.procmailrc:
:0:
Hello Patrick,
Am 2007-10-09 21:06:32, schrieb Patrick Shanahan:
Do you have something afterwards altering $MAILDIR,
AND
your procmail *path* variables should be quoted:
I am usung procmail since ober 8 years and have never quoted it.
SHELL=/bin/bash
SPOOL=/var/spool/mail
chars...
The original Log was:
8--
Subject: Re: Procmail
Folder: [EMAIL PROTECTED]/new/1192149195.19419_0.tp570.pr4006
8--
Using a full path would
Am 2007-10-10 15:29:08, schrieb Rem P Roberti:
Is it possible to use curly braces to nest conditions? For
example, there are two addresses that can be used for the FreeBSD
mailing list to which I subscribe, and I would like to incorporate them both
into the same
recipe.
Rem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Michelle Konzack [EMAIL PROTECTED] [10-14-07 12:43]:
Am 2007-10-09 21:06:32, schrieb Patrick Shanahan:
Do you have something afterwards altering $MAILDIR,
AND
your procmail *path* variables should be quoted:
I am usung procmail since ober
On 2007.10.13 05:33:27 +, Chris Bannister wrote:
On Tue, Oct 09, 2007 at 10:23:58AM -0700, Rem P Roberti wrote:
index. Otherwise, how would one get the chance to reply? Also, is it
possible to have the filtered messages placed in their respective
folders without all of the headers?
On Tue, Oct 09, 2007 at 05:15:22PM -0600, Joseph wrote:
If you have mbox it should be:
:0:
* ^From:[EMAIL PROTECTED]
$HOME/Mail/user
If maildir:
:0:
* ^From:[EMAIL PROTECTED]
$HOME/Mail/user/
For maildir, locking isn't needed, so the colon isn't needed after the
0, so:
:0
*
On Tue, Oct 09, 2007 at 10:23:58AM -0700, Rem P Roberti wrote:
index. Otherwise, how would one get the chance to reply? Also, is it
possible to have the filtered messages placed in their respective
folders without all of the headers?
Maybe you want something like this in your .muttrc:
#
* On Tue, Oct 09, 2007 Rem P Roberti ([EMAIL PROTECTED]) muttered:
Oh, brother! I didn't realize that you could get to the individual
folders from within Mutt by ESC c.
Actually, the default key binding for change-folder is c
ESCc is change-folder-readonly.
HTH,
Michael
--
The nice thing
* Breen Mullins [EMAIL PROTECTED] [2007-10-09 19:05 -0700]:
MAILDIR by itself isn't special in procmail. You usually set it so that
you can use it in your delivery recipes:
It is special. Quoting procmailrc(5):
MAILDIR Current directory while procmail is executing (that means
* Kyle Wheeler [EMAIL PROTECTED] [2007-10-09 21:23 -0500]:
On Tuesday, October 9 at 07:05 PM, quoth Breen Mullins:
MAILDIR by itself isn't special in procmail.
On the contrary, MAILDIR *IS* special. Reread the procmail
documentation. Specifically:
Right, of course. Thanks. (I knew that,
* Nicolas Rachinsky [EMAIL PROTECTED] [2007-10-10 09:28 +0200]:
* Breen Mullins [EMAIL PROTECTED] [2007-10-09 19:05 -0700]:
MAILDIR by itself isn't special in procmail. You usually set it so that
you can use it in your delivery recipes:
It is special. Quoting procmailrc(5):
Indeed, as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Rem P Roberti [EMAIL PROTECTED] [10-10-07 18:30]:
Is it possible to use curly braces to nest conditions?
yes
For example, there are two addresses that can be used for the FreeBSD
mailing list to which I subscribe, and I would like to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, October 10 at 03:29 PM, quoth Rem P Roberti:
Is it possible to use curly braces to nest conditions? For example,
there are two addresses that can be used for the FreeBSD mailing
list to which I subscribe, and I would like to
On 2007.10.10 17:46:58 +, Kyle Wheeler wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, October 10 at 03:29 PM, quoth Rem P Roberti:
Is it possible to use curly braces to nest conditions? For example,
there are two addresses that can be used for the FreeBSD mailing
On 2007.10.09 12:50:53 +, Kyle Wheeler wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, October 9 at 10:23 AM, quoth Rem P Roberti:
Boy, I'm missing something here. Ok...I did have the syntax wrong,
and now that I have the path to my mailboxes correctly stated in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, October 9 at 11:08 AM, quoth Rem P Roberti:
Oh, brother! I didn't realize that you could get to the individual
folders from within Mutt by ESC c. You want to laugh...I
responded to your last couple of posts by cut and paste!
Back at it (Kyle, are you out there?). I've been trying to set up
individual mailboxes for folks I receive mail from frequently. I
create the mailbox in .muttrc (mailboxes $HOME/Mail/user), and then a recipe
like this in
.procmailrc:
:0:
* ^From: [EMAIL PROTECTED]
user
But the mail isn't
On 10/09/07 16:06, Rem P Roberti wrote:
Back at it (Kyle, are you out there?). I've been trying to set up
individual mailboxes for folks I receive mail from frequently. I
create the mailbox in .muttrc (mailboxes $HOME/Mail/user), and then a recipe
like this in
.procmailrc:
:0:
*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, October 9 at 05:15 PM, quoth Joseph:
If you have mbox it should be:
:0:
* ^From:[EMAIL PROTECTED]
$HOME/Mail/user
In case it's not clear, the reason to use .* instead of just a space
is that the way From headers are typically sent is
On 2007.10.09 18:23:23 +, Kyle Wheeler wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, October 9 at 05:15 PM, quoth Joseph:
If you have mbox it should be:
:0:
* ^From:[EMAIL PROTECTED]
$HOME/Mail/user
In case it's not clear, the reason to use .* instead of just a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Rem P Roberti [EMAIL PROTECTED] [10-09-07 19:37]:
What I don't understand is that since the variable MAILDIR=$HOME/Mail
exists at the beginning of .procmailrc why is it necessary to state
the full path to the target mailbox in the recipe?
Do you
* Rem P Roberti [EMAIL PROTECTED] [2007-10-09 16:37 -0700]:
My thanks again to both of you. Creating my .procmailrc recipe in the
manner suggested by Joseph did the trick. What I don't understand is
that since the variable MAILDIR=$HOME/Mail exists at the beginning of
.procmailrc why is it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, October 9 at 04:37 PM, quoth Rem P Roberti:
My thanks again to both of you. Creating my .procmailrc recipe in
the manner suggested by Joseph did the trick. What I don't
understand is that since the variable MAILDIR=$HOME/Mail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, October 9 at 07:05 PM, quoth Breen Mullins:
MAILDIR by itself isn't special in procmail.
On the contrary, MAILDIR *IS* special. Reread the procmail
documentation. Specifically:
MAILDIR Current directory while procmail is
On 10/9/07, Rem P Roberti [EMAIL PROTECTED] wrote:
...snip...
getmail version 4.7.6
Python version 2.5.1 (r251:54863, Sep 16 2007, 14:19:57)
[GCC 3.4.6 [FreeBSD] 20060305]
Unhandled exception follows:
File /usr/local/bin/getmail, line 506, in main
destination_func =
On 2007.10.09 12:18:12 +, Dilip M wrote:
On 10/9/07, Rem P Roberti [EMAIL PROTECTED] wrote:
...snip...
getmail version 4.7.6
Python version 2.5.1 (r251:54863, Sep 16 2007, 14:19:57)
[GCC 3.4.6 [FreeBSD] 20060305]
Unhandled exception follows:
File
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, October 9 at 08:38 AM, quoth Rem P Roberti:
When I send a test message to myself with test as Subject, Procmail
does indeed filter the mail, creating the testing folder and putting
the mail there. But the mail goes directly to the target
What do you mean that mutt never sees it---if you open that mailbox,
is the new message missing? Is it not marked new? What's the
problem?
Is what marked new?
If you're upset that mutt didn't inform you hey! There's new mail in
a mailbox you aren't looking at!, keep in mind that mutt only keeps
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, October 9 at 09:28 AM, quoth Rem P Roberti:
What do you mean that mutt never sees it---if you open that mailbox,
is the new message missing? Is it not marked new? What's the
problem?
Is what marked new?
The new message.
If
I suspect you probably are just missing some syntax. For example,
mutt's mailboxes take full paths, not just names that are relative to
some other setting. So, for example, if procmail is saving messages to
$HOME/testing then you need to tell mutt:
mailboxes $HOME/testing
Otherwise, if you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, October 9 at 10:23 AM, quoth Rem P Roberti:
Boy, I'm missing something here. Ok...I did have the syntax wrong,
and now that I have the path to my mailboxes correctly stated in
.muttrc Mutt does indeed give me a message at the bottom
* Oliver Fuchs [EMAIL PROTECTED] [2002-09-06 20:09]:
Try this:
:0:
* ^TO_mutt-users@mutt\.org
mutt
:0:
* ^TO_mutt-users@gbnet\.net
mutt
:0:
* ^TO_mutt-announce@mutt\.org
mutt
or this:
:0:
* ^TO_mutt-(announce|users)@(mutt\.org|gbnet\.net)
mutt
Sven
On Fri, 06 Sep 2002, Sven Guckes wrote:
* Oliver Fuchs [EMAIL PROTECTED] [2002-09-06 20:09]:
Try this:
:0:
* ^TO_mutt-users@mutt\.org
mutt
:0:
* ^TO_mutt-users@gbnet\.net
mutt
:0:
* ^TO_mutt-announce@mutt\.org
mutt
or this:
:0:
*
On Fri, 06 Sep 2002 the mental interface of Oliver Fuchs told:
On Fri, 06 Sep 2002, Sven Guckes wrote:
[...]
or this:
:0:
* ^TO_mutt-(announce|users)(mutt\.org|gbnet\.net)
mutt
Sven
but also this in .muttrc:
set followup_to=yes
^^^
On Sat, 07 Sep 2002, Elimar Riesebieter wrote:
On Fri, 06 Sep 2002 the mental interface of Oliver Fuchs told:
On Fri, 06 Sep 2002, Sven Guckes wrote:
[...]
or this:
:0:
* ^TO_mutt-(announce|users)(mutt\.org|gbnet\.net)
mutt
Sven
but also this in
On Sat, 07 Sep 2002 the mental interface of Oliver Fuchs told:
[...]
Absolutely ... who wrote this?
Banned from the list.
No, banned from the pubs.
Skoal!
Elimar
--
Planung:
Ersatz des Zufalls durch den Irrtum.
-unknown-
msg30787/pgp0.pgp
Sorry to continue this off-topic thread, but Volker Kuhlmann pointed
out a bug and some things to improve in the script I sent out, so I'm
sending out a new version for the record (i.e. people searching the
list archives with Google).
:0
md5sum=| perl -e 'while (($_ = ) !/^\r?\n$/) { if (/^[
in message [EMAIL PROTECTED],
wrote parv/fastmail thusly...
in message [EMAIL PROTECTED],
wrote Sven Guckes thusly...
* parv [EMAIL PROTECTED] [2002-04-19 19:39]:
wrote Sven Guckes thusly...
...
:0
* ^[EMAIL PROTECTED]
IN.MUTT
:0
*
--Q0rSlbzrZN6k9QnT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! David T-G spake thus:
% A better solution is simply to have duplicates sent to ~/mail/duplicates
% instead of /dev/null, so that way you know what's
Rob --
...and then Feztaa said...
%
% Alas! David T-G spake thus:
% % A better solution is simply to have duplicates sent to ~/mail/duplicates
% % instead of /dev/null, so that way you know what's being filtered.
%
% ... but you'd still have the same problem even though you could manually
* parv [EMAIL PROTECTED] [2002-04-19 19:39]:
wrote Sven Guckes thusly...
=== http://www.math.fu-berlin.de/~guckes/setup/procmailrc
# 000710 - catch messages from gateway address on sonytel.be
:0
* ^[EMAIL PROTECTED]
IN.MUTT
# 000710 - added yahoogroups.com
:0
*
* John Iverson [EMAIL PROTECTED] [2002-04-19 20:48]:
Why not Just use the regular OR operator?:
:0
* ^TOmutt(-dev|-users)?@(ns.)?gbnet.net|\
^[EMAIL PROTECTED]|\
^TOmutt(-dev|-users)?@.*(cs.hmc.edu|mutt.org|yahoogroups.com)
IN.MUTT
How do you *quickly* turn off recognition
for [EMAIL
in message [EMAIL PROTECTED],
wrote Sven Guckes thusly...
* parv [EMAIL PROTECTED] [2002-04-19 19:39]:
wrote Sven Guckes thusly...
...
:0
* ^[EMAIL PROTECTED]
IN.MUTT
:0
* ^TOmutt(-dev|-users)?@.*(cs.hmc.edu|mutt.org|yahoogroups.com)
IN.MUTT
all these can be easily
David Kelly [EMAIL PROTECTED]:
Somehow I've missed the start of Edmund's .procmailrc. But why wouldn't
one do it this way rather than MD5 all that stuff manually? Have you
found the message-id header to be that unreliable?
Pointless paranoia really, but imagine this: someone could subscribe
Edmund GRIMLEY EVANS writes:
David Kelly [EMAIL PROTECTED]:
Somehow I've missed the start of Edmund's .procmailrc. But why wouldn't
one do it this way rather than MD5 all that stuff manually? Have you
found the message-id header to be that unreliable?
Pointless paranoia really, but
* Edmund GRIMLEY EVANS [EMAIL PROTECTED] [2002-04-17 23:59:39 +0100]:
David Kelly [EMAIL PROTECTED]:
Somehow I've missed the start of Edmund's .procmailrc. But why wouldn't
one do it this way rather than MD5 all that stuff manually? Have you
found the message-id header to be that
--OXfL5xGRrasGEqWY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Edmund GRIMLEY EVANS spake thus:
Pointless paranoia really, but imagine this: someone could subscribe
to the same mailing list as you, with an address
* Edmund GRIMLEY EVANS [EMAIL PROTECTED] [2002-04-17 21:31:00 +0100]:
Nicolas Rachinsky [EMAIL PROTECTED]:
I think getmail does better than fetchmail if the network goes down
while it's polling the server: fetchmail has an annoying habit of
losing its fetchids when this happens,
On Wed, Apr 17, 2002 at 10:42:46PM +0200, Nicolas Rachinsky wrote:
* Edmund GRIMLEY EVANS [EMAIL PROTECTED] [2002-04-17 21:31:00 +0100]:
Nicolas Rachinsky [EMAIL PROTECTED]:
I think getmail does better than fetchmail if the network goes down
while it's polling the server: fetchmail
Hi,
* Edmund GRIMLEY EVANS [04/17/02 22:31:00 CEST] wrote:
The start of my .procmailrc is below. The in-line Perl script removes
all header fields except Date, From, Subject, To and Cc. MD5 sums are
appended to $MAILDIR/MD5, so you should remove the beginning of that
file from time to time.
Cameron, et al --
...and then Cameron Simpson said...
%
% On 17:15 02 Mar 2002, christophe barbé [EMAIL PROTECTED] wrote:
% | It seems there is no option to avoid the use of the access time.
...
%
% Instead, I have my procmail recipe write a line to a log file when
% interesting email arrives
David,
% Instead, I have my procmail recipe write a line to a log file when
% interesting email arrives (i.e. only when one of a few recipes fires).
% And I have a small window which tails that logfile. If I were in text mode I
% could just tail that log in the background.
I like this,
I like this, and I've been looking for something this simple Can you
post or send your config for me to blatantly copy? :-)
I use a modified version of a program called root-tail
(wwwvarcx/root-tail) to tail -f my procmail log, /var/log/secure, and a
few other files Each one is displayed in a
://www.zip.com.au/~cs/scripts/mhdrs
which just recites the message headers in a shell-friendly form. For
example, this message gets:
FROM Cameron Simpson [EMAIL PROTECTED]
TO David T-G [EMAIL PROTECTED]
CC Mutt Users' List [EMAIL PROTECTED]
BCC
SUBJECT Re
Aaron, and list:
Aaron's suggested recipe works beautifully. In particular, it fixed the
odd Assigning... log entry. Thanks!
On 09/22/01, 10:56:45PM -0400, John P. Verel wrote:
Aaron,
Interesting. Your use of the only if the above succeeded is
something I'd not thought of. If would fix
At 14:09 -0400 22 Sep 2001, John P. Verel [EMAIL PROTECTED] wrote:
:0 fw:
* ^TO_kde-linux
| sed -e '/Subject:/s/\[kde-linux\] //g' KDE-linux
While this stripped off the string just fine, I was getting funny
results. Specifically, my mbox N flag was getting falsely set.
Examination of
On Sat, Aug 18, 2001 at 08:26:56PM +0200, Azzazel wrote:
Hi,
Does anybody use procmail for sorting incoming mail?
proc won't sort messages (I've tired test explained on faq page).
Or, maybe I shell use fetchmail for receiving messagess?
I rediscovered one reason why procmail won't sort.
On Sun, Aug 19, 2001 at 05:36:25AM -0400, Ken Weingold wrote:
: On Sun, Aug 19, 2001, Suresh Ramasubramanian wrote:
: Ken Weingold mutt [19/08/01 05:22 -0400]:
:
: One thing, too. It is possible that the MTA on your server is
: ignoring procmail. I had this issue once on a shell account
Eugene Lee mutt [20/08/01 00:49 -0700]:
If your MTA is not configured to use Procmail, or it's configured to
ignore ~/.forward (or any other user-maintained config file), you're
pretty much stuck. If your admin is physically accessible, try bribing
the person with food.
ITYM Beer.
quoting Joel Hammer:
Do you have a .forward file in your home directory?
yeap (|exec /usr/bin/procmail
DEFAULT=$HOME/Mail)
Then, do you have mistakes in your .procmailrc file.
do not know yet. I've set procmailrc just like you said but still it
won't work.
Now, I forget just how
Suresh Ramasubramanian [EMAIL PROTECTED] said something to this effect on
08/19/2001:
Ken Weingold mutt [19/08/01 05:22 -0400]:
One thing, too. It is possible that the MTA on your server is
ignoring procmail. I had this issue once on a shell account I got.
they use dmail, and it did
On Mon, Aug 20, 2001 at 10:35:55AM -0400, darren chamberlain wrote:
Suresh Ramasubramanian [EMAIL PROTECTED] said something to this effect on
08/19/2001:
My ISP uses Postfix, and it completely ignores both .procmailrc
and .forward files; I assume this was an administrative decision
on the
On Mon, Aug 20, 2001 at 12:24:21PM -0500, David Rock wrote:
On Mon, Aug 20, 2001 at 10:35:55AM -0400, darren chamberlain wrote:
Suresh Ramasubramanian [EMAIL PROTECTED] said something to this effect on
08/19/2001:
My ISP uses Postfix, and it completely ignores both .procmailrc
and
quoting Joel Hammer:
Now, I forget just how you make your mail agent honor the .forward file. That
will be left as an excersize to the student. Let me know when you find out.
Let's say I've solved the problem. But, nothing of making mutt honor the
.forward file, it was deleted (: and, then
1 - 100 of 178 matches
Mail list logo
