-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Terry Carmen escribió: >> Hi guys. I've been googling around looking for info on this without much >> sucess. Here we are: Some of my customers insist on sending bulk-email >> from their web php sites (you know, bulletins and such). My worst >> nightmare would be having our servers listed in any RBL list because of >> this. How do you guys deal with custommers sending bulk-mail? Are there >> any rules in postfix to prevent it, maybe even delaying them in the queue? > > Unfortunately, this is a human problem, not a technology problem. > > There are various "band-aid" approaches, like running the outbound mail > through spamassassin and HOLDing the "spammy" mail, however this may or may > not catch what you want, since even SpamAssassin has no idea if the user > actually wanted the mail or not.
Yes, we already do that, and more. In fact, I'm not that worried because of the contents of the emails, I'm mostly worried because sending emails to more than 500 people in the recipient list is not very polite, and can trigger undesired actions. People sometimes have poorly designed web pages with a not-too good php emailing code. For instance. I'd like to find a way (maybe through some header checks in outgoing email) so if it detects a large amount of recipients it triggers actions such as: 1.- Adding the 'Precedence: bulk' header field 2.- Clean the message for non-valid characters 3.- If a non-valid sender address is detected, block the sending (for instance, someone may send bulk-email with a From: [email protected] (the apache user) 4.- If the recipient list has invalid recipient domains block the whole sending. 5.- Of course, any modification of the email should be done before doing the dk/dkim signing, which we already do. Can this be (totally or partially) done? Thanks, Ignacio -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpU6hoACgkQoYMx3fsuWupSygCgraZ98tZkNMKLJ53Je0Qt1nNi 5HkAoLx6+xkp8K4nKRCaVadauqV7JIFl =1fQB -----END PGP SIGNATURE-----
