On Monday 23 February 2009, Theo Van Dinter wrote: >Oh, and having a sample mail via pastebin/etc would be handy if you >want more commentary about the mail. :)
<http://pastebin.ca/1345467> Thanks. The question is how to craft a procmail rule that will trigger on the 'unlisted' bit. >> On Mon, Feb 23, 2009 at 5:55 PM, Gene Heskett <gene.hesk...@verizon.net> wrote: >>> I've had zip luck getting a trigger line based on Undisclosed >>> Recipients:, or Unlisted Recipients: here, so I called up my .procmailrc >>> and tried to enter the check phrase by doing a copy/paste from the kmail >>> displayed line when in show all headers mode. But, when pasting that >>> into vim, there is an invisible linefeed occupying the underscores place >>> in the header line, and it doesn't show up in the show all headers >>> display. >>> >>> The input line looks like this: >>> >>> To: unlisted-recipients:; (no To-header on input)@gmail-pop.l.google.com >>> >>> But copy/pastes as: >>> To: _ >>> unlisted-recipients:; (no To-header on input)@gmail-pop.l.google.com >>> >>> Where the underscore is the hidden line feed. I save the message, and >>> inspected it with khexedit, but the saved version does not have an 0x0a >>> there. >>> >>> Anybody got an idea how the spammers have managed that? >>> >>> And better yet, how to defend against it as I'd like to /dev/null any >>> message with an unlisted header. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Q: What do you call the money you pay to the government when you ride into the country on the back of an elephant? A: A howdah duty.
