Re: [spamdyke-users] Moving from GreyLite

2015-06-19 Thread Philip Rhoades via spamdyke-users

Gary and Sam,

Thanks for the useful info!  I have SpamDyke running now with the simple 
conf and will start looking at the options.  I have some white  black 
lists to import to . .


BTW, it appears top-posting is OK here?

Regards,

Phil.


On 2015-06-20 05:52, Sam Clippinger via spamdyke-users wrote:

I'm not familiar with GreyLite at all, but connection-time means
spamdyke does its work while the message is still coming into your
mail server -- while the connection with the sending server is active.
This is as opposed to filtering messages in the mail queue, after the
remote server is no longer connected (and believes the message has
been delivered). The advantage of a connection-time filter is the
remote server sees the rejection and the spam is never stored on your
server at all. Rejecting messages after they've been queued requires
either sending a bounce message or delivering it to a user's Junk
folder.

This distinction comes up a lot around qmail regarding recipient
validation. By itself, qmail does not validate recipients when
messages are accepted. Any username at a valid domain is accepted,
then bounced later if the address turns out to be invalid. This leads
to the problem of backscatter spam -- spammers deliberately send
messages to invalid addresses and set the from address to their
intended target. A qmail server will bounce the message (complete with
spam or virus) to the victim. For qmail to validate recipients at
connection time requires a patch or a filter like spamdyke.

-- Sam Clippinger

On Jun 19, 2015, at 5:21 AM, Philip Rhoades via spamdyke-users
spamdyke-users@spamdyke.org wrote:


People,

I have been using GreyLite for many years but it hasn't been
supported for quite a while - I think it is time to update to
SpamDyke . . but I have some questions - first one:

I looked at the SpamDyke web site and it is still not clear to me -
it says 'connection-time means spamdyke evaluates and rejects spam
while the remote server is still delivering it' - does this mean it
does it at the TCP / mail envelope level? ie so it would be the same
as GreyLite? GL blocks and forces possibly bad mails to be resent
some time later which many spammers don't attempt . .

Thanks,

Phil.
--
Philip Rhoades

PO Box 896
Cowra NSW 2794
Australia
E-mail: p...@pricom.com.au
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users



___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users


--
Philip Rhoades

PO Box 896
Cowra  NSW  2794
Australia
E-mail:  p...@pricom.com.au
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users


Re: [spamdyke-users] Moving from GreyLite

2015-06-19 Thread Gary Gendel via spamdyke-users

Phil,

The greylisting feature of Spamdyke kicks in after whitelisting and 
blacklisting operations.  If these operations don't specifically reject 
or accept the incoming email then it is chosen for greylisting.  I 
suggest you scan it's features from the spamdyke homepage.  It sounds 
like it is a GreyLite replacement since it uses the connection 
information to determine whether to greylist.


There has been multiple discussions on whether greylisting is a good or 
bad spam filter.  In my case, I turned it off because sometimes 
registration confirmations aren't resent at all, are sent too late so 
they get caught in the greylist again, or they finally come through 
after they've expired.  I had to be proactive in these cases and 
whitelist that domain before I register.  For the small percentage of 
spam rejections over my other spamdyke filter settings, I decided it 
wasn't worth the hassle of false positive delays.


Gary

On 06/19/2015 06:21 AM, Philip Rhoades via spamdyke-users wrote:

People,

I have been using GreyLite for many years but it hasn't been supported 
for quite a while - I think it is time to update to SpamDyke . . but I 
have some questions - first one:


I looked at the SpamDyke web site and it is still not clear to me - it 
says 'connection-time means spamdyke evaluates and rejects spam 
while the remote server is still delivering it' - does this mean it 
does it at the TCP / mail envelope level? ie so it would be the same 
as GreyLite?  GL blocks and forces possibly bad mails to be resent 
some time later which many spammers don't attempt . .


Thanks,

Phil.





smime.p7s
Description: S/MIME Cryptographic Signature
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users


[spamdyke-users] Moving from GreyLite

2015-06-19 Thread Philip Rhoades via spamdyke-users

People,

I have been using GreyLite for many years but it hasn't been supported 
for quite a while - I think it is time to update to SpamDyke . . but I 
have some questions - first one:


I looked at the SpamDyke web site and it is still not clear to me - it 
says 'connection-time means spamdyke evaluates and rejects spam while 
the remote server is still delivering it' - does this mean it does it at 
the TCP / mail envelope level? ie so it would be the same as GreyLite?  
GL blocks and forces possibly bad mails to be resent some time later 
which many spammers don't attempt . .


Thanks,

Phil.
--
Philip Rhoades

PO Box 896
Cowra  NSW  2794
Australia
E-mail:  p...@pricom.com.au
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users


Re: [spamdyke-users] Moving from GreyLite

2015-06-19 Thread Sam Clippinger via spamdyke-users
I'm not familiar with GreyLite at all, but connection-time means spamdyke 
does its work while the message is still coming into your mail server -- while 
the connection with the sending server is active.  This is as opposed to 
filtering messages in the mail queue, after the remote server is no longer 
connected (and believes the message has been delivered).  The advantage of a 
connection-time filter is the remote server sees the rejection and the spam is 
never stored on your server at all.  Rejecting messages after they've been 
queued requires either sending a bounce message or delivering it to a user's 
Junk folder.

This distinction comes up a lot around qmail regarding recipient validation.  
By itself, qmail does not validate recipients when messages are accepted.  Any 
username at a valid domain is accepted, then bounced later if the address turns 
out to be invalid.  This leads to the problem of backscatter spam -- spammers 
deliberately send messages to invalid addresses and set the from address to 
their intended target.  A qmail server will bounce the message (complete with 
spam or virus) to the victim.  For qmail to validate recipients at connection 
time requires a patch or a filter like spamdyke.

-- Sam Clippinger




On Jun 19, 2015, at 5:21 AM, Philip Rhoades via spamdyke-users 
spamdyke-users@spamdyke.org wrote:

 People,
 
 I have been using GreyLite for many years but it hasn't been supported for 
 quite a while - I think it is time to update to SpamDyke . . but I have some 
 questions - first one:
 
 I looked at the SpamDyke web site and it is still not clear to me - it says 
 'connection-time means spamdyke evaluates and rejects spam while the remote 
 server is still delivering it' - does this mean it does it at the TCP / mail 
 envelope level? ie so it would be the same as GreyLite?  GL blocks and forces 
 possibly bad mails to be resent some time later which many spammers don't 
 attempt . .
 
 Thanks,
 
 Phil.
 -- 
 Philip Rhoades
 
 PO Box 896
 Cowra  NSW  2794
 Australia
 E-mail:  p...@pricom.com.au
 ___
 spamdyke-users mailing list
 spamdyke-users@spamdyke.org
 http://www.spamdyke.org/mailman/listinfo/spamdyke-users

___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users