Re: [spamdyke-users] Spamdyke GUI
Heya, I can't say what you are trying to do is a good thing, giving this kind of power to your customers is in my humble opinion, as Sam use to say, a solution looking for a problem. I think that in your case you will likely run over two or more customers disagreeing in the choice of filters, sooner than it may seem. I think that it would require of spamdyke to work on a much more user-level kind of configuration than what it is capable of today. (I may be completely wrong in this matter, tho, as I haven't configured spamdyke to its deepest maximum usefulness). Anyway, letting spam go thru and putting the responsability of deciding what to block on the customer, that and considering most customers do not have a good technical knowledge, looks wrong to me. You said that blocking e-mails without the consent of the customer is borderline illegal in Germany, but what if a customer end up putting by mistake one of those big providers in a blacklist? That would affect other customers as well, and you would end up taking the blame the same way! My advice is that you should declare your anti-spam policy when a customer signs in, exempting yourself from criminal responsability in case of legitimate mail being rejected. I don't know if that is ever acceptable in Germany though, and most importantly, in the market you serve. But those are just my 2 cents. Please don't beat me. :) Cheers Arthur Hi all, i've written a Spamdyke GUI for Plesk for my customers, so that they all have their own responsibility, if they want to use greylisting and are able to maintain their black-and whitelists. It's nice, as they all can see, what's really happening in the mailsystem and keep away spammers and welcome their customers... Rejecting mails without letting the customers know, is near the border to being illegal in Germany, because the customers can make me, or my company responsible for missing mails. But one problem i have is the logic of where i keep those lists. At the moment i just save them to the Plesk database and dump them regularly by cron-job to special files called customer_blacklist_ip, customer_blacklist_rdns, and so on, which are used by spamdyke. That's a good way to write them with root and keep all privileges healthy and i can let it send a report to me, what has been done. Do you think it's a good politic to activate them globally? I understand it in the way that every whitelisted entry should be a possible good sender for the others too. The critial point are the blacklists: Of course i avoided that they add known IP's, i.e. my mail server's network and local IP's and also created a button to check the reverse data. As far as i know, thats a way the big providers do it, i mean tagging mails manually as spam or ham. Am i right? Greetz, David ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Spamdyke GUI
Hi Arthur, first of all - I won't beat anyone here, as i asked for others' opinions. :) If you ask me, i would prefer to let all go through, but my server wouldn't survive that high load then. Without spamdyke my server load goes up from a load average of 0.10 to over 30.0 and more. I tried that... unvolunteerly... You're right, if you say i allow my users a lot, but the way i did it, i always get reports, when the list updates are done. If something goes wrong, it's on me to fix it. Thats always 30 minutes for me to react (theoretically). I didn't figure out a way to configure spamdyke to use per-domain-lists, so i've chosen this one. I think i'll give it a month or two as testing period, to see what my customers kill or not, do or not. Another thought is just to let them maintain the whitelist. hehe. All in all it's not only my decision. My boss wanted that. :-) Thanks for your statements about this. Arthur Girardi schrieb: Heya, I can't say what you are trying to do is a good thing, giving this kind of power to your customers is in my humble opinion, as Sam use to say, a solution looking for a problem. I think that in your case you will likely run over two or more customers disagreeing in the choice of filters, sooner than it may seem. I think that it would require of spamdyke to work on a much more user-level kind of configuration than what it is capable of today. (I may be completely wrong in this matter, tho, as I haven't configured spamdyke to its deepest maximum usefulness). Anyway, letting spam go thru and putting the responsability of deciding what to block on the customer, that and considering most customers do not have a good technical knowledge, looks wrong to me. You said that blocking e-mails without the consent of the customer is borderline illegal in Germany, but what if a customer end up putting by mistake one of those big providers in a blacklist? That would affect other customers as well, and you would end up taking the blame the same way! My advice is that you should declare your anti-spam policy when a customer signs in, exempting yourself from criminal responsability in case of legitimate mail being rejected. I don't know if that is ever acceptable in Germany though, and most importantly, in the market you serve. But those are just my 2 cents. Please don't beat me. :) Cheers Arthur Hi all, i've written a Spamdyke GUI for Plesk for my customers, so that they all have their own responsibility, if they want to use greylisting and are able to maintain their black-and whitelists. It's nice, as they all can see, what's really happening in the mailsystem and keep away spammers and welcome their customers... Rejecting mails without letting the customers know, is near the border to being illegal in Germany, because the customers can make me, or my company responsible for missing mails. But one problem i have is the logic of where i keep those lists. At the moment i just save them to the Plesk database and dump them regularly by cron-job to special files called customer_blacklist_ip, customer_blacklist_rdns, and so on, which are used by spamdyke. That's a good way to write them with root and keep all privileges healthy and i can let it send a report to me, what has been done. Do you think it's a good politic to activate them globally? I understand it in the way that every whitelisted entry should be a possible good sender for the others too. The critial point are the blacklists: Of course i avoided that they add known IP's, i.e. my mail server's network and local IP's and also created a button to check the reverse data. As far as i know, thats a way the big providers do it, i mean tagging mails manually as spam or ham. Am i right? Greetz, David ___ 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] Spamdyke GUI
I am running spamdykes greylisting with huschis SCP Plesk addon. Most of my customers are german ones. All customers domains have spamdyke enabled by default. By signing a hosting contract with me i tell them that greylisting is enabled and how they can switch it of. Thats it. None of my customers has switched it of, instead everybody is satisfied with the low to none spam. Yes it happened that a email was blocked. All of my customers, to which this happend, whitlisted the sender/sending mx/etc and thats it. --Stefan Hi all, i've written a Spamdyke GUI for Plesk for my customers, so that they all have their own responsibility, if they want to use greylisting and are able to maintain their black-and whitelists. It's nice, as they all can see, what's really happening in the mailsystem and keep away spammers and welcome their customers... Rejecting mails without letting the customers know, is near the border to being illegal in Germany, because the customers can make me, or my company responsible for missing mails. But one problem i have is the logic of where i keep those lists. At the moment i just save them to the Plesk database and dump them regularly by cron-job to special files called customer_blacklist_ip, customer_blacklist_rdns, and so on, which are used by spamdyke. That's a good way to write them with root and keep all privileges healthy and i can let it send a report to me, what has been done. Do you think it's a good politic to activate them globally? I understand it in the way that every whitelisted entry should be a possible good sender for the others too. The critial point are the blacklists: Of course i avoided that they add known IP's, i.e. my mail server's network and local IP's and also created a button to check the reverse data. As far as i know, thats a way the big providers do it, i mean tagging mails manually as spam or ham. Am i right? Greetz, David ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users __ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version 3518 (20081013) __ E-Mail wurde geprüft mit ESET NOD32 Antivirus. http://www.eset.com ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Spamdyke GUI
This sounds like a great project to me -- it's exactly what I had in mind when I added support for configuration directories. Specifically, if your tool updates the configuration file named _recipient_/domain.com, the changes will only affect recipients in domain.com. That way, your users can do anything they want (including completely disabling spamdyke's filters) and it will only affect their mail. This is a much better solution than allowing any user to edit the server's global configuration and affect everyone's mail. Not every filter can be activated or deactivated through configuration directories but most of them can (whitelists, blacklists, graylisting, rDNS filters and others). You should also check out the Plesk control panel that Haggybear is working on. That code may already include the features you're trying to build: http://www.haggybear.de/component/option,com_docman/task,doc_details/gid,21/Itemid,54/ BTW, if you build your tool to also work on non-Plesk servers, you'd probably find a large audience for it (especially on the QmailToaster mailing list). -- Sam Clippinger David Stiller wrote: Hi all, i've written a Spamdyke GUI for Plesk for my customers, so that they all have their own responsibility, if they want to use greylisting and are able to maintain their black-and whitelists. It's nice, as they all can see, what's really happening in the mailsystem and keep away spammers and welcome their customers... Rejecting mails without letting the customers know, is near the border to being illegal in Germany, because the customers can make me, or my company responsible for missing mails. But one problem i have is the logic of where i keep those lists. At the moment i just save them to the Plesk database and dump them regularly by cron-job to special files called customer_blacklist_ip, customer_blacklist_rdns, and so on, which are used by spamdyke. That's a good way to write them with root and keep all privileges healthy and i can let it send a report to me, what has been done. Do you think it's a good politic to activate them globally? I understand it in the way that every whitelisted entry should be a possible good sender for the others too. The critial point are the blacklists: Of course i avoided that they add known IP's, i.e. my mail server's network and local IP's and also created a button to check the reverse data. As far as i know, thats a way the big providers do it, i mean tagging mails manually as spam or ham. Am i right? Greetz, David ___ 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] Spamdyke GUI
Hey all, new to this list but I have to agree on this one: a non plesk project would be very interesting. We are running qmail toasters and it would be great if users could add senders to their own whitelists. Right now we have to add them to the global lists by hand. Great ideas out there, hope to hear more about it! Sebastian Sent on the TELUS Mobility network with BlackBerry -Original Message- From: Sam Clippinger [EMAIL PROTECTED] Date: Mon, 13 Oct 2008 15:30:49 To: spamdyke usersspamdyke-users@spamdyke.org Subject: Re: [spamdyke-users] Spamdyke GUI This sounds like a great project to me -- it's exactly what I had in mind when I added support for configuration directories. Specifically, if your tool updates the configuration file named _recipient_/domain.com, the changes will only affect recipients in domain.com. That way, your users can do anything they want (including completely disabling spamdyke's filters) and it will only affect their mail. This is a much better solution than allowing any user to edit the server's global configuration and affect everyone's mail. Not every filter can be activated or deactivated through configuration directories but most of them can (whitelists, blacklists, graylisting, rDNS filters and others). You should also check out the Plesk control panel that Haggybear is working on. That code may already include the features you're trying to build: http://www.haggybear.de/component/option,com_docman/task,doc_details/gid,21/Itemid,54/ BTW, if you build your tool to also work on non-Plesk servers, you'd probably find a large audience for it (especially on the QmailToaster mailing list). -- Sam Clippinger David Stiller wrote: Hi all, i've written a Spamdyke GUI for Plesk for my customers, so that they all have their own responsibility, if they want to use greylisting and are able to maintain their black-and whitelists. It's nice, as they all can see, what's really happening in the mailsystem and keep away spammers and welcome their customers... Rejecting mails without letting the customers know, is near the border to being illegal in Germany, because the customers can make me, or my company responsible for missing mails. But one problem i have is the logic of where i keep those lists. At the moment i just save them to the Plesk database and dump them regularly by cron-job to special files called customer_blacklist_ip, customer_blacklist_rdns, and so on, which are used by spamdyke. That's a good way to write them with root and keep all privileges healthy and i can let it send a report to me, what has been done. Do you think it's a good politic to activate them globally? I understand it in the way that every whitelisted entry should be a possible good sender for the others too. The critial point are the blacklists: Of course i avoided that they add known IP's, i.e. my mail server's network and local IP's and also created a button to check the reverse data. As far as i know, thats a way the big providers do it, i mean tagging mails manually as spam or ham. Am i right? Greetz, David ___ 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
Re: [spamdyke-users] Spamdyke GUI
Yes i looked at the sources and as far as i saw, that's very complex analysis, wich isn't necessary in my case. As my server is connecting to the internet, the module from Haggybear is rotating downloads of an update-script, ignoring that it should use a proxy and times out but doesn't recognize. I just need to know, who spammed, wich senders are important and black- or whitelist them. I'll modify my version to use the below mentioned config-dirs. As i'm always programming shell-scripts, it won't be hard to make it compatible to other systems, like QmailToaster. BTW, is http://www.shupp.org/toaster/; meant with that, or something else? Sam Clippinger schrieb: This sounds like a great project to me -- it's exactly what I had in mind when I added support for configuration directories. Specifically, if your tool updates the configuration file named _recipient_/domain.com, the changes will only affect recipients in domain.com. That way, your users can do anything they want (including completely disabling spamdyke's filters) and it will only affect their mail. This is a much better solution than allowing any user to edit the server's global configuration and affect everyone's mail. Not every filter can be activated or deactivated through configuration directories but most of them can (whitelists, blacklists, graylisting, rDNS filters and others). You should also check out the Plesk control panel that Haggybear is working on. That code may already include the features you're trying to build: http://www.haggybear.de/component/option,com_docman/task,doc_details/gid,21/Itemid,54/ BTW, if you build your tool to also work on non-Plesk servers, you'd probably find a large audience for it (especially on the QmailToaster mailing list). -- Sam Clippinger David Stiller wrote: Hi all, i've written a Spamdyke GUI for Plesk for my customers, so that they all have their own responsibility, if they want to use greylisting and are able to maintain their black-and whitelists. It's nice, as they all can see, what's really happening in the mailsystem and keep away spammers and welcome their customers... Rejecting mails without letting the customers know, is near the border to being illegal in Germany, because the customers can make me, or my company responsible for missing mails. But one problem i have is the logic of where i keep those lists. At the moment i just save them to the Plesk database and dump them regularly by cron-job to special files called customer_blacklist_ip, customer_blacklist_rdns, and so on, which are used by spamdyke. That's a good way to write them with root and keep all privileges healthy and i can let it send a report to me, what has been done. Do you think it's a good politic to activate them globally? I understand it in the way that every whitelisted entry should be a possible good sender for the others too. The critial point are the blacklists: Of course i avoided that they add known IP's, i.e. my mail server's network and local IP's and also created a button to check the reverse data. As far as i know, thats a way the big providers do it, i mean tagging mails manually as spam or ham. Am i right? Greetz, David ___ 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
Re: [spamdyke-users] Spamdyke GUI
Actually, the QmailToaster project I'm thinking of is hosted at: http://www.qmailtoaster.org/ It's basically a set of SRPMs you can download, build and install to get a fully functioning, fully patched qmail server. It's pretty slick. They have an active mailing list with some pretty knowledgeable people. Best of all, they release updates for important packages like SpamAssassin and ClamAV, so you can easily stay on the latest version. Also, I should mention that my example configuration directory was wrong (oops). To configure spamdyke for domain.com, you should actually create a file named _recipient_/com/domain. When in doubt, read the docs, don't take my word for anything. :) -- Sam Clippinger David Stiller wrote: Yes i looked at the sources and as far as i saw, that's very complex analysis, wich isn't necessary in my case. As my server is connecting to the internet, the module from Haggybear is rotating downloads of an update-script, ignoring that it should use a proxy and times out but doesn't recognize. I just need to know, who spammed, wich senders are important and black- or whitelist them. I'll modify my version to use the below mentioned config-dirs. As i'm always programming shell-scripts, it won't be hard to make it compatible to other systems, like QmailToaster. BTW, is http://www.shupp.org/toaster/; meant with that, or something else? Sam Clippinger schrieb: This sounds like a great project to me -- it's exactly what I had in mind when I added support for configuration directories. Specifically, if your tool updates the configuration file named _recipient_/domain.com, the changes will only affect recipients in domain.com. That way, your users can do anything they want (including completely disabling spamdyke's filters) and it will only affect their mail. This is a much better solution than allowing any user to edit the server's global configuration and affect everyone's mail. Not every filter can be activated or deactivated through configuration directories but most of them can (whitelists, blacklists, graylisting, rDNS filters and others). You should also check out the Plesk control panel that Haggybear is working on. That code may already include the features you're trying to build: http://www.haggybear.de/component/option,com_docman/task,doc_details/gid,21/Itemid,54/ BTW, if you build your tool to also work on non-Plesk servers, you'd probably find a large audience for it (especially on the QmailToaster mailing list). -- Sam Clippinger David Stiller wrote: Hi all, i've written a Spamdyke GUI for Plesk for my customers, so that they all have their own responsibility, if they want to use greylisting and are able to maintain their black-and whitelists. It's nice, as they all can see, what's really happening in the mailsystem and keep away spammers and welcome their customers... Rejecting mails without letting the customers know, is near the border to being illegal in Germany, because the customers can make me, or my company responsible for missing mails. But one problem i have is the logic of where i keep those lists. At the moment i just save them to the Plesk database and dump them regularly by cron-job to special files called customer_blacklist_ip, customer_blacklist_rdns, and so on, which are used by spamdyke. That's a good way to write them with root and keep all privileges healthy and i can let it send a report to me, what has been done. Do you think it's a good politic to activate them globally? I understand it in the way that every whitelisted entry should be a possible good sender for the others too. The critial point are the blacklists: Of course i avoided that they add known IP's, i.e. my mail server's network and local IP's and also created a button to check the reverse data. As far as i know, thats a way the big providers do it, i mean tagging mails manually as spam or ham. Am i right? Greetz, David ___ 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 mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
