Hi, answers within On Tue, Dec 09, 2014 at 02:53:50PM -0600, David Champion wrote: > * On 09 Dec 2014, John Long wrote: > > On Tue, Dec 09, 2014 at 02:54:59AM -0500, Jon LaBadie wrote: > > > On Tue, Dec 09, 2014 at 07:15:13AM +0000, John Long wrote: > > > > > In your RE expression you have two literal periods (m. and > > > .com) plus one meta-period (.*). One of the literal periods > > > is escaped (\.com) the other is not. > > > > > > Both literal periods should be the same (escaped or not escaped) > > > and the meta-period should be the opposite. > > > > Thanks. If I understood what you said and did this right then that did match > > the spammers but is still killing google mail. > > I'm not sure what exactly you need to match - your example in the first > mail looks like a paraphrasing, so not sure what parts are variable.
The messages seem to all have message-ids in the form bunchofch...@m.something.com They also have email ids in the form Idiot Spammer <id...@m.something.com> > However if your spammer's message-ids are actually showing an RFC822 > address format, you might try: > > ~i '\S+\s+<\S+@\S+>' > > I'm assuming your regex library supports \s, \S. PCRE does. Otherwise > you could try > > ~i '[^ ]+ +<[^ ]+@[^ ]+>' You lost me on these two regexps. What's going on here? > Also note the "spam" command, which can be used to classify spam. It's > normally for matching spam scores from spam filters, but you could use > it instead to add these messages as high-scoring spam. This allows you > to treat all spam in aggregate, distinctly from other scoring. > > http://www.mutt.org/doc/devel/manual.html#spam Thanks, I looked over this when I first asked about killfiling but I decided scoring was enough for my purposes. My only problem is not understanding how to match these bastards. All of the other miscreants have already been successfully killfiled. Thanks a lot, /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary / \ http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
