This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB3BBDDF716ADEDD59FB596D9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 11/09/2012 11:57 AM, Kevin Maziere Aubry wrote:
Hi all =20 I'm familiar with postfix and mail in general. And the first really easy thing to configure before mailscanner ( or spamassasin in standalone, reputation filter...) is greylisting. It tak= es 5mn to setup and it is really efficient. =20 I can handle it if needed.
Can you and Dan Yansy work up what the changes would be? Which files do you need to see? How about if we open a Trac ticket, attach the files you need to see/edit, and work through the specifics there? Then we can schedule deploying and testing the new configuration. I agree with Dave that we have some other items going that we need to work individually at a higher priority, but if you can line up the Postfix changes for one of sysadmins with root to deploy, perhaps we can make it relatively painless. - Karsten --=20 Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 --------------enigB3BBDDF716ADEDD59FB596D9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iD8DBQFQnWJj2ZIOBq0ODEERAvqzAKCJv4OH4ioc4KLJo1Exr7MBhx0GuwCg3uYI If0WUWH0XsXBpxxIk28vGlI= =xwWs -----END PGP SIGNATURE----- --------------enigB3BBDDF716ADEDD59FB596D9--