Robert Menschel wrote:
Hello Daryl,
Thursday, March 10, 2005, 5:51:26 PM, you wrote:
DCWOS> Whatever your favourite way of retrieving DNS records is, will work.
DCWOS> On Windows you could use nslookup, at a command prompt: ...
Thanks. That's a good start. Now, how will I know when a domain has
a
Hello Daryl,
Thursday, March 10, 2005, 5:51:26 PM, you wrote:
DCWOS> Robert Menschel wrote:
>> And that leads to the second question: what's the best way for an "end
>> user" to obtain/verify SPF records? I have all the capabilities of XP
>> (shudder) and Cygwin readily available, and can get Lin
Robert Menschel wrote:
And that leads to the second question: what's the best way for an "end
user" to obtain/verify SPF records? I have all the capabilities of XP
(shudder) and Cygwin readily available, and can get Linux command-line
capabilities via SSH to SARE's server, I believe.
Whatever your
On Wednesday, March 9, 2005, 6:20:10 PM, Robert Menschel wrote:
> Tuesday, March 8, 2005, 8:44:43 PM, Daryl wrote:
>>> Assumption: This activity will focus only on public newsletters,
>>> services, etc., which normally do not contain any private
>>> information. Therefore there will not be any pri
On Wednesday, March 9, 2005, 6:20:49 PM, Robert Menschel wrote:
> Wednesday, March 9, 2005, 1:00:33 AM, Jeff Chan wrote:
>>> Goal: There are public newsletters, services, etc., which a) do not
>>> spam, and b) can easily be mistaken as spam by SpamAssassin for a
>>> variety of reasons (overly aggr
Hello Daryl,
[BTW, thanks to you and others for the direct response/cc in addition
to the list posting. I get the list by digest, and so list-only
responses don't get to me until the digest is released.]
Wednesday, March 9, 2005, 6:55:50 PM, you wrote:
>> DCWOS> Don't forget about the new whitel
Robert Menschel wrote:
Hello Daryl,
Tuesday, March 8, 2005, 8:44:43 PM, you wrote:
DCWOS> Robert Menschel wrote:
DCWOS>
Summary: A group of volunteers will maintain a collected/distributed
whitelist, using SpamAssassin's whitelist_from_rcvd capabilities,
similar to (but in the opposite direction a
Hello Chris,
Wednesday, March 9, 2005, 7:30:20 AM, you wrote:
>>Summary: A group of volunteers will maintain a collected/distributed
>>whitelist, using SpamAssassin's whitelist_from_rcvd capabilities,
>>similar to (but in the opposite direction as) William Stearns'
>>collected/distributed blackli
Hello Jeff,
Wednesday, March 9, 2005, 1:00:33 AM, you wrote:
>> Goal: There are public newsletters, services, etc., which a) do not
>> spam, and b) can easily be mistaken as spam by SpamAssassin for a
>> variety of reasons (overly aggressive custom rules, wrongly taught
>> Bayes system, paid adve
Hello Daryl,
Tuesday, March 8, 2005, 8:44:43 PM, you wrote:
DCWOS> Robert Menschel wrote:
DCWOS>
>> Summary: A group of volunteers will maintain a collected/distributed
>> whitelist, using SpamAssassin's whitelist_from_rcvd capabilities,
>> similar to (but in the opposite direction as) William
Kelson wrote:
Chris Santerre wrote:
Second, I believe SPF records can be spoofed
Only to the extent that any DNS record can be spoofed.
use in a disposibal manner.
In the sense that you can create any SPF entry you want... for your own
domain. I could set one up with "+all" indicating that mail
Chris Santerre wrote:
Second, I believe SPF records can be spoofed
Only to the extent that any DNS record can be spoofed.
use in a disposibal manner.
In the sense that you can create any SPF entry you want... for your own
domain. I could set one up with "+all" indicating that mail sent via
any s
Chris Santerre wrote:
-Original Message-
From: Daryl C. W. O'Shea [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 09, 2005 11:04 AM
To: Chris Santerre
Cc: 'Robert Menschel'; users@spamassassin.apache.org
Subject: Re: Whitelist collection project
How do you propose that whit
>-Original Message-
>From: Daryl C. W. O'Shea [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, March 09, 2005 11:04 AM
>To: Chris Santerre
>Cc: 'Robert Menschel'; users@spamassassin.apache.org
>Subject: Re: Whitelist collection project
>
>
>Chris
On Wed, Mar 09, 2005 at 08:08:36AM -0800, Jeff Chan wrote:
> That should be safe, and we could probably still use them to
> limited effect in SURBLs to keep those domains off SURBLs.
It could also be used to generate default uridnsbl_skip_domain entries
as well. ;)
Including the domains in spams
On Wednesday, March 9, 2005, 8:03:49 AM, Daryl O'Shea wrote:
> Chris Santerre wrote:
>> This might just be the first time I disagree with you Bob ;)
>>
>> I don't see how this ruleset will not get abused. If I was a spammer I would
>> make sure all my spam hit these rules to let me in.
>>
>> As
Chris Santerre wrote:
This might just be the first time I disagree with you Bob ;)
I don't see how this ruleset will not get abused. If I was a spammer I would
make sure all my spam hit these rules to let me in.
As a research tool it is great! Already the SURBL whitelist is one of the
best arou
On Wednesday, March 9, 2005, 7:30:20 AM, Chris Santerre wrote:
> I don't see how this ruleset will not get abused. If I was a spammer I would
> make sure all my spam hit these rules to let me in.
> As a research tool it is great! Already the SURBL whitelist is one of the
> best around thanks to J
>-Original Message-
>From: Robert Menschel [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, March 08, 2005 11:13 PM
>To: users@spamassassin.apache.org
>Subject: Whitelist collection project
>
>
>OK, based on what little discussion there's been so far, here'
On Tuesday, March 8, 2005, 8:13:05 PM, Robert Menschel wrote:
> OK, based on what little discussion there's been so far, here's a
> draft proposal for people to think about.
> Summary: A group of volunteers will maintain a collected/distributed
> whitelist, using SpamAssassin's whitelist_from_rcvd
Robert Menschel wrote:
OK, based on what little discussion there's been so far, here's a
draft proposal for people to think about.
Summary: A group of volunteers will maintain a collected/distributed
whitelist, using SpamAssassin's whitelist_from_rcvd capabilities,
similar to (but in the opposite
OK, based on what little discussion there's been so far, here's a
draft proposal for people to think about.
Summary: A group of volunteers will maintain a collected/distributed
whitelist, using SpamAssassin's whitelist_from_rcvd capabilities,
similar to (but in the opposite direction as) William S
22 matches
Mail list logo
