Jump to content

New Whitelists for SpamCop Email System


Jeff G.

Recommended Posts

As I wrote in http://news.spamcop.net/pipermail/spamcop-...ber/011976.html:

I would like a capability of using new Whitelists in the following ways:

1. "email filtering whitelist", on a checkmark basis (like the IP Based

email filtering blacklists). This would include: IronPort's various Bonded

Sender lists; country-based lists (for example, EU countries for those EU

users interested in suing for EU spam) from services.net,

rbl.cluecentral.net, and blackholes.us; and others as they become available.

I personally would only check the box for IronPort's Bonded Sender Plus.

2. "personal domain whitelist" would be the new name of the current

"personal whitelist", on a new "personal whitelists" page. It would

continue to use the current rules, matching from the right side of the

"From" or "Sender" field, including matching beyond the [at] sign. Attempts to

report spam from domains on this list would be defaulted off by the

reporting system, and challenged with a confirmation dialog in interactive

mode.

3. "personal ip whitelist" would keep us from reporting our own mailservers

from Held Mail, which has been happening to more and more people recently.

It would also be on a new "personal whitelists" page. Attempts to report IP

Addresses on this list would be defaulted off by the reporting system, and

challenged with a confirmation dialog in interactive mode.

4. "personal localpart whitelist" would keep us from reporting messages from

various RFC2142-compliant addresses, like Postmaster and Abuse, plus

MAILER-DAEMON and <>, on a proactive basis. It would also be on a new

"personal whitelists" page. It would match from the left side of the "From"

or "Sender" field, including matching beyond the [at] sign. Attempts to report

spam from localparts on this list would be defaulted off by the reporting

system, and challenged with a confirmation dialog in interactive mode.

Of course, these would need to be countered by "personal blacklists",

including "personal domain blacklist", "personal ip blacklist", and

"personal localpart blacklist".

Also, precedence rules would be that a more specific (longer) listing has

more weight than a less specific (shorter) listing, and in case of a tie,

white has more weight than black.

What do you guys think?

Thanks!

Link to comment
Share on other sites

As I wrote in http://news.spamcop.net/pipermail/spamcop-...ber/011976.html:

I would like a capability of using new Whitelists in the following ways:

What do you guys think?

Thanks!

21603[/snapback]

JT is being a bit slow in using Bonded senders Whitelist? I believe there are other whitelists now as well

To me it is the way things will go in that mail will only be accepted from those servers registered on a Whitelist (which will have conditions applied to keep that server whitelisted)

I suspect if you get to many features like whitelisting our own IP it could slow down SpamCops mail server? If SpamCops mail hosts are not picking up your mailhost it suggests to me your provider is slack and needs to fix

Link to comment
Share on other sites

In addition to the above:

1

I've had problems from time to time with mailing lists (in addition to my goofy SBC/yahoo problem in posts elsewhere) that make the Reply-to: header the original sender's address as opposed to the list, or simply don't have a Reply-to header. I'd like to see more flexibility in what headers can be examined for white listing. At the least, (option to) compare the personal whitelist with From: and To: headers. At best, be able to whitelist on the contents of any header.

2

Seems silly to put in the work to duplicate the contents of the web mail address book in the personal whitelist, and maintain two lists. Would like to have the addresses in the book automatically treated as personal whitelist. The existing personal whitelist could still be used for partial right-side addresses & stuff that doesn't need to go in the address book.

The above are wish-list desires cheerfully thought up without any regard to the practicality of implementing. :)

Thanks,

Larry

Link to comment
Share on other sites

3. "personal ip whitelist" would keep us from reporting our own mailservers

from Held Mail,

21603[/snapback]

this should also have the effect of a anti-blacklist :)

(a message should not be held because of a blacklisted ip from my personal whitelist)

some mailservers of my ISP are blacklisted from time to time. Only for a few hours and only by error as my ISP claims... but if they are on the SCBL all my mail is held with all the other spam.

(messages with other listed IPs could still be held.)

Lukas

Link to comment
Share on other sites

  • 1 month later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...