Re: [spamdyke-users] Is there a way to populate the graylist database WITHOUT effectively doing graylisting
Hi Sam, in the first place, thank you for time and for this great soft 1) You can create the graylist entries for the addresses in [...] 2) You can use a configuration folder to turn off graylisting for I don't know which address will be graylisted, that's why I want to populate the database. What I'm trying to say if there's a method to do the whole graylisting process, without effectively delaying email. Something like what intuitively setting graylist-min-secs=0 would do (BTW i've tested it and it doesn't do that. I mean, create the directory structure, and compare the timestamp with current time, and then letting the e-mail proceed, since the minimum delay time is 0 ). What i'm trying to do is activate spamdyke with this setting, and then, giving enough time to populate the graylist database, ( for example graylist-max-secs seconds ) effectively activating the graylisting. All this is just for ease transition. Thank you again! --- David Sanchez Martin Administrador de Sistemas dsanc...@e2000.es GPG Key ID: 0x37E7AC1F E2000 Nuevas Tecnologías Tel : +34 902 830500 smime.p7s Description: S/MIME cryptographic signature ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Is there a way to populate thegraylistdatabase WITHOUT effectively doing graylisting
Hi Michael, So Set it to 1 minute. Certainly your users can wait 1 minute... I think greylisting may loose some of its effectiveness this way... Set it to 10 minutes, don't tell them it's there, and they likely won't even notice. I know, but what I'm trying to do is, IMHO a reasonable approach. See what's happening, populate the database, do some research on the results (may be doing some whitelists with that results) and then do the graylist the way it's thought to be. It's just a matter of prudence. Regards. smime.p7s Description: S/MIME cryptographic signature ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Is there a way to populate thegraylistdatabase WITHOUT effectively doing graylisting
David, That sounds like a neat idea, but I don't think it'd work. If you simply allow the session to complete and create a greylist entry for everything, you will have effectively whitelisted every incoming message, including the bad ones. Greylisting works because some spammers don't retry when a session fails. If everything passes, you've no way of knowing which ones would or would not have retried. The greylist database would be useless. Let me think about it. If greylisting is enabled as usual: When a foreign user sends a message to a local user is greylisted, then: 1.- It's created an entry in the greylisting database. 2.- It's blocked and each retry is blocked also at least for graylist-min-secs seconds. 3.- No further tests are passed. Session is closed. When graylist-min-secs time passes: 1.- The message passes greylist filter and touches the file. 2.- The message is tested against other filters. Ok, What i'm trying to accomplish: When a user foreign a message to a local then: 1.- The message passes greylist filter and touches the file. 2.- The message is tested against other filters. That will populate the database, that is what i want before putting graylist at work. Sorry, perhaps I'm missing something. Best regards. smime.p7s Description: S/MIME cryptographic signature ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] dumb question - redirect version info to file
Did you have a look at qtp-install-spamdyke?
# determine which version is already installed
#
a4_check_installed_version(){
sdver=$(spamdyke -v 21)
rc=$?
if [ $rc == 0 ]; then
sdverstring=$(echo $sdver | sed -e 's/^spamdyke //')
instver=${sdverstring%%.*}
else
instver=0
fi
}
;)
dnk wrote:
Bingo, bango, Sugar in the gas tank.
Works like a charm.
d
On 23-Apr-09, at 2:13 PM, Sebastian Grewe wrote:
Make that
spamdyke -v 2 version.txt
Cheers,
Sebastian
dnk wrote:
Hi there,
I am writing a home brew report on my qmail machines. I would like to
include the spamdyke version. So I tried:
spamdyke -v report.txt
No matter what I do, I can not get it to redirect the output to a
file.
D
___
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
--
-Eric 'shubes'
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Is there a way to populate thegraylistdatabase WITHOUT effectively doing graylisting
David Sánchez Martín wrote: David, That sounds like a neat idea, but I don't think it'd work. If you simply allow the session to complete and create a greylist entry for everything, you will have effectively whitelisted every incoming message, including the bad ones. Greylisting works because some spammers don't retry when a session fails. If everything passes, you've no way of knowing which ones would or would not have retried. The greylist database would be useless. Let me think about it. If greylisting is enabled as usual: When a foreign user sends a message to a local user is greylisted, then: 1.- It's created an entry in the greylisting database. 2.- It's blocked and each retry is blocked also at least for graylist-min-secs seconds. 3.- No further tests are passed. Session is closed. When graylist-min-secs time passes: 1.- The message passes greylist filter and touches the file. 2.- The message is tested against other filters. Ok, What i'm trying to accomplish: When a user foreign a message to a local then: 1.- The message passes greylist filter and touches the file. 2.- The message is tested against other filters. That will populate the database, that is what i want before putting graylist at work. Sorry, perhaps I'm missing something. Best regards. That will populate the database for all email. Including spammers. Any spammers who send messages during the period in which the database is being populated will get a free pass, even after greylisting is activated. Perhaps you can live with that. -- -Eric 'shubes' ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Is there a way to populate thegraylistdatabase WITHOUT effectively doing graylisting
I understand now. Basically, you want to add some addresses to the graylist filter but since you don't know which addresses to use, you're trying to use the graylist filter to collect that information. I have a different idea that will probably work better. Instead of finding a way to partially enable the graylist filter, just leave it turned off for a while. Run spamdyke so that it will log messages about incoming and outgoing email. Then, after a week or two, use the logs to discover which remote addresses are sending to your users and vice-versa. That will give better information anyway, since it will show which addresses your users are sending _to_ and how often. Those are the ones that most likely need to be added to the graylist filter. -- Sam Clippinger David Sánchez Martín wrote: David, That sounds like a neat idea, but I don't think it'd work. If you simply allow the session to complete and create a greylist entry for everything, you will have effectively whitelisted every incoming message, including the bad ones. Greylisting works because some spammers don't retry when a session fails. If everything passes, you've no way of knowing which ones would or would not have retried. The greylist database would be useless. Let me think about it. If greylisting is enabled as usual: When a foreign user sends a message to a local user is greylisted, then: 1.- It's created an entry in the greylisting database. 2.- It's blocked and each retry is blocked also at least for graylist-min-secs seconds. 3.- No further tests are passed. Session is closed. When graylist-min-secs time passes: 1.- The message passes greylist filter and touches the file. 2.- The message is tested against other filters. Ok, What i'm trying to accomplish: When a user foreign a message to a local then: 1.- The message passes greylist filter and touches the file. 2.- The message is tested against other filters. That will populate the database, that is what i want before putting graylist at work. Sorry, perhaps I'm missing something. Best regards. ___ 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
Re: [spamdyke-users] Is there a way to populate thegraylistdatabase WITHOUT effectively doing graylisting
I'm agree with Sam solution, that's the way to do a nice database,you can check which domains sends emails to your domain, then add to the graylist file or directory, after two weeks or 4 weeks will be better, then you turn on graylist. Users will see a nice service of mail, server will work better because graylisting it's a cool utility. David pienso que esa es la manera de hacerlo, pero sobre todo no puedes activar el graylisting con tan poco tiempo porque eso no seria graylisting. Revisa cada semana el log y vas añadiendo los distintos dominios de los que recibes email, o los añades al directorio de graylisting o en una lista whitelist para evitar chequeos. Despues de un mes, activas el graylisting y seguro que tus usuarios lo notaran. Pero debes de tener en cuenta que todo no puede ser, o una cosa o la otra, no ambas a la vez porque te va a dar problemas. Por ejemplo yo lo monte con el dominio ibm.com pero resulta que ibm usa subdominios... asi que tienes que tenerlo en cuenta porque un usuario puede recibir correos de es.ibm.com o uk.ibm.com, ie.ibm.com,etc... Suerte 2009/4/24 Sam Clippinger s...@silence.org: I understand now. Basically, you want to add some addresses to the graylist filter but since you don't know which addresses to use, you're trying to use the graylist filter to collect that information. I have a different idea that will probably work better. Instead of finding a way to partially enable the graylist filter, just leave it turned off for a while. Run spamdyke so that it will log messages about incoming and outgoing email. Then, after a week or two, use the logs to discover which remote addresses are sending to your users and vice-versa. That will give better information anyway, since it will show which addresses your users are sending _to_ and how often. Those are the ones that most likely need to be added to the graylist filter. -- Sam Clippinger David Sánchez Martín wrote: David, That sounds like a neat idea, but I don't think it'd work. If you simply allow the session to complete and create a greylist entry for everything, you will have effectively whitelisted every incoming message, including the bad ones. Greylisting works because some spammers don't retry when a session fails. If everything passes, you've no way of knowing which ones would or would not have retried. The greylist database would be useless. Let me think about it. If greylisting is enabled as usual: When a foreign user sends a message to a local user is greylisted, then: 1.- It's created an entry in the greylisting database. 2.- It's blocked and each retry is blocked also at least for graylist-min-secs seconds. 3.- No further tests are passed. Session is closed. When graylist-min-secs time passes: 1.- The message passes greylist filter and touches the file. 2.- The message is tested against other filters. Ok, What i'm trying to accomplish: When a user foreign a message to a local then: 1.- The message passes greylist filter and touches the file. 2.- The message is tested against other filters. That will populate the database, that is what i want before putting graylist at work. Sorry, perhaps I'm missing something. Best regards. ___ 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 ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
[spamdyke-users] spamdyke subdomain addon
Hi Sam when i was working to a Spanish IBM Reseller, I installed spamdyke, it works sucesfully. But i added to my whitelist ibm.com... But IBM uses subdomains... so whitelist ibm.com dosen't recognize very well emails from other subdomains of ibm.com uk.ibm.com es.ibm.com ie.ibm.com and so on.Can you add something to that? Pardon me for my little english. Thanks a lot for your time and help. Kind regards. ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] spamdyke subdomain addon
Try the Whitelist RDNS file and add .ibm.com Maybe that works for you. Cheers, Sebastian nightduke wrote: Hi Sam when i was working to a Spanish IBM Reseller, I installed spamdyke, it works sucesfully. But i added to my whitelist ibm.com... But IBM uses subdomains... so whitelist ibm.com dosen't recognize very well emails from other subdomains of ibm.com uk.ibm.com es.ibm.com ie.ibm.com and so on.Can you add something to that? Pardon me for my little english. Thanks a lot for your time and help. Kind regards. ___ 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
