X-Commands in body longer than 72-80 characters?
Are there any scripts or work-arounds for the problem of X-Command lines in the body of an email message being broken into two lines if they're longer than 72-80 characters? I don't know if something's changed in our organization, or if we just happened to not process any longer than this, but I can see in the mail logs that an X-Command that's too long gets broken into two lines, usually before the email address. These X-Commands then fail. I'm not much of a procmail user. Is it possible to tell the rc.local.00 script that if it finds an X-Command in the first line of a body, it should concatenate all the subsequent lines into one, until it comes to the first blank line? Then, the rule for X-Commands in the body of a message would be that the X-Command must be the first line in the body, and must be followed by a blank line. Thank you for your help and suggestions. -Kevin Zembower ----- E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
At 9:47 AM -0400 7/16/02, KEVIN ZEMBOWER is rumored to have typed:
Are there any scripts or work-arounds for the problem of X-Command lines in the body of an email message being broken into two lines if they're longer than 72-80 characters?
ROTFLMAO! (Sorry, couldn't resist.)
I don't know if something's changed in our organization, or if we just happened to not process any longer than this,
...or if client defaults were changed, or more likely people who don't know any better were hired...
but I can see in the mail logs that an X-Command that's too long gets broken into two lines, usually before the email address. These X-Commands then fail.
Ok, now sit down and brace yourself. THe solution requires no additional programming, indeed practically no computer-based work whatsoever on your part. But you're going to feel a little silly when I tell you the solution is to... Tell your people to stop word-wrapping their outbound messages. He, he...this isn't a procmail problem, nor is it a SmartList problem. The X-Command: is being wrapped by the CLIENT (that is, these people have word-wrap set to say 80-characters, and their client adds a hard return to wrap the text for a human reader), so teach your people how to properly turn off word-wrapping. In Eudora, it's simple to do on a per-message basis (there's a little clickable icon on each composition window); in Outhouse Expressed, lord only knows how many hoops they'll need to jump through. But this "Suspicious X-Command Format" problem isn't yours, it's theirs. Charlie (who _refuses_ to consider possible procmail-based solutions to rebuild the X-Command line when the senders are hard-wrapping their messages)
participants (2)
-
Charlie Summers -
KEVIN ZEMBOWER