Udi Mottelo | 1 Jan 10:07 2006
Picon
Picon

Re: howto create a archive tree folder with date variable ( definition wanted )

On Thu, 29 Dec 2005 bernard.schoenacker <at> free.fr wrote:

> hi,
>
> I seek a solution to define this expression for create a tree
> folder with in procmailrc :
>
> hour  ( hh;mm;ss )
> day  ( hours;min; day;month;yyyy )
> week   (  week 1 to 52  yyyy )
> half-month                  # definition wanted
> month  ( date +%m-%Y )
> quater                      # definition waned
> half-year		    # definition wanted
> year (
>
> archive folder tree
>
> $YEAR                                       #
>  |=> $ HALF-YEAR                           #
>       |=> $QUARTERLY   ( 1/ 2/ 3/ 4/ )     # ( springs; summer;... )
>           |=> $MONTHLY                     # ( from 1°/31 except february )
>               |=> $HALF-MONTH              #
>                   |=> $WEEKLY ( 7Days )    # ( 1 to 52 weeks / year )
>                       |=> $TODAY           #
>                           |=> $HOURLY      ##*
> *
> ## become other foreign syslog with heavy traffic activity
>
> momently, i have :
(Continue reading)

Udi Mottelo | 2 Jan 11:02 2006
Picon
Picon

Re: howto create a archive tree folder with date variable ( definition wanted )

On Sun, 1 Jan 2006, Udi Mottelo wrote:

> On Thu, 29 Dec 2005 bernard.schoenacker <at> free.fr wrote:
>
>> hi,
>> 
>> I seek a solution to define this expression for create a tree
>> folder with in procmailrc :
>> 
>> hour  ( hh;mm;ss )
>> day  ( hours;min; day;month;yyyy )
>> week   (  week 1 to 52  yyyy )
>> half-month                  # definition wanted
>> month  ( date +%m-%Y )
>> quater                      # definition waned
>> half-year		    # definition wanted
>> year (
>> 
>> archive folder tree
>> 
>> $YEAR                                       #
>>  |=> $ HALF-YEAR                           #
>>       |=> $QUARTERLY   ( 1/ 2/ 3/ 4/ )     # ( springs; summer;... )
>>           |=> $MONTHLY                     # ( from 1°/31 except february )
>>               |=> $HALF-MONTH              #
>>                   |=> $WEEKLY ( 7Days )    # ( 1 to 52 weeks / year )
>>                       |=> $TODAY           #
>>                           |=> $HOURLY      ##*
>> *
>> ## become other foreign syslog with heavy traffic activity
(Continue reading)

arbatax | 2 Jan 13:21 2006
Picon

newbie - help with a simple filtering recipe

Hi all,

I have a small server with 6 users and I am looking for a simple filter that can
sort the mail that is downloaded to one single account via fetchmail.

Mail should be sorted based on the "to" headers and copied to the relevant
mailboxes. With one exception: user1 should be able to get his own mail and
user2's mail as well.

The recipe kind of works as it is, but there are a couple of problems:

- if I send mail to user1, he gets 2 copies of the same message
- if I send mail to user2, he gets the mail, but user1 doesn't and the following
error is displayed in the log:

Error while writing to "/var/spool/mail/user1"

I have been struglging with the documentation for a couple of days bu this is as
far as I was able to get. Any help will be greatly appreciated.

RECIPE:

PATH = $HOME/bin
SHELL=/bin/sh
LOGFILE=/var/log/procmaillog
VERBOSE=yes
MAILDIR=$HOME/mail

:0Hc:
* ^(for|Cc|To).*user1 <at> mydomain\.com|.*user2 <at> mydomain\.com
(Continue reading)

Picon

Procmail & virtual domains

Hello,

I'm trying to configure qmail & spambouncer (SB) on my system.
Spambouncer is called by procmail as soon as a mail is received, then 
the result is stored inside the user mailbox.
I have already configured sb on a small system without problem. The 
result of the treatment produced by procmail and sb was stored on the 
mailbox directory specified inside the .procmailrc file (MAILDIR directive).
On this system, configuration was easy and works fine (one mailbox per 
user).

Now, I'would like to use SB on a system running the qmail agent, with 
multiple virtual domains configured for a single user (managed by vpopmail).
Things are more complex now. My maildir looks like this :

$home/mail/.qmail-files_for_domain1...
$home/mail/.qmail-files_for_domain2...
$home/mail/.qmail-files_for_domain3...
$home/mail/.domain1/....
$home/mail/.domain2/....
$home/mail/.domain3/....

Well, procmail can be called easely inside each .qmail-* files.

I just wonder how procmail will be able to find the good path to store 
the result of its treatment in that case ?

Thanks,

VF
(Continue reading)

Udi Mottelo | 3 Jan 09:29 2006
Picon
Picon

Re: newbie - help with a simple filtering recipe

On Mon, 2 Jan 2006, arbatax wrote:

> Hi all,
>
> I have a small server with 6 users and I am looking for a simple filter that can
> sort the mail that is downloaded to one single account via fetchmail.
>
> Mail should be sorted based on the "to" headers and copied to the relevant
> mailboxes. With one exception: user1 should be able to get his own mail and
> user2's mail as well.
>
> The recipe kind of works as it is, but there are a couple of problems:
>
> - if I send mail to user1, he gets 2 copies of the same message
> - if I send mail to user2, he gets the mail, but user1 doesn't and the following
> error is displayed in the log:
>
> Error while writing to "/var/spool/mail/user1"
>
> I have been struglging with the documentation for a couple of days bu this is as
> far as I was able to get. Any help will be greatly appreciated.
>
> RECIPE:
>
>
>
> PATH = $HOME/bin
> SHELL=/bin/sh
> LOGFILE=/var/log/procmaillog
> VERBOSE=yes
(Continue reading)

Mr Duck | 3 Jan 22:08 2006

OT: removing file attachments

All,

   The office for which I work uses procmail/demime to strip
certain file attachments from emails, more specifically
winmail.dat. For some reason, the version of Microsoft Outlook
we run chokes on this file, so we simply strip it from the
email.

   The problem comes when a second file is attached.  Demime
is stripping both files.

   I realize that this is a procmail thread, but was hoping
that a little leniency would be granted and someone might
know of a tool that I could use that would only strip out
the winmail.dat files.

Mr Duck
Volker Kuhlmann | 3 Jan 23:30 2006
Picon

Re: OT: removing file attachments

>    The office for which I work uses procmail/demime to strip
> certain file attachments from emails

>    The problem comes when a second file is attached.  Demime
> is stripping both files.

I too have been looking for an attachment stripper which gives me more
control, but haven't found one yet. So far I've used stripmime.pl. You
could hack it if you speak perl (and if you do, send me a copy!). I've
made some minor changes, which I put here:

http://volker.dnsalias.net/soft/script/stripmime-1.1.pl.3-vk

The script has no version management and doesn't seem looked after.
I'm looking for something better too.

Volker

--

-- 
Volker Kuhlmann			is possibly list0570 with the domain in header
http://volker.dnsalias.net/		Please do not CC list postings to me.
Gary Funck | 4 Jan 01:16 2006

RE: removing file attachments

> From: Mr Duck
> Sent: Tuesday, January 03, 2006 1:09 PM
> [...] someone might
> know of a tool that I could use that would only strip out
> the winmail.dat files.

Anything useful in this reply?
http://www.xray.mpe.mpg.de/mailing-lists/procmail/2002-10/msg00308.html
Don Russell | 4 Jan 08:11 2006

adding an Expires: header...

I receive mail from several places (news alerts etc) and in an effort to
prepare for some automated clean up, I add an Expires: header.

I'm pretty green with respect to procmail, and am asking for opinions
from more experienced people. I have a sample recipe from my .procmailrc
file.
It works fine, but my question is: is there a better way?

Thanks,
Don

:0
* ^From:.*notifier <at> fbo\.gov
{
   EXPIRE = `date --utc -R --date="+7 days"`
   :0 wfc
   | formail -I "Expires: $EXPIRE"

   :0 :
   MailingLists/fbo
}
Dallman Ross | 4 Jan 12:26 2006

Re: adding an Expires: header...

On Tue, Jan 03, 2006 at 11:11:16PM -0800, Don Russell wrote:

> It works fine, but my question is: is there a better way?

> 
> :0
> * ^From:.*notifier <at> fbo\.gov
> {
>    EXPIRE = `date --utc -R --date="+7 days"`
>    :0 wfc
>    | formail -I "Expires: $EXPIRE"
> 
>    :0 :
>    MailingLists/fbo
> }

Except for what seems to me to be an extraneous c-flag on your
nested recipe, it looks okay to me at a quick glance.  (You don't
need to copy a message in order to filter it with the f-flag.)  You
could add the h-flag to the first nested recipe, since formail is
only writing to the header.

If you define EXPIRE earlier on, you could remove the
nested recipe.  The trade-off is, you'd now be using up
env space, and, worse, running date, on every single message.
Hmm.  How about:

  :0 fw h
  * ^From:.*notifier <at> fbo\.gov
  | formail -I "Expires: `date --utc -R --date='+7 days'`"
(Continue reading)


Gmane