Re: man pages missing something

Hello 

Can u please tell me as how can split an attachment from the mail.
If yes pls mail me back as soon as possible. already i wrote  a 
perl program that is parsing the mail but if any mail comes with an
attachment is is in the MIME format and it comes with the mail body
so kindly help me  to solve this problem. I know this is really a 
silly matter that u all can solve it within a couple of  hours

Thanks

rabiya

Thu, 31 Oct 2002, Tom Allison wrote:

> Ruud H.G. van Tol wrote:
> > Hatto von Hatzfeld skribis:
> > 
> > 
> >>by "* ^From +\/[^ ]+ " (the
> >>space after the last + is important) one can easily extract the From_
> >>address and put it into MATCH.
> > 
> > 
> > 1. Why would you want the MATCH to end in a space? 
> >    (AFAIK, \/ is greedy-to-the-right)
> > 
> > 2. Using ^^From in stead of ^From is more accurate here.
> > 
> > 3. E-mail-addresses are allowed to have embedded whitespace.

Re: Howto split message attachment parts (was: man pages...)

On Fri, 1 Nov 2002, rabi wrote:

> Hello
>
> Can u please tell me as how can split an attachment from the mail.
> If yes pls mail me back as soon as possible. already i wrote  a
> perl program that is parsing the mail but if any mail comes with an
> attachment is is in the MIME format and it comes with the mail body
> so kindly help me  to solve this problem. I know this is really a
> silly matter that u all can solve it within a couple of  hours

	Try to use metamail(1):
o#!/bin/sh
METAMAIL_TMPDIR=$dir
export METAMAIL_TMPDIR
sed -e '/^Content.*multipart\/alternative/s/\/alternative/\/mixed/' |
metamail -r -y -w -q -x

	Now, you will find the parts of the message in $dir
	If you set the METAMAIL_TMPDIR in yours filerc you do not
	need the two first lines.  (You can do all the job from
	procmailrc too)

>
> Thanks
>
> rabiya
>
> [???]

pipe recipe problem

Hi,

When attempting to use a pipe in procmail with arguments, the arguments
seem to be interpreted as the destination directory.  What am I doing
wrong?

Example:

:0fw
|/usr/bin/spamassassin -P -p /var/www/html/webmail/data/ryans.spam

:0 H
* ^X-Spam-Status: Yes
$HOME/Maildir/.Spam/

Logfile:

procmail: Couldn't create or rename temp file
"/home/ryans/Maildir/tmp/1036163354.30640_
2./www/html/webmail/data/ryans.spammail"

Here are a few variables from my global config:
SHELL=/bin/bash
MAILDIR=$HOME/Maildir
DEFAULT=$HOME/Maildir/

Thanks,

Ryan

trouble with 8+char usernames with postfix

i am trying to run procmail being called by postfix. I added

mailbox_command = /usr/local/bin/procmail.orig -m 
/etc/procmail/procmailrc.internal

to my main.cf file and then restarted postfix.

works great for users with 7 char usernames or less, for 8 char or more the 
messages bounce with the following error message:

Oct 30 12:59:53 ncees postfix/smtpd[28572]: 232BB506: 
client=wolverine.emji.net[66.45.96.6]
Oct 30 12:59:53 ncees postfix/cleanup[28573]: 232BB506: 
message-id=<2147483647.1035982005 <at> [10.1.14.19]>
Oct 30 12:59:53 ncees postfix/smtpd[28572]: disconnect from 
wolverine.emji.net[66.45.96.6]
Oct 30 12:59:53 ncees postfix/qmgr[28566]: 232BB506: 
from=<stevem <at> emji.net>, size=803, nrcpt=1 (queue active)
Oct 30 12:59:53 ncees spamd[7751]: connection from localhost [127.0.0.1] at 
port 51101
Oct 30 12:59:53 ncees spamd[28586]: info: setuid to stevem11 succeeded
Oct 30 12:59:53 ncees spamd[28586]: processing message 
<2147483647.1035982005 <at> [1
0.1.14.19]> for stevem11:4577, expecting 892 bytes.
Oct 30 12:59:53 ncees spop3d[28588]: connect from 209.36.118.190
Oct 30 12:59:54 ncees spamd[28586]: clean message (0.8/5.0) for 
stevem11:4577 in 1.2 seconds, 892 bytes.
Oct 30 12:59:54 ncees postfix/local[28578]: 232BB506: 
to=stevem11 <at> ncees.org>, relay=local, delay=1, status=bounced (can't create 

extracting/working with body

Re: extracting/working with body

On Fri, 1 Nov 2002 the voices made ricardo <at> americasnet.com write:

> Hi everyone,
>
> Is there a way for procmail extract the body of a message and do
> something with it?
>
> I was trying to figure out a way in which I could get a signature of a
> message body (say run an MD5 on the body) and then check that against a
> database.
>
> Any ideas on how that could be done?

 Just read the manuals, nothing complicated about it; actually, the part that
could be complicated (depending on what tools you're using) is the database-
part, but that's both off-topic and you didn't give enough information (like
what database you're using) for anyone to be able to help with that part.

	/Tony
--

-- 
# Per scientiam ad libertatem! // Through knowledge towards freedom! #
# Genom kunskap mot frihet! =*= (c) 1999-2002 tony <at> svanstrom.com =*= #

     perl -e'print$_{$_} for sort%_=`lynx -dump svanstrom.com/t`'

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

Re: extracting/working with body

At 09:26 2002-11-01 -0700, ricardo <at> americasnet.com wrote:
>Is there a way for procmail extract the body of a message and do something 
>with it?

:0b
| some_prog_that_does_something_with_the_body

See 'man procmailrc' for an explanation.

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

Making procmail my LDA

Hello,

I have a question that seems difficult for me yet will probably seem like
child's play to you experts out there. I would like to know how I can find
out whether or not procmail is my LDA. I suspect it's not because I have no
etc/procmailrc file.

I've tried running procmail over a .forward file in my home folder but I do
not wish to do that anymore because I get bypassed locking errors in my
logfile. Since my user is initializing procmail, procmail is running under
the users UID and can't gain the permissions to lock the mail spool file.

But I know that if I run procmail as my LDA, this probably won't be a
problem. So I'd like to know how I can find out if procmail is my LDA. If
it's not how can I set it up as my LDA?

Currently I'm running procmail version 3.14 and my locking strategies are
dotlocking and fcnt1().

Thank you for your consideration

Joe Leske

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.381 / Virus Database: 214 - Release Date: 8/3/2002

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

Re: extracting/working with body

Re: Making procmail my LDA

On  2 Nov, Joe Leske wrote:
| Hello,
| 
| I have a question that seems difficult for me yet will probably seem like
| child's play to you experts out there. I would like to know how I can find
| out whether or not procmail is my LDA. I suspect it's not because I have no
| etc/procmailrc file.
| 
| I've tried running procmail over a .forward file in my home folder but I do
| not wish to do that anymore because I get bypassed locking errors in my
| logfile. Since my user is initializing procmail, procmail is running under
| the users UID and can't gain the permissions to lock the mail spool file.
| 
| But I know that if I run procmail as my LDA, this probably won't be a
| problem. So I'd like to know how I can find out if procmail is my LDA. If
| it's not how can I set it up as my LDA?
| 
| Currently I'm running procmail version 3.14 and my locking strategies are
| dotlocking and fcnt1().
| 
| Thank you for your consideration
| 

Lack of /etc/procmailrc does not reliably tell you it is not LDA. 
For example, procmail is configured as LDA out of the box w/ SuSE Linux
but no /etc/procmailrc is created IIRC.  I'm sure that's true of other
systems too.  After all, what goes in to /etc/procmailrc is up to the
owner.

Retrieve, *Read*, then run:

http://www.professional.org/procmail/procdiag.sh

It'll provide that information and much more.  For example (again), it
will alert you to ownership/permissions issues that might be the real
cause of your problems.

--

-- 
Reply to list please, or append "8" to "procmail" in address if you must.
Spammers' unrelenting address harvesting forces me to this...reluctantly.

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