*This message was transferred with a trial version of CommuniGate(tm) Pro*
Vern, you hit the nail right on the head.
The difference between a direct delivery and one via procmail is the From,
Return-Path: and Delivered-To: addition to the header.
None of your suggestion worked though. Still trying various and researching
docs. At least I now have a place to start.
Heinz
>On Fri, 29 Jan 1999, Heinz Wittenbecher wrote:
>>
>> In my /home/user/.qmail file I have: |/var/imap/qmail_deliver_wrapper
$LOCAL
>>
>> This wrapper calls cyrus deliver and processed error codes.
>>
>> The above works fine.
>
>Good.
>
>> The problem: I want to use procmail to filter mail and have not been able
to
>> figure out how.
>>
>> Have tried .qmail with: | preline /usr/bin/procmail
>> and .procmailrc with: : |/var/imap/qmail_deliver_wrapper $LOCAL
>
>Well, the error comes from cyrus deliver, not procmail. For some reason
>deliver doesn't like the headers. preline puts a From, Return-Path:,
>and Delivered-To: header at the top of the message. These are good
>things, especially when using procmail to filter messages.
>
>I don't have cyrus's IMAP so you'll have to do some testing on your own
>to figure out exactly what deliver doesn't like.
>
>preline has three args (man preline) that turn off these headers. Try
>'preline -d' and 'preline -r' and 'preline -dr' and see if one of those
>works. If it does, you could use formail (man formail) to strip out the
>appropriate header. For instance to get rid of the Return-Path:, put:
>
> |formail -I Return-Path: | /var/imap/qmail_deliver_wrapper $LOCAL
>
>In your .procmailrc. Or, you could add the formail command to the
>qmail_deliver_wrapper. Then you could remove the args from preline so
>that those variables are available for other procmail recipes.
>
>Hope this helps.
>
>Vern
>--
>\ \ / __| _ \ \ | Vern Hart
> \ \ / _| / . | [EMAIL PROTECTED]
> \_/ ___|_|_\_|\_|
>
> 1:53am up 48 day(s), 16:02, 17 users, load average: 0.07, 0.09, 0.18
>
>
