Re: [Declude.JunkMail] WhiteListing Isses

2008-12-06 Thread David Barker
Yes I think it should be possible. I think it is a great idea.

David Barker


From: Christopher Jaime [EMAIL PROTECTED]
Sent: Friday, December 05, 2008 5:41 PM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] WhiteListing Isses 

David Barker,

As a feature request, is it possible to add an option
AUTOWHITELIST   ON  to ignore a user's self added
email address in their address book?

- Chris J.

- Original Message - 
From: Michael Jaworski 
To: 
Sent: Monday, December 01, 2008 4:35 PM
Subject: [Declude.JunkMail] WhiteListing Isses


 We too are seeing a big jump in the number of spoofed senders hitting
 everyone who whitelists themselves in SmarterMail. Just about every 
 messages
 is weighted heavy but the whitelist counteracts the effort. The answer is 
 to
 tell the customers to remove themselves from their Trusted Senders list 
 and
 or Address book. We also turned off PREWHITELIST to allow the weighting 
 and
 adding a filter action that pulled those emails (HOLD) from the normal
 message flow thorugh the system.

 Maybe more important we are seeing a growing number of messages spoofing
 other users from the recipients domain. It is almost like they are mining
 associations from social networking or other online sources and using 
 those
 connections to use the whitelist system to allow spam in.

 Anyone seeing the same thing? Anyone have a new stratgey for this type of
 attack?

 Mike J




 ---
 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 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

 


---
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.


Re: [Declude.JunkMail] WhiteListing Isses

2008-12-05 Thread Christopher Jaime

David Barker,

As a feature request, is it possible to add an option
AUTOWHITELIST   ON  to ignore a user's self added
email address in their address book?

- Chris J.


- Original Message - 
From: Michael Jaworski [EMAIL PROTECTED]

To: declude.junkmail@declude.com
Sent: Monday, December 01, 2008 4:35 PM
Subject: [Declude.JunkMail] WhiteListing Isses




We too are seeing a big jump in the number of spoofed senders hitting
everyone who whitelists themselves in SmarterMail. Just about every 
messages
is weighted heavy but the whitelist counteracts the effort. The answer is 
to
tell the customers to remove themselves from their Trusted Senders list 
and
or Address book. We also turned off PREWHITELIST to allow the weighting 
and

adding a filter action that pulled those emails (HOLD) from the normal
message flow thorugh the system.

Maybe more important we are seeing a growing number of messages spoofing
other users from the recipients domain. It is almost like they are mining
associations from social networking or other online sources and using 
those

connections to use the whitelist system to allow spam in.

Anyone seeing the same thing? Anyone have a new stratgey for this type of
attack?

Mike J




---
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 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.



[Declude.JunkMail] WhiteListing Isses

2008-12-01 Thread Michael Jaworski
We too are seeing a big jump in the number of spoofed senders hitting
everyone who whitelists themselves in SmarterMail. Just about every messages
is weighted heavy but the whitelist counteracts the effort. The answer is to
tell the customers to remove themselves from their Trusted Senders list and
or Address book. We also turned off PREWHITELIST to allow the weighting and
adding a filter action that pulled those emails (HOLD) from the normal
message flow thorugh the system.

Maybe more important we are seeing a growing number of messages spoofing
other users from the recipients domain. It is almost like they are mining
associations from social networking or other online sources and using those
connections to use the whitelist system to allow spam in.

Anyone seeing the same thing? Anyone have a new stratgey for this type of
attack?

Mike J




---
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.



RE: [Declude.JunkMail] whitelisting/negative weights with DNSWL.org

2007-07-30 Thread David Barker
This is what I configured but did not find it to be anything out of the
ordinary.

David


#---
---
#http://www.dnswl.org/

#Categories (127.0.X.y):
# 2 - Financial services
# 3 - Newsletters
# 4 - Organisations (both for-profit [ie companies] and non-profit)
# 5 - Service/network providers
# 7 - Travel industry (listed separately since they are known for their high
false-positive rate),
# 8 - governments, administrations and international organisations
# 9 - Media and Tech companies
# 10 - some special cases. 

#Trustworthiness / Score (127.0.x.Y):
# 0 = none - only avoid outright blocking (eg Hotmail, Yahoo mailservers,
-0.1)
# 1 = low - reduce chance of false positives (-1.0)
# 2 = medium - make sure to avoid false positives but allow override for
clear cases (-10.0)
# 3 = high - avoid override (-100.0). 

DNSWL   IP4Rlist.dnswl.org  127.0.0.1
-1  0
DNSWL-PERS  IP4Rlist.dnswl.org  127.0.254.1
-1  0

DNSWL-FIN   IP4Rlist.dnswl.org  127.0.12.1
-1  0
DNSWL-FIN-LOW   IP4Rlist.dnswl.org  127.0.2.1   -3
0
#DNSWL-FIN-MID  IP4Rlist.dnswl.org  127.0.2.2   -5
0
DNSWL-FIN-HIGH  IP4Rlist.dnswl.org  127.0.2.3   -10
0

DNSWL-NEWS  IP4Rlist.dnswl.org  127.0.12.1
-1  0
DNSWL-NEWS-LOW  IP4Rlist.dnswl.org  127.0.3.1   -3
0
DNSWL-NEWS-MID  IP4Rlist.dnswl.org  127.0.3.2   -5
0
DNSWL-NEWS-HIGH IP4Rlist.dnswl.org  127.0.3.3   -10
0

DNSWL-NPO   IP4Rlist.dnswl.org  127.0.10.1
-1  0
DNSWL-NPO-LOW   IP4Rlist.dnswl.org  127.0.4.1   -3
0
DNSWL-NPO-MID   IP4Rlist.dnswl.org  127.0.4.1   -5
0
DNSWL-NPO-HIGH  IP4Rlist.dnswl.org  127.0.4.1   -10
0

DNSWL-SPIP4Rlist.dnswl.org  127.0.11.1
-1  0
DNSWL-SP-LOWIP4Rlist.dnswl.org  127.0.5.1
-3  0
#DNSWL-SP-MID   IP4Rlist.dnswl.org  127.0.5.2   -5
0
DNSWL-SP-HIGH   IP4Rlist.dnswl.org  127.0.5.3   -10
0

DNSWL-TRAVELIP4Rlist.dnswl.org  127.0.12.2
-1  0
DNSWL-TRAVEL-LOWIP4Rlist.dnswl.org  127.0.7.1
-3  0
DNSWL-TRAVEL-MIDIP4Rlist.dnswl.org  127.0.7.2
-5  0
DNSWL-TRAVEL-HIGH   IP4Rlist.dnswl.org  127.0.7.3
-10 0

DNSWL-GOV   IP4Rlist.dnswl.org  127.0.10.2
-1  0
DNSWL-GOV-LOW   IP4Rlist.dnswl.org  127.0.8.1   -3
0
DNSWL-GOV-MID   IP4Rlist.dnswl.org  127.0.8.2   -5
0
DNSWL-GOV-HIGH  IP4Rlist.dnswl.org  127.0.8.3   -10
0

DNSWL-MEDIA IP4Rlist.dnswl.org  127.0.12.3
-1  0
DNSWL-MEDIA-LOW IP4Rlist.dnswl.org  127.0.9.1   -3
0
DNSWL-MEDIA-MID IP4Rlist.dnswl.org  127.0.9.2   -5
0
DNSWL-MEDIA-HIGHIP4Rlist.dnswl.org  127.0.9.3
-10 0

DNSWL-UNSPECIP4Rlist.dnswl.org  127.0.1.1
-1  0
DNSWL-UNSPEC-LOWIP4Rlist.dnswl.org  127.0.10.1
-3  0
DNSWL-UNSPEC-MIDIP4Rlist.dnswl.org  127.0.10.2
-5  0
DNSWL-UNSPEC-HIGH   IP4Rlist.dnswl.org  127.0.10.3
-10 0

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott
Fisher
Sent: Saturday, July 28, 2007 11:57 AM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] whitelisting/negative weights with DNSWL.org

I'll give it a try. Here's what I will use/

DNSWL-FINANCIAL-NONEdnsbl   %IP4R%.list.dnswl.org
127.0.2.0   0   0
DNSWL-FINANCIAL-LOW dnsbl   %IP4R%.list.dnswl.org
127.0.2.1   0   0
DNSWL-FINANCIAL-MEDIUM  dnsbl   %IP4R%.list.dnswl.org
127.0.2.2   -10 0
DNSWL-FINANCIAL-HIGHdnsbl   %IP4R%.list.dnswl.org
127.0.2.3   -20 0
DNSWL-NEWSLETTERS-NONE  dnsbl   %IP4R%.list.dnswl.org
127.0.3.0   0   0
DNSWL-NEWSLETTERS-LOW   dnsbl   %IP4R%.list.dnswl.org
127.0.3.1   0   0
DNSWL-NEWSLETTERS-MEDIUMdnsbl   %IP4R%.list.dnswl.org
127.0.3.2   -10 0
DNSWL-NEWSLETTERS-HIGH  dnsbl   %IP4R%.list.dnswl.org
127.0.3.3   -20 0
DNSWL-ORGANIZATIONS-NONEdnsbl   %IP4R%.list.dnswl.org
127.0.4.0   0   0
DNSWL-ORGANIZATIONS-LOW dnsbl   %IP4R%.list.dnswl.org
127.0.4.1   0   0
DNSWL-ORGANIZATIONS-MEDIUM  dnsbl   %IP4R%.list.dnswl.org
127.0.4.2   -10 0
DNSWL-ORGANIZATIONS-HIGHdnsbl   %IP4R

RE: [Declude.JunkMail] whitelisting/negative weights with DNSWL.org

2007-07-30 Thread Scott Fisher
-David

I think you messed up on all the ones with a 0 in the third octet.

I also chose to run it only on the last header. I wouldn't whitelist/credit
on any information on any previous headers as they could easily be forged.
I did this with the dnsbl test. You could also do it by adding
DUL/DYNA/(there is another one too I think) in the test name. 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David
Barker
Sent: Monday, July 30, 2007 7:53 AM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] whitelisting/negative weights with DNSWL.org

This is what I configured but did not find it to be anything out of the
ordinary.

David


#---
---
#http://www.dnswl.org/

#Categories (127.0.X.y):
# 2 - Financial services
# 3 - Newsletters
# 4 - Organisations (both for-profit [ie companies] and non-profit)
# 5 - Service/network providers
# 7 - Travel industry (listed separately since they are known for their high
false-positive rate),
# 8 - governments, administrations and international organisations
# 9 - Media and Tech companies
# 10 - some special cases. 

#Trustworthiness / Score (127.0.x.Y):
# 0 = none - only avoid outright blocking (eg Hotmail, Yahoo mailservers,
-0.1)
# 1 = low - reduce chance of false positives (-1.0)
# 2 = medium - make sure to avoid false positives but allow override for
clear cases (-10.0)
# 3 = high - avoid override (-100.0). 

DNSWL   IP4Rlist.dnswl.org  127.0.0.1
-1  0
DNSWL-PERS  IP4Rlist.dnswl.org  127.0.254.1
-1  0

DNSWL-FIN   IP4Rlist.dnswl.org  127.0.12.1
-1  0
DNSWL-FIN-LOW   IP4Rlist.dnswl.org  127.0.2.1   -3
0
#DNSWL-FIN-MID  IP4Rlist.dnswl.org  127.0.2.2   -5
0
DNSWL-FIN-HIGH  IP4Rlist.dnswl.org  127.0.2.3   -10
0

DNSWL-NEWS  IP4Rlist.dnswl.org  127.0.12.1
-1  0
DNSWL-NEWS-LOW  IP4Rlist.dnswl.org  127.0.3.1   -3
0
DNSWL-NEWS-MID  IP4Rlist.dnswl.org  127.0.3.2   -5
0
DNSWL-NEWS-HIGH IP4Rlist.dnswl.org  127.0.3.3   -10
0

DNSWL-NPO   IP4Rlist.dnswl.org  127.0.10.1
-1  0
DNSWL-NPO-LOW   IP4Rlist.dnswl.org  127.0.4.1   -3
0
DNSWL-NPO-MID   IP4Rlist.dnswl.org  127.0.4.1   -5
0
DNSWL-NPO-HIGH  IP4Rlist.dnswl.org  127.0.4.1   -10
0

DNSWL-SPIP4Rlist.dnswl.org  127.0.11.1
-1  0
DNSWL-SP-LOWIP4Rlist.dnswl.org  127.0.5.1
-3  0
#DNSWL-SP-MID   IP4Rlist.dnswl.org  127.0.5.2   -5
0
DNSWL-SP-HIGH   IP4Rlist.dnswl.org  127.0.5.3   -10
0

DNSWL-TRAVELIP4Rlist.dnswl.org  127.0.12.2
-1  0
DNSWL-TRAVEL-LOWIP4Rlist.dnswl.org  127.0.7.1
-3  0
DNSWL-TRAVEL-MIDIP4Rlist.dnswl.org  127.0.7.2
-5  0
DNSWL-TRAVEL-HIGH   IP4Rlist.dnswl.org  127.0.7.3
-10 0

DNSWL-GOV   IP4Rlist.dnswl.org  127.0.10.2
-1  0
DNSWL-GOV-LOW   IP4Rlist.dnswl.org  127.0.8.1   -3
0
DNSWL-GOV-MID   IP4Rlist.dnswl.org  127.0.8.2   -5
0
DNSWL-GOV-HIGH  IP4Rlist.dnswl.org  127.0.8.3   -10
0

DNSWL-MEDIA IP4Rlist.dnswl.org  127.0.12.3
-1  0
DNSWL-MEDIA-LOW IP4Rlist.dnswl.org  127.0.9.1   -3
0
DNSWL-MEDIA-MID IP4Rlist.dnswl.org  127.0.9.2   -5
0
DNSWL-MEDIA-HIGHIP4Rlist.dnswl.org  127.0.9.3
-10 0

DNSWL-UNSPECIP4Rlist.dnswl.org  127.0.1.1
-1  0
DNSWL-UNSPEC-LOWIP4Rlist.dnswl.org  127.0.10.1
-3  0
DNSWL-UNSPEC-MIDIP4Rlist.dnswl.org  127.0.10.2
-5  0
DNSWL-UNSPEC-HIGH   IP4Rlist.dnswl.org  127.0.10.3
-10 0

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott
Fisher
Sent: Saturday, July 28, 2007 11:57 AM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] whitelisting/negative weights with DNSWL.org

I'll give it a try. Here's what I will use/

DNSWL-FINANCIAL-NONEdnsbl   %IP4R%.list.dnswl.org
127.0.2.0   0   0
DNSWL-FINANCIAL-LOW dnsbl   %IP4R%.list.dnswl.org
127.0.2.1   0   0
DNSWL-FINANCIAL-MEDIUM  dnsbl   %IP4R%.list.dnswl.org
127.0.2.2   -10 0
DNSWL-FINANCIAL-HIGHdnsbl   %IP4R%.list.dnswl.org
127.0.2.3   -20 0
DNSWL-NEWSLETTERS-NONE  dnsbl   %IP4R%.list.dnswl.org

RE: [Declude.JunkMail] whitelisting/negative weights with DNSWL.org

2007-07-30 Thread David Barker
Yes looks like I only had 1 with 0 in the 3rd octet, thanks for pointing
this out.

DNSWL   IP4Rlist.dnswl.org  127.0.0.1   -1  0

David

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott
Fisher
Sent: Monday, July 30, 2007 10:25 AM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] whitelisting/negative weights with DNSWL.org

-David

I think you messed up on all the ones with a 0 in the third octet.

I also chose to run it only on the last header. I wouldn't whitelist/credit
on any information on any previous headers as they could easily be forged.
I did this with the dnsbl test. You could also do it by adding
DUL/DYNA/(there is another one too I think) in the test name. 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David
Barker
Sent: Monday, July 30, 2007 7:53 AM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] whitelisting/negative weights with DNSWL.org

This is what I configured but did not find it to be anything out of the
ordinary.

David


#---
---
#http://www.dnswl.org/

#Categories (127.0.X.y):
# 2 - Financial services
# 3 - Newsletters
# 4 - Organisations (both for-profit [ie companies] and non-profit)
# 5 - Service/network providers
# 7 - Travel industry (listed separately since they are known for their high
false-positive rate),
# 8 - governments, administrations and international organisations
# 9 - Media and Tech companies
# 10 - some special cases. 

#Trustworthiness / Score (127.0.x.Y):
# 0 = none - only avoid outright blocking (eg Hotmail, Yahoo mailservers,
-0.1)
# 1 = low - reduce chance of false positives (-1.0)
# 2 = medium - make sure to avoid false positives but allow override for
clear cases (-10.0)
# 3 = high - avoid override (-100.0). 

DNSWL   IP4Rlist.dnswl.org  127.0.0.1
-1  0
DNSWL-PERS  IP4Rlist.dnswl.org  127.0.254.1
-1  0

DNSWL-FIN   IP4Rlist.dnswl.org  127.0.12.1
-1  0
DNSWL-FIN-LOW   IP4Rlist.dnswl.org  127.0.2.1   -3
0
#DNSWL-FIN-MID  IP4Rlist.dnswl.org  127.0.2.2   -5
0
DNSWL-FIN-HIGH  IP4Rlist.dnswl.org  127.0.2.3   -10
0

DNSWL-NEWS  IP4Rlist.dnswl.org  127.0.12.1
-1  0
DNSWL-NEWS-LOW  IP4Rlist.dnswl.org  127.0.3.1   -3
0
DNSWL-NEWS-MID  IP4Rlist.dnswl.org  127.0.3.2   -5
0
DNSWL-NEWS-HIGH IP4Rlist.dnswl.org  127.0.3.3   -10
0

DNSWL-NPO   IP4Rlist.dnswl.org  127.0.10.1
-1  0
DNSWL-NPO-LOW   IP4Rlist.dnswl.org  127.0.4.1   -3
0
DNSWL-NPO-MID   IP4Rlist.dnswl.org  127.0.4.1   -5
0
DNSWL-NPO-HIGH  IP4Rlist.dnswl.org  127.0.4.1   -10
0

DNSWL-SPIP4Rlist.dnswl.org  127.0.11.1
-1  0
DNSWL-SP-LOWIP4Rlist.dnswl.org  127.0.5.1
-3  0
#DNSWL-SP-MID   IP4Rlist.dnswl.org  127.0.5.2   -5
0
DNSWL-SP-HIGH   IP4Rlist.dnswl.org  127.0.5.3   -10
0

DNSWL-TRAVELIP4Rlist.dnswl.org  127.0.12.2
-1  0
DNSWL-TRAVEL-LOWIP4Rlist.dnswl.org  127.0.7.1
-3  0
DNSWL-TRAVEL-MIDIP4Rlist.dnswl.org  127.0.7.2
-5  0
DNSWL-TRAVEL-HIGH   IP4Rlist.dnswl.org  127.0.7.3
-10 0

DNSWL-GOV   IP4Rlist.dnswl.org  127.0.10.2
-1  0
DNSWL-GOV-LOW   IP4Rlist.dnswl.org  127.0.8.1   -3
0
DNSWL-GOV-MID   IP4Rlist.dnswl.org  127.0.8.2   -5
0
DNSWL-GOV-HIGH  IP4Rlist.dnswl.org  127.0.8.3   -10
0

DNSWL-MEDIA IP4Rlist.dnswl.org  127.0.12.3
-1  0
DNSWL-MEDIA-LOW IP4Rlist.dnswl.org  127.0.9.1   -3
0
DNSWL-MEDIA-MID IP4Rlist.dnswl.org  127.0.9.2   -5
0
DNSWL-MEDIA-HIGHIP4Rlist.dnswl.org  127.0.9.3
-10 0

DNSWL-UNSPECIP4Rlist.dnswl.org  127.0.1.1
-1  0
DNSWL-UNSPEC-LOWIP4Rlist.dnswl.org  127.0.10.1
-3  0
DNSWL-UNSPEC-MIDIP4Rlist.dnswl.org  127.0.10.2
-5  0
DNSWL-UNSPEC-HIGH   IP4Rlist.dnswl.org  127.0.10.3
-10 0

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott
Fisher
Sent: Saturday, July 28, 2007 11:57 AM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] whitelisting/negative weights with DNSWL.org

I'll give it a try. Here's what I will use/

DNSWL-FINANCIAL-NONE

RE: [Declude.JunkMail] whitelisting/negative weights with DNSWL.org

2007-07-28 Thread Scott Fisher
Ewww. Look at all the return codes!

I'd be interested in seeing some rates. Does it hit enough to work?

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gary
Steiner
Sent: Friday, July 27, 2007 6:42 PM
To: declude.junkmail@declude.com
Subject: [Declude.JunkMail] whitelisting/negative weights with DNSWL.org

Is anyone using DNSWL (www.dnswl.org) as a separate Declude test?  Seems
like it is incorporated into SpamAssassin.  Do they seem reliable?

Gary





---
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 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.



RE: [Declude.JunkMail] whitelisting/negative weights with DNSWL.org

2007-07-28 Thread Scott Fisher
-ORGANIZATIONS-MEDIUM  WARN
DNSWL-ORGANIZATIONS-HIGHWARN
DNSWL-ISP-NONE  WARN
DNSWL-ISP-LOW   WARN
DNSWL-ISP-MEDIUMWARN
DNSWL-ISP-HIGH  WARN
DNSWL-PRIVATE-NONE  WARN
DNSWL-PRIVATE-LOW   WARN
DNSWL-PRIVATE-MEDIUMWARN
DNSWL-PRIVATE-HIGH  WARN
DNSWL-TRAVEL-NONE   WARN
DNSWL-TRAVEL-LOWWARN
DNSWL-TRAVEL-MEDIUM WARN
DNSWL-TRAVEL-HIGH   WARN
DNSWL-GOVERNMENT-NONE   WARN
DNSWL-GOVERNMENT-LOWWARN
DNSWL-GOVERNMENT-MEDIUM WARN
DNSWL-GOVERNMENT-HIGH   WARN
DNSWL-MEDIA-NONEWARN
DNSWL-MEDIA-LOW WARN
DNSWL-MEDIA-MEDIUM  WARN
DNSWL-MEDIA-HIGHWARN
DNSWL-SPECIAL-NONE  WARN
DNSWL-SPECIAL-LOW   WARN
DNSWL-SPECIAL-MEDIUMWARN
DNSWL-SPECIAL-HIGH  WARN
DNSWL-EDUCATION-NONEWARN
DNSWL-EDUCATION-LOW WARN
DNSWL-EDUCATION-MEDIUM  WARN
DNSWL-EDUCATION-HIGHWARN
DNSWL-HEALTHCARE-NONE   WARN
DNSWL-HEALTHCARE-LOWWARN
DNSWL-HEALTHCARE-MEDIUM WARN
DNSWL-HEALTHCARE-HIGH   WARN
DNSWL-INDUSTRIAL-NONE   WARN
DNSWL-INDUSTRIAL-LOWWARN
DNSWL-INDUSTRIAL-MEDIUM WARN
DNSWL-INDUSTRIAL-HIGH   WARN
DNSWL-RETAIL-NONE   WARN
DNSWL-RETAIL-LOWWARN
DNSWL-RETAIL-MEDIUM WARN
DNSWL-RETAIL-HIGH   WARN

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gary
Steiner
Sent: Friday, July 27, 2007 6:42 PM
To: declude.junkmail@declude.com
Subject: [Declude.JunkMail] whitelisting/negative weights with DNSWL.org

Is anyone using DNSWL (www.dnswl.org) as a separate Declude test?  Seems
like it is incorporated into SpamAssassin.  Do they seem reliable?

Gary





---
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 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.



[Declude.JunkMail] whitelisting/negative weights with DNSWL.org

2007-07-27 Thread Gary Steiner
Is anyone using DNSWL (www.dnswl.org) as a separate Declude test?  Seems like 
it is incorporated into SpamAssassin.  Do they seem reliable?

Gary





---
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.



[Declude.JunkMail] whitelisting based on rev dns

2006-11-08 Thread Craig Edmonds



How can I whitelist 
based on Reverse DNS?

Kindest RegardsCraig Edmonds123 
Marbella InternetW: www.123marbella.com



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


Re: [Declude.JunkMail] whitelisting based on rev dns

2006-11-08 Thread Darin Cox



How about negative weighting instead of 
whitelisting.

If you want to do it selectively, you can create a 
quick Declude filter that you give a high negative weight to, and only include 
the domains that you want to pass through based on having REVDNS 
entries.
Darin.


- Original Message - 
From: Craig 
Edmonds 
To: declude.junkmail@declude.com 

Sent: Wednesday, November 08, 2006 1:24 PM
Subject: [Declude.JunkMail] whitelisting based on rev 
dns

How can I whitelist 
based on Reverse DNS?

Kindest RegardsCraig Edmonds123 
Marbella InternetW: www.123marbella.com

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


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


RE: [Declude.JunkMail] whitelisting based on rev dns

2006-11-08 Thread Colbeck, Andrew



Craig, I don't use any of the Declude WHITELIST features 
due to the potential for giving the sender carte blanche access; if a known good 
sender is sending crap, I still want to have a chance to block the 
crap.

What I do is counterweight.

I create a filter file called, say, CounterWeight.txt and 
in the global.cfg I give it zero weight for passing or 
failing.

Inside the filter file, I put in lines like 
this:

#Feb-01-2006 AC SurveyMonkey.com MAILFROM spoofs the email 
address of whomever is sending out the survey invitationsREMOTEIP -10 
CIDR 66.179.50.160/27REVDNS -5 ENDSWITH 
.surveymonkey.com
My preference is to use REMOTEIP tests, then REVDNS, then 
HELO, then HEADERS, then MAILFROM for reliablityand antispoofedness. 
Likewise, they get decending amounts of negative weight.

Another tip:

I put a test at the top of my CounterWeight file(s) 
that aborts processing if I don't want to reward a message with negative weight, 
such as if a prior filter test (according to the top-down order in global.cfg) 
of mine detected a known virus or junk email that I know I want to block 
regardless of whom it came from, e.g.

TESTSFAILED END CONTAINS VIRUSBOUNCE


TESTSFAILED END CONTAINS 
COMBOSNIFFER


Andrew 8)



  
  
  From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On Behalf Of Craig EdmondsSent: 
  Wednesday, November 08, 2006 10:25 AMTo: 
  declude.junkmail@declude.comSubject: [Declude.JunkMail] 
  whitelisting based on rev dnsImportance: 
  HighSensitivity: Confidential
  
  How can I 
  whitelist based on Reverse DNS?
  
  Kindest RegardsCraig 
  Edmonds123 Marbella InternetW: www.123marbella.com
  
  ---This E-mail came from the Declude.JunkMail mailing 
  list. Tounsubscribe, just send an E-mail to [EMAIL PROTECTED], 
  andtype "unsubscribe Declude.JunkMail". The archives can be foundat 
  http://www.mail-archive.com. 

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


Re: [Declude.JunkMail] whitelisting based on rev dns

2006-11-08 Thread Greg Evanitsky


On Nov 8, 2006, at 1:24 PM, Craig Edmonds wrote:


How can I whitelist based on Reverse DNS?


Create a filter with lines like

REVDNS  xxx  ENDSWITH  .abcdefghi.com

where xxx is weight to apply. Xxx could be a very high number to  
cause the message to be deleted or it could be a negative number.


In my revdns spam filter I also have the following lines at the top  
to save processor usage


SKIPIFWEIGHT  xx
STOPATFIRSTHIT

If the message's weight already exceeds xx the filter will be skipped.

Later,
Greg






---
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.



Re: [Declude.JunkMail] whitelisting based on rev dns

2006-11-08 Thread Nick Hayer




Craig Edmonds wrote:

  
  
  How
can I whitelist based on Reverse DNS?

REMOTEIP WHITELIST CIDR  64.4.240.0/20
REVDNS  WHITELIST ENDSWITH .paypal.com
etc...

-Nick

  
  Kindest Regards
Craig Edmonds
123 Marbella Internet
W: www.123marbella.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 came from the Declude.JunkMail mailing list.  Tounsubscribe, just send an E-mail to [EMAIL PROTECTED], andtype "unsubscribe Declude.JunkMail".  The archives can be foundat http://www.mail-archive.com.

RE: [Declude.JunkMail] whitelisting based on rev dns

2006-11-08 Thread Andy Schmidt



Absolutely, 

WHITELIST REVDNS 
.declude.com

You can alsocan create your own RDNSBL zone in your 
DNS server (that's what I did) and create one for SPF domains that spammers set 
up to reliably reject mail based on reverse DNS (thank you for them adhering to 
SPF!).
Then 
you set up a WhiteList zone for known "good" reverse DNS, which you use to 
subtract weight or combine with a filter to whitelist 
outright.

Best RegardsAndy SchmidtPhone: +1 201 934-3414 x20 
(Business)Fax: +1 201 934-9206 



From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of Craig EdmondsSent: 
Wednesday, November 08, 2006 01:25 PMTo: 
declude.junkmail@declude.comSubject: [Declude.JunkMail] whitelisting 
based on rev dnsImportance: HighSensitivity: 
Confidential

How can I whitelist 
based on Reverse DNS?

Kindest RegardsCraig Edmonds123 
Marbella InternetW: www.123marbella.com

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

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


RE: [Declude.JunkMail] whitelisting based on rev dns

2006-11-08 Thread Todd Richards
Is the Reverse DNS in the headers anywhere?  I've just been going out to
DNSReports.com and pulling it for the ones I want to add.  Easier way?

Todd
 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg
Evanitsky
Sent: Wednesday, November 08, 2006 12:56 PM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] whitelisting based on rev dns
Importance: High


On Nov 8, 2006, at 1:24 PM, Craig Edmonds wrote:

 How can I whitelist based on Reverse DNS?

Create a filter with lines like

REVDNS  xxx  ENDSWITH  .abcdefghi.com

where xxx is weight to apply. Xxx could be a very high number to cause the
message to be deleted or it could be a negative number.

In my revdns spam filter I also have the following lines at the top to save
processor usage

SKIPIFWEIGHT  xx
STOPATFIRSTHIT

If the message's weight already exceeds xx the filter will be skipped.

Later,
Greg






---
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 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.



Re: [Declude.JunkMail] whitelisting based on rev dns

2006-11-08 Thread Darrell \([EMAIL PROTECTED])
Todd,

As you know headers can be forged so its always best to manually look-up the 
IP.  As you said earlier you are using fpReview.  In the headers view you 
can right click and select resolve ip's to hostnames to get the reverse dns. 
Than after that you can highlight any of the text and automatically create a 
revdns entry in a filter.

We have a quick overview video showing the basic features at
http://www.invariantsystems.com/fpreview/screencaptures.htm
under video.

Darrell


Check out http://www.invariantsystems.com for utilities for Declude And 
Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTG 
Integration, and Log Parsers.

- Original Message - 
From: Todd Richards [EMAIL PROTECTED]
To: declude.junkmail@declude.com
Sent: Wednesday, November 08, 2006 4:13 PM
Subject: RE: [Declude.JunkMail] whitelisting based on rev dns


Is the Reverse DNS in the headers anywhere?  I've just been going out to
DNSReports.com and pulling it for the ones I want to add.  Easier way?

Todd


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg
Evanitsky
Sent: Wednesday, November 08, 2006 12:56 PM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] whitelisting based on rev dns
Importance: High


On Nov 8, 2006, at 1:24 PM, Craig Edmonds wrote:

 How can I whitelist based on Reverse DNS?

Create a filter with lines like

REVDNS  xxx  ENDSWITH  .abcdefghi.com

where xxx is weight to apply. Xxx could be a very high number to cause the
message to be deleted or it could be a negative number.

In my revdns spam filter I also have the following lines at the top to save
processor usage

SKIPIFWEIGHT  xx
STOPATFIRSTHIT

If the message's weight already exceeds xx the filter will be skipped.

Later,
Greg






---
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 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 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.



RE: [Declude.JunkMail] whitelisting based on rev dns

2006-11-08 Thread Andy Schmidt
Hi Todd,

You can configure Declude to add its own header with diagnostic information,
including the Reverse DNS, e.g.:

XINHEADER   X-Declude: Version %VERSION%; Code 0x%HEADERCODE% from
%REVDNS% [%REMOTEIP%]
XINHEADER   X-Declude: Triggered [%WEIGHT%] %TESTSFAILED%
XINHEADER   X-Countries: %COUNTRYCHAIN%
XINHEADER   Return-Path: %MAILFROM% 



Best Regards
Andy Schmidt

Phone:  +1 201 934-3414 x20 (Business)
Fax:+1 201 934-9206 


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Todd
Richards
Sent: Wednesday, November 08, 2006 04:13 PM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] whitelisting based on rev dns

Is the Reverse DNS in the headers anywhere?  I've just been going out to
DNSReports.com and pulling it for the ones I want to add.  Easier way?

Todd
 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg
Evanitsky
Sent: Wednesday, November 08, 2006 12:56 PM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] whitelisting based on rev dns
Importance: High


On Nov 8, 2006, at 1:24 PM, Craig Edmonds wrote:

 How can I whitelist based on Reverse DNS?

Create a filter with lines like

REVDNS  xxx  ENDSWITH  .abcdefghi.com

where xxx is weight to apply. Xxx could be a very high number to cause the
message to be deleted or it could be a negative number.

In my revdns spam filter I also have the following lines at the top to save
processor usage

SKIPIFWEIGHT  xx
STOPATFIRSTHIT

If the message's weight already exceeds xx the filter will be skipped.

Later,
Greg






---
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 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 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.



RE: [Declude.JunkMail] whitelisting based on rev dns

2006-11-08 Thread Colbeck, Andrew



In the header of the message, look at the last 
IP address in square brackets, this is the IP address of the sending email 
server. The text just before it is the HELO sent by it, and is often 
unreliable with legitimate mail, and practically a work of fiction with 
spam.To get the REVDNS that you can put in your filter files, go to a 
command prompt and use the name server lookup program with the IP address as the 
only parameter, e.g.C:\Tempnslookup 63.246.31.248Server: 
myinternal.DNS.serverAddress: 
192.168.0.1Name: smtp.declude.comAddress: 
63.246.31.248C:\TempSome admins don't mind the 
extra overhead, and use the XINHEADERand/or XOUTHEADER feature in their 
global.cfg to insertvarious lines into the header of every message that 
contain Declude variables like REVDNS. One common thing that comes up when 
doing this is that if you use the ALLRECIPS to document in the header who all 
the recipients are, you've just "blown the cover" on someone who sent a 
legitimate email with a BCC list of recipients in your domain(s). Don't do 
that.

Andrew 8)
 -Original Message- From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED]] On 
Behalf Of Todd Richards Sent: Wednesday, November 08, 2006 1:13 
PM To: declude.junkmail@declude.com Subject: RE: 
[Declude.JunkMail] whitelisting based on rev dns Is the Reverse 
DNS in the headers anywhere? I've just been going out to 
DNSReports.com and pulling it for the ones I want to add. Easier 
way? Todd -Original 
Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On 
Behalf Of Greg Evanitsky Sent: Wednesday, November 08, 2006 12:56 
PM To: declude.junkmail@declude.com Subject: Re: 
[Declude.JunkMail] whitelisting based on rev dns Importance: 
High On Nov 8, 2006, at 1:24 PM, Craig Edmonds 
wrote:  How can I whitelist based on Reverse 
DNS? Create a filter with lines like 
REVDNS xxx ENDSWITH .abcdefghi.com where xxx 
is weight to apply. Xxx could be a very high number to cause the message 
to be deleted or it could be a negative number. In my revdns 
spam filter I also have the following lines at the top to save processor 
usage SKIPIFWEIGHT xx 
STOPATFIRSTHIT If the message's weight already exceeds xx the 
filter will be skipped. Later, 
Greg --- 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 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 came from the Declude.JunkMail mailing list.  Tounsubscribe, just send an E-mail to [EMAIL PROTECTED], andtype "unsubscribe Declude.JunkMail".  The archives can be foundat http://www.mail-archive.com.


RE: [Declude.JunkMail] whitelisting based on rev dns

2006-11-08 Thread Todd Richards
Thanks Darrell.  That's a great feature (and I just purchased an fpReview
license)!

Todd


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darrell
([EMAIL PROTECTED])
Sent: Wednesday, November 08, 2006 3:52 PM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] whitelisting based on rev dns

Todd,

As you know headers can be forged so its always best to manually look-up the
IP.  As you said earlier you are using fpReview.  In the headers view you
can right click and select resolve ip's to hostnames to get the reverse dns.

Than after that you can highlight any of the text and automatically create a
revdns entry in a filter.

We have a quick overview video showing the basic features at
http://www.invariantsystems.com/fpreview/screencaptures.htm
under video.

Darrell


Check out http://www.invariantsystems.com for utilities for Declude And
Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTG
Integration, and Log Parsers.

- Original Message -
From: Todd Richards [EMAIL PROTECTED]
To: declude.junkmail@declude.com
Sent: Wednesday, November 08, 2006 4:13 PM
Subject: RE: [Declude.JunkMail] whitelisting based on rev dns


Is the Reverse DNS in the headers anywhere?  I've just been going out to
DNSReports.com and pulling it for the ones I want to add.  Easier way?

Todd


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg
Evanitsky
Sent: Wednesday, November 08, 2006 12:56 PM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] whitelisting based on rev dns
Importance: High


On Nov 8, 2006, at 1:24 PM, Craig Edmonds wrote:

 How can I whitelist based on Reverse DNS?

Create a filter with lines like

REVDNS  xxx  ENDSWITH  .abcdefghi.com

where xxx is weight to apply. Xxx could be a very high number to cause the
message to be deleted or it could be a negative number.

In my revdns spam filter I also have the following lines at the top to save
processor usage

SKIPIFWEIGHT  xx
STOPATFIRSTHIT

If the message's weight already exceeds xx the filter will be skipped.

Later,
Greg






---
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 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 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 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.



RE: [Declude.JunkMail] Whitelisting flaw in Declude?

2006-10-19 Thread Colbeck, Andrew



Yeah, what Matt said.

Message splitting before junkmail filtering would 
bepunishing for CPU time and somewhat more for disk time; message 
splitting for the sake of whitelisting (or alternate actions)after 
junkmail filtering would be an incremental cost.

And message splitting before junkmail filtering on a system 
that has a wildcard email address would be lethal for that 
system.

Andrew.


p.s. In my corporate network, we email each other a lot, 
and we see that Exchange "single instance storage" of a message only saves us 
20% of the disk space. And that includes single storage of a message in my 
Sent Items as well as in my neighbour's Inbox and the next guy's Deleted 
Items.


  
  
  From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On Behalf Of MattSent: 
  Wednesday, October 18, 2006 8:20 PMTo: 
  declude.junkmail@declude.comSubject: Re: [Declude.JunkMail] 
  Whitelisting flaw in Declude?
  I have some stats here that suggest otherwise. We only have 
  5% more recipients than messages that make it through our gateway, and we only 
  return permanent errors presently for mail bombing related activities. 
  This however is a dedicated gateway and not a hosted mail server, so stats 
  from a hosted mail server would see a slightly higher rate since most 
  multiple-recipient E-mails are internal to a server. If you are 
  splitting on a gateway and not splitting internal E-mail, you should see no 
  increase beyond my numbers.It's a doable solution if one has the 
  need.MattJay Sudowski - Handy Networks LLC wrote: 
  Also, realize that on servers processing a large volume of messages per
day, the additional IO necessary to create duplicate messages and header
files for each specific recipient would be a death sentence...


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
David Barker
Sent: Wednesday, October 18, 2006 9:30 AM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?

To create a duplicate message for each recipient is not a trivial issue.
This is a function of the mail server not Declude.

David Barker
Director of Product Development
Your Email security is our business
978.499.2933 office
978.988.1311 fax
[EMAIL PROTECTED]
 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
Kevin
Bilbee
Sent: Tuesday, October 17, 2006 5:08 PM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?

Delcude has always functioned like this.

What declude could do in this case is to duplicate the message for each
recipient and write a new header file to each recipient. Not a big
issue.
Deliver to the one that whitelists and run the spam checks for the
others.



Kevin Bilbee

  
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of 
Darin Cox
Sent: Tuesday, October 17, 2006 12:37 PM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?

It's actually more of an issue of how the mail server handles the 
message.
In the case of multiple recipients, since there is only one message 
file addressed to multiple recipients in the headers, it's either 
deliver or not deliver unless you rewrite the headers to modify the 
recipient list.  I think I'd rather not have the spam filtering system

  
alter that.  Add to the header, yes.  Alter the recipients, no.

Also, I have not come across a situation where I wanted to let a 
message go through to one recipient and not to others, except in the 
situation of lists which is a whole other topic.

Darin.


- Original Message -
From: "Dave Beckstrom" [EMAIL PROTECTED]
To: declude.junkmail@declude.com
Sent: Tuesday, October 17, 2006 3:11 PM
Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?


I would call that a flaw, then, in how Declude processes the
whitelist.
  
I have a listserver email address for which I do not want email spam 
checked.  This is because I don't want messages going out to the list 
that say SPAM in the subject line.  Because nobody who is not a member

  
on the list can post to the list, there is no problem whitelisting the

  
"TO"
address
for mail sent to the list server email address.

However, spammers will send an email to a dozen of our mail addresses
(12
recipients) one of which is the whitelised "TO" address for the 
listserver.
Because of the way Declude processes the whitelist, that means that 
the other 11 recipient receive the spam even though mail to them is 
not whitelisted.

That is a bad design on Declude's part, wouldn't you agree?  Anyone 
else feel that this needs to be rectified?




  -Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
  Darrell

  ([EMAIL PROTECTED])
Sent: Tuesday, October 17, 2006 11:25 AM
To: declude.junkmail@de

RE: [Declude.JunkMail] Whitelisting flaw in Declude?

2006-10-19 Thread Dave Beckstrom








A new tag (whitelistunique) which
only would whitelist if the email had a single recipient would solve the
problem and be much safer.

















From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Colbeck, Andrew
Sent: Thursday, October 19, 2006
11:45 AM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail]
Whitelisting flaw in Declude?





Yeah, what Matt said.



Message splitting before junkmail
filtering would bepunishing for CPU time and somewhat more for disk time;
message splitting for the sake of whitelisting (or alternate actions)after
junkmail filtering would be an incremental cost.



And message splitting before junkmail
filtering on a system that has a wildcard email address would be lethal for
that system.



Andrew.





p.s. In my corporate network, we email
each other a lot, and we see that Exchange single instance storage
of a message only saves us 20% of the disk space. And that includes
single storage of a message in my Sent Items as well as in my neighbour's Inbox
and the next guy's Deleted Items.













From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
On Behalf Of Matt
Sent: Wednesday, October 18, 2006
8:20 PM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail]
Whitelisting flaw in Declude?

I have some stats here that suggest otherwise.
We only have 5% more recipients than messages that make it through our gateway,
and we only return permanent errors presently for mail bombing related
activities. This however is a dedicated gateway and not a hosted mail
server, so stats from a hosted mail server would see a slightly higher rate
since most multiple-recipient E-mails are internal to a server. If you
are splitting on a gateway and not splitting internal E-mail, you should see no
increase beyond my numbers.

It's a doable solution if one has the need.

Matt


Jay Sudowski - Handy Networks LLC wrote: 

Also, realize that on servers processing a large volume of messages perday, the additional IO necessary to create duplicate messages and headerfiles for each specific recipient would be a death sentence...-Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf OfDavid BarkerSent: Wednesday, October 18, 2006 9:30 AMTo: declude.junkmail@declude.comSubject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?To create a duplicate message for each recipient is not a trivial issue.This is a function of the mail server not Declude.David BarkerDirector of Product DevelopmentYour Email security is our business978.499.2933 office978.988.1311 fax[EMAIL PROTECTED] -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf OfKevinBilbeeSent: Tuesday, October 17, 2006 5:08 PMTo: declude.junkmail@declude.comSubject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?Delcude has always functioned like this.What declude could do in this case is to duplicate the message for eachrecipient and write a new header file to each recipient. Not a bigissue.Deliver to the one that whitelists and run the spam checks for theothers.Kevin Bilbee 

-Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Darin CoxSent: Tuesday, October 17, 2006 12:37 PMTo: declude.junkmail@declude.comSubject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?It's actually more of an issue of how the mail server handles the message.In the case of multiple recipients, since there is only one message file addressed to multiple recipients in the headers, it's either deliver or not deliver unless you rewrite the headers to modify the recipient list. I think I'd rather not have the spam filtering system 

 

alter that. Add to the header, yes. Alter the recipients, no.Also, I have not come across a situation where I wanted to let a message go through to one recipient and not to others, except in the situation of lists which is a whole other topic.Darin.- Original Message -From: Dave Beckstrom [EMAIL PROTECTED]To: declude.junkmail@declude.comSent: Tuesday, October 17, 2006 3:11 PMSubject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?I would call that a flaw, then, in how Declude processes the 

whitelist. 

I have a listserver email address for which I do not want email spam checked. This is because I don't want messages going out to the list that say SPAM in the subject line. Because nobody who is not a member 

 

on the list can post to the list, there is no problem whitelisting the 

 

TOaddressfor mail sent to the list server email address.However, spammers will send an email to a dozen of our mail addresses(12recipients) one of which is the whitelised TO address for the listserver.Because of the way Declude processes the whitelist, that means that the other 11 recipient receive the spam even though mail to them is not whitelisted.That is a bad design on Declude's part, wouldn't you agree? Anyone else feel that this needs to be rectified? 

-Original Message-From

RE: [Declude.JunkMail] Whitelisting flaw in Declude?

2006-10-18 Thread David Barker
To create a duplicate message for each recipient is not a trivial issue.
This is a function of the mail server not Declude.

David Barker
Director of Product Development
Your Email security is our business
978.499.2933 office
978.988.1311 fax
[EMAIL PROTECTED]
 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin
Bilbee
Sent: Tuesday, October 17, 2006 5:08 PM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?

Delcude has always functioned like this.

What declude could do in this case is to duplicate the message for each
recipient and write a new header file to each recipient. Not a big issue.
Deliver to the one that whitelists and run the spam checks for the others.



Kevin Bilbee

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of 
 Darin Cox
 Sent: Tuesday, October 17, 2006 12:37 PM
 To: declude.junkmail@declude.com
 Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 It's actually more of an issue of how the mail server handles the 
 message.
 In the case of multiple recipients, since there is only one message 
 file addressed to multiple recipients in the headers, it's either 
 deliver or not deliver unless you rewrite the headers to modify the 
 recipient list.  I think I'd rather not have the spam filtering system 
 alter that.  Add to the header, yes.  Alter the recipients, no.
 
 Also, I have not come across a situation where I wanted to let a 
 message go through to one recipient and not to others, except in the 
 situation of lists which is a whole other topic.
 
 Darin.
 
 
 - Original Message -
 From: Dave Beckstrom [EMAIL PROTECTED]
 To: declude.junkmail@declude.com
 Sent: Tuesday, October 17, 2006 3:11 PM
 Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 
 I would call that a flaw, then, in how Declude processes the whitelist.
 
 I have a listserver email address for which I do not want email spam 
 checked.  This is because I don't want messages going out to the list 
 that say SPAM in the subject line.  Because nobody who is not a member 
 on the list can post to the list, there is no problem whitelisting the 
 TO
 address
 for mail sent to the list server email address.
 
 However, spammers will send an email to a dozen of our mail addresses
 (12
 recipients) one of which is the whitelised TO address for the 
 listserver.
 Because of the way Declude processes the whitelist, that means that 
 the other 11 recipient receive the spam even though mail to them is 
 not whitelisted.
 
 That is a bad design on Declude's part, wouldn't you agree?  Anyone 
 else feel that this needs to be rectified?
 
 
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
 Darrell
  ([EMAIL PROTECTED])
  Sent: Tuesday, October 17, 2006 11:25 AM
  To: declude.junkmail@declude.com
  Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
 
  If one user is whitelisted they all will be whitelisted for that
 email.
  There are some things you can do to prevent this like 
  BYPASSWHITELIST
 test.
 
  Darre;;
 
  
  -
 ---
  Check out http://www.invariantsystems.com for utilities for Declude
 And
  Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI
 integration,
 MRTG
  Integration, and Log Parsers.
 
  - Original Message -
  From: Dave Beckstrom [EMAIL PROTECTED]
  To: declude.junkmail@declude.com
  Sent: Tuesday, October 17, 2006 11:18 AM
  Subject: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 
  If an email is received that is addressed to multiple recipients, 
  one
 of
  whom is whitelisted, does Declude treat the email as whitelisted for
 all
  recipients?
 
 
 
 
 
  ---
  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 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 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 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 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

RE: [Declude.JunkMail] Whitelisting flaw in Declude? - David Barker

2006-10-18 Thread Dave Beckstrom
David,

I agree. 

But I do think the whitelisting needs to be changed.  I think you should add
a WhitelistUnique tag.

EG:

WhitelistUnique TO: [EMAIL PROTECTED]


The way the tag would function is that the email would only be treated as
whitelisted if [EMAIL PROTECTED] was the only address in the TO field and if 
the
carbon copy field is also blank.  This insures that spammers can't stack
multiple email addresses in the TO or CC fields, one address of which is
whitelisted, thus forcing the email to pass through Declude to ALL
RECIPIENTS rather than just to the whitelisted recipient.  


Besides the listserver problem I described, I can see some places wanting to
whitelist email to [EMAIL PROTECTED] or [EMAIL PROTECTED]  Spammers who have
figured out this gaping hole in Declude could easily force all email to a
site to be whitelisted by simply sending email to [EMAIL PROTECTED] and tagging
a dozen other addresses onto the TO field.  Not good.

Is my suggestion something that you can implement?



 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David
 Barker
 Sent: Wednesday, October 18, 2006 8:30 AM
 To: declude.junkmail@declude.com
 Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 To create a duplicate message for each recipient is not a trivial issue.
 This is a function of the mail server not Declude.
 
 David Barker
 Director of Product Development
 Your Email security is our business
 978.499.2933 office
 978.988.1311 fax
 [EMAIL PROTECTED]
 
 
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin
 Bilbee
 Sent: Tuesday, October 17, 2006 5:08 PM
 To: declude.junkmail@declude.com
 Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 Delcude has always functioned like this.
 
 What declude could do in this case is to duplicate the message for each
 recipient and write a new header file to each recipient. Not a big issue.
 Deliver to the one that whitelists and run the spam checks for the others.
 
 
 
 Kevin Bilbee
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
  Darin Cox
  Sent: Tuesday, October 17, 2006 12:37 PM
  To: declude.junkmail@declude.com
  Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
 
  It's actually more of an issue of how the mail server handles the
  message.
  In the case of multiple recipients, since there is only one message
  file addressed to multiple recipients in the headers, it's either
  deliver or not deliver unless you rewrite the headers to modify the
  recipient list.  I think I'd rather not have the spam filtering system
  alter that.  Add to the header, yes.  Alter the recipients, no.
 
  Also, I have not come across a situation where I wanted to let a
  message go through to one recipient and not to others, except in the
  situation of lists which is a whole other topic.
 
  Darin.
 
 
  - Original Message -
  From: Dave Beckstrom [EMAIL PROTECTED]
  To: declude.junkmail@declude.com
  Sent: Tuesday, October 17, 2006 3:11 PM
  Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 
  I would call that a flaw, then, in how Declude processes the whitelist.
 
  I have a listserver email address for which I do not want email spam
  checked.  This is because I don't want messages going out to the list
  that say SPAM in the subject line.  Because nobody who is not a member
  on the list can post to the list, there is no problem whitelisting the
  TO
  address
  for mail sent to the list server email address.
 
  However, spammers will send an email to a dozen of our mail addresses
  (12
  recipients) one of which is the whitelised TO address for the
  listserver.
  Because of the way Declude processes the whitelist, that means that
  the other 11 recipient receive the spam even though mail to them is
  not whitelisted.
 
  That is a bad design on Declude's part, wouldn't you agree?  Anyone
  else feel that this needs to be rectified?
 
 
 
   -Original Message-
   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
  Darrell
   ([EMAIL PROTECTED])
   Sent: Tuesday, October 17, 2006 11:25 AM
   To: declude.junkmail@declude.com
   Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
  
   If one user is whitelisted they all will be whitelisted for that
  email.
   There are some things you can do to prevent this like
   BYPASSWHITELIST
  test.
  
   Darre;;
  
   
   -
  ---
   Check out http://www.invariantsystems.com for utilities for Declude
  And
   Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI
  integration,
  MRTG
   Integration, and Log Parsers.
  
   - Original Message -
   From: Dave Beckstrom [EMAIL PROTECTED]
   To: declude.junkmail@declude.com
   Sent: Tuesday, October 17, 2006 11:18 AM
   Subject: [Declude.JunkMail] Whitelisting flaw

Re: [Declude.JunkMail] Whitelisting flaw in Declude? - David Barker

2006-10-18 Thread Darin Cox
Hi Dave,

A comment on the whitelist to required monitoring addresses... We don't
whitelist email to abuse@ or postmaster@ addresses.  Instead we have a
user-specific Declude config that allows mail through to those addresses.
So, we configure Declude to use this separate config for all postmaster and
abuse addresses for all domains.

That way we don't have a need to whitelist to these addresses, and we have
fine-grained control over what we let through to them.

Darin.


- Original Message - 
From: Dave Beckstrom [EMAIL PROTECTED]
To: declude.junkmail@declude.com
Sent: Wednesday, October 18, 2006 12:06 PM
Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude? - David Barker


David,

I agree.

But I do think the whitelisting needs to be changed.  I think you should add
a WhitelistUnique tag.

EG:

WhitelistUnique TO: [EMAIL PROTECTED]


The way the tag would function is that the email would only be treated as
whitelisted if [EMAIL PROTECTED] was the only address in the TO field and if 
the
carbon copy field is also blank.  This insures that spammers can't stack
multiple email addresses in the TO or CC fields, one address of which is
whitelisted, thus forcing the email to pass through Declude to ALL
RECIPIENTS rather than just to the whitelisted recipient.


Besides the listserver problem I described, I can see some places wanting to
whitelist email to [EMAIL PROTECTED] or [EMAIL PROTECTED]  Spammers who have
figured out this gaping hole in Declude could easily force all email to a
site to be whitelisted by simply sending email to [EMAIL PROTECTED] and tagging
a dozen other addresses onto the TO field.  Not good.

Is my suggestion something that you can implement?



 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David
 Barker
 Sent: Wednesday, October 18, 2006 8:30 AM
 To: declude.junkmail@declude.com
 Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?

 To create a duplicate message for each recipient is not a trivial issue.
 This is a function of the mail server not Declude.

 David Barker
 Director of Product Development
 Your Email security is our business
 978.499.2933 office
 978.988.1311 fax
 [EMAIL PROTECTED]


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin
 Bilbee
 Sent: Tuesday, October 17, 2006 5:08 PM
 To: declude.junkmail@declude.com
 Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?

 Delcude has always functioned like this.

 What declude could do in this case is to duplicate the message for each
 recipient and write a new header file to each recipient. Not a big issue.
 Deliver to the one that whitelists and run the spam checks for the others.



 Kevin Bilbee

  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
  Darin Cox
  Sent: Tuesday, October 17, 2006 12:37 PM
  To: declude.junkmail@declude.com
  Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
 
  It's actually more of an issue of how the mail server handles the
  message.
  In the case of multiple recipients, since there is only one message
  file addressed to multiple recipients in the headers, it's either
  deliver or not deliver unless you rewrite the headers to modify the
  recipient list.  I think I'd rather not have the spam filtering system
  alter that.  Add to the header, yes.  Alter the recipients, no.
 
  Also, I have not come across a situation where I wanted to let a
  message go through to one recipient and not to others, except in the
  situation of lists which is a whole other topic.
 
  Darin.
 
 
  - Original Message -
  From: Dave Beckstrom [EMAIL PROTECTED]
  To: declude.junkmail@declude.com
  Sent: Tuesday, October 17, 2006 3:11 PM
  Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 
  I would call that a flaw, then, in how Declude processes the whitelist.
 
  I have a listserver email address for which I do not want email spam
  checked.  This is because I don't want messages going out to the list
  that say SPAM in the subject line.  Because nobody who is not a member
  on the list can post to the list, there is no problem whitelisting the
  TO
  address
  for mail sent to the list server email address.
 
  However, spammers will send an email to a dozen of our mail addresses
  (12
  recipients) one of which is the whitelised TO address for the
  listserver.
  Because of the way Declude processes the whitelist, that means that
  the other 11 recipient receive the spam even though mail to them is
  not whitelisted.
 
  That is a bad design on Declude's part, wouldn't you agree?  Anyone
  else feel that this needs to be rectified?
 
 
 
   -Original Message-
   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
  Darrell
   ([EMAIL PROTECTED])
   Sent: Tuesday, October 17, 2006 11:25 AM
   To: declude.junkmail@declude.com
   Subject: Re: [Declude.JunkMail] Whitelisting flaw

RE: [Declude.JunkMail] Whitelisting flaw in Declude? - David Barker

2006-10-18 Thread Dave Beckstrom
Darin,

We don't whitelist those addresses at all.  But I could see other companies
wanting to do so.  

This idea that if one address is whitelisted, then they all are, is not a
good situation.  It is good in that some folks might want Declude to process
that way, in which case the current whitelist will work for them.  Its not
good from the standpoint that there is no alternative mechanism.

If Declude has access to all of the envelope information, they should easily
be able to add a new tag that only whitelists an address if it's the only
address in the envelope.


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darin
Cox
 Sent: Wednesday, October 18, 2006 11:15 AM
 To: declude.junkmail@declude.com
 Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude? - David
Barker
 
 Hi Dave,
 
 A comment on the whitelist to required monitoring addresses... We don't
 whitelist email to abuse@ or postmaster@ addresses.  Instead we have a
 user-specific Declude config that allows mail through to those addresses.
 So, we configure Declude to use this separate config for all postmaster
and
 abuse addresses for all domains.
 
 That way we don't have a need to whitelist to these addresses, and we have
 fine-grained control over what we let through to them.
 
 Darin.
 
 
 - Original Message -
 From: Dave Beckstrom [EMAIL PROTECTED]
 To: declude.junkmail@declude.com
 Sent: Wednesday, October 18, 2006 12:06 PM
 Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude? - David
Barker
 
 
 David,
 
 I agree.
 
 But I do think the whitelisting needs to be changed.  I think you should
add
 a WhitelistUnique tag.
 
 EG:
 
 WhitelistUnique TO: [EMAIL PROTECTED]
 
 
 The way the tag would function is that the email would only be treated as
 whitelisted if [EMAIL PROTECTED] was the only address in the TO field and if
the
 carbon copy field is also blank.  This insures that spammers can't stack
 multiple email addresses in the TO or CC fields, one address of which
is
 whitelisted, thus forcing the email to pass through Declude to ALL
 RECIPIENTS rather than just to the whitelisted recipient.
 
 
 Besides the listserver problem I described, I can see some places wanting
to
 whitelist email to [EMAIL PROTECTED] or [EMAIL PROTECTED]  Spammers who have
 figured out this gaping hole in Declude could easily force all email to a
 site to be whitelisted by simply sending email to [EMAIL PROTECTED] and
tagging
 a dozen other addresses onto the TO field.  Not good.
 
 Is my suggestion something that you can implement?
 
 
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
David
  Barker
  Sent: Wednesday, October 18, 2006 8:30 AM
  To: declude.junkmail@declude.com
  Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
  To create a duplicate message for each recipient is not a trivial issue.
  This is a function of the mail server not Declude.
 
  David Barker
  Director of Product Development
  Your Email security is our business
  978.499.2933 office
  978.988.1311 fax
  [EMAIL PROTECTED]
 
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Kevin
  Bilbee
  Sent: Tuesday, October 17, 2006 5:08 PM
  To: declude.junkmail@declude.com
  Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
  Delcude has always functioned like this.
 
  What declude could do in this case is to duplicate the message for each
  recipient and write a new header file to each recipient. Not a big
issue.
  Deliver to the one that whitelists and run the spam checks for the
others.
 
 
 
  Kevin Bilbee
 
   -Original Message-
   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
   Darin Cox
   Sent: Tuesday, October 17, 2006 12:37 PM
   To: declude.junkmail@declude.com
   Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
  
   It's actually more of an issue of how the mail server handles the
   message.
   In the case of multiple recipients, since there is only one message
   file addressed to multiple recipients in the headers, it's either
   deliver or not deliver unless you rewrite the headers to modify the
   recipient list.  I think I'd rather not have the spam filtering system
   alter that.  Add to the header, yes.  Alter the recipients, no.
  
   Also, I have not come across a situation where I wanted to let a
   message go through to one recipient and not to others, except in the
   situation of lists which is a whole other topic.
  
   Darin.
  
  
   - Original Message -
   From: Dave Beckstrom [EMAIL PROTECTED]
   To: declude.junkmail@declude.com
   Sent: Tuesday, October 17, 2006 3:11 PM
   Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
  
  
   I would call that a flaw, then, in how Declude processes the
whitelist.
  
   I have a listserver email address for which I do not want email spam
   checked.  This is because I don't want

Re: [Declude.JunkMail] Whitelisting flaw in Declude? - David Barker

2006-10-18 Thread Darrell \([EMAIL PROTECTED])
Dave,

By using BYPASSWHITELIST you can kinda set this functionality up.  Have you 
looked at that?

Darrell

Check out http://www.invariantsystems.com for utilities for Declude And 
Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTG 
Integration, and Log Parsers.

- Original Message - 
From: Dave Beckstrom [EMAIL PROTECTED]
To: declude.junkmail@declude.com
Sent: Wednesday, October 18, 2006 12:06 PM
Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude? - David Barker


David,

I agree.

But I do think the whitelisting needs to be changed.  I think you should add
a WhitelistUnique tag.

EG:

WhitelistUnique TO: [EMAIL PROTECTED]


The way the tag would function is that the email would only be treated as
whitelisted if [EMAIL PROTECTED] was the only address in the TO field and if 
the
carbon copy field is also blank.  This insures that spammers can't stack
multiple email addresses in the TO or CC fields, one address of which is
whitelisted, thus forcing the email to pass through Declude to ALL
RECIPIENTS rather than just to the whitelisted recipient.


Besides the listserver problem I described, I can see some places wanting to
whitelist email to [EMAIL PROTECTED] or [EMAIL PROTECTED]  Spammers who have
figured out this gaping hole in Declude could easily force all email to a
site to be whitelisted by simply sending email to [EMAIL PROTECTED] and tagging
a dozen other addresses onto the TO field.  Not good.

Is my suggestion something that you can implement?



 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David
 Barker
 Sent: Wednesday, October 18, 2006 8:30 AM
 To: declude.junkmail@declude.com
 Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?

 To create a duplicate message for each recipient is not a trivial issue.
 This is a function of the mail server not Declude.

 David Barker
 Director of Product Development
 Your Email security is our business
 978.499.2933 office
 978.988.1311 fax
 [EMAIL PROTECTED]


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin
 Bilbee
 Sent: Tuesday, October 17, 2006 5:08 PM
 To: declude.junkmail@declude.com
 Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?

 Delcude has always functioned like this.

 What declude could do in this case is to duplicate the message for each
 recipient and write a new header file to each recipient. Not a big issue.
 Deliver to the one that whitelists and run the spam checks for the others.



 Kevin Bilbee

  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
  Darin Cox
  Sent: Tuesday, October 17, 2006 12:37 PM
  To: declude.junkmail@declude.com
  Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
 
  It's actually more of an issue of how the mail server handles the
  message.
  In the case of multiple recipients, since there is only one message
  file addressed to multiple recipients in the headers, it's either
  deliver or not deliver unless you rewrite the headers to modify the
  recipient list.  I think I'd rather not have the spam filtering system
  alter that.  Add to the header, yes.  Alter the recipients, no.
 
  Also, I have not come across a situation where I wanted to let a
  message go through to one recipient and not to others, except in the
  situation of lists which is a whole other topic.
 
  Darin.
 
 
  - Original Message -
  From: Dave Beckstrom [EMAIL PROTECTED]
  To: declude.junkmail@declude.com
  Sent: Tuesday, October 17, 2006 3:11 PM
  Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 
  I would call that a flaw, then, in how Declude processes the whitelist.
 
  I have a listserver email address for which I do not want email spam
  checked.  This is because I don't want messages going out to the list
  that say SPAM in the subject line.  Because nobody who is not a member
  on the list can post to the list, there is no problem whitelisting the
  TO
  address
  for mail sent to the list server email address.
 
  However, spammers will send an email to a dozen of our mail addresses
  (12
  recipients) one of which is the whitelised TO address for the
  listserver.
  Because of the way Declude processes the whitelist, that means that
  the other 11 recipient receive the spam even though mail to them is
  not whitelisted.
 
  That is a bad design on Declude's part, wouldn't you agree?  Anyone
  else feel that this needs to be rectified?
 
 
 
   -Original Message-
   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
  Darrell
   ([EMAIL PROTECTED])
   Sent: Tuesday, October 17, 2006 11:25 AM
   To: declude.junkmail@declude.com
   Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
  
   If one user is whitelisted they all will be whitelisted for that
  email.
   There are some things you

RE: [Declude.JunkMail] Whitelisting flaw in Declude?

2006-10-18 Thread Kevin Bilbee
Other mail gateways do it. Why would it be so difficult to duplicate the 
message and the header changing the recipients in the individual header files?



Kevin Bilbee

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
 David Barker
 Sent: Wednesday, October 18, 2006 6:30 AM
 To: declude.junkmail@declude.com
 Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 To create a duplicate message for each recipient is not a trivial
 issue.
 This is a function of the mail server not Declude.
 
 David Barker
 Director of Product Development
 Your Email security is our business
 978.499.2933 office
 978.988.1311 fax
 [EMAIL PROTECTED]
 
 
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
 Kevin
 Bilbee
 Sent: Tuesday, October 17, 2006 5:08 PM
 To: declude.junkmail@declude.com
 Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 Delcude has always functioned like this.
 
 What declude could do in this case is to duplicate the message for each
 recipient and write a new header file to each recipient. Not a big
 issue.
 Deliver to the one that whitelists and run the spam checks for the
 others.
 
 
 
 Kevin Bilbee
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
  Darin Cox
  Sent: Tuesday, October 17, 2006 12:37 PM
  To: declude.junkmail@declude.com
  Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
 
  It's actually more of an issue of how the mail server handles the
  message.
  In the case of multiple recipients, since there is only one message
  file addressed to multiple recipients in the headers, it's either
  deliver or not deliver unless you rewrite the headers to modify the
  recipient list.  I think I'd rather not have the spam filtering
 system
  alter that.  Add to the header, yes.  Alter the recipients, no.
 
  Also, I have not come across a situation where I wanted to let a
  message go through to one recipient and not to others, except in the
  situation of lists which is a whole other topic.
 
  Darin.
 
 
  - Original Message -
  From: Dave Beckstrom [EMAIL PROTECTED]
  To: declude.junkmail@declude.com
  Sent: Tuesday, October 17, 2006 3:11 PM
  Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 
  I would call that a flaw, then, in how Declude processes the
 whitelist.
 
  I have a listserver email address for which I do not want email spam
  checked.  This is because I don't want messages going out to the list
  that say SPAM in the subject line.  Because nobody who is not a
 member
  on the list can post to the list, there is no problem whitelisting
 the
  TO
  address
  for mail sent to the list server email address.
 
  However, spammers will send an email to a dozen of our mail addresses
  (12
  recipients) one of which is the whitelised TO address for the
  listserver.
  Because of the way Declude processes the whitelist, that means that
  the other 11 recipient receive the spam even though mail to them is
  not whitelisted.
 
  That is a bad design on Declude's part, wouldn't you agree?  Anyone
  else feel that this needs to be rectified?
 
 
 
   -Original Message-
   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
  Darrell
   ([EMAIL PROTECTED])
   Sent: Tuesday, October 17, 2006 11:25 AM
   To: declude.junkmail@declude.com
   Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
  
   If one user is whitelisted they all will be whitelisted for that
  email.
   There are some things you can do to prevent this like
   BYPASSWHITELIST
  test.
  
   Darre;;
  
   ---
 -
   -
  ---
   Check out http://www.invariantsystems.com for utilities for Declude
  And
   Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI
  integration,
  MRTG
   Integration, and Log Parsers.
  
   - Original Message -
   From: Dave Beckstrom [EMAIL PROTECTED]
   To: declude.junkmail@declude.com
   Sent: Tuesday, October 17, 2006 11:18 AM
   Subject: [Declude.JunkMail] Whitelisting flaw in Declude?
  
  
   If an email is received that is addressed to multiple recipients,
   one
  of
   whom is whitelisted, does Declude treat the email as whitelisted
 for
  all
   recipients?
  
  
  
  
  
   ---
   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 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 came from the Declude.JunkMail mailing list.  To
  unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type
  unsubscribe

Re: [Declude.JunkMail] Whitelisting flaw in Declude?

2006-10-18 Thread Darrell \([EMAIL PROTECTED])
Mail gateways or anti-spam products for mail gateways?

Darrell

Check out http://www.invariantsystems.com for utilities for Declude And 
Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTG 
Integration, and Log Parsers.

- Original Message - 
From: Kevin Bilbee [EMAIL PROTECTED]
To: declude.junkmail@declude.com
Sent: Wednesday, October 18, 2006 1:16 PM
Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?


Other mail gateways do it. Why would it be so difficult to duplicate the 
message and the header changing the recipients in the individual header 
files?



Kevin Bilbee

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
 David Barker
 Sent: Wednesday, October 18, 2006 6:30 AM
 To: declude.junkmail@declude.com
 Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?

 To create a duplicate message for each recipient is not a trivial
 issue.
 This is a function of the mail server not Declude.

 David Barker
 Director of Product Development
 Your Email security is our business
 978.499.2933 office
 978.988.1311 fax
 [EMAIL PROTECTED]


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
 Kevin
 Bilbee
 Sent: Tuesday, October 17, 2006 5:08 PM
 To: declude.junkmail@declude.com
 Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?

 Delcude has always functioned like this.

 What declude could do in this case is to duplicate the message for each
 recipient and write a new header file to each recipient. Not a big
 issue.
 Deliver to the one that whitelists and run the spam checks for the
 others.



 Kevin Bilbee

  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
  Darin Cox
  Sent: Tuesday, October 17, 2006 12:37 PM
  To: declude.junkmail@declude.com
  Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
 
  It's actually more of an issue of how the mail server handles the
  message.
  In the case of multiple recipients, since there is only one message
  file addressed to multiple recipients in the headers, it's either
  deliver or not deliver unless you rewrite the headers to modify the
  recipient list.  I think I'd rather not have the spam filtering
 system
  alter that.  Add to the header, yes.  Alter the recipients, no.
 
  Also, I have not come across a situation where I wanted to let a
  message go through to one recipient and not to others, except in the
  situation of lists which is a whole other topic.
 
  Darin.
 
 
  - Original Message -
  From: Dave Beckstrom [EMAIL PROTECTED]
  To: declude.junkmail@declude.com
  Sent: Tuesday, October 17, 2006 3:11 PM
  Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 
  I would call that a flaw, then, in how Declude processes the
 whitelist.
 
  I have a listserver email address for which I do not want email spam
  checked.  This is because I don't want messages going out to the list
  that say SPAM in the subject line.  Because nobody who is not a
 member
  on the list can post to the list, there is no problem whitelisting
 the
  TO
  address
  for mail sent to the list server email address.
 
  However, spammers will send an email to a dozen of our mail addresses
  (12
  recipients) one of which is the whitelised TO address for the
  listserver.
  Because of the way Declude processes the whitelist, that means that
  the other 11 recipient receive the spam even though mail to them is
  not whitelisted.
 
  That is a bad design on Declude's part, wouldn't you agree?  Anyone
  else feel that this needs to be rectified?
 
 
 
   -Original Message-
   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
  Darrell
   ([EMAIL PROTECTED])
   Sent: Tuesday, October 17, 2006 11:25 AM
   To: declude.junkmail@declude.com
   Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
  
   If one user is whitelisted they all will be whitelisted for that
  email.
   There are some things you can do to prevent this like
   BYPASSWHITELIST
  test.
  
   Darre;;
  
   ---
 -
   -
  ---
   Check out http://www.invariantsystems.com for utilities for Declude
  And
   Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI
  integration,
  MRTG
   Integration, and Log Parsers.
  
   - Original Message -
   From: Dave Beckstrom [EMAIL PROTECTED]
   To: declude.junkmail@declude.com
   Sent: Tuesday, October 17, 2006 11:18 AM
   Subject: [Declude.JunkMail] Whitelisting flaw in Declude?
  
  
   If an email is received that is addressed to multiple recipients,
   one
  of
   whom is whitelisted, does Declude treat the email as whitelisted
 for
  all
   recipients?
  
  
  
  
  
   ---
   This E-mail came from the Declude.JunkMail mailing list.  To
   unsubscribe, just send an E-mail to [EMAIL PROTECTED

RE: [Declude.JunkMail] Whitelisting flaw in Declude?

2006-10-18 Thread Kevin Bilbee
Anti-spam\virus mail gateways.

I know barracuda, (now Symantec), does the splitting for whitelisting.



Kevin Bilbee

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
 Darrell ([EMAIL PROTECTED])
 Sent: Wednesday, October 18, 2006 10:48 AM
 To: declude.junkmail@declude.com
 Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 Mail gateways or anti-spam products for mail gateways?
 
 Darrell
 ---
 -
 Check out http://www.invariantsystems.com for utilities for Declude And
 Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI integration,
 MRTG
 Integration, and Log Parsers.
 
 - Original Message -
 From: Kevin Bilbee [EMAIL PROTECTED]
 To: declude.junkmail@declude.com
 Sent: Wednesday, October 18, 2006 1:16 PM
 Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 
 Other mail gateways do it. Why would it be so difficult to duplicate
 the
 message and the header changing the recipients in the individual header
 files?
 
 
 
 Kevin Bilbee
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
  David Barker
  Sent: Wednesday, October 18, 2006 6:30 AM
  To: declude.junkmail@declude.com
  Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
  To create a duplicate message for each recipient is not a trivial
  issue.
  This is a function of the mail server not Declude.
 
  David Barker
  Director of Product Development
  Your Email security is our business
  978.499.2933 office
  978.988.1311 fax
  [EMAIL PROTECTED]
 
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
  Kevin
  Bilbee
  Sent: Tuesday, October 17, 2006 5:08 PM
  To: declude.junkmail@declude.com
  Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
  Delcude has always functioned like this.
 
  What declude could do in this case is to duplicate the message for
 each
  recipient and write a new header file to each recipient. Not a big
  issue.
  Deliver to the one that whitelists and run the spam checks for the
  others.
 
 
 
  Kevin Bilbee
 
   -Original Message-
   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
   Darin Cox
   Sent: Tuesday, October 17, 2006 12:37 PM
   To: declude.junkmail@declude.com
   Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
  
   It's actually more of an issue of how the mail server handles the
   message.
   In the case of multiple recipients, since there is only one message
   file addressed to multiple recipients in the headers, it's either
   deliver or not deliver unless you rewrite the headers to modify the
   recipient list.  I think I'd rather not have the spam filtering
  system
   alter that.  Add to the header, yes.  Alter the recipients, no.
  
   Also, I have not come across a situation where I wanted to let a
   message go through to one recipient and not to others, except in
 the
   situation of lists which is a whole other topic.
  
   Darin.
  
  
   - Original Message -
   From: Dave Beckstrom [EMAIL PROTECTED]
   To: declude.junkmail@declude.com
   Sent: Tuesday, October 17, 2006 3:11 PM
   Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
  
  
   I would call that a flaw, then, in how Declude processes the
  whitelist.
  
   I have a listserver email address for which I do not want email
 spam
   checked.  This is because I don't want messages going out to the
 list
   that say SPAM in the subject line.  Because nobody who is not a
  member
   on the list can post to the list, there is no problem whitelisting
  the
   TO
   address
   for mail sent to the list server email address.
  
   However, spammers will send an email to a dozen of our mail
 addresses
   (12
   recipients) one of which is the whitelised TO address for the
   listserver.
   Because of the way Declude processes the whitelist, that means that
   the other 11 recipient receive the spam even though mail to them is
   not whitelisted.
  
   That is a bad design on Declude's part, wouldn't you agree?  Anyone
   else feel that this needs to be rectified?
  
  
  
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
 Of
   Darrell
([EMAIL PROTECTED])
Sent: Tuesday, October 17, 2006 11:25 AM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
   
If one user is whitelisted they all will be whitelisted for that
   email.
There are some things you can do to prevent this like
BYPASSWHITELIST
   test.
   
Darre;;
   
-
 --
  -
-
   ---
Check out http://www.invariantsystems.com for utilities for
 Declude
   And
Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI
   integration,
   MRTG
Integration, and Log Parsers

RE: [Declude.JunkMail] Whitelisting flaw in Declude?

2006-10-18 Thread Jay Sudowski - Handy Networks LLC
Also, realize that on servers processing a large volume of messages per
day, the additional IO necessary to create duplicate messages and header
files for each specific recipient would be a death sentence...


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
David Barker
Sent: Wednesday, October 18, 2006 9:30 AM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?

To create a duplicate message for each recipient is not a trivial issue.
This is a function of the mail server not Declude.

David Barker
Director of Product Development
Your Email security is our business
978.499.2933 office
978.988.1311 fax
[EMAIL PROTECTED]
 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Kevin
Bilbee
Sent: Tuesday, October 17, 2006 5:08 PM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?

Delcude has always functioned like this.

What declude could do in this case is to duplicate the message for each
recipient and write a new header file to each recipient. Not a big
issue.
Deliver to the one that whitelists and run the spam checks for the
others.



Kevin Bilbee

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of 
 Darin Cox
 Sent: Tuesday, October 17, 2006 12:37 PM
 To: declude.junkmail@declude.com
 Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 It's actually more of an issue of how the mail server handles the 
 message.
 In the case of multiple recipients, since there is only one message 
 file addressed to multiple recipients in the headers, it's either 
 deliver or not deliver unless you rewrite the headers to modify the 
 recipient list.  I think I'd rather not have the spam filtering system

 alter that.  Add to the header, yes.  Alter the recipients, no.
 
 Also, I have not come across a situation where I wanted to let a 
 message go through to one recipient and not to others, except in the 
 situation of lists which is a whole other topic.
 
 Darin.
 
 
 - Original Message -
 From: Dave Beckstrom [EMAIL PROTECTED]
 To: declude.junkmail@declude.com
 Sent: Tuesday, October 17, 2006 3:11 PM
 Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 
 I would call that a flaw, then, in how Declude processes the
whitelist.
 
 I have a listserver email address for which I do not want email spam 
 checked.  This is because I don't want messages going out to the list 
 that say SPAM in the subject line.  Because nobody who is not a member

 on the list can post to the list, there is no problem whitelisting the

 TO
 address
 for mail sent to the list server email address.
 
 However, spammers will send an email to a dozen of our mail addresses
 (12
 recipients) one of which is the whitelised TO address for the 
 listserver.
 Because of the way Declude processes the whitelist, that means that 
 the other 11 recipient receive the spam even though mail to them is 
 not whitelisted.
 
 That is a bad design on Declude's part, wouldn't you agree?  Anyone 
 else feel that this needs to be rectified?
 
 
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
 Darrell
  ([EMAIL PROTECTED])
  Sent: Tuesday, October 17, 2006 11:25 AM
  To: declude.junkmail@declude.com
  Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
 
  If one user is whitelisted they all will be whitelisted for that
 email.
  There are some things you can do to prevent this like 
  BYPASSWHITELIST
 test.
 
  Darre;;
 
  
  -
 ---
  Check out http://www.invariantsystems.com for utilities for Declude
 And
  Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI
 integration,
 MRTG
  Integration, and Log Parsers.
 
  - Original Message -
  From: Dave Beckstrom [EMAIL PROTECTED]
  To: declude.junkmail@declude.com
  Sent: Tuesday, October 17, 2006 11:18 AM
  Subject: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 
  If an email is received that is addressed to multiple recipients, 
  one
 of
  whom is whitelisted, does Declude treat the email as whitelisted for
 all
  recipients?
 
 
 
 
 
  ---
  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 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 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

Re: [Declude.JunkMail] Whitelisting flaw in Declude? - David Barker

2006-10-18 Thread Darin Cox
What I was trying to do was outline a solution that didn't include
whitelisting.  I'm against whitelisting due to it's inability to
differentiate between levels of grey in the spam-fighting process.  Instead,
pure weighting systems can assign negative weights as needed, but still
block _really_ bad mail, but I probably deviated from the main point too
much.

Back to the argument and playing devil's advocate on myself, rewriting of
the Q*.SMD file is something we do to assist in adjusting weights in the
spam filtering process, or reporting FPs or missed spam to sniffer.   We
have fairly simple VBS scripts that do it for us, so something like that
could adopted for use in exploding the Q file and create the appropriate
message copies to each recipient.  I do agree with David B. that it is
better handled by the mail server, though.

Darin.


- Original Message - 
From: Dave Beckstrom [EMAIL PROTECTED]
To: declude.junkmail@declude.com
Sent: Wednesday, October 18, 2006 12:27 PM
Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude? - David Barker


Darin,

We don't whitelist those addresses at all.  But I could see other companies
wanting to do so.

This idea that if one address is whitelisted, then they all are, is not a
good situation.  It is good in that some folks might want Declude to process
that way, in which case the current whitelist will work for them.  Its not
good from the standpoint that there is no alternative mechanism.

If Declude has access to all of the envelope information, they should easily
be able to add a new tag that only whitelists an address if it's the only
address in the envelope.


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darin
Cox
 Sent: Wednesday, October 18, 2006 11:15 AM
 To: declude.junkmail@declude.com
 Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude? - David
Barker

 Hi Dave,

 A comment on the whitelist to required monitoring addresses... We don't
 whitelist email to abuse@ or postmaster@ addresses.  Instead we have a
 user-specific Declude config that allows mail through to those addresses.
 So, we configure Declude to use this separate config for all postmaster
and
 abuse addresses for all domains.

 That way we don't have a need to whitelist to these addresses, and we have
 fine-grained control over what we let through to them.

 Darin.


 - Original Message -
 From: Dave Beckstrom [EMAIL PROTECTED]
 To: declude.junkmail@declude.com
 Sent: Wednesday, October 18, 2006 12:06 PM
 Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude? - David
Barker


 David,

 I agree.

 But I do think the whitelisting needs to be changed.  I think you should
add
 a WhitelistUnique tag.

 EG:

 WhitelistUnique TO: [EMAIL PROTECTED]


 The way the tag would function is that the email would only be treated as
 whitelisted if [EMAIL PROTECTED] was the only address in the TO field and if
the
 carbon copy field is also blank.  This insures that spammers can't stack
 multiple email addresses in the TO or CC fields, one address of which
is
 whitelisted, thus forcing the email to pass through Declude to ALL
 RECIPIENTS rather than just to the whitelisted recipient.


 Besides the listserver problem I described, I can see some places wanting
to
 whitelist email to [EMAIL PROTECTED] or [EMAIL PROTECTED]  Spammers who have
 figured out this gaping hole in Declude could easily force all email to a
 site to be whitelisted by simply sending email to [EMAIL PROTECTED] and
tagging
 a dozen other addresses onto the TO field.  Not good.

 Is my suggestion something that you can implement?



  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
David
  Barker
  Sent: Wednesday, October 18, 2006 8:30 AM
  To: declude.junkmail@declude.com
  Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
  To create a duplicate message for each recipient is not a trivial issue.
  This is a function of the mail server not Declude.
 
  David Barker
  Director of Product Development
  Your Email security is our business
  978.499.2933 office
  978.988.1311 fax
  [EMAIL PROTECTED]
 
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Kevin
  Bilbee
  Sent: Tuesday, October 17, 2006 5:08 PM
  To: declude.junkmail@declude.com
  Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
  Delcude has always functioned like this.
 
  What declude could do in this case is to duplicate the message for each
  recipient and write a new header file to each recipient. Not a big
issue.
  Deliver to the one that whitelists and run the spam checks for the
others.
 
 
 
  Kevin Bilbee
 
   -Original Message-
   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
   Darin Cox
   Sent: Tuesday, October 17, 2006 12:37 PM
   To: declude.junkmail@declude.com
   Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
  
   It's

Re: [Declude.JunkMail] Whitelisting flaw in Declude?

2006-10-18 Thread Matt




FYI, Alligate also does splitting.

Matt



Kevin Bilbee wrote:

  Anti-spam\virus mail gateways.

I know barracuda, (now Symantec), does the splitting for whitelisting.



Kevin Bilbee

  
  
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
Darrell ([EMAIL PROTECTED])
Sent: Wednesday, October 18, 2006 10:48 AM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?

Mail gateways or anti-spam products for mail gateways?

Darrell
---
-
Check out http://www.invariantsystems.com for utilities for Declude And
Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI integration,
MRTG
Integration, and Log Parsers.

- Original Message -
From: "Kevin Bilbee" [EMAIL PROTECTED]
To: declude.junkmail@declude.com
Sent: Wednesday, October 18, 2006 1:16 PM
Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?


Other mail gateways do it. Why would it be so difficult to duplicate
the
message and the header changing the recipients in the individual header
files?



Kevin Bilbee



  -Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
David Barker
Sent: Wednesday, October 18, 2006 6:30 AM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?

To create a duplicate message for each recipient is not a trivial
issue.
This is a function of the mail server not Declude.

David Barker
Director of Product Development
Your Email security is our business
978.499.2933 office
978.988.1311 fax
[EMAIL PROTECTED]


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
Kevin
Bilbee
Sent: Tuesday, October 17, 2006 5:08 PM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?

Delcude has always functioned like this.

What declude could do in this case is to duplicate the message for
  

each


  recipient and write a new header file to each recipient. Not a big
issue.
Deliver to the one that whitelists and run the spam checks for the
others.



Kevin Bilbee

  
  
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
Darin Cox
Sent: Tuesday, October 17, 2006 12:37 PM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?

It's actually more of an issue of how the mail server handles the
message.
In the case of multiple recipients, since there is only one message
file addressed to multiple recipients in the headers, it's either
deliver or not deliver unless you rewrite the headers to modify the
recipient list.  I think I'd rather not have the spam filtering

  
  system
  
  
alter that.  Add to the header, yes.  Alter the recipients, no.

Also, I have not come across a situation where I wanted to let a
message go through to one recipient and not to others, except in

  

the


  
situation of lists which is a whole other topic.

Darin.


- Original Message -
From: "Dave Beckstrom" [EMAIL PROTECTED]
To: declude.junkmail@declude.com
Sent: Tuesday, October 17, 2006 3:11 PM
Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?


I would call that a flaw, then, in how Declude processes the

  
  whitelist.
  
  
I have a listserver email address for which I do not want email

  

spam


  
checked.  This is because I don't want messages going out to the

  

list


  
that say SPAM in the subject line.  Because nobody who is not a

  
  member
  
  
on the list can post to the list, there is no problem whitelisting

  
  the
  
  
"TO"
address
for mail sent to the list server email address.

However, spammers will send an email to a dozen of our mail

  

addresses


  
(12
recipients) one of which is the whitelised "TO" address for the
listserver.
Because of the way Declude processes the whitelist, that means that
the other 11 recipient receive the spam even though mail to them is
not whitelisted.

That is a bad design on Declude's part, wouldn't you agree?  Anyone
else feel that this needs to be rectified?





  -Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf
  

  

Of


  
Darrell


  ([EMAIL PROTECTED])
Sent: Tuesday, October 17, 2006 11:25 AM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?

If one user is whitelisted they all will be whitelisted fo

Re: [Declude.JunkMail] Whitelisting flaw in Declude?

2006-10-18 Thread Matt




I have some stats here that suggest otherwise. We only have 5% more
recipients than messages that make it through our gateway, and we only
return permanent errors presently for mail bombing related activities.
This however is a dedicated gateway and not a hosted mail server, so
stats from a hosted mail server would see a slightly higher rate since
most multiple-recipient E-mails are internal to a server. If you are
splitting on a gateway and not splitting internal E-mail, you should
see no increase beyond my numbers.

It's a doable solution if one has the need.

Matt


Jay Sudowski - Handy Networks LLC wrote:

  Also, realize that on servers processing a large volume of messages per
day, the additional IO necessary to create duplicate messages and header
files for each specific recipient would be a death sentence...


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
David Barker
Sent: Wednesday, October 18, 2006 9:30 AM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?

To create a duplicate message for each recipient is not a trivial issue.
This is a function of the mail server not Declude.

David Barker
Director of Product Development
Your Email security is our business
978.499.2933 office
978.988.1311 fax
[EMAIL PROTECTED]
 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
Kevin
Bilbee
Sent: Tuesday, October 17, 2006 5:08 PM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?

Delcude has always functioned like this.

What declude could do in this case is to duplicate the message for each
recipient and write a new header file to each recipient. Not a big
issue.
Deliver to the one that whitelists and run the spam checks for the
others.



Kevin Bilbee

  
  
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of 
Darin Cox
Sent: Tuesday, October 17, 2006 12:37 PM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?

It's actually more of an issue of how the mail server handles the 
message.
In the case of multiple recipients, since there is only one message 
file addressed to multiple recipients in the headers, it's either 
deliver or not deliver unless you rewrite the headers to modify the 
recipient list.  I think I'd rather not have the spam filtering system

  
  
  
  
alter that.  Add to the header, yes.  Alter the recipients, no.

Also, I have not come across a situation where I wanted to let a 
message go through to one recipient and not to others, except in the 
situation of lists which is a whole other topic.

Darin.


- Original Message -
From: "Dave Beckstrom" [EMAIL PROTECTED]
To: declude.junkmail@declude.com
Sent: Tuesday, October 17, 2006 3:11 PM
Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?


I would call that a flaw, then, in how Declude processes the

  
  whitelist.
  
  
I have a listserver email address for which I do not want email spam 
checked.  This is because I don't want messages going out to the list 
that say SPAM in the subject line.  Because nobody who is not a member

  
  
  
  
on the list can post to the list, there is no problem whitelisting the

  
  
  
  
"TO"
address
for mail sent to the list server email address.

However, spammers will send an email to a dozen of our mail addresses
(12
recipients) one of which is the whitelised "TO" address for the 
listserver.
Because of the way Declude processes the whitelist, that means that 
the other 11 recipient receive the spam even though mail to them is 
not whitelisted.

That is a bad design on Declude's part, wouldn't you agree?  Anyone 
else feel that this needs to be rectified?





  -Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
  

Darrell


  ([EMAIL PROTECTED])
Sent: Tuesday, October 17, 2006 11:25 AM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?

If one user is whitelisted they all will be whitelisted for that
  

email.


  There are some things you can do to prevent this like 
BYPASSWHITELIST
  

test.


  Darre;;


-
  

---


  Check out http://www.invariantsystems.com for utilities for Declude
  

And


  Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI
  

integration,
MRTG


  Integration, and Log Parsers.

- Original Message -
From: "Dave Beckstrom" [EMAIL PROTECTED]
To: declude.junkmail@declude.com
Sent: Tuesday, October 17, 2006 11:18 AM
Subject: [Declude.JunkMail] Whitelisting flaw in Declude?


If an email is received 

[Declude.JunkMail] Whitelisting flaw in Declude?

2006-10-17 Thread Dave Beckstrom
If an email is received that is addressed to multiple recipients, one of
whom is whitelisted, does Declude treat the email as whitelisted for all
recipients?





---
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.



Re: [Declude.JunkMail] Whitelisting flaw in Declude?

2006-10-17 Thread Darrell \([EMAIL PROTECTED])
If one user is whitelisted they all will be whitelisted for that email. 
There are some things you can do to prevent this like BYPASSWHITELIST test.

Darre;;


Check out http://www.invariantsystems.com for utilities for Declude And 
Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTG 
Integration, and Log Parsers.

- Original Message - 
From: Dave Beckstrom [EMAIL PROTECTED]
To: declude.junkmail@declude.com
Sent: Tuesday, October 17, 2006 11:18 AM
Subject: [Declude.JunkMail] Whitelisting flaw in Declude?


If an email is received that is addressed to multiple recipients, one of
whom is whitelisted, does Declude treat the email as whitelisted for all
recipients?





---
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 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.



RE: [Declude.JunkMail] Whitelisting flaw in Declude?

2006-10-17 Thread Dave Beckstrom
I would call that a flaw, then, in how Declude processes the whitelist.

I have a listserver email address for which I do not want email spam
checked.  This is because I don't want messages going out to the list that
say SPAM in the subject line.  Because nobody who is not a member on the
list can post to the list, there is no problem whitelisting the TO address
for mail sent to the list server email address.

However, spammers will send an email to a dozen of our mail addresses (12
recipients) one of which is the whitelised TO address for the listserver.
Because of the way Declude processes the whitelist, that means that the
other 11 recipient receive the spam even though mail to them is not
whitelisted.

That is a bad design on Declude's part, wouldn't you agree?  Anyone else
feel that this needs to be rectified?



 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Darrell
 ([EMAIL PROTECTED])
 Sent: Tuesday, October 17, 2006 11:25 AM
 To: declude.junkmail@declude.com
 Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 If one user is whitelisted they all will be whitelisted for that email.
 There are some things you can do to prevent this like BYPASSWHITELIST
test.
 
 Darre;;
 
 
 Check out http://www.invariantsystems.com for utilities for Declude And
 Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI integration,
MRTG
 Integration, and Log Parsers.
 
 - Original Message -
 From: Dave Beckstrom [EMAIL PROTECTED]
 To: declude.junkmail@declude.com
 Sent: Tuesday, October 17, 2006 11:18 AM
 Subject: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 
 If an email is received that is addressed to multiple recipients, one of
 whom is whitelisted, does Declude treat the email as whitelisted for all
 recipients?
 
 
 
 
 
 ---
 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 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 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.



Re: [Declude.JunkMail] Whitelisting flaw in Declude?

2006-10-17 Thread Darin Cox
It's actually more of an issue of how the mail server handles the message.
In the case of multiple recipients, since there is only one message file
addressed to multiple recipients in the headers, it's either deliver or not
deliver unless you rewrite the headers to modify the recipient list.  I
think I'd rather not have the spam filtering system alter that.  Add to the
header, yes.  Alter the recipients, no.

Also, I have not come across a situation where I wanted to let a message go
through to one recipient and not to others, except in the situation of lists
which is a whole other topic.

Darin.


- Original Message - 
From: Dave Beckstrom [EMAIL PROTECTED]
To: declude.junkmail@declude.com
Sent: Tuesday, October 17, 2006 3:11 PM
Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?


I would call that a flaw, then, in how Declude processes the whitelist.

I have a listserver email address for which I do not want email spam
checked.  This is because I don't want messages going out to the list that
say SPAM in the subject line.  Because nobody who is not a member on the
list can post to the list, there is no problem whitelisting the TO address
for mail sent to the list server email address.

However, spammers will send an email to a dozen of our mail addresses (12
recipients) one of which is the whitelised TO address for the listserver.
Because of the way Declude processes the whitelist, that means that the
other 11 recipient receive the spam even though mail to them is not
whitelisted.

That is a bad design on Declude's part, wouldn't you agree?  Anyone else
feel that this needs to be rectified?



 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Darrell
 ([EMAIL PROTECTED])
 Sent: Tuesday, October 17, 2006 11:25 AM
 To: declude.junkmail@declude.com
 Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?

 If one user is whitelisted they all will be whitelisted for that email.
 There are some things you can do to prevent this like BYPASSWHITELIST
test.

 Darre;;

 
 Check out http://www.invariantsystems.com for utilities for Declude And
 Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI integration,
MRTG
 Integration, and Log Parsers.

 - Original Message -
 From: Dave Beckstrom [EMAIL PROTECTED]
 To: declude.junkmail@declude.com
 Sent: Tuesday, October 17, 2006 11:18 AM
 Subject: [Declude.JunkMail] Whitelisting flaw in Declude?


 If an email is received that is addressed to multiple recipients, one of
 whom is whitelisted, does Declude treat the email as whitelisted for all
 recipients?





 ---
 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 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 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 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.



RE: [Declude.JunkMail] Whitelisting flaw in Declude?

2006-10-17 Thread Kevin Bilbee
Delcude has always functioned like this.

What declude could do in this case is to duplicate the message for each 
recipient and write a new header file to each recipient. Not a big issue. 
Deliver to the one that whitelists and run the spam checks for the others.



Kevin Bilbee

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
 Darin Cox
 Sent: Tuesday, October 17, 2006 12:37 PM
 To: declude.junkmail@declude.com
 Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 It's actually more of an issue of how the mail server handles the
 message.
 In the case of multiple recipients, since there is only one message
 file
 addressed to multiple recipients in the headers, it's either deliver or
 not
 deliver unless you rewrite the headers to modify the recipient list.  I
 think I'd rather not have the spam filtering system alter that.  Add to
 the
 header, yes.  Alter the recipients, no.
 
 Also, I have not come across a situation where I wanted to let a
 message go
 through to one recipient and not to others, except in the situation of
 lists
 which is a whole other topic.
 
 Darin.
 
 
 - Original Message -
 From: Dave Beckstrom [EMAIL PROTECTED]
 To: declude.junkmail@declude.com
 Sent: Tuesday, October 17, 2006 3:11 PM
 Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 
 I would call that a flaw, then, in how Declude processes the whitelist.
 
 I have a listserver email address for which I do not want email spam
 checked.  This is because I don't want messages going out to the list
 that
 say SPAM in the subject line.  Because nobody who is not a member on
 the
 list can post to the list, there is no problem whitelisting the TO
 address
 for mail sent to the list server email address.
 
 However, spammers will send an email to a dozen of our mail addresses
 (12
 recipients) one of which is the whitelised TO address for the
 listserver.
 Because of the way Declude processes the whitelist, that means that the
 other 11 recipient receive the spam even though mail to them is not
 whitelisted.
 
 That is a bad design on Declude's part, wouldn't you agree?  Anyone
 else
 feel that this needs to be rectified?
 
 
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
 Darrell
  ([EMAIL PROTECTED])
  Sent: Tuesday, October 17, 2006 11:25 AM
  To: declude.junkmail@declude.com
  Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
 
  If one user is whitelisted they all will be whitelisted for that
 email.
  There are some things you can do to prevent this like BYPASSWHITELIST
 test.
 
  Darre;;
 
  -
 ---
  Check out http://www.invariantsystems.com for utilities for Declude
 And
  Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI
 integration,
 MRTG
  Integration, and Log Parsers.
 
  - Original Message -
  From: Dave Beckstrom [EMAIL PROTECTED]
  To: declude.junkmail@declude.com
  Sent: Tuesday, October 17, 2006 11:18 AM
  Subject: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 
  If an email is received that is addressed to multiple recipients, one
 of
  whom is whitelisted, does Declude treat the email as whitelisted for
 all
  recipients?
 
 
 
 
 
  ---
  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 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 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 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 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.



RE: [Declude.JunkMail] Whitelisting flaw in Declude?

2006-10-17 Thread Dave Beckstrom
Hi Darin,

Thanks for the great explanation.   You always offer good feedback.   Thanks
to everyone else who replied, too.

Which is the lesser of two evils  --  Whitelist email to all recipients even
though only one recipient is in the whitelist; or ignore the whitelist
request entirely if the email has multiple recipients and only one of whom
is in the whitelist?



 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darin
Cox
 Sent: Tuesday, October 17, 2006 2:37 PM
 To: declude.junkmail@declude.com
 Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 It's actually more of an issue of how the mail server handles the message.
 In the case of multiple recipients, since there is only one message file
 addressed to multiple recipients in the headers, it's either deliver or
not
 deliver unless you rewrite the headers to modify the recipient list.  I
 think I'd rather not have the spam filtering system alter that.  Add to
the
 header, yes.  Alter the recipients, no.
 
 Also, I have not come across a situation where I wanted to let a message
go
 through to one recipient and not to others, except in the situation of
lists
 which is a whole other topic.
 
 Darin.
 
 
 - Original Message -
 From: Dave Beckstrom [EMAIL PROTECTED]
 To: declude.junkmail@declude.com
 Sent: Tuesday, October 17, 2006 3:11 PM
 Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 
 I would call that a flaw, then, in how Declude processes the whitelist.
 
 I have a listserver email address for which I do not want email spam
 checked.  This is because I don't want messages going out to the list that
 say SPAM in the subject line.  Because nobody who is not a member on the
 list can post to the list, there is no problem whitelisting the TO
address
 for mail sent to the list server email address.
 
 However, spammers will send an email to a dozen of our mail addresses (12
 recipients) one of which is the whitelised TO address for the
listserver.
 Because of the way Declude processes the whitelist, that means that the
 other 11 recipient receive the spam even though mail to them is not
 whitelisted.
 
 That is a bad design on Declude's part, wouldn't you agree?  Anyone else
 feel that this needs to be rectified?
 
 
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
 Darrell
  ([EMAIL PROTECTED])
  Sent: Tuesday, October 17, 2006 11:25 AM
  To: declude.junkmail@declude.com
  Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
 
  If one user is whitelisted they all will be whitelisted for that email.
  There are some things you can do to prevent this like BYPASSWHITELIST
 test.
 
  Darre;;
 
  
  Check out http://www.invariantsystems.com for utilities for Declude And
  Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI integration,
 MRTG
  Integration, and Log Parsers.
 
  - Original Message -
  From: Dave Beckstrom [EMAIL PROTECTED]
  To: declude.junkmail@declude.com
  Sent: Tuesday, October 17, 2006 11:18 AM
  Subject: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 
  If an email is received that is addressed to multiple recipients, one of
  whom is whitelisted, does Declude treat the email as whitelisted for all
  recipients?
 
 
 
 
 
  ---
  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 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 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 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 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.



Re: [Declude.JunkMail] Whitelisting flaw in Declude?

2006-10-17 Thread Darin Cox
Hi Dave,

We've always let the message get delivered to everyone. So far no
complaints.

The only real problem we've had with whitelisting is with auto whitelisting
from webmail contact lists.  While this is a useful feature, it does result
in spam getting through that forges the users address.  It would be
preferable if some tests could be exempted from whitelisting, or even
better, instead of whitelisting applying a negative weight to messages from
the webmail contact list.  That way SPF FAIL could still filter out forging
spam, while contact list whitelisting/negative weighting could allow
everything else through.

Darin.


- Original Message - 
From: Dave Beckstrom [EMAIL PROTECTED]
To: declude.junkmail@declude.com
Sent: Tuesday, October 17, 2006 8:13 PM
Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?


Hi Darin,

Thanks for the great explanation.   You always offer good feedback.   Thanks
to everyone else who replied, too.

Which is the lesser of two evils  --  Whitelist email to all recipients even
though only one recipient is in the whitelist; or ignore the whitelist
request entirely if the email has multiple recipients and only one of whom
is in the whitelist?



 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darin
Cox
 Sent: Tuesday, October 17, 2006 2:37 PM
 To: declude.junkmail@declude.com
 Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?

 It's actually more of an issue of how the mail server handles the message.
 In the case of multiple recipients, since there is only one message file
 addressed to multiple recipients in the headers, it's either deliver or
not
 deliver unless you rewrite the headers to modify the recipient list.  I
 think I'd rather not have the spam filtering system alter that.  Add to
the
 header, yes.  Alter the recipients, no.

 Also, I have not come across a situation where I wanted to let a message
go
 through to one recipient and not to others, except in the situation of
lists
 which is a whole other topic.

 Darin.


 - Original Message -
 From: Dave Beckstrom [EMAIL PROTECTED]
 To: declude.junkmail@declude.com
 Sent: Tuesday, October 17, 2006 3:11 PM
 Subject: RE: [Declude.JunkMail] Whitelisting flaw in Declude?


 I would call that a flaw, then, in how Declude processes the whitelist.

 I have a listserver email address for which I do not want email spam
 checked.  This is because I don't want messages going out to the list that
 say SPAM in the subject line.  Because nobody who is not a member on the
 list can post to the list, there is no problem whitelisting the TO
address
 for mail sent to the list server email address.

 However, spammers will send an email to a dozen of our mail addresses (12
 recipients) one of which is the whitelised TO address for the
listserver.
 Because of the way Declude processes the whitelist, that means that the
 other 11 recipient receive the spam even though mail to them is not
 whitelisted.

 That is a bad design on Declude's part, wouldn't you agree?  Anyone else
 feel that this needs to be rectified?



  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
 Darrell
  ([EMAIL PROTECTED])
  Sent: Tuesday, October 17, 2006 11:25 AM
  To: declude.junkmail@declude.com
  Subject: Re: [Declude.JunkMail] Whitelisting flaw in Declude?
 
  If one user is whitelisted they all will be whitelisted for that email.
  There are some things you can do to prevent this like BYPASSWHITELIST
 test.
 
  Darre;;
 
  
  Check out http://www.invariantsystems.com for utilities for Declude And
  Imail.  IMail/Declude Overflow Queue Monitoring, SURBL/URI integration,
 MRTG
  Integration, and Log Parsers.
 
  - Original Message -
  From: Dave Beckstrom [EMAIL PROTECTED]
  To: declude.junkmail@declude.com
  Sent: Tuesday, October 17, 2006 11:18 AM
  Subject: [Declude.JunkMail] Whitelisting flaw in Declude?
 
 
  If an email is received that is addressed to multiple recipients, one of
  whom is whitelisted, does Declude treat the email as whitelisted for all
  recipients?
 
 
 
 
 
  ---
  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 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 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 came from the Declude.JunkMail mailing list.  To
 unsubscribe, just

[Declude.JunkMail] Whitelisting not working for all items

2006-02-06 Thread Troy D. Hilton
Title: Whitelisting not working for all items






Hello All,

Ive got a WHITELIST FROM RULE setup for emails from a domain, @regsoft.com to my clients email. As of Saturday it stopped whitelisting emails from regsoft.com to my client. The only thing it shows in the headers is that its failing the Weight10 and SPAMCOP tests. When I check SPAMCOP for the domain I dont see it listed. Whitelisting seems to be working for other domains and emails but not this one.

What would cause this to just start happening? I thought that whitelisting and email address or domain would supersede any spam tests?

Troy D. Hilton

Serveon, Inc.

[EMAIL PROTECTED]

302-529-8640






RE: [Declude.JunkMail] Whitelisting not working for all items

2006-02-06 Thread Samuel J Stanaitis
Title: Whitelisting not working for all items








Ive had the whitelist miss
addresses quite a bit Seems to work better for just @domain.com
and not the whole address in my situation





Cheers,

Sam



Samuel J Stanaitis, Network Administrator

Decorative Product Source, Inc.

(877)-650-8054 x160

[EMAIL PROTECTED]













From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Troy D. Hilton
Sent: Monday, February 06, 2006
12:28 PM
To: Declude.JunkMail@declude.com
Subject: [Declude.JunkMail]
Whitelisting not working for all items





Hello
All,

Ive
got a WHITELIST FROM RULE setup for
emails
from a domain, @regsoft.com
to my clients email. As of Saturday it stopped whitelisting emails from
regsoft.com
to my
client. The only thing it shows in the headers is that its failing the
Weight10 and SPAMCOP tests. When I check SPAMCOP for the domain I dont
see it listed. Whitelisting seems to be working for other domains and emails
but not this one.

What
would cause this to just start happening? I thought that whitelisting and email
address or domain would supersede any spam tests?

Troy D. Hilton

Serveon, Inc.

[EMAIL PROTECTED]

302-529-8640








RE: [Declude.JunkMail] Whitelisting email address

2006-01-18 Thread Jeff Cochran



Casselberry? Hello from Naples. 
:)

Same issue, I'm the email admin for the City of 
Naples. We used to tweak filters continuously because of this. 
Routinely get questioned about why a message didn't get through and why so much 
spam gets through. We've gone to a defense in depth on this. Signed 
up with Postini for first level SPAM/Virus, and it gave us two benefits. 
The first is it dropped the load on our server by 85% or so eliminating 99% of 
the blatant spam and most viruses. It also gives the user an opportunity 
to view and manage their own quarrantined files. We use Declude to further 
tweak the incoming mail, and add a second virus scanning point. We 
primarily do two things, one is add a subject indicating possible spam, the 
other is using black lists for specific addresses. The spam header can be 
sorted in Outlook on the client side to further separate the spam but still 
allow the user to review the messages if they wish.

Of course the last thing we did was assign the City 
Manager's admin the task of reviewing his mail, plus my boss, the Director of 
Technology Services, checks his quarrantine every morning. 
:)

Have we bounced a citizen's mail? Occasionally. 
We apologize and white list their address. Somehow they seem to understand 
if the [EMAIL PROTECTED] spam filters ate their email.

If you want to reach me off-list, work email is "jcochran 
at naplesgov dot com".

Jeff


From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of IS - Systems 
Eng. (Karl Drugge)Sent: Tuesday, January 17, 2006 5:18 
PMTo: Declude.JunkMail@declude.comSubject: RE: 
[Declude.JunkMail] Whitelisting email address



Believe me, Id love to 
find a way to do it, but when I HAVE to receive emails from hideously 
mis-configured servers, whack-job citizens, and other municipalities with less 
then stellar I.T. staff from any where at any time, not bouncing becomes the 
worse of two evils. 

As an example, if I 
DELETE an email from a citizen because it meets my delete criteria ( lets say a 
nut-job, retired, self declared IT samurai with a shareware SMTP server, on a 
dial up account to a local home based ISP run by his best friend ) I can ( and 
have ) been questioned by the City Manager on exactly WHY he didnt get this 
email, because this nut-job shows up to a city council meeting and has a foaming 
at the mouth fit in public. Technical explanations dont cut it in the political 
arena. I have to, at the very least, send something back to notify the 
originator that the email was bounced, unless its so horribly mal-formed, or 
chock full of key words, that it I can absolutely guarantee its spam. 


But, if someone wants 
to take a crack at it, Ill be more than happy to post my config 
files.



Karl Drugge






-Original 
Message-From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
On Behalf Of MattSent: Tuesday, January 17, 2006 4:28 
PMTo: 
Declude.JunkMail@declude.comSubject: Re: [Declude.JunkMail] 
Whitelisting email address


Karl,Getting 
blacklisted for bouncing spam back to forged addresses would probably be a lot 
worse than missing a stray message that shouldn't have been blocked. This 
certainly can happen, especially if you get a lot of zombie generated 
spam.It is also of course a big pain dealing with servers that bounce 
this stuff back to forged addresses. Today I'm under heavy attack from 
multiple sources of backscatter. Backscatter costs others time, money and 
frustration. It's not fair if it is avoidable. Please reconsider 
your choices. Maybe we can help you figure out a better way to deal with 
this.MattIS - Systems Eng. (Karl Drugge) wrote: 


I hold at 
20, bounce at 40, and delete at 60.


I realize 
bouncing is bad, but were government, so I have to be careful about outright 
deleting email without notifying someone, somewhere.

Karl 
Drugge






-Original 
Message-From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED]] 
On Behalf Of BrianSent: Tuesday, January 17, 2006 3:38 
PMTo: Declude.JunkMail@declude.comSubject: Re: [Declude.JunkMail] 
Whitelisting email address



What are you using for 
a hold weight and delete weight?



Brian



- Original Message 
- 

From: IS - 
Systems Eng. (Karl Drugge) 

To: Declude.JunkMail@declude.com 


Sent: Tuesday, 
January 17, 2006 3:17 PM

Subject: RE: 
[Declude.JunkMail] Whitelisting email address



I can 
confirm that.

If a 
single email address is white listed, then all of them get white 
listed.

The 
solution was a line like this : BYPASSWHITELIST 
bypasswhitelist 45 
6 
0 0

If an 
email was over weight 45, AND it also had 6 or more recipients, than it bypassed 
the white-listing and checked it normally.

I never 
tried to do it with individual config files.. But that might work, if it didn't 
affect all the recipients.



Karl 
Drugge






-Original 
Message-From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED]] 
On Behalf Of BrianSent: Tuesday, January 17, 2006 2:16 
PMTo: Declud

[Declude.JunkMail] Whitelisting email address

2006-01-17 Thread Brian
I have a customer who wants to receive all emails without having declude 
check them for spam.

My question, is can this be done?

And then can it be done so that if a message comes in and it is a message 
that contains their email address and several other email address on our 
domain, that it can only be sent to their address prior to the spam checks?

I hope this makes sense.

Thanks in advance,

Brian T.


---
[This E-mail was scanned for viruses by Declude EVA 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.


Re: [Declude.JunkMail] Whitelisting email address

2006-01-17 Thread Dean Lawrence
Hi Brian,

Yes, this can be done with the Pro version. You can have per-user configurations. You can't not have Declude scan the mail, but you can set this individual's configuration to ignore all test results and deliver the mail. As far as I know, this shouldn't have any affect on other recipients of the email.


Dean
On 1/17/06, Brian [EMAIL PROTECTED] wrote:
I have a customer who wants to receive all emails without having decludecheck them for spam.My question, is can this be done?
And then can it be done so that if a message comes in and it is a messagethat contains their email address and several other email address on ourdomain, that it can only be sent to their address prior to the spam checks?
I hope this makes sense.Thanks in advance,Brian T.---[This E-mail was scanned for viruses by Declude EVA www.declude.com]---This E-mail came from the 
Declude.JunkMail mailing list.Tounsubscribe, just send an E-mail to [EMAIL PROTECTED], andtype unsubscribe Declude.JunkMail.The archives can be found
at http://www.mail-archive.com.-- __Dean Lawrence, CIO/PartnerInternet Data Technology
888.GET.IDT1 ext. 701 * fax: 888.438.4381http://www.idatatech.com/Corporate Internet Development and Marketing Specialists 


Re: [Declude.JunkMail] Whitelisting email address

2006-01-17 Thread Shayne Embry
We have found that if one of the addresses is whitelisted, then every recipient's address gets whitelisted. This may be unique to SmarterMail/Declude. I don't remember having the problem with IMail, but we haven't used it in over a year.Shayne   Hi Brian,  Yes, this can be done with the Pro version. You can have per-user configurations. You can't not have Declude scan the mail, but you can set this individual's configuration to ignore all test results and deliver the mail. As far as I know, this shouldn't have any affect on other recipients of the email.   Dean On 1/17/06, Brian [EMAIL PROTECTED] wrote: I have a customer who wants to receive all emails without having decludecheck them for spam.My question, is can this be done? And then can it be done so that if a message comes in and it is a messagethat contains their email address and several other email address on ourdomain, that it can only be sent to their address prior to the spam checks? I hope this makes sense.Thanks in advance,Brian T.---


RE: [Declude.JunkMail] Whitelisting email address

2006-01-17 Thread John Carter



Can't he go into global.cfg and use
WHITELIST TO receiving_domain

or is that a Pro version thing?

John


From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of Shayne 
EmbrySent: Tuesday, January 17, 2006 12:12 PMTo: 
Declude.JunkMail@declude.comSubject: Re: [Declude.JunkMail] 
Whitelisting email address
We have found that if one of the addresses is 
whitelisted, then every recipient's address gets whitelisted. This may be unique 
to SmarterMail/Declude. I don't remember having the problem with IMail, but we 
haven't used it in over a year.Shayne


Hi Brian,

Yes, this can be done with the Pro version. You can have per-user 
configurations. You can't not have Declude scan the mail, but you can set this 
individual's configuration to ignore all test results and deliver the mail. As 
far as I know, this shouldn't have any affect on other recipients of the email. 


Dean
On 1/17/06, Brian 
[EMAIL PROTECTED] wrote: 
I 
  have a customer who wants to receive all emails without having 
  decludecheck them for spam.My question, is can this be done? 
  And then can it be done so that if a message comes in and it is a 
  messagethat contains their email address and several other email address 
  on ourdomain, that it can only be sent to their address prior to the spam 
  checks? I hope this makes sense.Thanks in 
  advance,Brian T.---


RE: [Declude.JunkMail] Whitelisting email address

2006-01-17 Thread Goran Jovanovic








You can also do 



WHITELIST TO [EMAIL PROTECTED]



Not sure about Standard vs Pro





Goran
 Jovanovic

Omega Network Solutions











From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Carter
Sent: Tuesday, January 17, 2006
1:38 PM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail]
Whitelisting email address





Can't he go into global.cfg and use

WHITELIST TO receiving_domain



or is that a Pro version thing?



John









From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Shayne Embry
Sent: Tuesday, January 17, 2006
12:12 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail]
Whitelisting email address

We have found that if one of the
addresses is whitelisted, then every recipient's address gets whitelisted. This
may be unique to SmarterMail/Declude. I don't remember having the problem with
IMail, but we haven't used it in over a year.

Shayne









Hi Brian,











Yes, this can be done with the Pro version. You can have per-user
configurations. You can't not have Declude scan the mail, but you can set this
individual's configuration to ignore all test results and deliver the mail. As
far as I know, this shouldn't have any affect on other recipients of the email.












Dean







On 1/17/06, Brian
[EMAIL PROTECTED] wrote:


I have a customer who wants to receive all emails without having
declude
check them for spam.

My question, is can this be done? 

And then can it be done so that if a message comes in and it is a message
that contains their email address and several other email address on our
domain, that it can only be sent to their address prior to the spam checks? 

I hope this makes sense.

Thanks in advance,

Brian T.


---










Re: [Declude.JunkMail] Whitelisting email address

2006-01-17 Thread Brian



Irecall that happening with IMail as 
well. That is why I was wondering if I did something wrong 
before.

Brian

- Original Message - 
From: Shayne 
Embry 
To: Declude.JunkMail@declude.com 

Sent: Tuesday, January 17, 2006 1:12 PM
Subject: Re: [Declude.JunkMail] Whitelisting email 
address
We have found that if one of the 
addresses is whitelisted, then every recipient's address gets whitelisted. This 
may be unique to SmarterMail/Declude. I don't remember having the problem with 
IMail, but we haven't used it in over a year.Shayne


Hi Brian,

Yes, this can be done with the Pro version. You can have per-user 
configurations. You can't not have Declude scan the mail, but you can set this 
individual's configuration to ignore all test results and deliver the mail. As 
far as I know, this shouldn't have any affect on other recipients of the email. 


Dean
On 1/17/06, Brian 
[EMAIL PROTECTED] wrote: 
I 
  have a customer who wants to receive all emails without having 
  decludecheck them for spam.My question, is can this be done? 
  And then can it be done so that if a message comes in and it is a 
  messagethat contains their email address and several other email address 
  on ourdomain, that it can only be sent to their address prior to the spam 
  checks? I hope this makes sense.Thanks in 
  advance,Brian T.---


RE: [Declude.JunkMail] Whitelisting email address

2006-01-17 Thread IS - Systems Eng. \(Karl Drugge\)







I can confirm that.



If a single email address is white listed,
then all of them get white listed.



The
solution was a line like this : BYPASSWHITELIST bypasswhitelist 45 6 0 0



If an
email was over weight 45, AND it also had 6 or more recipients, than it
bypassed the white-listing and checked it normally.



I never
tried to do it with individual config files.. But that might work, if it didnt
affect all the recipients.







Karl Drugge















-Original Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian
Sent: Tuesday,
 January 17, 2006 2:16 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail]
Whitelisting email address







Irecall that happening with
IMail as well. That is why I was wondering if I did something wrong
before.











Brian











- Original Message - 



From: Shayne
Embry 





To: Declude.JunkMail@declude.com






Sent: Tuesday, January
 17, 2006 1:12 PM





Subject: Re:
[Declude.JunkMail] Whitelisting email address











We
have found that if one of the addresses is whitelisted, then every recipient's
address gets whitelisted. This may be unique to SmarterMail/Declude. I don't
remember having the problem with IMail, but we haven't used it in over a year.

Shayne









Hi Brian,











Yes, this can be done with the Pro version. You can
have per-user configurations. You can't not have Declude scan the mail, but you
can set this individual's configuration to ignore all test results and deliver
the mail. As far as I know, this shouldn't have any affect on other recipients
of the email. 











Dean







On 1/17/06, Brian [EMAIL PROTECTED]
wrote: 

I have a customer who wants to receive all emails
without having declude
check them for spam.

My question, is can this be done? 

And then can it be done so that if a message comes in and it is a message
that contains their email address and several other email address on our
domain, that it can only be sent to their address prior to the spam checks? 

I hope this makes sense.

Thanks in advance,

Brian T.


---







--





PLEASE NOTE : Florida has a very broad
public records law. Most written communications to or from City officials
regarding City business are public records available to the public and media
upon request. Your E-mail communications may be subject to public disclosure.






PLEASE NOTE : Florida has a very broad public records law. Most written communications to or from City officials regarding City business are public records available to the public and media upon request. Your E-mail communications may be subject to public disclosure.


Re: [Declude.JunkMail] Whitelisting email address

2006-01-17 Thread Brian



What are you using for a hold weight and delete 
weight?

Brian

- Original Message - 
From: IS - 
Systems Eng. (Karl Drugge) 
To: Declude.JunkMail@declude.com 

Sent: Tuesday, January 17, 2006 3:17 PM
Subject: RE: [Declude.JunkMail] Whitelisting email 
address



I can confirm 
that.

If a single email 
address is white listed, then all of them get white listed.

The solution was a line 
like this : BYPASSWHITELIST bypasswhitelist 
45 
6 
0 0

If an email was over 
weight 45, AND it also had 6 or more recipients, than it bypassed the 
white-listing and checked it normally.

I never tried to do it 
with individual config files.. But that might work, if it didnÂ’t affect all the 
recipients.



Karl 
Drugge






-Original 
Message-From: 
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
On Behalf Of BrianSent: Tuesday, January 17, 
2006 2:16 
PMTo: 
Declude.JunkMail@declude.comSubject: Re: [Declude.JunkMail] 
Whitelisting email address



Irecall that happening with 
IMail as well. That is why I was wondering if I did something wrong 
before.



Brian



- Original Message - 


From: Shayne 
Embry 

To: Declude.JunkMail@declude.com 


Sent: 
Tuesday, January 17, 
2006 1:12 
PM

Subject: Re: 
[Declude.JunkMail] Whitelisting email address


We have 
found that if one of the addresses is whitelisted, then every recipient's 
address gets whitelisted. This may be unique to SmarterMail/Declude. I don't 
remember having the problem with IMail, but we haven't used it in over a 
year.Shayne




Hi Brian,



Yes, this can be done with the Pro version. 
You can have per-user configurations. You can't not have Declude scan the mail, 
but you can set this individual's configuration to ignore all test results and 
deliver the mail. As far as I know, this shouldn't have any affect on other 
recipients of the email. 



Dean

On 
1/17/06, Brian [EMAIL PROTECTED] wrote: 
I have a customer who wants to receive all 
emails without having decludecheck them for spam.My question, is can 
this be done? And then can it be done so that if a message comes in and 
it is a messagethat contains their email address and several other email 
address on ourdomain, that it can only be sent to their address prior to the 
spam checks? I hope this makes sense.Thanks in 
advance,Brian T.---

--

PLEASE NOTE : Florida has a 
very broad public records law. Most written communications to or from City 
officials regarding City business are public records available to the public and 
media upon request. Your E-mail communications may be subject to public 
disclosure.
PLEASE NOTE : Florida has 
a very broad public records law. Most written communications to or from City 
officials regarding City business are public records available to the public and 
media upon request. Your E-mail communications may be subject to public 
disclosure.


RE: [Declude.JunkMail] Whitelisting email address

2006-01-17 Thread IS - Systems Eng. \(Karl Drugge\)







I hold at 20, bounce at 40, and delete at
60.





I realize bouncing is bad, but were
government, so I have to be careful about outright deleting email without
notifying someone, somewhere.



Karl Drugge















-Original Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian
Sent: Tuesday, January 17, 2006
3:38 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail]
Whitelisting email address







What are you using for a hold weight
and delete weight?











Brian











- Original Message - 



From: IS
- Systems Eng. (Karl Drugge) 





To: Declude.JunkMail@declude.com






Sent: Tuesday,
January 17, 2006 3:17 PM





Subject: RE:
[Declude.JunkMail] Whitelisting email address













I can confirm that.



If a single email address
is white listed, then all of them get white listed.



The solution was a line
like this : BYPASSWHITELIST bypasswhitelist
45
6
0 0



If an email was over
weight 45, AND it also had 6 or more recipients, than it bypassed the
white-listing and checked it normally.



I never tried to do it
with individual config files.. But that might work, if it didn't affect all the
recipients.







Karl Drugge















-Original Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian
Sent: Tuesday, January 17, 2006
2:16 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail]
Whitelisting email address







Irecall that happening with
IMail as well. That is why I was wondering if I did something wrong
before.











Brian











- Original Message - 



From: Shayne Embry 





To: Declude.JunkMail@declude.com






Sent: Tuesday,
January 17, 2006 1:12 PM





Subject: Re:
[Declude.JunkMail] Whitelisting email address











We
have found that if one of the addresses is whitelisted, then every recipient's
address gets whitelisted. This may be unique to SmarterMail/Declude. I don't
remember having the problem with IMail, but we haven't used it in over a year.

Shayne













Hi Brian,











Yes, this can be done with the Pro version. You can
have per-user configurations. You can't not have Declude scan the mail, but you
can set this individual's configuration to ignore all test results and deliver
the mail. As far as I know, this shouldn't have any affect on other recipients
of the email. 











Dean







On 1/17/06, Brian [EMAIL PROTECTED]
wrote: 

I have a customer who wants to receive all emails
without having declude
check them for spam.

My question, is can this be done? 

And then can it be done so that if a message comes in and it is a message
that contains their email address and several other email address on our
domain, that it can only be sent to their address prior to the spam checks? 

I hope this makes sense.

Thanks in advance,

Brian T.


---







--





PLEASE NOTE : Florida has a very broad public records
law. Most written communications to or from City officials regarding City
business are public records available to the public and media upon request.
Your E-mail communications may be subject to public disclosure.







PLEASE NOTE : Florida has a
very broad public records law. Most written communications to or from City
officials regarding City business are public records available to the public
and media upon request. Your E-mail communications may be subject to public
disclosure.







--





PLEASE NOTE : Florida has a very broad public records
law. Most written communications to or from City officials regarding City
business are public records available to the public and media upon request.
Your E-mail communications may be subject to public disclosure.






PLEASE NOTE : Florida has a very broad public records law. Most written communications to or from City officials regarding City business are public records available to the public and media upon request. Your E-mail communications may be subject to public disclosure.


Re: [Declude.JunkMail] Whitelisting email address

2006-01-17 Thread Matt




Karl,

Getting blacklisted for bouncing spam back to forged addresses would
probably be a lot worse than missing a stray message that shouldn't
have been blocked. This certainly can happen, especially if you get a
lot of zombie generated spam.

It is also of course a big pain dealing with servers that bounce this
stuff back to forged addresses. Today I'm under heavy attack from
multiple sources of backscatter. Backscatter costs others time, money
and frustration. It's not fair if it is avoidable. Please reconsider
your choices. Maybe we can help you figure out a better way to deal
with this.

Matt



IS - Systems Eng. (Karl Drugge) wrote:

  
  
  
  
  
  
  I hold at
20, bounce at 40, and delete at
60.
  
  
  I realize
bouncing is bad, but were
government, so I have to be careful about outright deleting email
without
notifying someone, somewhere.
  
  Karl Drugge
  
  
  
  
  
  
  
  -Original
Message-
  From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Brian
  Sent: Tuesday, January
17, 2006
3:38 PM
  To:
Declude.JunkMail@declude.com
  Subject: Re:
[Declude.JunkMail]
Whitelisting email address
  
  
  
  What are
you using for a hold weight
and delete weight?
  
  
  
  
  
  Brian
  
  
  
  
  
  -
Original Message - 
  
  From: IS
- Systems Eng. (Karl Drugge) 
  
  
  To: Declude.JunkMail@declude.com
  
  
  
  Sent: Tuesday,
January 17, 2006 3:17 PM
  
  
  Subject: RE:
[Declude.JunkMail] Whitelisting email address
  
  
  
  
  
  
  I can
confirm that.
  
  If a single
email address
is white listed, then all of them get white listed.
  
  The solution
was a line
like this : BYPASSWHITELIST bypasswhitelist
45
6
0 0
  
  If an email
was over
weight 45, AND it also had 6 or more recipients, than it bypassed the
white-listing and checked it normally.
  
  I never
tried to do it
with individual config files.. But that might work, if it didn't affect
all the
recipients.
  
  
  
  Karl Drugge
  
  
  
  
  
  
  
  -Original
Message-
  From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Brian
  Sent: Tuesday, January
17, 2006
2:16 PM
  To:
Declude.JunkMail@declude.com
  Subject: Re:
[Declude.JunkMail]
Whitelisting email address
  
  
  
  Irecall
that happening with
IMail as well. That is why I was wondering if I did something wrong
before.
  
  
  
  
  
  Brian
  
  
  
  
  
  -
Original Message - 
  
  From: Shayne
Embry 
  
  
  To: Declude.JunkMail@declude.com
  
  
  
  Sent: Tuesday,
January 17, 2006 1:12 PM
  
  
  Subject: Re:
[Declude.JunkMail] Whitelisting email address
  
  
  
  
  
  We
have found that if one of the addresses is whitelisted, then every
recipient's
address gets whitelisted. This may be unique to SmarterMail/Declude. I
don't
remember having the problem with IMail, but we haven't used it in over
a year.
  
Shayne
  
  
  
  
  
  Hi
Brian,
  
  
  
  
  
  Yes,
this can be done with the Pro version. You can
have per-user configurations. You can't not have Declude scan the mail,
but you
can set this individual's configuration to ignore all test results and
deliver
the mail. As far as I know, this shouldn't have any affect on other
recipients
of the email. 
  
  
  
  
  
  Dean
  

  
  
  On 1/17/06, Brian [EMAIL PROTECTED]
wrote: 
  I have
a customer who wants to receive all emails
without having declude
check them for spam.
  
My question, is can this be done? 
  
And then can it be done so that if a message comes in and it is a
message
that contains their email address and several other email address on our
domain, that it can only be sent to their address prior to the spam
checks? 
  
I hope this makes sense.
  
Thanks in advance,
  
Brian T.
  
  
---
  
  
  
  --
  
  
  PLEASE
NOTE : Florida has a very broad public records
law. Most written communications to or from City officials regarding
City
business are public records available to the public and media upon
request.
Your E-mail communications may be subject to public disclosure.
  
  
  
  PLEASE NOTE :
Florida has a
very broad public records law. Most written communications to or from
City
officials regarding City business are public records available to the
public
and media upon request. Your E-mail communications may be subject to
public
disclosure.
  
  
  
  --
  
  
  PLEASE
NOTE : Florida has a very broad public records
law. Most written communications to or from City officials regarding
City
business are public records available to the public and media upon
request.
Your E-mail communications may be subject to public disclosure.
  
  
  
  PLEASE NOTE :
Florida has a very broad public records law. Most written
communications to or from City officials regarding City business are
public records available to the public and media upon request. Your
E-mail communications may be subject to public disclosure.





RE: [Declude.JunkMail] Whitelisting email address

2006-01-17 Thread David Lewis-Waller
I would second that. We were blacklisted by SORBS when one of OUR customers
autoresponded to a forged sender, which happended to be a SORBS admin or
tarpit address. We passed the 'fine' of delisting back to the customer as a
salutatory lesson but not before we received many complaints of senders
email not being delivered because of draconian single point failure tests
some ISP's / corporates have in place.

David 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matt
Sent: 17 January 2006 21:28
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting email address

Karl,

Getting blacklisted for bouncing spam back to forged addresses would
probably be a lot worse than missing a stray message that shouldn't have
been blocked.  This certainly can happen, especially if you get a lot of
zombie generated spam.

It is also of course a big pain dealing with servers that bounce this stuff
back to forged addresses.  Today I'm under heavy attack from multiple
sources of backscatter.  Backscatter costs others time, money and
frustration.  It's not fair if it is avoidable.  Please reconsider your
choices.  Maybe we can help you figure out a better way to deal with this.

Matt



IS - Systems Eng. (Karl Drugge) wrote: 

I hold at 20, bounce at 40, and delete at 60.

 

I realize bouncing is bad, but we're government, so I have to be
careful about outright deleting email without notifying someone, somewhere.

 

Karl Drugge

 

 

 

 

 

 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian
Sent: Tuesday, January 17, 2006 3:38 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting email address

 

What are you using for a hold weight and delete weight?

 

Brian

 

- Original Message - 

From: IS - Systems Eng. (Karl Drugge)
mailto:[EMAIL PROTECTED]  

To: Declude.JunkMail@declude.com 

Sent: Tuesday, January 17, 2006 3:17 PM

Subject: RE: [Declude.JunkMail] Whitelisting email address

 

I can confirm that.

 

If a single email address is white listed, then all of them get
white listed.

 

The solution was a line like this : BYPASSWHITELIST
bypasswhitelist  45 6  0  0

 

If an email was over weight 45, AND it also had 6 or more
recipients, than it bypassed the white-listing and checked it normally.

 

I never tried to do it with individual config files.. But that might
work, if it didn't affect all the recipients.

 

 

Karl Drugge

 

 

 

 

 

 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian
Sent: Tuesday, January 17, 2006 2:16 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting email address

 

I recall that happening with IMail as well.  That is why I was
wondering if I did something wrong before.

 

Brian

 

- Original Message - 

From: Shayne Embry mailto:[EMAIL PROTECTED]  

To: Declude.JunkMail@declude.com 

Sent: Tuesday, January 17, 2006 1:12 PM

Subject: Re: [Declude.JunkMail] Whitelisting email address

 

We have found that if one of the addresses is whitelisted, then
every recipient's address gets whitelisted. This may be unique to
SmarterMail/Declude. I don't remember having the problem with IMail, but we
haven't used it in over a year.

Shayne





Hi Brian,

 

Yes, this can be done with the Pro version. You can have per-user
configurations. You can't not have Declude scan the mail, but you can set
this individual's configuration to ignore all test results and deliver the
mail. As far as I know, this shouldn't have any affect on other recipients
of the email. 

 

Dean

 

On 1/17/06, Brian [EMAIL PROTECTED] wrote: 

I have a customer who wants to receive all emails without having
declude
check them for spam.

My question, is can this be done? 

And then can it be done so that if a message comes in and it is a
message
that contains their email address and several other email address on
our
domain, that it can only be sent to their address prior to the spam
checks? 

I hope this makes sense.

Thanks in advance,

Brian T.


---

--

PLEASE NOTE : Florida has a very broad public

RE: [Declude.JunkMail] Whitelisting email address

2006-01-17 Thread IS - Systems Eng. \(Karl Drugge\)







Believe me, Id love to find a way
to do it, but when I HAVE to receive emails from hideously mis-configured
servers, whack-job citizens, and other municipalities with less then stellar
I.T. staff from any where at any time, not bouncing becomes the worse of
two evils. 



As an example, if I DELETE an email from a
citizen because it meets my delete criteria ( lets say a nut-job,
retired, self declared IT samurai with a shareware SMTP server, on a dial up
account to a local home based ISP run by his best friend ) I can ( and have )
been questioned by the City Manager on exactly WHY he didnt get this
email, because this nut-job shows up to a city council meeting and has a
foaming at the mouth fit in public. Technical explanations dont cut it
in the political arena. I have to, at the very least, send something back to
notify the originator that the email was bounced, unless its so horribly
mal-formed, or chock full of key words, that it I can absolutely guarantee its
spam. 



But, if someone wants to take a crack at
it, Ill be more than happy to post my config files.







Karl Drugge















-Original
Message-
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt
Sent: Tuesday, January 17, 2006 4:28
PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail]
Whitelisting email address





Karl,

Getting blacklisted for bouncing spam back to forged addresses would probably
be a lot worse than missing a stray message that shouldn't have been
blocked. This certainly can happen, especially if you get a lot of zombie
generated spam.

It is also of course a big pain dealing with servers that bounce this stuff
back to forged addresses. Today I'm under heavy attack from multiple
sources of backscatter. Backscatter costs others time, money and
frustration. It's not fair if it is avoidable. Please reconsider
your choices. Maybe we can help you figure out a better way to deal with
this.

Matt



IS - Systems Eng. (Karl Drugge) wrote: 



I hold at 20, bounce at
40, and delete at 60.





I realize bouncing is
bad, but were government, so I have to be careful about outright
deleting email without notifying someone, somewhere.



Karl Drugge















-Original
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
On Behalf Of Brian
Sent: Tuesday, January 17, 2006
3:38 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail]
Whitelisting email address







What are you using
for a hold weight and delete weight?











Brian











- Original
Message - 



From: IS
- Systems Eng. (Karl Drugge) 





To: Declude.JunkMail@declude.com






Sent: Tuesday,
January 17, 2006 3:17 PM





Subject: RE:
[Declude.JunkMail] Whitelisting email address













I can
confirm that.



If a
single email address is white listed, then all of them get white listed.



The
solution was a line like this : BYPASSWHITELIST
bypasswhitelist 45
6
0 0



If an
email was over weight 45, AND it also had 6 or more recipients, than it
bypassed the white-listing and checked it normally.



I never
tried to do it with individual config files.. But that might work, if it didn't
affect all the recipients.







Karl
Drugge















-Original
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
On Behalf Of Brian
Sent: Tuesday, January 17, 2006
2:16 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail]
Whitelisting email address







Irecall that
happening with IMail as well. That is why I was wondering if I did
something wrong before.











Brian











- Original
Message - 



From: Shayne
Embry 





To: Declude.JunkMail@declude.com






Sent: Tuesday,
January 17, 2006 1:12 PM





Subject: Re:
[Declude.JunkMail] Whitelisting email address











We have found that if one of the addresses is whitelisted,
then every recipient's address gets whitelisted. This may be unique to
SmarterMail/Declude. I don't remember having the problem with IMail, but we
haven't used it in over a year.

Shayne

















Hi Brian,











Yes, this can be done
with the Pro version. You can have per-user configurations. You can't not have
Declude scan the mail, but you can set this individual's configuration to
ignore all test results and deliver the mail. As far as I know, this shouldn't
have any affect on other recipients of the email. 











Dean







On
1/17/06, Brian [EMAIL PROTECTED] wrote:


I have a customer who
wants to receive all emails without having declude
check them for spam.

My question, is can this be done? 

And then can it be done so that if a message comes in and it is a message
that contains their email address and several other email address on our
domain, that it can only be sent to their address prior to the spam checks? 

I hope this makes sense.

Thanks in advance,

Brian T.


---







--





PLEASE NOTE : Florida has
a very broad public records law. Most written

RE: [Declude.JunkMail] Whitelisting email address

2006-01-17 Thread David Lewis-Waller
Karl,

Why delete or bounce? In the scenario that litigation should dictate that
you can't delete or bounce then having to deal with the huge volume of
junkmail is an option that you must live with. 

Can I suggest that rather than reap the whirlwind of customer ire you pass
something back to them in the form of empowerment. I am of course making a
number of assumptions but why not simply declare:

A) you are not going to delete or bounce
B) you are going to appropraitely mark email
C) you empower your users (perhaps by an Imail filter) make their own
decisions (and take some responbility for their email) by giving them the
power to delete bounce on your markings e.g. SPAM-VHIGH.

Just a thought...

David 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of IS - Systems Eng.
(Karl Drugge)
Sent: 17 January 2006 22:18
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] Whitelisting email address

Believe me, I'd love to find a way to do it, but when I HAVE to receive
emails from hideously mis-configured servers, whack-job citizens, and other
municipalities with less then stellar I.T. staff. from any where at any
time, not bouncing becomes the worse of two evils. 

 

As an example, if I DELETE an email from a citizen because it meets my
delete criteria ( let's say a nut-job, retired, self declared IT samurai
with a shareware SMTP server, on a dial up account to a local home based ISP
run by his best friend ) I can ( and have ) been questioned by the City
Manager on exactly WHY he didn't get this email, because this nut-job shows
up to a city council meeting and has a foaming at the mouth fit in public.
Technical explanations don't cut it in the political arena. I have to, at
the very least, send something back to notify the originator that the email
was bounced, unless it's so horribly mal-formed, or chock full of key words,
that it I can absolutely guarantee it's spam.   

 

But, if someone wants to take a crack at it, I'll be more than happy to post
my config files.

 

 

Karl Drugge

 

 

 

 

 

 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matt
Sent: Tuesday, January 17, 2006 4:28 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting email address

 

Karl,

Getting blacklisted for bouncing spam back to forged addresses would
probably be a lot worse than missing a stray message that shouldn't have
been blocked.  This certainly can happen, especially if you get a lot of
zombie generated spam.

It is also of course a big pain dealing with servers that bounce this stuff
back to forged addresses.  Today I'm under heavy attack from multiple
sources of backscatter.  Backscatter costs others time, money and
frustration.  It's not fair if it is avoidable.  Please reconsider your
choices.  Maybe we can help you figure out a better way to deal with this.

Matt



IS - Systems Eng. (Karl Drugge) wrote: 

I hold at 20, bounce at 40, and delete at 60.

 

I realize bouncing is bad, but we're government, so I have to be careful
about outright deleting email without notifying someone, somewhere.

 

Karl Drugge

 

 

 

 

 

 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian
Sent: Tuesday, January 17, 2006 3:38 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting email address

 

What are you using for a hold weight and delete weight?

 

Brian

 

- Original Message - 

From: IS - Systems Eng. (Karl Drugge) mailto:[EMAIL PROTECTED]  

To: Declude.JunkMail@declude.com 

Sent: Tuesday, January 17, 2006 3:17 PM

Subject: RE: [Declude.JunkMail] Whitelisting email address

 

I can confirm that.

 

If a single email address is white listed, then all of them get white
listed.

 

The solution was a line like this : BYPASSWHITELIST  bypasswhitelist  45
6  0  0

 

If an email was over weight 45, AND it also had 6 or more recipients, than
it bypassed the white-listing and checked it normally.

 

I never tried to do it with individual config files.. But that might work,
if it didn't affect all the recipients.

 

 

Karl Drugge

 

 

 

 

 

 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian
Sent: Tuesday, January 17, 2006 2:16 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting email address

 

I recall that happening with IMail as well.  That is why I was wondering if
I did something wrong before.

 

Brian

 

- Original Message - 

From: Shayne Embry mailto:[EMAIL PROTECTED]  

To: Declude.JunkMail@declude.com 

Sent: Tuesday, January 17, 2006 1:12 PM

Subject: Re: [Declude.JunkMail] Whitelisting email address

 

We have found that if one of the addresses is whitelisted, then every
recipient's address gets whitelisted. This may be unique to
SmarterMail/Declude. I don't remember having the problem

Re: [Declude.JunkMail] Whitelisting email address

2006-01-17 Thread Matt




Karl,

What would be best would be to set up a system for the review and
reprocessing of false positives. It would likely also help to add some
external tests such as Sniffer so as to improve your spam blocking and
rely less on single tests that could be contributing to your false
positive issue. Approaching this from the perspective of bouncing
E-mail as a solution is to miss the essence of the real problem and
create another one in it's place. The fact that you both hold and
bounce E-mail suggests that this is simply an issue with the
practicality of reviewing what would otherwise get blocked. Your
perspective of this being the lesser of two evils is likely the
result of not yet being blacklisted since their is no double that the
same City Manager would yell even louder if he couldn't send E-mail to
his friends and constituents than he would when missing E-mails from
whack-job citizens.

If it is not within your abilities to procure and/or design new filters
and add such review functionality, you might consider outsourcing to a
third-party than can resolve these problems, or you might want to
consider subject tagging in the place of holding or bouncing E-mail,
and then have the E-mail clients filter messages with the tagged
subjects into Junk folders that they can choose to either review or
ignore.

Matt




IS - Systems Eng. (Karl Drugge) wrote:

  
  
  
  
  
  
  Believe me,
Id love to find a way
to do it, but when I HAVE to receive emails from hideously
mis-configured
servers, whack-job citizens, and other municipalities with less then
stellar
I.T. staff from any where at any time, not bouncing becomes the worse
of
two evils. 
  
  As an
example, if I DELETE an email from a
citizen because it meets my delete criteria ( lets say a nut-job,
retired, self declared IT samurai with a shareware SMTP server, on a
dial up
account to a local home based ISP run by his best friend ) I can ( and
have )
been questioned by the City Manager on exactly WHY he didnt get this
email, because this nut-job shows up to a city council meeting and has
a
foaming at the mouth fit in public. Technical explanations dont cut it
in the political arena. I have to, at the very least, send something
back to
notify the originator that the email was bounced, unless its so
horribly
mal-formed, or chock full of key words, that it I can absolutely
guarantee its
spam. 
  
  But, if
someone wants to take a crack at
it, Ill be more than happy to post my config files.
  
  
  
  Karl Drugge
  
  
  
  
  
  
  
  -Original
Message-
  From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Matt
  Sent: Tuesday, January
17, 2006 4:28
PM
  To:
Declude.JunkMail@declude.com
  Subject: Re:
[Declude.JunkMail]
Whitelisting email address
  
  
  Karl,
  
Getting blacklisted for bouncing spam back to forged addresses would
probably
be a lot worse than missing a stray message that shouldn't have been
blocked. This certainly can happen, especially if you get a lot of
zombie
generated spam.
  
It is also of course a big pain dealing with servers that bounce this
stuff
back to forged addresses. Today I'm under heavy attack from multiple
sources of backscatter. Backscatter costs others time, money and
frustration. It's not fair if it is avoidable. Please reconsider
your choices. Maybe we can help you figure out a better way to deal
with
this.
  
Matt
  
  
  
IS - Systems Eng. (Karl Drugge) wrote: 
  
  I hold at
20, bounce at
40, and delete at 60.
  
  
  I realize
bouncing is
bad, but were government, so I have to be careful about outright
deleting email without notifying someone, somewhere.
  
  Karl Drugge
  
  
  
  
  
  
  
  -Original
Message-
  From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
  On Behalf Of Brian
  Sent: Tuesday, January
17, 2006
3:38 PM
  To: Declude.JunkMail@declude.com
  Subject: Re:
[Declude.JunkMail]
Whitelisting email address
  
  
  
  What are you using
for a hold weight and delete weight?
  
  
  
  
  
  Brian
  
  
  
  
  
  - Original
Message - 
  
  From: IS
- Systems Eng. (Karl Drugge) 
  
  
  To: Declude.JunkMail@declude.com
  
  
  
  Sent: Tuesday,
January 17, 2006 3:17 PM
  
  
  Subject: RE:
[Declude.JunkMail] Whitelisting email address
  
  
  
  
  
  
  I can
confirm that.
  
  If a
single email address is white listed, then all of them get white listed.
  
  The
solution was a line like this : BYPASSWHITELIST
bypasswhitelist 45
6
0 0
  
  If an
email was over weight 45, AND it also had 6 or more recipients, than it
bypassed the white-listing and checked it normally.
  
  I never
tried to do it with individual config files.. But that might work, if
it didn't
affect all the recipients.
  
  
  
  Karl
Drugge
  
  
  
  
  
  
  
  -Original
Message-
  From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
  On Behalf Of Brian
  Sent: Tuesday, January
17, 2006
2:16 PM
  To: Declude.JunkMail@declude.com
  Subject: Re:
[Declude.JunkMail]
Whitelisting email address

[Declude.JunkMail] Whitelisting

2005-10-31 Thread Serge
Title: Message



Hi 
all
I am 
tryi,g to find why an email was whitelisted
I 
suspect autowhitelist, but how can i confirm ?
the 
logs shows this:
10/31/2005 07:23:52 QC64AD3B100E67716 Skipping4 
E-mail from [EMAIL PROTECTED] ; 
whitelisted [EMAIL PROTECTED] 
].


Re: [Declude.JunkMail] Whitelisting

2005-10-31 Thread Scott Fisher
Title: Message



I'm pretty confident that the "Skipping4 E-mail 
from " means an address book whitelist.

  - Original Message - 
  From: 
  Serge 
  To: Declude.JunkMail@declude.com 
  
  Sent: Monday, October 31, 2005 3:35 
  AM
  Subject: [Declude.JunkMail] 
  Whitelisting
  
  Hi 
  all
  I 
  am tryi,g to find why an email was whitelisted
  I 
  suspect autowhitelist, but how can i confirm ?
  the logs shows this:
  10/31/2005 07:23:52 QC64AD3B100E67716 Skipping4 
  E-mail from [EMAIL PROTECTED] ; 
  whitelisted [EMAIL PROTECTED] 
  ].


Re: [Declude.JunkMail] Whitelisting

2005-10-31 Thread Travis Sullivan
You can double check by scanning the whitelist section in your global.cfg 
file and address books for the text string.


Travis

- Original Message - 
From: Serge [EMAIL PROTECTED]

To: Declude.JunkMail@declude.com
Sent: Monday, October 31, 2005 10:39 AM
Subject: Re: [Declude.JunkMail] Whitelisting


Messagethanks scott, that confirms my thoughts

 - Original Message - 
 From: Scott Fisher

 To: Declude.JunkMail@declude.com
 Sent: Monday, October 31, 2005 2:38 PM
 Subject: Re: [Declude.JunkMail] Whitelisting


 I'm pretty confident that the Skipping4 E-mail from  means an address 
book whitelist.
   - Original Message - 
   From: Serge

   To: Declude.JunkMail@declude.com
   Sent: Monday, October 31, 2005 3:35 AM
   Subject: [Declude.JunkMail] Whitelisting


   Hi all
   I am tryi,g to find why an email was whitelisted
   I suspect autowhitelist, but how can i confirm ?
   the logs shows this:
   10/31/2005 07:23:52 QC64AD3B100E67716 Skipping4 E-mail from 
[EMAIL PROTECTED] ; whitelisted [EMAIL PROTECTED] ].


---
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.


Re: [Declude.JunkMail] Whitelisting

2005-10-31 Thread Serge
Title: Message



thanks scott, that confirms 
mythoughts


  - Original Message - 
  From: 
  Scott 
  Fisher 
  To: Declude.JunkMail@declude.com 
  
  Sent: Monday, October 31, 2005 2:38 
  PM
  Subject: Re: [Declude.JunkMail] 
  Whitelisting
  
  I'm pretty confident that the "Skipping4 E-mail 
  from " means an address book whitelist.
  
- Original Message - 
From: 
Serge 
To: Declude.JunkMail@declude.com 

Sent: Monday, October 31, 2005 3:35 
AM
Subject: [Declude.JunkMail] 
Whitelisting

Hi all
I am tryi,g to find why an email was 
whitelisted
I suspect autowhitelist, but how can i confirm 
?
the logs shows this:
10/31/2005 07:23:52 QC64AD3B100E67716 Skipping4 
E-mail from [EMAIL PROTECTED] 
; whitelisted [EMAIL PROTECTED] 
].


Re: [Declude.JunkMail] Whitelisting

2005-07-27 Thread Richard Farris



So whitelisting the recipient is always a last 
resort? Better to find out where they are not getting their mail and 
whitelist that or find out why they are not getting their expected 
mail..?
Richard FarrisEthixs Online1.270.247. 
Office1.800.548.3877 Tech Support"Crossroads to a Cleaner 
Internet"

  - Original Message - 
  From: 
  David 
  Franco-Rocha [ Declude ] 
  To: Declude.JunkMail@declude.com 
  
  Sent: Tuesday, July 26, 2005 8:59 
AM
  Subject: Re: [Declude.JunkMail] 
  Whitelisting
  
  Richard,
  
  The problem here is, first of all, that Declude 
  does not look at the cc: or bcc: in the headers. It deals with recipients of 
  the email solely on the basis of what is in the message envelope (q*.smd 
  file), which is discarded by IMail after processing; all you eventually see is 
  the contents of the message itself (the d*.smd file).
  
  Whitelisting ensures that the email will pass all 
  tests. Under optimal circumstances, if an email source or destination is 
  whitelisted, all tests should be skipped. If there are two recipients and only 
  one were whitelisted, the headers of te email would have to indicate a 
  whitelisted weight of 0 for one recipient and the actual weight for the other 
  (non-whitelisted) recipient. That would necessitate two different sets of 
  headers, which would require two separate message files and therefore two 
  separate envelopes: If the non-whitelisted weight exceeded the HOLD threshold, 
  one copy of the email would be placed into the HOLD folder with the envelope 
  modified for that single recipient; the other would be whitelisted and the 
  held recipient would be deleted from that envelope. In other words, Declude 
  would have to generate multiple emails from a single email, which is not 
  practical. How would Declude assign a new queue number to the duplicate email? 
  If one recipient were whitelisted and the other had a weight of 5 (to be 
  delivered), there would be different sets of headers and therefore different 
  emails. They could not both have the same queue number because they could no 
  be placed into the spool at the same time (one would overwrite the 
  other).
  
  The email server generates a separate copy of the 
  email for each recipient after processing by Declude. However, there is no 
  practical way for Declude to create multiple emails from a single 
  message.
  
  David Franco-Rocha
  Declude Technical Support
  
  
  
- Original Message - 
From: 
Richard 
Farris 
To: Declude.JunkMail@declude.com 

Sent: Monday, July 25, 2005 4:24 
PM
Subject: [Declude.JunkMail] 
Whitelisting

I just took out all the email addresses I had 
whitelisted in my Global file last week because I thought this would 
helpstop more spam getting thruand of course folks are now 
emailing me saying they are missing mail..newsletters and 
such...

My question is "Why is it not possible with 
Declude to whitelist an email address and it only applies to that email 
address and not any others that might be in CC or BCC"?
Richard FarrisEthixs Online1.270.247. 
Office1.800.548.3877 Tech Support"Crossroads to a Cleaner 
Internet"

  - Original Message - 
  From: 
  Matt 
  
  To: Declude.JunkMail@declude.com 
  
  Sent: Monday, July 25, 2005 1:47 
  PM
  Subject: Re: [Declude.JunkMail] 
  Filter not triggering
  Kevin,Just a thought if you wanted to confirm this 
  as a bug, maybe try a filter for this same message, but match a full word 
  to see if it triggers. I did decode this segment and there is no 
  additional encoding or other tricks that would cause a filter to not 
  hit.IMO, knowing about bugs like this would be very helpful at 
  times, especially considering the time that it would take each one of us 
  that was affected by it to figure it out on our own. Maybe if 
  Declude doesn't want to post this information on their site, we could take 
  it upon ourselves to share such information with the list when it is 
  discovered. This is for the most part how the list used to function 
  in the old days, though most of us seemed to desire a page dedicated to 
  the topic regardless.MattKevin Bilbee 
  wrote: 
  



Well that would explain why many of my filters are not as 
effective as they used to be. Has Declude announced when the fix will be 
available



Kevin Bilbee

  -Original Message-From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]]On 
  Behalf Of John CarterSent: Monday, July 25, 2005 8:05 
  AMTo: Declude.JunkMail@declude.comSubject: 
  RE: [Declude.JunkMail] Filter not triggering
  I have reported to Declude a problem 
 

Re: [Declude.JunkMail] Whitelisting

2005-07-27 Thread Darrell \([EMAIL PROTECTED])

Richard,

Instead of whitelisting we use negative weight on DNS names.

REVDNS -10 ENDSWITH .dell.com

Darrell

DLAnalyzer - Comprehensive reporting for Declude Junkmail and Virus.
http://www.invariantsystems.com




Richard Farris writes:


So whitelisting the recipient is always a last resort?  Better to find out 
where they are not getting their mail and whitelist that or find out why they 
are not getting their expected mail..?

Richard Farris
Ethixs Online
1.270.247. Office
1.800.548.3877 Tech Support
Crossroads to a Cleaner Internet

  - Original Message -
  From: David Franco-Rocha [ Declude ]
  To: Declude.JunkMail@declude.com
  Sent: Tuesday, July 26, 2005 8:59 AM
  Subject: Re: [Declude.JunkMail] Whitelisting


  Richard,

  The problem here is, first of all, that Declude does not look at the cc: or 
bcc: in the headers. It deals with recipients of the email solely on the basis 
of what is in the message envelope (q*.smd file), which is discarded by IMail 
after processing; all you eventually see is the contents of the message itself 
(the d*.smd file).

  Whitelisting ensures that the email will pass all tests. Under optimal 
circumstances, if an email source or destination is whitelisted, all tests 
should be skipped. If there are two recipients and only one were whitelisted, 
the headers of te email would have to indicate a whitelisted weight of 0 for 
one recipient and the actual weight for the other (non-whitelisted) recipient. 
That would necessitate two different sets of headers, which would require two 
separate message files and therefore two separate envelopes: If the 
non-whitelisted weight exceeded the HOLD threshold, one copy of the email would 
be placed into the HOLD folder with the envelope modified for that single 
recipient; the other would be whitelisted and the held recipient would be 
deleted from that envelope. In other words, Declude would have to generate 
multiple emails from a single email, which is not practical. How would Declude 
assign a new queue number to the duplicate email? If one recipient were 
whitelisted and the other had a weight of 5 (to be delivered), there would be 
different sets of headers and therefore different emails. They could not both 
have the same queue number because they could no be placed into the spool at 
the same time (one would overwrite the other).

  The email server generates a separate copy of the email for each recipient 
after processing by Declude. However, there is no practical way for Declude to 
create multiple emails from a single message.

  David Franco-Rocha
  Declude Technical Support


- Original Message -
From: Richard Farris
To: Declude.JunkMail@declude.com
Sent: Monday, July 25, 2005 4:24 PM
Subject: [Declude.JunkMail] Whitelisting


I just took out all the email addresses I had whitelisted in my Global file 
last week because I thought this would help stop more spam getting thruand 
of course folks are now emailing me saying they are missing mail..newsletters 
and such...

My question is Why is it not possible with Declude to whitelist an email 
address and it only applies to that email address and not any others that might be in CC 
or BCC?

Richard Farris
Ethixs Online
1.270.247. Office
1.800.548.3877 Tech Support
Crossroads to a Cleaner Internet

  - Original Message -
  From: Matt
  To: Declude.JunkMail@declude.com
  Sent: Monday, July 25, 2005 1:47 PM
  Subject: Re: [Declude.JunkMail] Filter not triggering


  Kevin,

  Just a thought if you wanted to confirm this as a bug, maybe try a filter 
for this same message, but match a full word to see if it triggers.  I did 
decode this segment and there is no additional encoding or other tricks that 
would cause a filter to not hit.

  IMO, knowing about bugs like this would be very helpful at times, 
especially considering the time that it would take each one of us that was 
affected by it to figure it out on our own.  Maybe if Declude doesn't want to 
post this information on their site, we could take it upon ourselves to share 
such information with the list when it is discovered.  This is for the most 
part how the list used to function in the old days, though most of us seemed to 
desire a page dedicated to the topic regardless.

  Matt





  Kevin Bilbee wrote:
Well that would explain why many of my filters are not as effective as 
they used to be. Has Declude announced when the fix will be available



Kevin Bilbee
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of John 
Carter
  Sent: Monday, July 25, 2005 8:05 AM
  To: Declude.JunkMail@declude.com
  Subject: RE: [Declude.JunkMail] Filter not triggering


  I have reported to Declude a problem with the CONTAINS statement.  
Prior to 2.0.6

Re: [Declude.JunkMail] Whitelisting

2005-07-26 Thread David Franco-Rocha [ Declude ]



Richard,

The problem here is, first of all, that Declude 
does not look at the cc: or bcc: in the headers. It deals with recipients of the 
email solely on the basis of what is in the message envelope (q*.smd file), 
which is discarded by IMail after processing; all you eventually see is the 
contents of the message itself (the d*.smd file).

Whitelisting ensures that the email will pass all 
tests. Under optimal circumstances, if an email source or destination is 
whitelisted, all tests should be skipped. If there are two recipients and only 
one were whitelisted, the headers of te email would have to indicate a 
whitelisted weight of 0 for one recipient and the actual weight for the other 
(non-whitelisted) recipient. That would necessitate two different sets of 
headers, which would require two separate message files and therefore two 
separate envelopes: If the non-whitelisted weight exceeded the HOLD threshold, 
one copy of the email would be placed into the HOLD folder with the envelope 
modified for that single recipient; the other would be whitelisted and the held 
recipient would be deleted from that envelope. In other words, Declude would 
have to generate multiple emails from a single email, which is not practical. 
How would Declude assign a new queue number to the duplicate email? If one 
recipient were whitelisted and the other had a weight of 5 (to be delivered), 
there would be different sets of headers and therefore different emails. They 
could not both have the same queue number because they could no be placed into 
the spool at the same time (one would overwrite the other).

The email server generates a separate copy of the 
email for each recipient after processing by Declude. However, there is no 
practical way for Declude to create multiple emails from a single 
message.

David Franco-Rocha
Declude Technical Support



  - Original Message - 
  From: 
  Richard 
  Farris 
  To: Declude.JunkMail@declude.com 
  
  Sent: Monday, July 25, 2005 4:24 PM
  Subject: [Declude.JunkMail] 
  Whitelisting
  
  I just took out all the email addresses I had 
  whitelisted in my Global file last week because I thought this would 
  helpstop more spam getting thruand of course folks are now emailing 
  me saying they are missing mail..newsletters and such...
  
  My question is "Why is it not possible with 
  Declude to whitelist an email address and it only applies to that email 
  address and not any others that might be in CC or BCC"?
  Richard FarrisEthixs Online1.270.247. 
  Office1.800.548.3877 Tech Support"Crossroads to a Cleaner 
  Internet"
  
- Original Message - 
From: 
Matt 

To: Declude.JunkMail@declude.com 

Sent: Monday, July 25, 2005 1:47 
PM
Subject: Re: [Declude.JunkMail] Filter 
not triggering
Kevin,Just a thought if you wanted to confirm this as 
a bug, maybe try a filter for this same message, but match a full word to 
see if it triggers. I did decode this segment and there is no 
additional encoding or other tricks that would cause a filter to not 
hit.IMO, knowing about bugs like this would be very helpful at 
times, especially considering the time that it would take each one of us 
that was affected by it to figure it out on our own. Maybe if Declude 
doesn't want to post this information on their site, we could take it upon 
ourselves to share such information with the list when it is 
discovered. This is for the most part how the list used to function in 
the old days, though most of us seemed to desire a page dedicated to the 
topic regardless.MattKevin Bilbee wrote: 

  
  

  Well that would explain why many of my filters are not as effective 
  as they used to be. Has Declude announced when the fix will be 
  available
  
  
  
  Kevin Bilbee
  
-Original Message-From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED]]On 
Behalf Of John CarterSent: Monday, July 25, 2005 8:05 
AMTo: Declude.JunkMail@declude.comSubject: 
RE: [Declude.JunkMail] Filter not triggering
I have reported to Declude a problem with the 
"CONTAINS" statement. Prior to 2.0.6 (or somewhere around 
there)it worked oncharacter match, but after an upgrade to 
Declude it only works on a word match. (In other words you could not 
longer match on a string of characters within a word.) This would 
affect your situation.

I believe the fix is caught up in the wait for the 
newest version (the one they are testing now.)

John


From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED]] 
On Behalf Of Kevin BilbeeSent: Monday, July 25, 2005 
9:10 AMTo: JunkMail DecludeSubject: 
[Declude.JunkMail] Filter not triggering
The attache

[Declude.JunkMail] Whitelisting

2005-07-25 Thread Richard Farris



I just took out all the email addresses I had 
whitelisted in my Global file last week because I thought this would 
helpstop more spam getting thruand of course folks are now emailing me 
saying they are missing mail..newsletters and such...

My question is "Why is it not possible with Declude 
to whitelist an email address and it only applies to that email address and not 
any others that might be in CC or BCC"?
Richard FarrisEthixs Online1.270.247. 
Office1.800.548.3877 Tech Support"Crossroads to a Cleaner 
Internet"

  - Original Message - 
  From: 
  Matt 
  To: Declude.JunkMail@declude.com 
  
  Sent: Monday, July 25, 2005 1:47 PM
  Subject: Re: [Declude.JunkMail] Filter 
  not triggering
  Kevin,Just a thought if you wanted to confirm this as a 
  bug, maybe try a filter for this same message, but match a full word to see if 
  it triggers. I did decode this segment and there is no additional 
  encoding or other tricks that would cause a filter to not hit.IMO, 
  knowing about bugs like this would be very helpful at times, especially 
  considering the time that it would take each one of us that was affected by it 
  to figure it out on our own. Maybe if Declude doesn't want to post this 
  information on their site, we could take it upon ourselves to share such 
  information with the list when it is discovered. This is for the most 
  part how the list used to function in the old days, though most of us seemed 
  to desire a page dedicated to the topic 
  regardless.MattKevin Bilbee wrote: 
  



Well that would explain why many of my filters are not as effective 
as they used to be. Has Declude announced when the fix will be 
available



Kevin Bilbee

  -Original Message-From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]]On 
  Behalf Of John CarterSent: Monday, July 25, 2005 8:05 
  AMTo: Declude.JunkMail@declude.comSubject: 
  RE: [Declude.JunkMail] Filter not triggering
  I have reported to Declude a problem with the 
  "CONTAINS" statement. Prior to 2.0.6 (or somewhere around 
  there)it worked oncharacter match, but after an upgrade to 
  Declude it only works on a word match. (In other words you could not 
  longer match on a string of characters within a word.) This would 
  affect your situation.
  
  I believe the fix is caught up in the wait for the 
  newest version (the one they are testing now.)
  
  John
  
  
  From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]] 
  On Behalf Of Kevin BilbeeSent: Monday, July 25, 2005 
  9:10 AMTo: JunkMail DecludeSubject: 
  [Declude.JunkMail] Filter not triggering
  The attached email is not getting trapped by 
  my STOCKFILTER??? Here are the log lines. They do not indicate any issues 
  with the STOCKFILTER. In the STOCKFILTER this line should be 
  hitting
  
  BODY 10CONTAINS (OTC:
  Any idea why this email is not triggering 
  this line and assigning 10 points Could declude not be decoding the 
  BASE64 This also seems to be an intermittent issue!
  
  
  07/24/2005 19:57:36 Q551E097C0333 Filter 
  HELOFILTER: Not skipping E-mail due to current weight of 2.07/24/2005 
  19:57:36 Q551E097C0333 Filter VIRUSTRAP: Not skipping E-mail due to 
  current weight of 2.07/24/2005 19:57:36 Q551E097C0333 Filter 
  REVDNSFILTER: Not skipping E-mail due to current weight of 
  2.07/24/2005 19:57:36 Q551E097C0333 Filter: Set max weight to 
  19.07/24/2005 19:57:36 Q551E097C0333 Filter: Set max weight to 
  13.07/24/2005 19:57:36 Q551E097C0333 Filter: Set max weight to 
  14.07/24/2005 19:57:36 Q551E097C0333 Filter: Set max weight to 
  5.07/24/2005 19:57:36 Q551E097C0333 Filter STOCKFILTER: Not 
  skipping E-mail due to current weight of 2.07/24/2005 19:57:36 
  Q551E097C0333 Filter: Set max weight to 15.07/24/2005 19:57:36 
  Q551E097C0333 Filter BODYFILTER: Not skipping E-mail due to current 
  weight of 2.07/24/2005 19:57:36 Q551E097C0333 NOABUSE:2 . 
  Total weight = 2.07/24/2005 19:57:36 Q551E097C0333 Using 
  [incoming] CFG file D:\IMAIL\Declude\$default$.junkmail.07/24/2005 
  19:57:36 Q551E097C0333 Redirecting [EMAIL PROTECTED] 
  to file 
  D:\Imail\declude\junkmailfiles\standardabrasives.com.junkmail.07/24/2005 
  19:57:36 Q551E097C0333 Msg failed NOABUSE ("Not supporting [EMAIL PROTECTED]"). Action="">07/24/2005 
  19:57:36 Q551E097C0333 Msg failed BASE64 (A binary encoded text or 
  HTML section was found in this E-mail.). Action="">07/24/2005 
  19:57:36 Q551E097C0333 L1 Message OK07/24/2005 19:57:36 
  Q551E097C0333 Subject: Stocks in Play07/24/2005 19:57:36 
  Q551E097C0333 From: [EMAIL PROTECTED] 
  To: [EMAIL PROTECTED] 
  IP: 200.182.78.150 ID: 

[Declude.JunkMail] Whitelisting

2005-04-26 Thread Chris Anton
Hi All,
Having trouble whitelisting a specific Class C IP range in Junkmail Standard.  
Using the WHITELIST IP 66.155.125 in global.cfg (separated by spaces, not 
tabs).  Syntax seems identical to the one listed in the manual. However, 
Junkmail is still running all tests on mail from this IP range.  Any thoughts?

Thanks for the Help!
-Chris

Chris Anton
Web Solutions, Inc.
Tel: 203-235- x25
---
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.


Re: [Declude.JunkMail] Whitelisting

2005-04-26 Thread Matt




I messed that up, it should be 66.155.125.0/24

Matt


Chris Anton wrote:

  Hi All,
Having trouble whitelisting a specific Class C IP range in Junkmail Standard.  Using the "WHITELIST IP 66.155.125" in global.cfg (separated by spaces, not tabs).  Syntax seems identical to the one listed in the manual. However, Junkmail is still running all tests on mail from this IP range.  Any thoughts?

Thanks for the Help!
-Chris

Chris Anton
Web Solutions, Inc.
Tel: 203-235- x25
---
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.


  


-- 
=
MailPure custom filters for Declude JunkMail Pro.
http://www.mailpure.com/software/
=




Re: [Declude.JunkMail] Whitelisting

2005-04-26 Thread Matt
Chris,
That's not a valid entry, you only have three of the dotted quads and 
the Global.cfg requires either a full IP or a CIDR range.  For the class 
C you would want to use 66.155.125/24.

Matt

Chris Anton wrote:
Hi All,
Having trouble whitelisting a specific Class C IP range in Junkmail Standard.  Using the 
WHITELIST IP 66.155.125 in global.cfg (separated by spaces, not tabs).  
Syntax seems identical to the one listed in the manual. However, Junkmail is still 
running all tests on mail from this IP range.  Any thoughts?
Thanks for the Help!
-Chris
Chris Anton
Web Solutions, Inc.
Tel: 203-235- x25
---
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.
 

--
=
MailPure custom filters for Declude JunkMail Pro.
http://www.mailpure.com/software/
=
---
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.


Re: [Declude.JunkMail] Whitelisting

2005-04-26 Thread Chris Anton
Matt,
Thanks, that fixed it right away.
-Chris
---
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.


Re: [Declude.JunkMail] Whitelisting our Domain

2005-04-05 Thread Jeff Pereira
someone please tell me that this was a joke.


- Original Message - 
From: Imail Admin [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 6:18 PM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain


 Just curious: does SmarterMail use SMTP or something similar?
 
 Ben
 

---
[This E-mail scanned for viruses by Declude Virus]

---
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.


Re: [Declude.JunkMail] Whitelisting our Domain

2005-04-05 Thread Dan Geiser
I think it uses STP...The Racer's Edge.

- Original Message - 
From: Imail Admin [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 6:18 PM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain


 Just curious: does SmarterMail use SMTP or something similar?

 Ben

 - Original Message - 
 From: Darin Cox [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Monday, April 04, 2005 7:39 AM
 Subject: Re: [Declude.JunkMail] Whitelisting our Domain


  Yes.
 
  If all users send through your server, then use SMTP AUTH on all clients
 and
  configure Junkmail to whitelist AUTHing users.  If not, but all mail
comes
  in from static IPs, you could use an IP whitelist to bypass for those
IPs.
 
  Darin.
 
 
  - Original Message - 
  From: Kevin Stanford [EMAIL PROTECTED]
  To: Declude.JunkMail@declude.com
  Sent: Monday, April 04, 2005 10:25 AM
  Subject: [Declude.JunkMail] Whitelisting our Domain
 
 
  If we whitelist our domain will Spam that spoofs our email addresses and
  domain also be whitelisted? If so, how can I circumvent it?
 
  Thanks,
 
  Kevin
 
  ---
  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 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 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.
 ---
 E-mail scanned for viruses by Nexus (http://www.ntgrp.com/mailscan)





---
E-mail scanned for viruses by Nexus (http://www.ntgrp.com/mailscan)

---
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.


RE: [Declude.JunkMail] Whitelisting our Domain

2005-04-05 Thread Dan Horne
No, it uses MTP, the precursor to SMTP. 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dan Geiser
Sent: Tuesday, April 05, 2005 10:35 AM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting our Domain

I think it uses STP...The Racer's Edge.

- Original Message -
From: Imail Admin [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 6:18 PM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain


 Just curious: does SmarterMail use SMTP or something similar?

 Ben

 - Original Message - 
 From: Darin Cox [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Monday, April 04, 2005 7:39 AM
 Subject: Re: [Declude.JunkMail] Whitelisting our Domain


  Yes.
 
  If all users send through your server, then use SMTP AUTH on all
clients
 and
  configure Junkmail to whitelist AUTHing users.  If not, but all mail
comes
  in from static IPs, you could use an IP whitelist to bypass for
those
IPs.
 
  Darin.
 
 
  - Original Message - 
  From: Kevin Stanford [EMAIL PROTECTED]
  To: Declude.JunkMail@declude.com
  Sent: Monday, April 04, 2005 10:25 AM
  Subject: [Declude.JunkMail] Whitelisting our Domain
 
 
  If we whitelist our domain will Spam that spoofs our email addresses
and
  domain also be whitelisted? If so, how can I circumvent it?
 
  Thanks,
 
  Kevin
 
  ---
  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 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 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.
 ---
 E-mail scanned for viruses by Nexus (http://www.ntgrp.com/mailscan)





---
E-mail scanned for viruses by Nexus (http://www.ntgrp.com/mailscan)

---
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 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.


Re: [Declude.JunkMail] Whitelisting our Domain

2005-04-05 Thread Imail Admin
Alright guys, it was only a typo, no need to get in  a huff.  If you had
looked at Darin's message that I quoted, you would see he was talking about
SMTP Auth, and that was my question, not just SMTP.  My fingers just can't
keep up with my thoughts.  We use IMail 7.15, which does not support SMTP
Auth, and that's just about the only feature I regret missing from 8.x.  We
plan to look at Smarter Mail at some point, and I was curious if they had a
similar feature so that we can whitelist our domains (which was the topic
here, remember?) with Declude JM.  Feel better?

Ben

P.S. Actually, we don't use SMTP either.  We take each mesasge that is to go
out, hand write them on small slips of paper, tie those to the backs of
squirrels, and send those out the door.  We tried sending the scraps of
paper by US Mail, but that was less reliable.

- Original Message - 
From: Dan Horne [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Tuesday, April 05, 2005 8:07 AM
Subject: RE: [Declude.JunkMail] Whitelisting our Domain


No, it uses MTP, the precursor to SMTP.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dan Geiser
Sent: Tuesday, April 05, 2005 10:35 AM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting our Domain

I think it uses STP...The Racer's Edge.

- Original Message -
From: Imail Admin [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 6:18 PM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain


 Just curious: does SmarterMail use SMTP or something similar?

 Ben

 - Original Message - 
 From: Darin Cox [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Monday, April 04, 2005 7:39 AM
 Subject: Re: [Declude.JunkMail] Whitelisting our Domain


  Yes.
 
  If all users send through your server, then use SMTP AUTH on all
clients
 and
  configure Junkmail to whitelist AUTHing users.  If not, but all mail
comes
  in from static IPs, you could use an IP whitelist to bypass for
those
IPs.
 
  Darin.
 
 
  - Original Message - 
  From: Kevin Stanford [EMAIL PROTECTED]
  To: Declude.JunkMail@declude.com
  Sent: Monday, April 04, 2005 10:25 AM
  Subject: [Declude.JunkMail] Whitelisting our Domain
 
 
  If we whitelist our domain will Spam that spoofs our email addresses
and
  domain also be whitelisted? If so, how can I circumvent it?
 
  Thanks,
 
  Kevin
 
  ---
  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 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 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.
 ---
 E-mail scanned for viruses by Nexus (http://www.ntgrp.com/mailscan)





---
E-mail scanned for viruses by Nexus (http://www.ntgrp.com/mailscan)

---
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 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 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.


Re: [Declude.JunkMail] Whitelisting our Domain

2005-04-05 Thread Matt




Someone reported recently that WHITELIST AUTH won't yet work with
SmarterMail because it isn't sharing that information in a format that
Declude can use, but apparently they are considering adding it to their
next major version.

That's definitely a deal breaker for me until it comes. I suspect that
there might be other minutia that I rely upon that could cause issues,
and I'm hoping to learn more from others as people start to migrate.

Matt



Imail Admin wrote:

  Alright guys, it was only a typo, no need to get in  a huff.  If you had
looked at Darin's message that I quoted, you would see he was talking about
SMTP Auth, and that was my question, not just SMTP.  My fingers just can't
keep up with my thoughts.  We use IMail 7.15, which does not support SMTP
Auth, and that's just about the only feature I regret missing from 8.x.  We
plan to look at Smarter Mail at some point, and I was curious if they had a
similar feature so that we can whitelist our domains (which was the topic
here, remember?) with Declude JM.  Feel better?

Ben

P.S. Actually, we don't use SMTP either.  We take each mesasge that is to go
out, hand write them on small slips of paper, tie those to the backs of
squirrels, and send those out the door.  We tried sending the scraps of
paper by US Mail, but that was less reliable.

- Original Message - 
From: "Dan Horne" [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Tuesday, April 05, 2005 8:07 AM
Subject: RE: [Declude.JunkMail] Whitelisting our Domain


No, it uses MTP, the precursor to SMTP.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Dan Geiser
Sent: Tuesday, April 05, 2005 10:35 AM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting our Domain

I think it uses STP...The Racer's Edge.

- Original Message -
From: "Imail Admin" [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 6:18 PM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain


  
  
Just curious: does SmarterMail use SMTP or something similar?

Ben

- Original Message - 
From: "Darin Cox" [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 7:39 AM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain




  Yes.

If all users send through your server, then use SMTP AUTH on all
  

  
  clients
  
  
and


  configure Junkmail to whitelist AUTHing users.  If not, but all mail
  

  
  comes
  
  

  in from static IPs, you could use an IP whitelist to bypass for
  

  
  those
IPs.
  
  

  Darin.


- Original Message - 
From: "Kevin Stanford" [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 10:25 AM
Subject: [Declude.JunkMail] Whitelisting our Domain


If we whitelist our domain will Spam that spoofs our email addresses
  

  
  and
  
  

  domain also be whitelisted? If so, how can I circumvent it?

Thanks,

Kevin

---
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 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 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.
---
E-mail scanned for viruses by Nexus (http://www.ntgrp.com/mailscan)




  
  

---
E-mail scanned for viruses by Nexus (http://www.ntgrp.com/mailscan)

---
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 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 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.


  


-- 
=
MailPure custom filters for Declude JunkMail Pro.
http://www.mailpure.com/software/
=




RE: [Declude.JunkMail] Whitelisting our Domain

2005-04-05 Thread Dan Horne
Actually it isn't that Imail 7 doesn't support SMTP Auth, it does.  It's
that it doesn't report whether a user has Authed in the message
envelope, which was added in 8.  Declude looks at the envelope for the
WHITELIST AUTH feature. 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Imail Admin
Sent: Tuesday, April 05, 2005 5:10 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting our Domain

Alright guys, it was only a typo, no need to get in  a huff.  If you had
looked at Darin's message that I quoted, you would see he was talking
about SMTP Auth, and that was my question, not just SMTP.  My fingers
just can't keep up with my thoughts.  We use IMail 7.15, which does not
support SMTP Auth, and that's just about the only feature I regret
missing from 8.x.  We plan to look at Smarter Mail at some point, and I
was curious if they had a similar feature so that we can whitelist our
domains (which was the topic here, remember?) with Declude JM.  Feel
better?

Ben

P.S. Actually, we don't use SMTP either.  We take each mesasge that is
to go out, hand write them on small slips of paper, tie those to the
backs of squirrels, and send those out the door.  We tried sending the
scraps of paper by US Mail, but that was less reliable.

- Original Message -
From: Dan Horne [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Tuesday, April 05, 2005 8:07 AM
Subject: RE: [Declude.JunkMail] Whitelisting our Domain


No, it uses MTP, the precursor to SMTP.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dan Geiser
Sent: Tuesday, April 05, 2005 10:35 AM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting our Domain

I think it uses STP...The Racer's Edge.

- Original Message -
From: Imail Admin [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 6:18 PM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain


 Just curious: does SmarterMail use SMTP or something similar?

 Ben

 - Original Message - 
 From: Darin Cox [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Monday, April 04, 2005 7:39 AM
 Subject: Re: [Declude.JunkMail] Whitelisting our Domain


  Yes.
 
  If all users send through your server, then use SMTP AUTH on all
clients
 and
  configure Junkmail to whitelist AUTHing users.  If not, but all mail
comes
  in from static IPs, you could use an IP whitelist to bypass for
those
IPs.
 
  Darin.
 
 
  - Original Message - 
  From: Kevin Stanford [EMAIL PROTECTED]
  To: Declude.JunkMail@declude.com
  Sent: Monday, April 04, 2005 10:25 AM
  Subject: [Declude.JunkMail] Whitelisting our Domain
 
 
  If we whitelist our domain will Spam that spoofs our email addresses
and
  domain also be whitelisted? If so, how can I circumvent it?
 
  Thanks,
 
  Kevin
 
  ---
  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 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 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.
 ---
 E-mail scanned for viruses by Nexus (http://www.ntgrp.com/mailscan)





---
E-mail scanned for viruses by Nexus (http://www.ntgrp.com/mailscan)

---
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 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 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 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.


Re: [Declude.JunkMail] Whitelisting our Domain

2005-04-05 Thread Darin Cox
Being in Florida, we use gators.  We tried the usual pigeons initially, but
they got eaten by the gators.  Some of the messages actually still made it
to the intended destination as the gators sought out the recipients' pools,
but we opted to just use them directly instead of messing with the pigeons
at all.  Works pretty well for those near the rivers and lakes, but we have
gotten few complaints about slow delivery from those who aren't.  Usually
the complaints stop once the messages actually arrive, though.

On a more serious note, I believe SmarterMail will pass the SMTP Auth info
on to Declude.  Hopefully someone at CPHZ will chime in on this to verify
that WHITELIST AUTH does work with SmarterMail.

Darin.


- Original Message - 
From: Imail Admin [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Tuesday, April 05, 2005 5:10 PM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain


Alright guys, it was only a typo, no need to get in  a huff.  If you had
looked at Darin's message that I quoted, you would see he was talking about
SMTP Auth, and that was my question, not just SMTP.  My fingers just can't
keep up with my thoughts.  We use IMail 7.15, which does not support SMTP
Auth, and that's just about the only feature I regret missing from 8.x.  We
plan to look at Smarter Mail at some point, and I was curious if they had a
similar feature so that we can whitelist our domains (which was the topic
here, remember?) with Declude JM.  Feel better?

Ben

P.S. Actually, we don't use SMTP either.  We take each mesasge that is to go
out, hand write them on small slips of paper, tie those to the backs of
squirrels, and send those out the door.  We tried sending the scraps of
paper by US Mail, but that was less reliable.

- Original Message - 
From: Dan Horne [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Tuesday, April 05, 2005 8:07 AM
Subject: RE: [Declude.JunkMail] Whitelisting our Domain


No, it uses MTP, the precursor to SMTP.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dan Geiser
Sent: Tuesday, April 05, 2005 10:35 AM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting our Domain

I think it uses STP...The Racer's Edge.

- Original Message -
From: Imail Admin [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 6:18 PM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain


 Just curious: does SmarterMail use SMTP or something similar?

 Ben

 - Original Message - 
 From: Darin Cox [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Monday, April 04, 2005 7:39 AM
 Subject: Re: [Declude.JunkMail] Whitelisting our Domain


  Yes.
 
  If all users send through your server, then use SMTP AUTH on all
clients
 and
  configure Junkmail to whitelist AUTHing users.  If not, but all mail
comes
  in from static IPs, you could use an IP whitelist to bypass for
those
IPs.
 
  Darin.
 
 
  - Original Message - 
  From: Kevin Stanford [EMAIL PROTECTED]
  To: Declude.JunkMail@declude.com
  Sent: Monday, April 04, 2005 10:25 AM
  Subject: [Declude.JunkMail] Whitelisting our Domain
 
 
  If we whitelist our domain will Spam that spoofs our email addresses
and
  domain also be whitelisted? If so, how can I circumvent it?
 
  Thanks,
 
  Kevin
 
  ---
  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 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 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.
 ---
 E-mail scanned for viruses by Nexus (http://www.ntgrp.com/mailscan)





---
E-mail scanned for viruses by Nexus (http://www.ntgrp.com/mailscan)

---
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 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 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 came

Re: [Declude.JunkMail] Whitelisting our Domain

2005-04-05 Thread Darin Cox
Ok, I see Matt chimed in to let us know that CPHZ and SmarterTools are still
working on getting WHITELIST AUTH to work.

Darin.


- Original Message - 
From: Darin Cox [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Tuesday, April 05, 2005 5:34 PM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain


Being in Florida, we use gators.  We tried the usual pigeons initially, but
they got eaten by the gators.  Some of the messages actually still made it
to the intended destination as the gators sought out the recipients' pools,
but we opted to just use them directly instead of messing with the pigeons
at all.  Works pretty well for those near the rivers and lakes, but we have
gotten few complaints about slow delivery from those who aren't.  Usually
the complaints stop once the messages actually arrive, though.

On a more serious note, I believe SmarterMail will pass the SMTP Auth info
on to Declude.  Hopefully someone at CPHZ will chime in on this to verify
that WHITELIST AUTH does work with SmarterMail.

Darin.


- Original Message - 
From: Imail Admin [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Tuesday, April 05, 2005 5:10 PM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain


Alright guys, it was only a typo, no need to get in  a huff.  If you had
looked at Darin's message that I quoted, you would see he was talking about
SMTP Auth, and that was my question, not just SMTP.  My fingers just can't
keep up with my thoughts.  We use IMail 7.15, which does not support SMTP
Auth, and that's just about the only feature I regret missing from 8.x.  We
plan to look at Smarter Mail at some point, and I was curious if they had a
similar feature so that we can whitelist our domains (which was the topic
here, remember?) with Declude JM.  Feel better?

Ben

P.S. Actually, we don't use SMTP either.  We take each mesasge that is to go
out, hand write them on small slips of paper, tie those to the backs of
squirrels, and send those out the door.  We tried sending the scraps of
paper by US Mail, but that was less reliable.

- Original Message - 
From: Dan Horne [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Tuesday, April 05, 2005 8:07 AM
Subject: RE: [Declude.JunkMail] Whitelisting our Domain


No, it uses MTP, the precursor to SMTP.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dan Geiser
Sent: Tuesday, April 05, 2005 10:35 AM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting our Domain

I think it uses STP...The Racer's Edge.

- Original Message -
From: Imail Admin [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 6:18 PM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain


 Just curious: does SmarterMail use SMTP or something similar?

 Ben

 - Original Message - 
 From: Darin Cox [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Monday, April 04, 2005 7:39 AM
 Subject: Re: [Declude.JunkMail] Whitelisting our Domain


  Yes.
 
  If all users send through your server, then use SMTP AUTH on all
clients
 and
  configure Junkmail to whitelist AUTHing users.  If not, but all mail
comes
  in from static IPs, you could use an IP whitelist to bypass for
those
IPs.
 
  Darin.
 
 
  - Original Message - 
  From: Kevin Stanford [EMAIL PROTECTED]
  To: Declude.JunkMail@declude.com
  Sent: Monday, April 04, 2005 10:25 AM
  Subject: [Declude.JunkMail] Whitelisting our Domain
 
 
  If we whitelist our domain will Spam that spoofs our email addresses
and
  domain also be whitelisted? If so, how can I circumvent it?
 
  Thanks,
 
  Kevin
 
  ---
  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 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 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.
 ---
 E-mail scanned for viruses by Nexus (http://www.ntgrp.com/mailscan)





---
E-mail scanned for viruses by Nexus (http://www.ntgrp.com/mailscan)

---
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 came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type

RE: [Declude.JunkMail] Whitelisting our Domain

2005-04-05 Thread Kevin Bilbee
See previous post

SmarterMail does support SMTP Auth but it does not at this time spaa that
info off to declude.


Kevin Bilbee

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of Darin Cox
 Sent: Tuesday, April 05, 2005 2:34 PM
 To: Declude.JunkMail@declude.com
 Subject: Re: [Declude.JunkMail] Whitelisting our Domain


 Being in Florida, we use gators.  We tried the usual pigeons
 initially, but
 they got eaten by the gators.  Some of the messages actually still made it
 to the intended destination as the gators sought out the
 recipients' pools,
 but we opted to just use them directly instead of messing with the pigeons
 at all.  Works pretty well for those near the rivers and lakes,
 but we have
 gotten few complaints about slow delivery from those who aren't.  Usually
 the complaints stop once the messages actually arrive, though.

 On a more serious note, I believe SmarterMail will pass the SMTP Auth info
 on to Declude.  Hopefully someone at CPHZ will chime in on this to verify
 that WHITELIST AUTH does work with SmarterMail.

 Darin.


 - Original Message -
 From: Imail Admin [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Tuesday, April 05, 2005 5:10 PM
 Subject: Re: [Declude.JunkMail] Whitelisting our Domain


 Alright guys, it was only a typo, no need to get in  a huff.  If you had
 looked at Darin's message that I quoted, you would see he was
 talking about
 SMTP Auth, and that was my question, not just SMTP.  My fingers just can't
 keep up with my thoughts.  We use IMail 7.15, which does not support SMTP
 Auth, and that's just about the only feature I regret missing
 from 8.x.  We
 plan to look at Smarter Mail at some point, and I was curious if
 they had a
 similar feature so that we can whitelist our domains (which was the topic
 here, remember?) with Declude JM.  Feel better?

 Ben

 P.S. Actually, we don't use SMTP either.  We take each mesasge
 that is to go
 out, hand write them on small slips of paper, tie those to the backs of
 squirrels, and send those out the door.  We tried sending the scraps of
 paper by US Mail, but that was less reliable.

 - Original Message -
 From: Dan Horne [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Tuesday, April 05, 2005 8:07 AM
 Subject: RE: [Declude.JunkMail] Whitelisting our Domain


 No, it uses MTP, the precursor to SMTP.

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Dan Geiser
 Sent: Tuesday, April 05, 2005 10:35 AM
 To: Declude.JunkMail@declude.com
 Subject: Re: [Declude.JunkMail] Whitelisting our Domain

 I think it uses STP...The Racer's Edge.

 - Original Message -
 From: Imail Admin [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Monday, April 04, 2005 6:18 PM
 Subject: Re: [Declude.JunkMail] Whitelisting our Domain


  Just curious: does SmarterMail use SMTP or something similar?
 
  Ben
 
  - Original Message -
  From: Darin Cox [EMAIL PROTECTED]
  To: Declude.JunkMail@declude.com
  Sent: Monday, April 04, 2005 7:39 AM
  Subject: Re: [Declude.JunkMail] Whitelisting our Domain
 
 
   Yes.
  
   If all users send through your server, then use SMTP AUTH on all
 clients
  and
   configure Junkmail to whitelist AUTHing users.  If not, but all mail
 comes
   in from static IPs, you could use an IP whitelist to bypass for
 those
 IPs.
  
   Darin.
  
  
   - Original Message -
   From: Kevin Stanford [EMAIL PROTECTED]
   To: Declude.JunkMail@declude.com
   Sent: Monday, April 04, 2005 10:25 AM
   Subject: [Declude.JunkMail] Whitelisting our Domain
  
  
   If we whitelist our domain will Spam that spoofs our email addresses
 and
   domain also be whitelisted? If so, how can I circumvent it?
  
   Thanks,
  
   Kevin
  
   ---
   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 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 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.
  ---
  E-mail scanned for viruses by Nexus (http://www.ntgrp.com/mailscan)
 
 
 


 ---
 E-mail scanned for viruses by Nexus (http://www.ntgrp.com/mailscan)

 ---
 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

RE: [Declude.JunkMail] Whitelisting our Domain

2005-04-05 Thread Kevin Bilbee



According to SmarterMail it will be availabel in 3.0 which will be 
availabel arrount August.


Kevin 
Bilbee

  -Original Message-From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]On Behalf Of 
  MattSent: Tuesday, April 05, 2005 2:27 PMTo: 
  Declude.JunkMail@declude.comSubject: Re: [Declude.JunkMail] 
  Whitelisting our DomainSomeone reported recently that 
  WHITELIST AUTH won't yet work with SmarterMail because it isn't sharing that 
  information in a format that Declude can use, but apparently they are 
  considering adding it to their next major version.That's definitely a 
  deal breaker for me until it comes. I suspect that there might be other 
  minutia that I rely upon that could cause issues, and I'm hoping to learn more 
  from others as people start to migrate.MattImail Admin 
  wrote: 
  Alright guys, it was only a typo, no need to get in  a huff.  If you had
looked at Darin's message that I quoted, you would see he was talking about
SMTP Auth, and that was my question, not just SMTP.  My fingers just can't
keep up with my thoughts.  We use IMail 7.15, which does not support SMTP
Auth, and that's just about the only feature I regret missing from 8.x.  We
plan to look at Smarter Mail at some point, and I was curious if they had a
similar feature so that we can whitelist our domains (which was the topic
here, remember?) with Declude JM.  Feel better?

Ben

P.S. Actually, we don't use SMTP either.  We take each mesasge that is to go
out, hand write them on small slips of paper, tie those to the backs of
squirrels, and send those out the door.  We tried sending the scraps of
paper by US Mail, but that was less reliable.

- Original Message - 
From: "Dan Horne" [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Tuesday, April 05, 2005 8:07 AM
Subject: RE: [Declude.JunkMail] Whitelisting our Domain


No, it uses MTP, the precursor to SMTP.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Dan Geiser
Sent: Tuesday, April 05, 2005 10:35 AM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting our Domain

I think it uses STP...The Racer's Edge.

- Original Message -
From: "Imail Admin" [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 6:18 PM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain


  
Just curious: does SmarterMail use SMTP or something similar?

Ben

- Original Message - 
From: "Darin Cox" [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 7:39 AM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain



  Yes.

If all users send through your server, then use SMTP AUTH on all
  clients
  
and

  configure Junkmail to whitelist AUTHing users.  If not, but all mail
  comes
  

  in from static IPs, you could use an IP whitelist to bypass for
  those
IPs.
  

  Darin.


- Original Message - 
From: "Kevin Stanford" [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 10:25 AM
Subject: [Declude.JunkMail] Whitelisting our Domain


If we whitelist our domain will Spam that spoofs our email addresses
  and
  

  domain also be whitelisted? If so, how can I circumvent it?

Thanks,

Kevin

---
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 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 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.
---
E-mail scanned for viruses by Nexus (http://www.ntgrp.com/mailscan)





---
E-mail scanned for viruses by Nexus (http://www.ntgrp.com/mailscan)

---
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 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 came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type

RE: [Declude.JunkMail] Whitelisting our Domain

2005-04-05 Thread Michael Jaworski
My reading was Declude uses the SmartMail Address book as it is used in
iMail but does not yet look at the white list feature in SmarterMail.

Michael Jaworski
Puget Sound Network, Inc.



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kevin Bilbee
Sent: Tuesday, April 05, 2005 3:00 PM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] Whitelisting our Domain


See previous post

SmarterMail does support SMTP Auth but it does not at this time spaa that
info off to declude.


Kevin Bilbee

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of Darin Cox
 Sent: Tuesday, April 05, 2005 2:34 PM
 To: Declude.JunkMail@declude.com
 Subject: Re: [Declude.JunkMail] Whitelisting our Domain


 Being in Florida, we use gators.  We tried the usual pigeons 
 initially, but they got eaten by the gators.  Some of the messages 
 actually still made it to the intended destination as the gators 
 sought out the recipients' pools,
 but we opted to just use them directly instead of messing with the pigeons
 at all.  Works pretty well for those near the rivers and lakes,
 but we have
 gotten few complaints about slow delivery from those who aren't.  Usually
 the complaints stop once the messages actually arrive, though.

 On a more serious note, I believe SmarterMail will pass the SMTP Auth 
 info on to Declude.  Hopefully someone at CPHZ will chime in on this 
 to verify that WHITELIST AUTH does work with SmarterMail.

 Darin.


 - Original Message -
 From: Imail Admin [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Tuesday, April 05, 2005 5:10 PM
 Subject: Re: [Declude.JunkMail] Whitelisting our Domain


 Alright guys, it was only a typo, no need to get in  a huff.  If you 
 had looked at Darin's message that I quoted, you would see he was 
 talking about SMTP Auth, and that was my question, not just SMTP.  My 
 fingers just can't keep up with my thoughts.  We use IMail 7.15, which 
 does not support SMTP Auth, and that's just about the only feature I 
 regret missing from 8.x.  We
 plan to look at Smarter Mail at some point, and I was curious if
 they had a
 similar feature so that we can whitelist our domains (which was the topic
 here, remember?) with Declude JM.  Feel better?

 Ben

 P.S. Actually, we don't use SMTP either.  We take each mesasge that is 
 to go out, hand write them on small slips of paper, tie those to the 
 backs of squirrels, and send those out the door.  We tried sending the 
 scraps of paper by US Mail, but that was less reliable.

 - Original Message -
 From: Dan Horne [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Tuesday, April 05, 2005 8:07 AM
 Subject: RE: [Declude.JunkMail] Whitelisting our Domain


 No, it uses MTP, the precursor to SMTP.

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Dan Geiser
 Sent: Tuesday, April 05, 2005 10:35 AM
 To: Declude.JunkMail@declude.com
 Subject: Re: [Declude.JunkMail] Whitelisting our Domain

 I think it uses STP...The Racer's Edge.

 - Original Message -
 From: Imail Admin [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Monday, April 04, 2005 6:18 PM
 Subject: Re: [Declude.JunkMail] Whitelisting our Domain


  Just curious: does SmarterMail use SMTP or something similar?
 
  Ben
 
  - Original Message -
  From: Darin Cox [EMAIL PROTECTED]
  To: Declude.JunkMail@declude.com
  Sent: Monday, April 04, 2005 7:39 AM
  Subject: Re: [Declude.JunkMail] Whitelisting our Domain
 
 
   Yes.
  
   If all users send through your server, then use SMTP AUTH on all
 clients
  and
   configure Junkmail to whitelist AUTHing users.  If not, but all 
   mail
 comes
   in from static IPs, you could use an IP whitelist to bypass for
 those
 IPs.
  
   Darin.
  
  
   - Original Message -
   From: Kevin Stanford [EMAIL PROTECTED]
   To: Declude.JunkMail@declude.com
   Sent: Monday, April 04, 2005 10:25 AM
   Subject: [Declude.JunkMail] Whitelisting our Domain
  
  
   If we whitelist our domain will Spam that spoofs our email 
   addresses
 and
   domain also be whitelisted? If so, how can I circumvent it?
  
   Thanks,
  
   Kevin
  
   ---
   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 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 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

Re: [Declude.JunkMail] Whitelisting our Domain

2005-04-05 Thread Matt




The only thing that I know is from the following post:


http://www.mail-archive.com/declude.junkmail@declude.com/msg23838.html

Matt



Darin Cox wrote:

  Ok, I see Matt chimed in to let us know that CPHZ and SmarterTools are still
working on getting WHITELIST AUTH to work.

Darin.


- Original Message - 
From: "Darin Cox" [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Tuesday, April 05, 2005 5:34 PM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain


Being in Florida, we use gators.  We tried the usual pigeons initially, but
they got eaten by the gators.  Some of the messages actually still made it
to the intended destination as the gators sought out the recipients' pools,
but we opted to just use them directly instead of messing with the pigeons
at all.  Works pretty well for those near the rivers and lakes, but we have
gotten few complaints about slow delivery from those who aren't.  Usually
the complaints stop once the messages actually arrive, though.

On a more serious note, I believe SmarterMail will pass the SMTP Auth info
on to Declude.  Hopefully someone at CPHZ will chime in on this to verify
that WHITELIST AUTH does work with SmarterMail.

Darin.


- Original Message - 
From: "Imail Admin" [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Tuesday, April 05, 2005 5:10 PM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain


Alright guys, it was only a typo, no need to get in  a huff.  If you had
looked at Darin's message that I quoted, you would see he was talking about
SMTP Auth, and that was my question, not just SMTP.  My fingers just can't
keep up with my thoughts.  We use IMail 7.15, which does not support SMTP
Auth, and that's just about the only feature I regret missing from 8.x.  We
plan to look at Smarter Mail at some point, and I was curious if they had a
similar feature so that we can whitelist our domains (which was the topic
here, remember?) with Declude JM.  Feel better?

Ben

P.S. Actually, we don't use SMTP either.  We take each mesasge that is to go
out, hand write them on small slips of paper, tie those to the backs of
squirrels, and send those out the door.  We tried sending the scraps of
paper by US Mail, but that was less reliable.

- Original Message - 
From: "Dan Horne" [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Tuesday, April 05, 2005 8:07 AM
Subject: RE: [Declude.JunkMail] Whitelisting our Domain


No, it uses MTP, the precursor to SMTP.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Dan Geiser
Sent: Tuesday, April 05, 2005 10:35 AM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting our Domain

I think it uses STP...The Racer's Edge.

- Original Message -
From: "Imail Admin" [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 6:18 PM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain


  
  
Just curious: does SmarterMail use SMTP or something similar?

Ben

- Original Message - 
From: "Darin Cox" [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 7:39 AM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain




  Yes.

If all users send through your server, then use SMTP AUTH on all
  

  
  clients
  
  
and


  configure Junkmail to whitelist AUTHing users.  If not, but all mail
  

  
  comes
  
  

  in from static IPs, you could use an IP whitelist to bypass for
  

  
  those
IPs.
  
  

  Darin.


- Original Message - 
From: "Kevin Stanford" [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 10:25 AM
Subject: [Declude.JunkMail] Whitelisting our Domain


If we whitelist our domain will Spam that spoofs our email addresses
  

  
  and
  
  

  domain also be whitelisted? If so, how can I circumvent it?

Thanks,

Kevin

---
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 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 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.
---
E-mail scanned for viruses by Nexus (http://www.ntgrp.com/mailscan)




  
  

---
E-mail scanned for viruses by Nex

RE: [Declude.JunkMail] Whitelisting our Domain

2005-04-05 Thread John Tolmachoff \(Lists\)
Looking at the address book/list/file is entirely different than WHITELIST
AUTH.

Using the address file is AUTOWHITELIST either ON or OFF.

John T
eServices For You


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-
 [EMAIL PROTECTED] On Behalf Of Michael Jaworski
 Sent: Tuesday, April 05, 2005 3:06 PM
 To: Declude.JunkMail@declude.com
 Subject: RE: [Declude.JunkMail] Whitelisting our Domain
 
 My reading was Declude uses the SmartMail Address book as it is used in
 iMail but does not yet look at the white list feature in SmarterMail.
 
 Michael Jaworski
 Puget Sound Network, Inc.
 
 
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Bilbee
 Sent: Tuesday, April 05, 2005 3:00 PM
 To: Declude.JunkMail@declude.com
 Subject: RE: [Declude.JunkMail] Whitelisting our Domain
 
 
 See previous post
 
 SmarterMail does support SMTP Auth but it does not at this time spaa that
 info off to declude.
 
 
 Kevin Bilbee
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] Behalf Of Darin Cox
  Sent: Tuesday, April 05, 2005 2:34 PM
  To: Declude.JunkMail@declude.com
  Subject: Re: [Declude.JunkMail] Whitelisting our Domain
 
 
  Being in Florida, we use gators.  We tried the usual pigeons
  initially, but they got eaten by the gators.  Some of the messages
  actually still made it to the intended destination as the gators
  sought out the recipients' pools,
  but we opted to just use them directly instead of messing with the
pigeons
  at all.  Works pretty well for those near the rivers and lakes,
  but we have
  gotten few complaints about slow delivery from those who aren't.
Usually
  the complaints stop once the messages actually arrive, though.
 
  On a more serious note, I believe SmarterMail will pass the SMTP Auth
  info on to Declude.  Hopefully someone at CPHZ will chime in on this
  to verify that WHITELIST AUTH does work with SmarterMail.
 
  Darin.
 
 
  - Original Message -
  From: Imail Admin [EMAIL PROTECTED]
  To: Declude.JunkMail@declude.com
  Sent: Tuesday, April 05, 2005 5:10 PM
  Subject: Re: [Declude.JunkMail] Whitelisting our Domain
 
 
  Alright guys, it was only a typo, no need to get in  a huff.  If you
  had looked at Darin's message that I quoted, you would see he was
  talking about SMTP Auth, and that was my question, not just SMTP.  My
  fingers just can't keep up with my thoughts.  We use IMail 7.15, which
  does not support SMTP Auth, and that's just about the only feature I
  regret missing from 8.x.  We
  plan to look at Smarter Mail at some point, and I was curious if
  they had a
  similar feature so that we can whitelist our domains (which was the
topic
  here, remember?) with Declude JM.  Feel better?
 
  Ben
 
  P.S. Actually, we don't use SMTP either.  We take each mesasge that is
  to go out, hand write them on small slips of paper, tie those to the
  backs of squirrels, and send those out the door.  We tried sending the
  scraps of paper by US Mail, but that was less reliable.
 
  - Original Message -
  From: Dan Horne [EMAIL PROTECTED]
  To: Declude.JunkMail@declude.com
  Sent: Tuesday, April 05, 2005 8:07 AM
  Subject: RE: [Declude.JunkMail] Whitelisting our Domain
 
 
  No, it uses MTP, the precursor to SMTP.
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of Dan Geiser
  Sent: Tuesday, April 05, 2005 10:35 AM
  To: Declude.JunkMail@declude.com
  Subject: Re: [Declude.JunkMail] Whitelisting our Domain
 
  I think it uses STP...The Racer's Edge.
 
  - Original Message -
  From: Imail Admin [EMAIL PROTECTED]
  To: Declude.JunkMail@declude.com
  Sent: Monday, April 04, 2005 6:18 PM
  Subject: Re: [Declude.JunkMail] Whitelisting our Domain
 
 
   Just curious: does SmarterMail use SMTP or something similar?
  
   Ben
  
   - Original Message -
   From: Darin Cox [EMAIL PROTECTED]
   To: Declude.JunkMail@declude.com
   Sent: Monday, April 04, 2005 7:39 AM
   Subject: Re: [Declude.JunkMail] Whitelisting our Domain
  
  
Yes.
   
If all users send through your server, then use SMTP AUTH on all
  clients
   and
configure Junkmail to whitelist AUTHing users.  If not, but all
mail
  comes
in from static IPs, you could use an IP whitelist to bypass for
  those
  IPs.
   
Darin.
   
   
- Original Message -
From: Kevin Stanford [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 10:25 AM
Subject: [Declude.JunkMail] Whitelisting our Domain
   
   
If we whitelist our domain will Spam that spoofs our email
addresses
  and
domain also be whitelisted? If so, how can I circumvent it?
   
Thanks,
   
Kevin
   
---
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

[Declude.JunkMail] Whitelisting our Domain

2005-04-04 Thread Kevin Stanford
If we whitelist our domain will Spam that spoofs our email addresses and 
domain also be whitelisted? If so, how can I circumvent it?

Thanks,
Kevin
---
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.


Re: [Declude.JunkMail] Whitelisting our Domain

2005-04-04 Thread gbirdsall
I'm using IMail 7.14 and I noticted that in the Declude help page that
WHITELIST AUTH only works with V8 and above?

Is there any way to do this with V7.14?


 Yes.

 If all users send through your server, then use SMTP AUTH on all clients
 and
 configure Junkmail to whitelist AUTHing users.  If not, but all mail comes
 in from static IPs, you could use an IP whitelist to bypass for those IPs.

 Darin.


 - Original Message -
 From: Kevin Stanford [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Monday, April 04, 2005 10:25 AM
 Subject: [Declude.JunkMail] Whitelisting our Domain


 If we whitelist our domain will Spam that spoofs our email addresses and
 domain also be whitelisted? If so, how can I circumvent it?

 Thanks,

 Kevin

 ---
 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 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 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.


Re: [Declude.JunkMail] Whitelisting our Domain

2005-04-04 Thread Darin Cox
Yes.

If all users send through your server, then use SMTP AUTH on all clients and
configure Junkmail to whitelist AUTHing users.  If not, but all mail comes
in from static IPs, you could use an IP whitelist to bypass for those IPs.

Darin.


- Original Message - 
From: Kevin Stanford [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 10:25 AM
Subject: [Declude.JunkMail] Whitelisting our Domain


If we whitelist our domain will Spam that spoofs our email addresses and
domain also be whitelisted? If so, how can I circumvent it?

Thanks,

Kevin

---
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 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.


Re: [Declude.JunkMail] Whitelisting our Domain

2005-04-04 Thread Darin Cox
Oops.. not that I know of.  I believe it wasn't until V8 that IMail passed
the info to Junkmail.  Your best bet may be IP whitelists (negative
weighting, really) using the ipfile test.

Darin.


- Original Message - 
From: [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 10:43 AM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain


I'm using IMail 7.14 and I noticted that in the Declude help page that
WHITELIST AUTH only works with V8 and above?

Is there any way to do this with V7.14?


 Yes.

 If all users send through your server, then use SMTP AUTH on all clients
 and
 configure Junkmail to whitelist AUTHing users.  If not, but all mail comes
 in from static IPs, you could use an IP whitelist to bypass for those IPs.

 Darin.


 - Original Message -
 From: Kevin Stanford [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Monday, April 04, 2005 10:25 AM
 Subject: [Declude.JunkMail] Whitelisting our Domain


 If we whitelist our domain will Spam that spoofs our email addresses and
 domain also be whitelisted? If so, how can I circumvent it?

 Thanks,

 Kevin

 ---
 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 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 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 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.


RE: [Declude.JunkMail] Whitelisting our Domain

2005-04-04 Thread David Barker
It depends on the reason for using WHITELIST AUTH if it is because outgoing
mail is being marked as spam or held you can look at the settings and
ACTIONS in global.cfg also you could try adding the following line to your
global.cfg

WHITELIST FROM @yourdomain.com

Where yourdomain is actually the name of your domain

David B
www.declude.com

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Darin Cox
Sent: Monday, April 04, 2005 11:03 AM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting our Domain

Oops.. not that I know of.  I believe it wasn't until V8 that IMail passed
the info to Junkmail.  Your best bet may be IP whitelists (negative
weighting, really) using the ipfile test.

Darin.


- Original Message -
From: [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 10:43 AM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain


I'm using IMail 7.14 and I noticted that in the Declude help page that
WHITELIST AUTH only works with V8 and above?

Is there any way to do this with V7.14?


 Yes.

 If all users send through your server, then use SMTP AUTH on all clients
 and
 configure Junkmail to whitelist AUTHing users.  If not, but all mail comes
 in from static IPs, you could use an IP whitelist to bypass for those IPs.

 Darin.


 - Original Message -
 From: Kevin Stanford [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Monday, April 04, 2005 10:25 AM
 Subject: [Declude.JunkMail] Whitelisting our Domain


 If we whitelist our domain will Spam that spoofs our email addresses and
 domain also be whitelisted? If so, how can I circumvent it?

 Thanks,

 Kevin

 ---
 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 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 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 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.


__ NOD32 1.1044 (20050402) Information __

This message was checked by NOD32 antivirus system.
http://www.nod32.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.


Re: [Declude.JunkMail] Whitelisting our Domain

2005-04-04 Thread Darin Cox
Yes, but he originally asked how to avoid all spam that forged their domain
from also being whitelisted.  Without IMail 8, the best way that I know of
is to use a negative weight instead of a whitelist.  While some spam may
slip through from the negative weight, this can be tuned to keep the amount
low.

Darin.


- Original Message - 
From: David Barker [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 11:13 AM
Subject: RE: [Declude.JunkMail] Whitelisting our Domain


It depends on the reason for using WHITELIST AUTH if it is because outgoing
mail is being marked as spam or held you can look at the settings and
ACTIONS in global.cfg also you could try adding the following line to your
global.cfg

WHITELIST FROM @yourdomain.com

Where yourdomain is actually the name of your domain

David B
www.declude.com

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Darin Cox
Sent: Monday, April 04, 2005 11:03 AM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Whitelisting our Domain

Oops.. not that I know of.  I believe it wasn't until V8 that IMail passed
the info to Junkmail.  Your best bet may be IP whitelists (negative
weighting, really) using the ipfile test.

Darin.


- Original Message -
From: [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 10:43 AM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain


I'm using IMail 7.14 and I noticted that in the Declude help page that
WHITELIST AUTH only works with V8 and above?

Is there any way to do this with V7.14?


 Yes.

 If all users send through your server, then use SMTP AUTH on all clients
 and
 configure Junkmail to whitelist AUTHing users.  If not, but all mail comes
 in from static IPs, you could use an IP whitelist to bypass for those IPs.

 Darin.


 - Original Message -
 From: Kevin Stanford [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Monday, April 04, 2005 10:25 AM
 Subject: [Declude.JunkMail] Whitelisting our Domain


 If we whitelist our domain will Spam that spoofs our email addresses and
 domain also be whitelisted? If so, how can I circumvent it?

 Thanks,

 Kevin

 ---
 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 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 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 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.


__ NOD32 1.1044 (20050402) Information __

This message was checked by NOD32 antivirus system.
http://www.nod32.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 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.


Re: [Declude.JunkMail] Whitelisting our Domain

2005-04-04 Thread gbirdsall
Yes, some of my users outgoing mail is being marked as spam.

So the best way would be to set up negative weights for IP addresses?  Is
there a way to do IP ranges with declude?

 Yes, but he originally asked how to avoid all spam that forged their
 domain
 from also being whitelisted.  Without IMail 8, the best way that I know of
 is to use a negative weight instead of a whitelist.  While some spam may
 slip through from the negative weight, this can be tuned to keep the
 amount
 low.

 Darin.


 - Original Message -
 From: David Barker [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Monday, April 04, 2005 11:13 AM
 Subject: RE: [Declude.JunkMail] Whitelisting our Domain


 It depends on the reason for using WHITELIST AUTH if it is because
 outgoing
 mail is being marked as spam or held you can look at the settings and
 ACTIONS in global.cfg also you could try adding the following line to your
 global.cfg

 WHITELIST FROM @yourdomain.com

 Where yourdomain is actually the name of your domain

 David B
 www.declude.com

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Darin Cox
 Sent: Monday, April 04, 2005 11:03 AM
 To: Declude.JunkMail@declude.com
 Subject: Re: [Declude.JunkMail] Whitelisting our Domain

 Oops.. not that I know of.  I believe it wasn't until V8 that IMail passed
 the info to Junkmail.  Your best bet may be IP whitelists (negative
 weighting, really) using the ipfile test.

 Darin.


 - Original Message -
 From: [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Monday, April 04, 2005 10:43 AM
 Subject: Re: [Declude.JunkMail] Whitelisting our Domain


 I'm using IMail 7.14 and I noticted that in the Declude help page that
 WHITELIST AUTH only works with V8 and above?

 Is there any way to do this with V7.14?


 Yes.

 If all users send through your server, then use SMTP AUTH on all clients
 and
 configure Junkmail to whitelist AUTHing users.  If not, but all mail
 comes
 in from static IPs, you could use an IP whitelist to bypass for those
 IPs.

 Darin.


 - Original Message -
 From: Kevin Stanford [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Monday, April 04, 2005 10:25 AM
 Subject: [Declude.JunkMail] Whitelisting our Domain


 If we whitelist our domain will Spam that spoofs our email addresses and
 domain also be whitelisted? If so, how can I circumvent it?

 Thanks,

 Kevin

 ---
 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 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 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 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.


 __ NOD32 1.1044 (20050402) Information __

 This message was checked by NOD32 antivirus system.
 http://www.nod32.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 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 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.


Re: [Declude.JunkMail] Whitelisting our Domain

2005-04-04 Thread Kevin Stanford
I do have version 8. I don't think that I can use SMTP AUTH because I have 
Webshield for SMTP that sits in front of Imail. If I try the IP bypass 
route will it get confused because Webshield will pass (relay) it to Imail 
with an internal IP address?

Kevin
At 10:02 AM 04/04/05, Darin Cox wrote:
Oops.. not that I know of.  I believe it wasn't until V8 that IMail passed
the info to Junkmail.  Your best bet may be IP whitelists (negative
weighting, really) using the ipfile test.
Darin.
- Original Message -
From: [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 10:43 AM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain
I'm using IMail 7.14 and I noticted that in the Declude help page that
WHITELIST AUTH only works with V8 and above?
Is there any way to do this with V7.14?
 Yes.

 If all users send through your server, then use SMTP AUTH on all clients
 and
 configure Junkmail to whitelist AUTHing users.  If not, but all mail comes
 in from static IPs, you could use an IP whitelist to bypass for those IPs.

 Darin.


 - Original Message -
 From: Kevin Stanford [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Monday, April 04, 2005 10:25 AM
 Subject: [Declude.JunkMail] Whitelisting our Domain


 If we whitelist our domain will Spam that spoofs our email addresses and
 domain also be whitelisted? If so, how can I circumvent it?

 Thanks,

 Kevin

 ---
 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 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 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 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 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.


Re: [Declude.JunkMail] Whitelisting our Domain

2005-04-04 Thread Imail Admin
Just curious: does SmarterMail use SMTP or something similar?

Ben

- Original Message - 
From: Darin Cox [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, April 04, 2005 7:39 AM
Subject: Re: [Declude.JunkMail] Whitelisting our Domain


 Yes.

 If all users send through your server, then use SMTP AUTH on all clients
and
 configure Junkmail to whitelist AUTHing users.  If not, but all mail comes
 in from static IPs, you could use an IP whitelist to bypass for those IPs.

 Darin.


 - Original Message - 
 From: Kevin Stanford [EMAIL PROTECTED]
 To: Declude.JunkMail@declude.com
 Sent: Monday, April 04, 2005 10:25 AM
 Subject: [Declude.JunkMail] Whitelisting our Domain


 If we whitelist our domain will Spam that spoofs our email addresses and
 domain also be whitelisted? If so, how can I circumvent it?

 Thanks,

 Kevin

 ---
 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 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 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.


[Declude.JunkMail] Whitelisting for one user

2005-01-19 Thread Michael Hoyt
I have one user who uses a dial-up connection on weekends to e-mail through
our e-mail server.  I would like to be able to allow his e-mail to NOT be
checked for spam when it is addressed to local recipients.

I am currently running iMail version 7.15, Declude version 1.75 Standard(no
current service agreement-sorry Scott), and up-to-date Sniffer with service
agreement.  All users Authenticate, no relay except for a couple of internal
IP addresses.

After looking through the archives I have determined that what I really want
is the WHITELIST AUTH feature that requires an up-to-date Declude and iMail
8 or above.

Because I am cheap (and because it all works OK as-is) my question is:  If I
use the WHITELIST feature in Declude's global.cfg file for this user, how
easy would spammers find it to send to users in my domain as this user?

My current work-around is a FROM FILE that takes a few points off of the
Declude score for e-mail from this user.

Thank you,

Michael Hoyt
Communication Arts
110 Constitution Drive
Menlo Park, CA  94025
(650) 326-6040  fax:(650) 326-1648

e-mail: [EMAIL PROTECTED]
Web Site: http://www.commarts.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.


RE: [Declude.JunkMail] Whitelisting Issue

2004-12-21 Thread Kami Razvan
Hi Chris:

No- that statement goes into Global.cfg.

In our global statement all Whitelist issues are at the top so in ours it is
one of the first few lines..

Regards,
Kami 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris Patterson
Sent: Monday, December 20, 2004 6:17 PM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] Whitelisting Issue

Very Nice,

Should I add anything to the default.junkmail file? 

EMERGENCYBYPASS WARN ??


Thanks,
 
Chris Patterson, CCNA
Network Engineer
Rapid Systems



-Original Message-
From: Kami Razvan [mailto:[EMAIL PROTECTED]
Sent: Monday, December 20, 2004 5:57 PM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] Whitelisting Issue

Chris:

We were having a similar issue- Scott suggested the following:

EMERGENCYBYPASS bypasswhitelist 40  2   0   0

So now if the weight passes 40 the whitelist will not work if 2 more people
are in the list.

You can adjust the settings per your environment.

Regards,
Kami 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris Patterson
Sent: Monday, December 20, 2004 5:50 PM
To: Declude.JunkMail@declude.com
Subject: [Declude.JunkMail] Whitelisting Issue

Hi all,

I am having trouble with an issue where spam is getting by showing
whitelisted in the header.  Neither the domain or e-mail address that it is
coming from is whitelisted in the global config, nor are they showing as
Auth-user.

However, one of the recipients (local user) is Whitelisted; which you can't
see because they are apparently in the BCC field .

Apparently it is causing all recipients on this e-mail to receive it as
Whitelisted. Has anyone else ran into this issue?

Thanks,
 
Chris Patterson, CCNA
Network Engineer
Rapid Systems

---
[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.

---
[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.


[Declude.JunkMail] Whitelisting Issue

2004-12-20 Thread Chris Patterson
Hi all,

I am having trouble with an issue where spam is getting by showing
whitelisted in the header.  Neither the domain or e-mail address that it
is coming from is whitelisted in the global config, nor are they showing
as Auth-user.

However, one of the recipients (local user) is Whitelisted; which you
can't see because they are apparently in the BCC field .

Apparently it is causing all recipients on this e-mail to receive it as
Whitelisted. Has anyone else ran into this issue?

Thanks,
 
Chris Patterson, CCNA
Network Engineer
Rapid Systems

---
[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.


RE: [Declude.JunkMail] Whitelisting Issue

2004-12-20 Thread Kami Razvan
Chris:

We were having a similar issue- Scott suggested the following:

EMERGENCYBYPASS bypasswhitelist 40  2   0   0

So now if the weight passes 40 the whitelist will not work if 2 more people
are in the list.

You can adjust the settings per your environment.

Regards,
Kami 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris Patterson
Sent: Monday, December 20, 2004 5:50 PM
To: Declude.JunkMail@declude.com
Subject: [Declude.JunkMail] Whitelisting Issue

Hi all,

I am having trouble with an issue where spam is getting by showing
whitelisted in the header.  Neither the domain or e-mail address that it is
coming from is whitelisted in the global config, nor are they showing as
Auth-user.

However, one of the recipients (local user) is Whitelisted; which you can't
see because they are apparently in the BCC field .

Apparently it is causing all recipients on this e-mail to receive it as
Whitelisted. Has anyone else ran into this issue?

Thanks,
 
Chris Patterson, CCNA
Network Engineer
Rapid Systems

---
[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.


RE: [Declude.JunkMail] Whitelisting Issue

2004-12-20 Thread John Tolmachoff \(Lists\)
That is why whitelisting from or to an e-mail address is very touchy and
dangerous.

Why is anything for that user configured to be whitelisted?

John Tolmachoff
Engineer/Consultant/Owner
eServices For You


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-
 [EMAIL PROTECTED] On Behalf Of Chris Patterson
 Sent: Monday, December 20, 2004 2:50 PM
 To: Declude.JunkMail@declude.com
 Subject: [Declude.JunkMail] Whitelisting Issue
 
 Hi all,
 
 I am having trouble with an issue where spam is getting by showing
 whitelisted in the header.  Neither the domain or e-mail address that it
 is coming from is whitelisted in the global config, nor are they showing
 as Auth-user.
 
 However, one of the recipients (local user) is Whitelisted; which you
 can't see because they are apparently in the BCC field .
 
 Apparently it is causing all recipients on this e-mail to receive it as
 Whitelisted. Has anyone else ran into this issue?
 
 Thanks,
 
 Chris Patterson, CCNA
 Network Engineer
 Rapid Systems
 
 ---
 [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.


RE: [Declude.JunkMail] Whitelisting Issue

2004-12-20 Thread Chris Patterson
Very Nice,

Should I add anything to the default.junkmail file? 

EMERGENCYBYPASS WARN ??


Thanks,
 
Chris Patterson, CCNA
Network Engineer
Rapid Systems



-Original Message-
From: Kami Razvan [mailto:[EMAIL PROTECTED] 
Sent: Monday, December 20, 2004 5:57 PM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] Whitelisting Issue

Chris:

We were having a similar issue- Scott suggested the following:

EMERGENCYBYPASS bypasswhitelist 40  2   0   0

So now if the weight passes 40 the whitelist will not work if 2 more
people
are in the list.

You can adjust the settings per your environment.

Regards,
Kami 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris Patterson
Sent: Monday, December 20, 2004 5:50 PM
To: Declude.JunkMail@declude.com
Subject: [Declude.JunkMail] Whitelisting Issue

Hi all,

I am having trouble with an issue where spam is getting by showing
whitelisted in the header.  Neither the domain or e-mail address that it
is
coming from is whitelisted in the global config, nor are they showing as
Auth-user.

However, one of the recipients (local user) is Whitelisted; which you
can't
see because they are apparently in the BCC field .

Apparently it is causing all recipients on this e-mail to receive it as
Whitelisted. Has anyone else ran into this issue?

Thanks,
 
Chris Patterson, CCNA
Network Engineer
Rapid Systems

---
[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.


RE: [Declude.JunkMail] Whitelisting Issue

2004-12-20 Thread Chris Patterson
He likes his spam.

I am wide open to better ideas, other than teaching spammers how to be
better spammers.

Thanks,
 
Chris Patterson, CCNA
Network Engineer



-Original Message-
From: John Tolmachoff (Lists) [mailto:[EMAIL PROTECTED] 
Sent: Monday, December 20, 2004 6:09 PM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] Whitelisting Issue

That is why whitelisting from or to an e-mail address is very touchy and
dangerous.

Why is anything for that user configured to be whitelisted?

John Tolmachoff
Engineer/Consultant/Owner
eServices For You


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-
 [EMAIL PROTECTED] On Behalf Of Chris Patterson
 Sent: Monday, December 20, 2004 2:50 PM
 To: Declude.JunkMail@declude.com
 Subject: [Declude.JunkMail] Whitelisting Issue
 
 Hi all,
 
 I am having trouble with an issue where spam is getting by showing
 whitelisted in the header.  Neither the domain or e-mail address that
it
 is coming from is whitelisted in the global config, nor are they
showing
 as Auth-user.
 
 However, one of the recipients (local user) is Whitelisted; which you
 can't see because they are apparently in the BCC field .
 
 Apparently it is causing all recipients on this e-mail to receive it
as
 Whitelisted. Has anyone else ran into this issue?
 
 Thanks,
 
 Chris Patterson, CCNA
 Network Engineer
 Rapid Systems
 
 ---
 [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.


Re: [Declude.JunkMail] Whitelisting Issue

2004-12-20 Thread Roderick A. Anderson
Chris Patterson wrote:

 Hi all,
 
 I am having trouble with an issue where spam is getting by showing
 whitelisted in the header.  Neither the domain or e-mail address that it
 is coming from is whitelisted in the global config, nor are they showing
 as Auth-user.
 
 However, one of the recipients (local user) is Whitelisted; which you
 can't see because they are apparently in the BCC field .
 
 Apparently it is causing all recipients on this e-mail to receive it as
 Whitelisted. Has anyone else ran into this issue?

Yes we did.  Our solution was to go with an IMGate server and serialize
the messages.  This will not work for messages sent from user-to-user
(domain-to-domain also) on the same iMail system.  the mesage gets
passed to Declude which does it's magic then passed back to iMail for
final delivery.  Any spam checks passed of failed for one recipient
apply to all.  The bcc issue is trickier still.


Rod
-- 
Roderick A. Anderson
Technology Services Management Group
http://www.technologyservicesmanagementgroup.com/
Spokane WA, 99202
---
[This E-mail scanned for viruses by Declude Virus]

---
[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.


  1   2   3   >