Hi Eric, Thanks for your help. Will do it my server.
On Fri, May 9, 2014 at 12:13 AM, Eric Shubert <[email protected]> wrote: > Spamdyke augments other spam filters (it's not a matter of using one or > another, you should use both), and is highly efficient. It will actually > lessen the load on your server considerably. This is because it can reject > spam before it's even transmitted or scanned. Spamdyke also has virtually > no false positives (subject to configuration of course). > > You really should be running spamdyke. Installing it is as simple as > running the qtp-install-spamdyke script, which is included in the > qmailtoaster-plus package. Spamdyke is also included in the 'stock' > configuration for QMT going forward (beginning with the yum-capable binary > packages). > > That being said, if you're not using spamdyke and you want to add or > change the RBLs being used, you should modify the > /var/qmail/control/rblsmtpd file appropriately. > > RBLs are generally implemented outside the scope of spamassassin, as it's > more effectively done there. > > Note, spamdyke also has RBL filtering, so if using spamdyke, that's the > place to manage your RBLs. > > -- > -Eric 'shubes' > > > On 05/07/2014 11:39 PM, Chandran Manikandan wrote: > >> Hi Eric, >> Thanks for your advise. Am using spamassassin now and not running >> spamdyke package on my system . kindly let me know to add blacklist in >> spamassassin file. >> >> >> On Thu, May 8, 2014 at 3:02 AM, Eric Shubert <[email protected] >> <mailto:[email protected]>> wrote: >> >> On 05/04/2014 08:36 PM, Chandran Manikandan wrote: >> >>> Dear All, >>> I have received such emails like below as generated from my domain >>> and send to my domain. How to avoid this kind of emails. It's >>> generated from my domain name but it's does not have this email >>> account in my domain. >>> >>> * >>> * >>> >>> *From:*[email protected] >>> <mailto:[email protected]> >>> [mailto:[email protected]] >>> *Sent:* Friday, 2 May, 2014 3:54 PM >>> *Subject:* Financial Management ICV Information Session >>> >>> >>> -- >>> *Thanks,* >>> *Manikandan.C* >>> *System Administrator* >>> >> >> So long as all of your users authenticate when submitting emails and >> they submit only via your server, you can blacklist your domain in >> the spamdyke blacklist_senders file: >> @shubes.net <http://shubes.net> >> >> This is counter intuitive, but it works great. Since all legit >> senders authenticate, the spamdyke filters don't apply to them. This >> effectively says "if the message says it's coming from my domain and >> the sender hasn't authenticated, reject it". >> >> -- >> -Eric 'shubes' >> >> >> >> >> -- >> *Thanks,* >> *Manikandan.C* >> *System Administrator* >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- *Thanks,* *Manikandan.C* *System Administrator*
