Tim wrote, | It's supposed to be legal to break headers into multiple lines | by adding whitespace at the front of each "continuation line." | According to the mail specs, these headers should be considered | equivalent: | | X-Command: twp@rootsweb.com password subscribe joe@example.com | | and | | X-Command: twp@rootsweb.com password | subscribe joe@example.com And there you have it. Tim indented the word "subscribe" when he sent his post but somewhere between his keyboard and my screen, the indentation was eaten by something beyond his control or mine. (Yes, I do regularly receive mail with indentations in the text.) The same thing is happening to Kevin's list maintainers. My only suggestion is to tell them to leave a blank line below the top-of-the-body X-Command:'s arguments and any other text. Then, a recipe like this ... :0Bbfw # note trailing period in condition * $ ^^X-Command:(.*\<)?$password(\>.*)^. | sed '2,/^$/s/./ &/' will indent the wrapped lines into proper continuation lines. It does require the password to get onto the top line before the first break. Hmm... it is possible to get rid of the blank line at the neck (and thus move the X-Command: into the head) in the same sed invocation, but I'm too headachy to write the sed code for that right now.