egrep body & folder delivery recipe problem

hi, 

...my problem is i want to deliver mail - headers+body -- only if
regex in a file match at least one body line.  otherwise, deliver
mail to junk folder.  i don't know how how to check the status code
of a pipe and still be able to have the complete message, not only
the body.

i had searched the archives, but i keep hitting upon variations of
these...

  :0:
  * B ?? <regex>
  <action>

  :0 fw:
  | formail -I "" | egrep -f <file>

  :0 fbw:
  | egrep -f <file>

currently i have the following, which, of course, gives false
positives, but works as written...

:0
* ^TOminolta <at> (e|yahoo)groups?\.com
{
  :0 w:
  * ? /usr/bin/egrep -i -f ${HOME}/cf/mail/minolta-regex.list
  folder

Re: Multiple Users with one login

At 18:17 2002-02-28 -0800, chris did say:
>I got it work with the following setup. At least it passed all the tests I
>put to it. I am sure there is a way to simplify it, not to mention I have to
>add a new ruleset for each To: I plan to filter. I need to add some loop
>checks, etc...

Tell me, how well does it work for:

To: email1 <at> domain.com, email2 <at> domain.com

Bcc: email2 <at> domain.com

To: email2 <at> domain.com
Cc: email1 <at> domain.com

To: somemailinglist
Cc: email2 <at> domain.com

etc ?

>I am glad to just get it working.

If you say so.

Your indentation (or lack thereof, though perhaps it was brought on by your 
mailer?) makes it rather difficult to follow your ruleset here, and I don't 
follow why you use:

         :0
         {

Like an Alias...

Hi there...
I would like to create a rule in procmailrc file... but it's not working...
like:

if the message is from * <at> mydomain.com and the message is to
linux <at> mydomain.com
send the message to linux-addr <at> mydomain.com

so...
---- Start
:0
*    ^From:.* <at> mydomain.com*
*    ^To:.*linux <at> mydomain.com*
{
    :0
    ! linux-addr <at> mydomain.com
}
----- End

but... didn't work...
anyone could help me?!

and i'd like to increase with two conditions... like
*    ^cc:.*linux <at> mydomain.com*
*    ^bcc:.*linux <at> mydomain.com*

please... i need to make this with procmail...

Thanks!!

Re: Like an Alias...

> From: "Fred" <mfleao <at> planae.com.br>

> Subject: Like an Alias...

"Touched for the very first time"?

> :0
> *    ^From:.* <at> mydomain.com*
> *    ^To:.*linux <at> mydomain.com*
> {
>     :0
>     ! linux-addr <at> mydomain.com
> }
> ----- End
>
> but... didn't work...
> anyone could help me?!

First, you don't want or need the asterisks at the end of
your expression.  (Even if you did, those are syntactically
wrong.)

Second, you don't need to start a nested brace to do a
simple forwared.

Third, you should get in the habit of quoting dots, as they
are special characters to procmail when unquoted (meaning
"any char").

	:0

Re: .forward does call autoreply.proc but no message gets sent

At 13:14 2002-03-01 +0000, Support did say:

># NetStructure AutoReply
>"| exec /usr/bin/procmail /usr/ins/intel/gui/bin/autoreply.proc #
>obantec-dial"

Where'd you find this syntax?

Besides the forward syntax being wrong, the procmail commandline isn't valid.

Perhaps you should try the .forward syntax shown at the foot of my 
disclaimer page - that should work right off.

What are the perms on the procmail script itself?

>######################################################################
># global autoreply procmail script

If it really is "global" perhaps it aught to be chucked under 
/etc/procmailrcs/ (which procmail treats specially, see the main 
manpage).  Also, typically procmail scripts are '.rc' files.

>:0 Whc: $HOME/vacation.lock

$HOME/vacation.cache$LOCKEXT

would be a trite more authentic for the lockfile name.

>#Check if VACATION file is found in the user's home directory
>* ? test -f $HOME/.vacation

Procmail outgoing filter

Re: Procmail outgoing filter

At 17:16 2002-03-01 -0300, Antonio Lenda Filho did say:
>Hi there. I´m looking for a solution to filter sendmail´s outgoing 
>messages using procmail. I´ve found several ways to do it but no one seems 
>to work. Does anyone got an effective soluction for this problem and could 
>post it?

Follow the link to my disclaimer.  There's some tentative stuff there about 
invoking procmail from within sendmail.  It can be done, but it isn't 
efficient (to get the message back into sendmail involves RE-INVOKING 
sendmail with the message, which will add an additional received header).

---
  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.

_______________________________________________
procmail mailing list
procmail <at> lists.RWTH-Aachen.DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

Re: Procmail outgoing filter

At 18:21 2002-03-01 -0600, David W. Tamkin did say:
>| efficient (to get the message back into sendmail involves RE-INVOKING
>| sendmail with the message, which will add an additional received header).
>
>The problem of the extra Received: header can be relieved, can it not, by
>having the procmailrc for outgoing mail call formail (more inefficiency,
>whee!) to remove the one added by the first pass through sendmail.

The headers aren't the same.  For one, the original received should 
identify the local origin - the new one (which the procmail invoked 
sendmail will add) would identify procmail as the origin.  In the grand 
scheme, probably not a big deal - but it is something to watch for.

---
  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.

_______________________________________________
procmail mailing list
procmail <at> lists.RWTH-Aachen.DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

Re: procmail error when forwarding to a razor database

At 08:37 2002-03-03 -0600, Mike Loiterman wrote:

>I'm trying to set up a local mail account that I can forward messages
>to so that they will be reported to the Razor database.  All that I
>need to do is run the command
>"| spamassassin -r"on the messages.

Why can't you just invoke this from your procmail rule?

:0
* somecondition
| spamassassin -r

>Someone suggested doing an alias in /etc/mail/aliases that looked
>like this:
>
>spam:    "|/usr/bin/spamassassin -r"
>
>I keep getting a procmail error that says "unknown user".  I am doing
>"newaliases" in between each modification.

If you re-read your post, you might notice that you're not showing the 
procmail commands you're using to try to send mail to this user (if you're 
doing it from procmail, why aren't you just piping it to spamassassin, 
similar to what is shown above?)

The alias support and the command to run to rebuild the db both are going 
to be rather dependant upon what MTA you're using.  I see no confirmation 
that you're running sendmail.

What is your prog mailer (Assuming you're using sendmail, in sendmail.cf, 
the "Mprog" line and the few lines after it define it).  That is what 
should be invoking the defined alias.  Have you tried running your MTA in 
address testing mode to confirm that it is resolving the alias?  See your 
MTA docs.

---
  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.

_______________________________________________
procmail mailing list
procmail <at> lists.RWTH-Aachen.DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

Re: procmail error when forwarding to a razor database

"Mike Loiterman" <mike <at> ascendency.net> writes:
>I'm trying to set up a local mail account that I can forward messages
>to so that they will be reported to the Razor database.  All that I
>need to do is run the command 
>"| spamassassin -r"on the messages. 
>
>Someone suggested doing an alias in /etc/mail/aliases that looked
>like this:
>
>spam:    "|/usr/bin/spamassassin -r"

Did you run newaliases after changing the /etc/mail/aliases file?

>I keep getting a procmail error that says "unknown user".  I am doing
>"newaliases" in between each modification.

That isn't a procmail error but rather a sendmail error because it
doesn't see the alias.

Philip Guenther
_______________________________________________
procmail mailing list
procmail <at> lists.RWTH-Aachen.DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail