diff --git a/en_US.ISO8859-1/articles/Makefile b/en_US.ISO8859-1/articles/Makefile index 259deea664..17422513d9 100644 --- a/en_US.ISO8859-1/articles/Makefile +++ b/en_US.ISO8859-1/articles/Makefile @@ -1,47 +1,48 @@ # $FreeBSD$ SUBDIR = SUBDIR+= 5-roadmap SUBDIR+= checkpoint SUBDIR+= committers-guide SUBDIR+= console-server SUBDIR+= contributing SUBDIR+= contributors SUBDIR+= cvs-freebsd SUBDIR+= cvsup-advanced SUBDIR+= dialup-firewall SUBDIR+= diskless-x SUBDIR+= euro SUBDIR+= explaining-bsd SUBDIR+= fbsd-from-scratch SUBDIR+= filtering-bridges SUBDIR+= fonts SUBDIR+= formatting-media SUBDIR+= freebsd-questions SUBDIR+= hats SUBDIR+= hubs SUBDIR+= ipsec-must SUBDIR+= java-tomcat SUBDIR+= laptop SUBDIR+= mailing-list-faq SUBDIR+= mh SUBDIR+= multi-os SUBDIR+= new-users SUBDIR+= pam SUBDIR+= portbuild SUBDIR+= pr-guidelines SUBDIR+= problem-reports SUBDIR+= pxe +SUBDIR+= relaydelay SUBDIR+= releng SUBDIR+= releng-packages SUBDIR+= serial-uart SUBDIR+= solid-state SUBDIR+= storage-devices SUBDIR+= vinum SUBDIR+= vm-design SUBDIR+= zip-drive # ROOT_SYMLINKS+= new-users DOC_PREFIX?= ${.CURDIR}/../.. .include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/en_US.ISO8859-1/articles/relaydelay/Makefile b/en_US.ISO8859-1/articles/relaydelay/Makefile new file mode 100644 index 0000000000..68d6d001fc --- /dev/null +++ b/en_US.ISO8859-1/articles/relaydelay/Makefile @@ -0,0 +1,16 @@ +# +# $FreeBSD$ +# +# Article: Using greylisting with FreeBSD + +DOC?= article + +FORMATS?= html + +INSTALL_COMPRESSED?=gz +INSTALL_ONLY_COMPRESSED?= + +SRCS= article.sgml + +DOC_PREFIX?= ${.CURDIR}/../../.. +.include "${DOC_PREFIX}/share/mk/doc.project.mk" diff --git a/en_US.ISO8859-1/articles/relaydelay/article.sgml b/en_US.ISO8859-1/articles/relaydelay/article.sgml new file mode 100644 index 0000000000..5988de6193 --- /dev/null +++ b/en_US.ISO8859-1/articles/relaydelay/article.sgml @@ -0,0 +1,295 @@ + + + +%man; + + + +%freebsd; + + +%trademarks; + + + +]> + +
+ + Using greylist with &os; + + + Tom + Rhodes + +
trhodes@FreeBSD.org
+ + + + + 2004 + The &os; Documentation Project + + + + An article written for the sole purpose of explaining + the relaydelay system on a &os; mail server. A relaydelay + or greylisting server cuts down on spam simply by issuing + a TEMPFAIL error message to + every incoming email. The purpose behind this idea + is that most spammers use their personal computers with + software to do their spamming. A real mail server should + queue the message and try to send it later. Thus the + spammer most likely moves on to the next host in place + of trying to send the email again. This is an excellent + idea; at least until the spammers begin to use software + that offers try again. But how does this work exactly? + Well, when an email is received the message + ID is stored in a database, the + TEMPFAIL is returned along with the + email. If the email is resent, the message + ID will be checked against the message + IDs currently stored in the database. + If it exists than the email is permitted to reach its + intended recipient. Otherwise, the ID + will be stored and a TEMPFAIL will + be issued. This cycle will continue with every email which + comes into the server. From my personal experience, this + really does cut 90% of the spam. + + + + + Basic configuration + + &os; 4.X includes perl in the base + system, but we need the threaded perl. + Users of &os; 5.X may start the process after the forthcoming + note. + + Remove the base perl and all + traces of perl from the system with + the following command: + + &prompt.root find / -name '*perl*' | xargs rm -rf + + + This will require all ports which require + perl to be rebuilt and reinstalled; + sysutils/portupgrade + is perfect for this. At least it will point out which + ports have been removed and which will need to be + reinstalled. + + + Install lang/perl5.8 + with the USE_THREADS=yes variable + set. The current version of perl + may need to be removed first, errors will be reported + by the install process if that requirement exists. + + + &os; 4.X users will need to run the + use.perl command in the + work work directory. The + permissions may need to be altered to make the + file executable first, I just set it to 755 + with chmod. From this point + on, all users of &os; 4.X should uncomment the + NOPERL option in their local + make.conf file. Otherwise + the base perl will be reinstalled + during the next upgrade. + + + Now for the database server; + MySQL is perfect for this + sort of work. Install the + databases/mysql40-server + along with + databases/p5-DBD-mysql40. + The previous port should imply the installation of + databases/p5-DBI-137 + so that knocks off another step. + + Install the perl based portable + server plugin, net/p5-Net-Daemon + port. Most of these port installations should have + been straight forward. The next step will be more + involved. + + Now install the + mail/p5-Sendmail-Milter + port. As of this writing the Makefile + contains a line beginning with BROKEN, + just remove it or comment it out. It is only marked + this way because &os; does not either have nor installs + a threaded perl package. Once that + line is removed it should build and install perfectly + fine. + + Create a directory to hold temporary configuration + files: + + &prompt.root; mkdir /tmp/relaydelay + &prompt.root; cd /tmp/relaydelay + + Now that we have a temporary directory to work in, the + following URLs should be sent to the + fetch command: + + &prompt.root; fetch http://projects.puremagic.com/greylisting/releases/relaydelay-0.04.tgz + &prompt.root; fetch http://lists.puremagic.com/pipermail/greylist-users/2003-September/000261.html + + + + The source code should now be unpacked: + + &prompt.root; gunzip -C relaydelay-0.04.tgz | tar xvf - + + There should now be several files into the temporary directory + by this point. The appropriate information can now be passed to + the database server by importing it from the + mysql.sql file: + + &prompt.root; mysql < relaydelay-0.04/mysql.sql + + And patch the other files with the + relaydelay.bin by running: + + &prompt.root; patch -d /tmp/relaydelay/relaydelay-0.04 < relaydelay.bin + + Edit the relaydelay.conf and the + db_maintenance.pl file to append the + correct username and password for the + MySQL database. If the database was + built and installed like the above then no users or passwords + exist. This should be altered before putting this into + production, that is covered in the database documentation and + is beyond the scope of this document. + + Change the working directory to the + relaydelay-0.04 + directory: + + &prompt.root; cd relaydelay-0.04 + + Copy or move the configuration files to their respective + directories: + + &prompt.root; mv db_maintenance.pl relaydelay.pl /usr/local/sbin + &prompt.root; mv relaydelay.conf /etc/mail + &prompt.root; mv relaydelay.sh /usr/local/etc/rc.d/ + + Test the current configuration by running: + + &prompt.root; sh /usr/local/etc/rc.d/relaydelay.sh start + + + This file will not exist if the previous &man.mv.1; commands + were neglected. + + + If everything worked correctly a new file, + relaydelay.log should exist in + /var/log. It should + contain something similar to the following text: + + Loaded Config File: /etc/mail/relaydelay.conf +Using connection 'local:/var/run/relaydelay.sock' for filter relaydelay +DBI Connecting to DBI:mysql:database=relaydelay:host=localhost:port=3306 +Spawned relaydelay daemon process 38277. +Starting Sendmail::Milter 0.18 engine. + + If this does not appear then something went wrong, review + the screen output or look for anything new in the + messages log file. + + Glue everything together by adding the following line to + /etc/mail/sendmail.mc or the customized + site specific mc file: + + INPUT_MAIL_FILTER(`relaydelay', `S=local:/var/run/relaydelay.sock, T=S:1m;R:2m;E:3m')dnl + + Rebuild and reinstall the files in the + /etc/mail directory and restart + sendmail. A quick make + restart should do the trick. + + Obtain the perl script located at + + http://lists.puremagic.com/pipermail/greylist-users/2003-November/000327.html + and save it in the + relaydelay-0.04 + directory. In the following examples this script is + referred to as addlist.pl. + + Edit the whitelist_ip.txt file and + modify it to include IP addresses of servers + which should have the explicit abilities to bypass the + relaydelay filters. i.e.: domains + from which email will not be issued a + TEMPFAIL when received. + + Some examples could include: + + 192.168. # My internal network. +66.218.66 # Yahoo groups has unique senders. + + The blacklist_ip.txt file should + be treated similarly but with reversed rules. List within + this file IPs which should be denied without + being issued a TEMPFAIL. This list of + domains will never have the opportunity to prove that they are + legitimate email servers. + + These files should now be imported into the database with + the addlist.pl script obtained a few + lines ago: + + &prompt.root; perl addlist.pl -whitelist 9999-12-31 23:59:59 < whitelist_ip.txt + + &prompt.root; perl addlist.pl -blacklist 9999-12-31 23:59:59 < blacklist_ip.txt + + To have relaydelay start with + every system boot, add the + to the + /etc/rc.conf file. + + The /var/log/relaydelay.log log file + should slowly fill up with success stories. Lines like the + following should appear after a short time, depending on how + busy the mail server is. + + === 2004-05-24 21:03:22 === +Stored Sender: <someasshole@flawed-example.com> +Passed Recipient: <local_user@pittgoth.com> + Relay: example.net [XXX.XX.XXX.XX] - If_Addr: MY_IP_ADDRESS + RelayIP: XX.XX.XX.XX - RelayName: example.net - RelayIdent: - PossiblyForged: 0 + From: someasshole@flawed-example.com - To: local_user + InMailer: esmtp - OutMailer: local - QueueID: i4P13Lo6000701111 + Email is known but block has not expired. Issuing a tempfail. rowid: 51 + IN ABORT CALLBACK - PrivData: 0<someasshole@flawed-example.com> + + The following line may now be added to + /etc/newsyslog.conf to cause for + relaydelay.log rotation at every + 100 Kb: + + /var/log/relaydelay.log 644 3 100 * Z + + + At some point there was an error about improper + perl variables in the + /etc/mail/relaydelay.conf. If those + two variables are commented out then configuration may + proceed as normal. Just remember to uncomment them before + starting the relaydelay process. + + +