headers
Clive Crous | 3 Jun 2010 03:10
Picon
Gravatar

trouble getting maildir format message storage

Hello everyone,

I'm having a hard time getting anything other than a single file named
"?" (question-mark) created into which all my emails are being stored.

The only "odd" looking information in the output is the following:
"rocmail: Couldn't chdir to "/home/clive

This is the content of one of my procmailrc files (only 4 lines):
MAILDIR=/home/clive

:0
Mail/clive.crous <at> gmail.com/

I have several files like this each run individually for different
email addresses of mine.
A single massively-huge file is generated which contains everything
and is named:

/home/clive/Mail/clive.crous <at> gmail.com/?

I'm attempting to get maildir style storage with cur/new/tmp
structures and one file per message.
Any advice or help would be greatly appreciated!

Thank you,
Clive Crous
Permalink | Reply | 0 comments |
headers
Hylton Conacher (ZR1HPC | 6 Jun 2010 11:46
Picon

Test: Please ignore

oomjebafloob
Permalink | Reply | 0 comments |
headers
Hylton Conacher (ZR1HPC | 6 Jun 2010 12:06
Picon

Help needed.

Hi,

Please let me know if tis is the correct address to use for procmail
queries on using procmail. If I recall correctly there was a
procmail-users list but I have had all requests to subscribe to it
rejected as not being available.

Please advise

Thanks
Regards
Hylton
--

-- 
========================================================================
Lions Club member of http://www.fishhoeklionsclub.org.za
Using openSuSE 11.0 with KDE
Skype: hylton.conacher
========================================================================
Permalink | Reply | 3 comments |
headers
Charles Gregory | 6 Jun 2010 15:09

Re: Help needed.

On Sun, 6 Jun 2010, Hylton Conacher (ZR1HPC) wrote:
> Please let me know if tis is the correct address to use for procmail
> queries on using procmail. If I recall correctly there was a
> procmail-users list but I have had all requests to subscribe to it
> rejected as not being available.

The address you are using *IS* the procmail users list.
Just send your inquiries here.

And for future reference, please do not send an 'unsubscribe' request to 
the actual list. There is a link at the bottom of every list mail for a
web page where you can manage your subscription or cancel it.

- C
Permalink | Reply | 0 comments |
headers
Charles Gregory | 6 Jun 2010 15:12

Re: [pro] Help needed.


Oh, and please pay close attention to your headers when 'replying' to a 
post. It is considered good netiquette to reply to the list and not e-mail 
responses directly to the individual sender of a list posting. 
Unfortunately, with the settings on the procmail list, most mail clients 
will 'default' to sending a reply to the sender and not the list.\
So you will need to 'reply to all' and then manually remove the sender 
from the headers.

- C
Permalink | Reply | 0 comments |
headers
Professional Software Engineering | 6 Jun 2010 16:17

Re: Help needed.

At 12:06 2010-06-06 +0200, Hylton Conacher (ZR1HPC) wrote:
>Please let me know if tis is the correct address to use for procmail
>queries on using procmail. If I recall correctly there was a
>procmail-users list but I have had all requests to subscribe to it
>rejected as not being available.

IIRC, the procmail-users list was a reflector for this list.  procmail.org 
had some hosting issues some years ago (er, like 8 or 10 years now), and 
the procmail-users ceased to be used as a result.

As to the test message - try to avoid sending such things since when the 
test is successful, you'll have deposited a worthless message into the 
inbox of hundreds (or in some case, thousands) of recipients.  Sending you 
actual query would be better - as yet, theres still no procmail question 
posed to the group on your behalf.

Note that the archives of the procmail list can be searched through one of 
several public archives, including:

         <http://www.xray.mpe.mpg.de/mailing-lists/procmail/>

---
  Sean B. Straw / Professional Software Engineering

  Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
  Please DO NOT carbon me on list replies.  I'll get my copy from the list.
Permalink | Reply | 0 comments |
headers
Hylton Conacher (ZR1HPC | 7 Jun 2010 07:46
Picon

EOF and future recipes

Is there a way for the procmailrc file to signal an end to the list of
recipes even though there may still be incomplete or partial recipes
below the EOF i.e.

#Assignments
Recipe 1
EOF
Recipe 2

Could it be as simple as inserting EOF on a new line after the last
recipe I want executed i.e. Recipe 2 above would not be executed as it
is after the EOF?

Regards
Hylton

--

-- 
========================================================================
Lions Club member of http://www.fishhoeklionsclub.org.za
Using openSuSE 11.0 with KDE
Skype: hylton.conacher
========================================================================
Permalink | Reply | 14 comments |
headers
Olivier Nicole | 7 Jun 2010 07:49
Picon
Favicon

Re: EOF and future recipes

> Is there a way for the procmailrc file to signal an end to the list of
> recipes even though there may still be incomplete or partial recipes
> below the EOF i.e.

Comment them out?

Olivier
Permalink | Reply | 0 comments |
headers
Professional Software Engineering | 7 Jun 2010 08:12

Re: EOF and future recipes

At 07:46 2010-06-07 +0200, Hylton Conacher (ZR1HPC) wrote:
>Is there a way for the procmailrc file to signal an end to the list of
>recipes even though there may still be incomplete or partial recipes
>below the EOF i.e.

It's a good idea not to have incomplete (i.e. syntactically broken) recipes 
in a live config.

Perhaps you could explain what you're trying to accomplish - why would you 
have incomplete recipes in a live config?  Is it that you really wish to 
force a premature abort (and if so, why have the other recipes anyway?)

You can unset HOST:

HOST=

This will terminate the processing of the current rcfile and NOT generate 
an error.

---
  Sean B. Straw / Professional Software Engineering

  Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
  Please DO NOT carbon me on list replies.  I'll get my copy from the list.
Permalink | Reply | 11 comments |
headers
Hylton Conacher (ZR1HPC | 7 Jun 2010 11:12
Picon

Re: EOF and future recipes

Professional Software Engineering wrote:
> At 07:46 2010-06-07 +0200, Hylton Conacher (ZR1HPC) wrote:
>> Is there a way for the procmailrc file to signal an end to the list of
>> recipes even though there may still be incomplete or partial recipes
>> below the EOF i.e.
> 
> It's a good idea not to have incomplete (i.e. syntactically broken)
> recipes in a live config.
> 
> Perhaps you could explain what you're trying to accomplish - why would
> you have incomplete recipes in a live config?  Is it that you really
> wish to force a premature abort (and if so, why have the other recipes
> anyway?)

I receive a LARGE number of emails(Approx 1500 per month) that are
sorted into their different folders and the really important ones stay
in my Inbox to be looked at first.

I would therefore like to having a working procmailrc file that I can
periodically add to. It is very possible that I remember part of a
future recipe but nothing more. I would therefore add the details I can
remember into the procmail file as part of a future recipe and know that
Procmail will not process the text I have jotted down because there was
and EOF before it.

As Olivier stated earlier I could just comment them out but procmail
will still read the file to the end. Apart from this there are currently
 over 5 A4 pages of recipes that need completing when the relevant email
arrives i.e. 5 pg to be commented out, line by line!
(Continue reading)

Permalink | Reply | 10 comments |

Gmane