headers
David W. Tamkin | 1 Aug 1999 03:52
Picon
Favicon

Re: limit to number of recipes?

Glen asked,

| Is there a limit to the number of recipes that Procmail can read within
| the $HOME/.procmailrc file?  It seems that when I approach 20 or so my
| email program collapses and won't download the mail.

Could you be so short of RAM that procmail can't fit both the message and the
rcfile in memory?

Under assorted Unix variants I've had very, very long rcfiles, and the only
problems have been errors in my recipes.

Glen, what happens if you split it into several files and use INCLUDERC?
Permalink | Reply | 0 comments |
headers
Eric Smith | 2 Aug 1999 00:11
Favicon

getting the rule right.


Hi

Here is the first bit of the _first_ (normally hidden  header of mails from the vim list.  I
want to use this header to trap mail from the list.  There is a reason why I
want to use this particular header.

>From vim-return-152

This catches the mail but is too indiscriminate:
:0:
*^From .*vim*
vim

These two both fail to catch the mail
:0:
*^From .*vim-ret
vim

:0:
*^From .*vim-ret*
vim

I cannot understand why the last ones do not match the header above.
Any suggestions?

Thanx

--

-- 
Eric
(Continue reading)

Permalink | Reply | 3 comments |
headers
Mike Zimmerman | 2 Aug 1999 03:42

procmail only functioning when logged in?

I've just switched ISPs and am seeing something odd
that I cannot figure out yet.

Took my old .procmailrc file, copied over the .forward,
and thought I was ready to go.

however what I have found is that procmail only functions
when I am logged in AND am in my mailer (in my case
I still use elm).

If I am not logged in, and not in the mailer, then no filtering
takes place.

Relevant info (I guess/hope)

-rwsr-sr-x   1 root     mail        58532 Apr  6 18:55 /usr/bin/procmail* 

-rw-r--r--   1 zimmy    zimmy         805 Jul 30 10:47 .procmailrc 

-rw-r--r--   1 zimmy    zimmy          59 Jul 23 14:23 .forward     

which contains 
"|IFS=' ' && exec /usr/bin/procmail -f- || exit 75 #zimmy"  

maybe the suid bit on world for procmail?

from my .procmailrc

PATH=/home/zimmy/bin:/usr/bin:/usr/ucb:/bin:/usr/local/bin:.
MAILDIR=/home/zimmy/Mail      # You'd better make sure it exists
(Continue reading)

Permalink | Reply | 0 comments |
headers
Stephen Hill | 2 Aug 1999 04:01
Picon
Favicon

Re: getting the rule right.

On Mon, 2 Aug 1999, Eric Smith wrote:
> These two both fail to catch the mail
> :0:
> *^From .*vim-ret
> vim
> 
> 
> :0:
> *^From .*vim-ret*
> vim
> 
> 
> I cannot understand why the last ones do not match the header above.
> Any suggestions?

I could be corrected, but I believe that these can be seen to "say" look for the word "From" at
the beginning of the line, followed by a space AND THEN FOLLOWED BY ONE OR MORE CHARACTERS,
followed by "vim-ret".  In the second rule, the trailing * is unnecessary, and the two filters are
the same.  Since your data is "From vim-ret", the filter fails because of my upper-cased comment
above.  If you make either rule "^From.*vim-ret", it will trip, although with the possibility of
false positives in cases like "From anyvim-retiree", etc.  If you know that the ^From line will be
the only only one that you wish to trap, try "^From vim-ret".

Best of luck,
  Steve 

------------------------------------------- 
E-mail: 
   Home:  steveh <at> iname.com
-------------------------------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
Walter Dnes | 3 Aug 1999 03:50
Picon

Re: getting the rule right.

On Mon, 2 Aug 1999 00:11:38 +0200, Eric Smith <eric <at> fruitcom.com>
wrote:

>:0:
>*^From .*vim-ret
>vim

  Shouldn't that be...

 *^From vim-ret

...possibly even...

 *^From.*vim-ret

  There's no need for the ".*" if you already have the space
in your regular expression.  Also, there is no need for a
trailing ".*", let alone "*".

--

-- 
Walter Dnes <waltdnes <at> interlog.com> procmail spamfilter
http://www.interlog.com/~waltdnes/spamdunk/spamdunk.htm
Permalink | Reply | 0 comments |
headers
Umar Goldeli | 3 Aug 1999 08:41
Picon

MAILDIR+Sendmail Virtusertable

Greetings,

I am rather new to procmail and also new to the list.

I've been wrestling with procmail all morning to achieve what I thought
would have been considered something simple.. :)

What I'm trying to do is get a Linux box to host mail services for various
domains and then deliver the mail into a different MAILDIR depending on
the destination domain. E.g.:

Mail to user <at> abc.com goes to /var/spool/abc.com/u/s/user
Mail to user <at> xyz.com goes to /var/spool/xyz.com/u/s/user

I figure that I'll probably have to change the Mlocal line in
/etc/sendmail.cf as well to perhaps pass the username from the
virtusertable as well?

Any information would be *greatly* appreciated.

Thanks in advance...

Cheers,
Umar.
Permalink | Reply | 0 comments |
headers
Christophe Zwecker | 3 Aug 1999 09:34
Picon

filter number <at> foobar.com

Hi,

I need to bounce (with a small text) mail that doesn follow the
pattern of a six digit number as the username. Anyother char than
number or less than six digits is supposed to bounce. 
How would I address such a thing ?

thx for any hints
--

-- 
Christophe Zwecker                     mail: doc <at> zwecker.de
Hamburg, Germany                        fon: +49 179 3994867

UNIX is user-friendly. It's just not ignorant-friendly and 
idiot-friendly.Build a system even a fool can use,and only 
a fool will want to use it.
Permalink | Reply | 19 comments |
headers
Martin McCarthy | 3 Aug 1999 09:21
Picon
Picon

Re: getting the rule right.

> Here is the first bit of the _first_ (normally hidden header of mails
> from the vim list.  I want to use this header to trap mail from the
> list.  There is a reason why I want to use this particular header.
> 
> >From vim-return-152
> 
> 
> This catches the mail but is too indiscriminate:
> :0:
> *^From .*vim*
> vim
> 
> These two both fail to catch the mail
> :0:
> *^From .*vim-ret
> vim
> 
> 
> :0:
> *^From .*vim-ret*
> vim
> 
> 
> I cannot understand why the last ones do not match the header above.
> Any suggestions?

One of the best things to do, if you have something happening that you
don't understand, is to set the VERBOSE variable in your .procmailrc and
get procmail to tell you exactly what it is doing.
(Continue reading)

Permalink | Reply | 0 comments |
headers
John Poltorak | 3 Aug 1999 09:48
Picon

Extracting lines from emails

How would I go about using procmail to create a list of all the
Message-IDs in all my emails?

--

-- 
John
Permalink | Reply | 5 comments |
headers
Bert Hiddink | 3 Aug 1999 18:34
Picon

Sendmail error message

Hello,

I want to send out (by means of a Perl script invoqued from the web) 
a message to a certain number of subscriber using /usr/sbin/sendmail. 
When the e-mail is correct, there is no problem. However, when there 
is an address with an incorrect format f.e. hiddink  _ <at> galileo.or.cr, 
sendmail sends the following message to the web:

hiddink  _  <at> ... User unknown galileo.or.cr... User unknown 
/nonexistent/dead.letter... cannot
open /nonexistent/dead.letter: No such file or directory 

This presents 2 problems for me:
1) I do not want these error messages to be printed to the 
subscriber, I would like them only to be logged to an administrator.

2) I am on a virtual server, I do not have administrative control 
over sendmail or sendmail.cf. Appearantly, the error-messages are 
stored per default to /nonexistent/dead.letter which does not exist. 
Therefore, error-messages are lost and besides, I do not have acces 
to them.

Would it be possible for procmail to send out these messages? Since I 
have administrative control over procmail, this would enable me to 
log the error-messages there where I want?

Or would there be other solutions?

Many thanks in advance for your help!
(Continue reading)

Permalink | Reply | 1 comment |

Gmane