Kevin Bilbree said:

"It would also be advantagous for large providers to place there outbound
mail sources in a WOT file or files based on how the server are used. They
could have a WOT file for subscribers outboud delivery or confirmation
notices."

That would certainly be great.  I think everyone would want AT&T, ComCast
and RoadRunner to tell us what there outbound mail servers are.  WOT would
be an easily maintained way to do this.

In a weighting system, this would also let us "put up with a mail server"
that you are used to getting good mail from when some 3rd party lists it,
and not throw away all the outbound mail from that server, i.e. let the
content filters make up the difference in deciding that a message is spam,
rather than deciding on the current spamminess of the whole server.

For another good reason, how many times has someone posted to this list and
asked for help to decide what mailers and ISPs need negative weighting to
allow them?  I know I did it.

WOT has some promise here because of the depth parameter: as an ISP, Chuck
might have more liberal filters, so one might score his server with a depth
of 2, or one could decide that only a few private companies have sufficient
standards, and they are your only entries with a score of 1 depth.

Adding to your own WOT the ISPs and private companies with which you've had
problems helps to disseminate a favourable opinion of companies that
otherwise rate poorly, even if the only problem with them is salty language
by their users, or they are at an unfortunate ISP, or have an ill-favoured
mail server, an ill-favoured domain or tld, or poor smtp administration.

Andrew 8)

-----Original Message-----
From: Kevin Bilbee [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, December 10, 2003 4:23 PM
To: [EMAIL PROTECTED]
Subject: RE: [Declude.JunkMail] Web-o-Trust


After reading the WOT site and the posts here. I think the best use for this
is a dynamic trusted whitelist. For example I have my mail server and my
gateway mail servers. My web servers that send out notices and our
orderentry server that sends out emails. I would list all of these IPs in my
WOT file. Now that I have done that. If another mail admin trusts my WOT
file and if I add or remove a server I just update my WOT file and they
automatically trust the new server. If I change providers and my IP block. I
just update my WOT file. If the new block is in blacklists because it was
previously held by a spammer. My mail would then have less of a chance of
being deleted or held as spam. Also if the class C gets blacklisted due to
another subnet in the the class C spamming. My mail would have a better
chance of not being blocked.

It would also be advantagous for large providers to place there outbound
mail sources in a WOT file or files based on how the server are used. They
could have a WOT file for subscribers outboud delivery or confirmation
notices.


Kevin Bilbee



> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of R. Scott Perry
> Sent: Wednesday, December 10, 2003 3:55 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [Declude.JunkMail] Web-o-Trust
>
>
>
> >What if a spammer get into the loop? and corrupts the shared
> whitelist? is
> >this possible?
>
> It can happen, but a spammer would have to do a lot of work for little
> payout.  They would have to get someone to trust them to get "in
> the loop",
> while not knowing how many people will trust them -- and not knowing how
> quickly they may be omitted.  One of the keys here is limiting how much
> recursion can be done.  For example, if you trust our WOT file, and those
> of our customers, but none further -- then the only way a spammer can get
> their IP whitelisted on your server is if *we* trust them.  If you think
> that the WOT system isn't going to attract spammers, you might
> not want to
> place any limits, so that if one of our customers trusts one of their
> customers that trusts a friend of theirs who trusts a spammer, you can
> always omit them.
>
> Then, with Declude JunkMail, you can use negative weighting, which would
> make it even more difficult for a spammer to get their E-mail
> through with WOT.
>
> >So Let me summarize the way I think this works.
> >
> >1) I setup a WOT file for my domain/server
> >2) I whitelist entries the WOT file
> >3) I link the WOT file to other trusted WOT files
> >4) The linked WOTs have whitelisted items and linked WOT files
>
> I think that is right.  :)
>
> The WOT file on your website is essentially a list of your IPs and people
> you trust.  Presumably, that's where you would start when creating a
> list.  The list would contain your IPs, and would include the people you
> trust as well (and the people they trust, and so on), within the limits
> that are given.
>
> Because of the "web" nature of this, there is no one specific starting
> point, except for your own WOT file.  We're linked to most of the people
> who use Web-o-Trust, so by including us, you include them as
> well.  However, at this point, nobody knows about *your* WOT
> file.  So you
> let us know the URL for your WOT file, and we add you to ours.
> Since we're
> linked to most of the people who use Web-o-Trust, when we add you, most
> people will be whitelisting you as well (not everybody, though, because
> some may omit us or you, or may have recursion limits that
> prevent you from
> being seen).
>
>
>                                                     -Scott
> ---
> Declude JunkMail: The advanced anti-spam solution for IMail mailservers.
> Declude Virus: Catches known viruses and is the leader in mailserver
> vulnerability detection.
> Find out what you've been missing: Ask about our free 30-day evaluation.
>
> ---
> [This E-mail was scanned for viruses by Declude Virus
(http://www.declude.com)]

---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail".  The archives can be found
at http://www.mail-archive.com.

---
[This E-mail was scanned for viruses by Declude Virus
(http://www.declude.com)]

---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail".  The archives can be found
at http://www.mail-archive.com.
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]

---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail".  The archives can be found
at http://www.mail-archive.com.

Reply via email to