Module submissions, reviews, etc.

2014-06-13 Thread Philip A. Prindeville
What's the best place to get a module reviewed for inclusion into a future version of SA, or to discuss possible core changes to SA? Thanks, -Philip

Re: Magical mystery colon

2010-02-01 Thread Philip A. Prindeville
On 02/01/2010 05:35 AM, Mark Martinec wrote: > On Saturday January 30 2010 21:16:01 Philip A. Prindeville wrote: > >> Also, how come the eval block: >> unless (eval "require $thing") {...} >> doesn't contain a terminating ';', i.e.: >&

Re: Magical mystery colon

2010-01-31 Thread Philip A. Prindeville
On 01/30/2010 12:24 PM, Karsten Bräckelmann wrote: > On Sat, 2010-01-30 at 12:16 -0800, Philip A. Prindeville wrote: > >> I ran "yum update" on my FC11 machine a couple of days ago, and now I'm >> getting nightly cron errors: >> > Would be nice an

Magical mystery colon

2010-01-30 Thread Philip A. Prindeville
I ran "yum update" on my FC11 machine a couple of days ago, and now I'm getting nightly cron errors: plugin: failed to parse plugin (from @INC): syntax error at (eval 84) line 1, near "require Mail::SpamAssassin:" plugin: failed to parse plugin (from @INC): syntax error at (eval 148) line 1, ne

Holding yahoo!'s feet to the fire

2009-12-07 Thread Philip A. Prindeville
Some good news... possibly. I finally complained to ARIN (for the 4th time) that the contact information for the Inktomi address blocks was incorrect, as Inktomi hasn't existed as a corporate (and legal) entity for some time... it was acquired by Yahoo! 3 years ago, and their address blocks hav

Re: Undisclosed recipients :; -- again

2009-12-02 Thread Philip A. Prindeville
On 11/30/2009 03:15 AM, Matus UHLAR - fantomas wrote: > On 27.11.09 14:04, Philip A. Prindeville wrote: > >> for the ruleset: >> > >> header __L_UNDISCLOSED1 To:raw =~ /undisclosed-recipients: ;/ >> > just FYI, sendmail can be configure

Re: Undisclosed recipients :; -- again

2009-11-27 Thread Philip A. Prindeville
John Hardin wrote: On Fri, 27 Nov 2009, Philip A. Prindeville wrote: header __L_UNDISCLOSED1 To:raw =~ /undisclosed-recipients: ;/ Just how do I go about figuring out what the "To:raw" value is (for example)? header __TO_RAW To:raw =~ /.+/ If you're analyzing

Re: Undisclosed recipients :; -- again

2009-11-27 Thread Philip A. Prindeville
John Hardin wrote: On Mon, 23 Nov 2009, LuKreme wrote: On Nov 23, 2009, at 12:05, Philip Prindeville wrote: I want to block all messages that I'm getting that have: To: undisclosed recipients: ; undisclosed recipients is used for Bcc: mail I used it all the time. And you WILL 'block' le

More of a philosophical question

2009-11-11 Thread Philip A. Prindeville
This isn't so much of a technical question as a policy one. I get a lot of spam which looks like: Return-Path: Received: from web.biz.mail.sk1.yahoo.com (web.biz.mail.sk1.yahoo.com [74.6.114.43]) by mail.redfish-solutions.com (8.14.3/8.14.3) with SMTP id nA8KXHbF007914 for ; Sun