UNIX for Dummies Questions & Answers

Dear elmonty,

In the example below, procmail uses the f, b and w flags. That might help you.

Code:

:0
* ^Content-Type: *text/plain
{
  :0 fbw
  * ^Content-Transfer-Encoding: *quoted-printable
  | mimencode -u -q

  :0 Afhw 
  | formail -I "Content-Transfer-Encoding: 8bit"

  :0 fbw 
  * ^Content-Transfer-Encoding: *base64 | mimencode -u -b

  :0 Afhw 
  | formail -I "Content-Transfer-Encoding: 8bit" 
}

Well, I don't want to use the PHP script as a filter. And I don't want to put a lock or a wait on it, because it could be running for a while. Its purpose is to launch a task that will process all the messages in the queue folder.

I couldn't see anything in the manual that explains this behavior.

Based on my read of how procmail works, you must put a wait on it (and maybe a lockfile) because procmail will not wait for the PHP script to return (does not generate the successful return code), and this seems to perhaps explain what you are observing.

This also seems to explain why your hack is required, based on my read of the examples and documents.
Neo

Two thoughts:

1. It doesn't explain why the delivery stops for plain text mails but not HTML mails. The current version of the PHP script isn't doing any processing of the message at all -- it's just a placeholder. And its logic doesn't treat HTML mails any differently. It just forwards the message to multiple recipients.

2. According to what I've read of how procmail works, it shouldn't matter what the script does or whether it waits. If procmail calls a program and the c or f flags aren't specified, it's supposed to stop delivery.

I agree.

I'm not a procmail expert and have ran out of clues.

Thanks for the dialog. Sorry I could not help more.