I wanted to follow up on this thread with a word of thanks to both the
Spamassassin developer and user communities for the input, and for their
years of hard work into SA.
I'm hopefully not being obsequious here, what many of you may not know is
that I wrote and helped publish the first spam
On Tue, Mar 3, 2009 at 01:20, J.D. Falk jdfalk-li...@cybernothing.org wrote:
Jason Bertoch wrote:
That being said, maybe the rule description should include the reporting
addresses. Why would I look on the SA wiki for a place to report
ReturnPath, Habeas, and BondedSender complaints?
At 17:20 02-03-2009, J.D. Falk wrote:
(BTW, a quick visit to your favorite search engine should alleviate
any fears that either Neil or I are marketers.)
I can confirm that J.D. is not in marketing.
He did not top-post or send his message in HTML format. :-)
Regards,
-sm
-Original Message-
From: Neil Schwartzman [mailto:neil.schwartz...@returnpath.net]
Sent: Monday, March 02, 2009 12:22 AM
To: Spamassassin
Subject: Re: ReturnPath, Habeas, BondedSender
Good first step, now how about an RFC complaint abuse@ address?
So you can complain about
That being said, maybe the rule description should include the reporting
addresses. Why would I look on the SA wiki for a place to report
ReturnPath, Habeas, and BondedSender complaints?
actually, the wiki is the right place -- the idea for rule documentation is that
the detailed doc for each
Jason Bertoch wrote:
That being said, maybe the rule description should include the reporting
addresses. Why would I look on the SA wiki for a place to report
ReturnPath, Habeas, and BondedSender complaints?
What's the process for updating rule descriptions?
(BTW, a quick visit to your
We have created an entry on the Spamassassin wiki
http://wiki.apache.org/spamassassin/ReportingSpam
Thanks.. Last time I tried via your web site, I had a salesperson call me
trying to convince me I should pay return path to 'bless' my marketing
emails.
Good first step, how, about an RFC
We have created an entry on the Spamassassin wiki
http://wiki.apache.org/spamassassin/ReportingSpam
Sorry, but these people have no clue: RFC's? What the heck.
Received: from 38.109.196.48 ([38.109.196.48]) by rpnyex01.rpcorp.local
([192.168.1.16]) with Microsoft Exchange Server HTTP-DAV ;
On Sun, 2009-03-01 at 20:55 -0500, Michael Scheidell wrote:
We have created an entry on the Spamassassin wiki
http://wiki.apache.org/spamassassin/ReportingSpam
Thanks.. Last time I tried via your web site, I had a salesperson call me
trying to convince me I should pay return path to
On 01/03/09 7:58 PM, Michael Scheidell scheid...@secnap.net wrote:
And why is this original email supposed to be a high priority? Must be a
marketing person posting it.
Hah. Marketing. Yeah right. That's what it says in my sig. Oh, no wait ...
I believe the reason the email was highest
On 01/03/09 7:55 PM, Michael Scheidell scheid...@secnap.net wrote:
Good first step, how, about an RFC complaint abuse@ address?
So you can complain about any errant returnpath.net emails? That has always
been in place. It would be inappropriate to complain about certified client
emails to our
On 01/03/09 7:55 PM, Michael Scheidell scheid...@secnap.net wrote:
Last time I tried via your web site, I had a salesperson call me
trying to convince me I should pay return path to 'bless' my marketing
emails.
BTW: I trust your pointed out the error of his ways. If this ever happens
We have created an entry on the Spamassassin wiki
http://wiki.apache.org/spamassassin/ReportingSpam
--
Neil Schwartzman
Director, Accreditation Standards Security
Sender Score Certified | Sender Score Safelist
Return Path Inc.
0142002038
On Sat, 28 Feb 2009, Neil Schwartzman wrote:
We have created an entry on the Spamassassin wiki
http://wiki.apache.org/spamassassin/ReportingSpam
Broken link in section Setup of special aliases in Postfix to forward spams
and hams: http://gtmp.org/publications/sa-postfix-en.
--
Sahil Tandon
14 matches
Mail list logo
