Date: Mon, 13 Aug 2007 08:30:38 +0200 From: peter@bsdly.net (Peter N. M. Hansteen) To: Daniel Gerzo <danger@FreeBSD.org> Cc: freebsd-doc@freebsd.org, Alec <alec@barea.org> Subject: Re: email address on http://docs.freebsd.org/mail/archive Message-ID: <873ayorlo1.fsf@thingy.datadok.no> In-Reply-To: <224945138.20070813003105@rulez.sk> (Daniel Gerzo's message of "Mon, 13 Aug 2007 00:31:05 %2B0200") References: <3962.206.248.190.92.1186944927.squirrel@mail.vmstat.org> <46BF6809.2000406@FreeBSD.org> <1270.206.248.190.92.1186953629.squirrel@mail.vmstat.org> <224945138.20070813003105@rulez.sk>
next in thread | previous in thread | raw e-mail | index | archive | help
Daniel Gerzo <danger@FreeBSD.org> writes: > Actually, there is almost nothing you can do about it. I would > recommed you to install and properly configure spam filters and > maybe to implement graylisting if you have problems with spam. In my book, greylisting is not a maybe if you want a sane mail environment. Unfortunately there's a lot of uninformed comment floating around, the fact is that the few wrinkles that need to be worked around (large outgoing server farms, incompetently run mail services) are easy to work around, and it ends up saving you time and power. - P -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.datadok.no/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?873ayorlo1.fsf>