Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On 20/10/15 21:10, Axb wrote: On 10/20/2015 10:04 PM, RW wrote: On Tue, 20 Oct 2015 13:29:45 -0500 (CDT) sha...@shanew.net wrote: I already have rules that score for these tlds in received or envelope from, but I'm getting tired of making the regular expression longer and longer (in two

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On Tue, 20 Oct 2015, Rob McEwen wrote: On 10/20/2015 12:13 PM, sha...@shanew.net wrote: Unlike Larry (and others) I DO want to block the vast majority of the new tlds, because we see nothing but spam from them (and my users tend toward the more false-positives than false-negatives side of

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On 10/20/2015 12:13 PM, sha...@shanew.net wrote: Unlike Larry (and others) I DO want to block the vast majority of the new tlds, because we see nothing but spam from them (and my users tend toward the more false-positives than false-negatives side of the spectrum). Rather than maintain a list

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

If you have 3.4.1 and use sa-update then we add new tlds to a rule file that is then parsed. This does not block those tlds. It let's the engine recognize the urls for further rules. If you have a tld that is missed and you are using 3.4.1 with sa-update, let us know. Regards, KAM On

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

I've got 3.4.1 installed and sa-update runs regularly. Unlike Larry (and others) I DO want to block the vast majority of the new tlds, because we see nothing but spam from them (and my users tend toward the more false-positives than false-negatives side of the spectrum). Rather than maintain a

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On 10/20/2015 10:04 PM, RW wrote: On Tue, 20 Oct 2015 13:29:45 -0500 (CDT) sha...@shanew.net wrote: I already have rules that score for these tlds in received or envelope from, but I'm getting tired of making the regular expression longer and longer (in two different places), and I know

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On Tue, 20 Oct 2015 13:29:45 -0500 (CDT) sha...@shanew.net wrote: > I already have rules that score for these tlds in received or envelope > from, but I'm getting tired of making the regular expression longer > and longer (in two different places), and I know there's a smarter > way. Whether

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On Mon, 19 Oct 2015, Larry Goldman wrote: I found that much of the SPAM had a BAYES_00 score of -1.9, which was defeating the contribution of the other tests. A closer inspection of the raw source revealed invisible gibberish text which, I assume, is designed to thwart the default BAYES_00

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

So, to reply to my own question: CPanel is well documented and is supported only via forum .

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On 19 Oct 2015, at 15:22, Larry Goldman wrote: I found that much of the SPAM had a BAYES_00 score of -1.9, which was defeating the contribution of the other tests. A closer inspection of the raw source revealed invisible gibberish text which, I assume, is designed to thwart the default

Re: Simplicity (was Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains)

On 13 Oct 2015, at 15:46, Dianne Skoll wrote: CPanel is just a "hosting control panel" used by a bazillion hosting providers. It's a more sophisticated version of Webmin and the like; Or *less* depending on your concept of 'sophisticated'... It is slicker, but it is much more tightly bound

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On 13 Oct 2015, at 15:08, Larry Goldman wrote: My experience to date is that GoDaddy doesn’t really support the internals of CPanel, and CPanel doesn’t provide end-user customer support either. Cheap is indeed cheap. Skilled individualized MTA & anti-spam support is NOT cheap. I figured I

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On 13 Oct 2015, at 16:04, Larry Goldman wrote: Point me to the documentation of the SpamAssassin framework. You mentioned being a Mac user so in addition to the website Dianne pointed you to or manually installing from the SA source tarball, you can get a working installation with all of

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On 10/14/2015 12:00 PM, Bill Cole wrote: Describe, in detail, the new SA technology which fights abuse of new TLDs. Prior to v3.4.1, the mechanism for detecting and parsing hostnames to identify body URIs used an embedded array of hardcoded domains in

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On Wed, 2015-10-14 at 10:36 -0400, Bill Cole wrote: > Self-hosting email is feasible if you have a proper business-fit > Internet connection: static IP, rDNS in your own domain, no filtering > or DNS hijacking. MacOS X Server isn't a horrible (any more... ) mail > server and if you're willing to

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On Tue, 13 Oct 2015, Kevin A. McGrail wrote: At the end of the day, if you are having problems with new TLDs, ONE solution is to use something that uses SA 3.4.1 and has sa-update configured so you get updates with said new TLDs. I think maybe people are confused about how exactly this

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On 12/10/15 19:15, Larry Goldman wrote: On Oct 2, 2015 6:47:41 am RW wrote: On Thu, 1 Oct 2015 18:53:16 -0700 Larry Goldman wrote: I?m running SpamAssassin on CPanel shared hosting (GoDaddy). For several weeks, I?ve been inundated with spam from various new top-level domains: .date, .win,,

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On 10/12/2015 2:15 PM, Larry Goldman wrote: I’m using the CPanel shared hosting on GoDaddy. Inside there, SpamAssassin is running. GoDaddy might not be running sa-update or a new enough version of SA to take advantage of the TLD updates we can push centrally.

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

The _idea_ of CPanel is a good one: a low-cost, do-it-all solution which a broader range of tech-savvy users can manage. It seems that the current GoDaddy/CPanel configuration I’m using is obviously not up to the task of distinguishing SPAM in today’s world. If there is not an easy fix within

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

no! the idea of cpanel, webmin and what not is trying to provide a reduced and limited interface for users with no clue and give them the felling they have some clue what they are doing if you rely on capnel you better maintain no public server at all, take money and pay somebody who knows

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

So, it is not possible to simplify the process of managing an email server via an easy-to-use software user interface? > On Oct 13, 2015, at 12:19 PM, Reindl Harald wrote: > > no! > > the idea of cpanel, webmin and what not is trying to provide a reduced and > limited

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

Am 13.10.2015 um 21:24 schrieb Larry Goldman: So, it is not possible to simplify the process of managing an email server via an easy-to-use software user interface? not really someone needs to understand the setup *and* maintain it because spam is a moving target - there is no easy

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

I couldn’t pay a full-time guy for what I’m paying to use CPanel. I was hoping/expecting that the $ all of us shared users of CPanel are paying for the product would eventually be paying a full-time guy/gurl to support the product. > On Oct 13, 2015, at 12:19 PM, Reindl Harald

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

Am 13.10.2015 um 21:34 schrieb Larry Goldman: I couldn’t pay a full-time guy for what I’m paying to use CPanel. I was hoping/expecting that the $ all of us shared users of CPanel are paying for the product would eventually be paying a full-time guy/gurl to support the product. that is what

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

Am 13.10.2015 um 21:48 schrieb Larry Goldman: It seems that a basic function of an email service provider, these days, is to keep up with spam. There is nothing unusual about my email. SpamAssassin is a framework: a framework with seemingly no documentation at all no documentationat all?

Simplicity (was Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains)

On Tue, 13 Oct 2015 12:24:53 -0700 Larry Goldman wrote: > So, it is not possible to simplify the process of managing an email > server via an easy-to-use software user interface? I think if your goal is to simplify the process of managing an email server,

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On Tue, 13 Oct 2015 13:04:36 -0700 Larry Goldman wrote: > Point me to the documentation of the SpamAssassin framework. Where > are rules documented? What are the current rules? Describe, in > detail, the new SA technology which fights abuse of new TLDs. man

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On Tue, 13 Oct 2015 16:11:49 -0400 Dianne Skoll wrote: > Or if you want an online resource, > https://spamassassin.apache.org/full/3.1.x/doc/Mail_SpamAssassin_Conf.html D'oh, that's a link to an old version... sorry.

Re: Simplicity (was Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains)

On Tue, 13 Oct 2015 12:42:04 -0700 Larry Goldman wrote: > As a customer of CPanel, I was expecting the "competent someone else > who is supposed to simplify the process of managing an email server > for me" already to be working for CPanel. CPanel is just a

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

Am 13.10.2015 um 21:02 schrieb Larry Goldman: I’ve seen CPanel hosted on several other ISPs. It would be quite unfortunate (for them and for their users) if their email product could not reliably catch spam. and i have seen so much shit from ISP's long ago that i started in 2005 to host

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

My experience to date is that GoDaddy doesn’t really support the internals of CPanel, and CPanel doesn’t provide end-user customer support either. I figured I would try to solve the problem myself (with this mailing list’s help), or consider hosting my own (OS X) email server so I have full

Re: Simplicity (was Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains)

I’m ready to get down and dirty if necessary. As a customer of CPanel, I was expecting the “competent someone else who is supposed to simplify the process of managing an email server for me" already to be working for CPanel. > On Oct 13, 2015, at 12:32 PM, Dianne Skoll

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

It seems that a basic function of an email service provider, these days, is to keep up with spam. There is nothing unusual about my email. SpamAssassin is a framework: a framework with seemingly no documentation at all. I was considering downloading the source files to see if the framework is

CPanel (was Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains)

On Tue, 13 Oct 2015 12:48:58 -0700 Larry Goldman wrote: > SpamAssassin is a framework: a framework with seemingly no > documentation at all. I was considering downloading the source files > to see if the framework is documented there. Is that what it takes

Re: Simplicity (was Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains)

On 10/13/2015 3:42 PM, Larry Goldman wrote: I’m ready to get down and dirty if necessary. As a customer of CPanel, I was expecting the “competent someone else who is supposed to simplify the process of managing an email server for me" already to be working for CPanel. Agreed. I think the

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

Point me to the documentation of the SpamAssassin framework. Where are rules documented? What are the current rules? Describe, in detail, the new SA technology which fights abuse of new TLDs. Thank you for your advice. I don’t really plan on devoting my life to administering my generic email

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

Way the best answer, Dianne! Thanks! > On Oct 13, 2015, at 1:11 PM, Dianne Skoll wrote: > > On Tue, 13 Oct 2015 13:04:36 -0700 > Larry Goldman wrote: > >> Point me to the documentation of the SpamAssassin framework. Where >> are

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

It seems that the new domains are appearing faster than I can keep up. Continual manual updates by every SA admin seems unfeasible. How does SA solve this problem? > On Oct 13, 2015, at 2:33 AM, Paul Stead wrote: > > On 12/10/15 19:15, Larry Goldman wrote: >> On

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

> On Oct 13, 2015, at 6:49 AM, Kevin A. McGrail wrote: > > On 10/12/2015 2:15 PM, Larry Goldman wrote: >> I’m using the CPanel shared hosting on GoDaddy. Inside there, SpamAssassin >> is running. > GoDaddy might not be running sa-update or a new enough version of SA to take

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On 10/13/2015 2:55 PM, Larry Goldman wrote: It seems that the new domains are appearing faster than I can keep up. Continual manual updates by every SA admin seems unfeasible. How does SA solve this problem? By adding the TLDs to the config files distributed by sa-update that work with SA

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

Am 13.10.2015 um 20:40 schrieb Larry Goldman: It seems that CPanel is an independent product that GoDaddy serves. It may be that the version of CPanel in use is not using up-to-date SA, which is a problem. How can I determine which version of SA is being used, without terminal access? you

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On 10/13/2015 2:40 PM, Larry Goldman wrote: On Oct 13, 2015, at 6:49 AM, Kevin A. McGrail > wrote: On 10/12/2015 2:15 PM, Larry Goldman wrote: I’m using the CPanel shared hosting on GoDaddy. Inside there, SpamAssassin is running. GoDaddy might

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

I’ve seen CPanel hosted on several other ISPs. It would be quite unfortunate (for them and for their users) if their email product could not reliably catch spam. > On Oct 13, 2015, at 11:56 AM, Reindl Harald wrote: > > > > Am 13.10.2015 um 20:40 schrieb Larry

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On 10/13/2015 4:14 PM, Larry Goldman wrote: Way the best answer, Dianne! Thanks! To add a 3rd answer, I want you to know that you ARE correct. Godaddy provides you a service which is not functioning as you would like. Who they choose, what their vendors choose, etc. is not really your job as

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On Oct 2, 2015 6:47:41 am RW wrote: >> On Thu, 1 Oct 2015 18:53:16 -0700 >> Larry Goldman wrote: >> >> From http://spamassassin.apache.org : >> >> Latest News >> >> 2015-04-30: SpamAssassin 3.4.1 has been released! Highlights >> include: >> >> improved

Re: SpamAssassin Rules Regarding Abuse of New Top Level Domains

On Thu, 1 Oct 2015 18:53:16 -0700 Larry Goldman wrote: > From http://spamassassin.apache.org: > > > Latest News > > > > 2015-04-30: SpamAssassin 3.4.1 has been released! Highlights > > include: > > > > improved automation to help combat spammers that are abusing new > > top level domains; >

SpamAssassin Rules Regarding Abuse of New Top Level Domains

From http://spamassassin.apache.org: > Latest News > > 2015-04-30: SpamAssassin 3.4.1 has been released! Highlights include: > > improved automation to help combat spammers that are abusing new top level > domains; > I’m running SpamAssassin on CPanel shared hosting (GoDaddy). For several