Saving mail in MAILDIR format

I am presently using Sendmail on a FreeBSD 5.4 system. I have ProcMail 
installed and am using it in a limited capacity.

By default, mail saved in /var/mail is saved in MBOX format. I would 
like to have it saved in MAILDIR format. I was told that ProcMail could 
accomplish this feat. How do I go about making it save mail 
in /var/mail in MAILBOX format by default?

Thank!

--

-- 
Gerard Seibert
gerard <at> seibercom.net

PGP: http://www.seibercom.net/sig/gerard.asc

____________________________________________________________
procmail mailing list   Procmail homepage: http://www.procmail.org/
procmail <at> lists.RWTH-Aachen.DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

Re: Saving mail in MAILDIR format

On Apr 1, 2006, at 6:27 AM, Gerard Seibert wrote:

> How do I go about making it save mail in /var/mail in MAILBOX format 
> by default?

Is /var/mail really where you want to save it like that?
Normally, I'd choose the user's home directory, in which case, the 
statement in /etc/procmailrc is:

	DEFAULT=$HOME/Maildir/

It's not the "Maildir" that does it, but the trailing "/".
But I expect that the effect you are looking for could be had as 
follows:

	DEFAULT=/var/mail/$LOGNAME/

It's just that I would advise against it... as /var/mail is "expected" 
to be full of mbox files, and who knows what surprises await you....

Aloha mai Nai`a!
--

-- 
"Please have your Internet License             http://kapu.net/~mjwise/
   and Usenet Registration handy..."

Re: recipe to add keywords to an imap message

Sur 2006-03-31, Don Russell skribis:
> NM Public wrote:
>> [snip]
>>
>> I just did some experiments with this on a new system that I'm
>> setting up and discovered that you need to "seed" the
>> mbox-formatted mailbox with a message that contains the IMAP
>> keyword(s) that you want to use. That will ensure that the first
>> message in the mbox is a pseudo message that includes a header
>> like this:
>>
>>   X-IMAP: 1143223486 0000000047 $Label5
>>
>> Do NOT try to create this header by hand. Instead use a decent
>> IMAP client and the IMAP protocol to assign keyword(s) to any
>> message in the target mailbox. To set keywords with Pine, see the
>> instructions here:
>>
>>   <http://www.ii.com/internet/messaging/pine/pc/#keywords>
>>
>> Also note that this only works with UW IMAP (AFAIK).
>
> That's very interesting, and more in line with the sort of thing I was
> expecting. The replies I got from the Thunderbird people made a
> distinction between "headers" and ading keywords to the imap message.
> The later made me think there were some imap commands I had to use....
>
> But... I added this recipe to my /etc/procmail file and it works very
> well. Maybeby coincidence rather than by design? I do notice that when I
> view the e-mail source on the client though, there are no X-Keyword:

Re: can't create user output file

On Thu, 30 Mar 2006, David Koski wrote:

> Only errors about quotas:
>
> Mar 27 00:32:40 mail kernel: VFS: Can't read quota structure for id 583.
> Mar 27 06:10:56 mail kernel: VFS: Quota for id 596 referenced but not present.
> Mar 27 06:10:56 mail kernel: VFS: Can't read quota structure for id 596.
> Mar 27 07:08:23 mail kernel: VFS: Quota for id 597 referenced but not present.
>
> But hog has none:
>
> # quota hog
> Disk quotas for user hog (uid 489): none

 	Quota problem, but the user has no quota limits?  I'm sory
 	that I can't help you.  Yet, looks like a bug.  However, the
 	right way to see quota status is:  quota -v hog
 	If the user has no quota limits you should see zero in the fields

Bye,
  Udi

Re: recipe to add keywords to an imap message

NM Public wrote:
> Sur 2006-03-31, Don Russell skribis:
>   
> [snip]
> I'm happy to hear that this works with Dovecot IMAP and I've 
> added that bit of information to the #keywords section of my 
> Procmail Quick Start. Question: What mailbox format are you using 
> with Dovecot? I assume mbox, but want to make sure. It would be 
> very cool if the X-Keywords header also worked with 
> maildir-formatted mailboxes, but I suspect it doesn't (since the 
> IMAP metadata is stored in the filename and sometimes in separate 
> files when maildir mailboxes are used).

Yes, I am using mbox format.

I read that is a better format to ue when there are more than a couple 
of thousand mail messages kept.

But, I suppose maildir was invented for a reason... 

DR

Re: Can't get action | to work

On Tue, Mar 28, 2006 at 09:41:51PM -0500, fleet <at> teachout.org wrote:

> On Tue, 28 Mar 2006, Dallman Ross wrote:

> >        :0 c:
> >        * ^Return-Path:.* <at> hotmail
> >        * ^Subject:.*\/[^ 	].*
> >        spamtest/gotcha
> >
> >        :0 A
> >        | echo -e $TIME "bounce address" $MATCH "\n" spamtest/spam.log
> >
> >        :0
> >        spamtest/spamlast
> 
> Ok.  This works; but I have some questions.

Before I get to your questions, let me give a warning that I have
been reminded (elsewhere, coincidentally) that there is a bug in
my algorithm above.  That is, if the Subject is empty, the
recipe set won't run right.  One solution is to collect the Subject
earlier on, unconditionally.

> 1. I'm still seeing the pipe command being assigned to LASTFOLDER.
> procmail: Assigning "LASTFOLDER= echo -e $TIME "bounce address" $MATCH >>
>           spamtest/spam.log"
> >From fleet <at> teachout.org Sat Mar 25 23:27:06 2006 -0500
>  Subject: 60% off Generíc Víagra

That's normal, because for the original message that is being eaten by

Anti-Spam Tactic

---------- begin forwarded message from Mail Delivery Subsystem ----------

On Tue Mar 28 03:35:26 2006 Michelle Konzack wrote:

[snip]

Thanks for the additional information, Michelle.

It's been a long time since I last heard from anyone in La Belle France.

I used to live in a little place called Thomery, near Fountainbleau, but that
was many years ago.  I think I got the spelling on all that correct, (I hope).


William Vance

Re: Can't get action | to work

Am 2006-03-27 21:05:59, schrieb fleet <at> teachout.org:

> Here's my entire test recipe:
> 
>       :0
>       * ^Return-Path:.* <at> hotmail
>          {
>             :0
>             * $ ^Subject:$WS\/.*$
>             | (echo -e $TIME "bounce address" $MATCH "\n" >> spamtest/spam.log)
> 
>             :0
>             spamtest/gotcha
>          }

AFAIK...
----8<----------------------------------------------------------
:0
* ^Return-Path:.* <at> hotmail
* $ ^Subject:$WS\/.*$
{
  BLUB=`echo "$TIME bounce address $MATCH" >> spamtest/spam.log`

  :0
  spamtest/gotcha
}
----8<----------------------------------------------------------

should be enough.  The rest is your homework.

Re: recipe to add keywords to an imap message

Am 2006-04-02 06:57:03, schrieb Don Russell:

> I read that is a better format to ue when there are more than a couple 
> of thousand mail messages kept.

???

> But, I suppose maildir was invented for a reason... 

Maildir is there to keep you from screwing up, if you have several
10.000' mesages in your folders...  My own ~/Maildir/ holds now
around 7 Million messages in around 1400 Mailfolders...

One of the biggest folders are <debian-user> 490.000 Msg, <lkm>
420.00 msg and <debian-user-german> 230.000 msg.

Try to open such Mailboxes without Maildir...

And if new messagers are arriving, lockig will kill your nervs.

Greetings
    Michelle Konzack

--

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
Michelle Konzack   Apt. 917                  ICQ #328449886
                   50, rue de Soultz         MSM LinuxMichi
0033/3/88452356    67100 Strasbourg/France   IRC #Debian (irc.icq.com)

Re: Can't get action | to work

Michelle Konzack schreef:

> * $ ^Subject:$WS\/.*$

That is an awkward way to capture the value of the Subject header field.
Only the first whitespace is chopped (there can be more), and the ending
newline is captured too.

Put this somewhere at the start

  H_SUBJ   # unset
  :0
  * $ ^Subject:.*\/[^$WS].*
  { H_SUBJ = "$MATCH" }

and use ${H_SUBJ} in your further recipes.

> {
>   BLUB=`echo "$TIME bounce address $MATCH" >> spamtest/spam.log`

With the awkward caption, that would write out $MATCH including the
extra newline.

--

-- 
Ruud