On Wed, Mar 14, 2012 at 02:27:42PM +1100, Peter Ross wrote:
Quoting "Mike Fabre" <mike+luv@fabre.id.au>:
Hi, I have a postfix & dovecot server set up, and I have been given the task of making it put a arbitrary 5-10 minute delay for every email that comes through, whether it be for sent mail or received mail doesn't matter.
Does a configuration as described here work?
Postfix on a dialup machine http://www.postfix.org/STANDARD_CONFIGURATION_README.html#dialup
You could put one more relay in your chain and run the delivery
randomized, instead of in the dialup script.
Apologies if this was discussed before, I probably missed a handful of mails in the thread.
Brilliant, this works perfectly. Thanks, I'll use a cronjob to push all messages through every 5-10 minutes that should work well enough. -- Mike Fabre
On 14/03/12 15:08, Mike Fabre wrote:
On Wed, Mar 14, 2012 at 02:27:42PM +1100, Peter Ross wrote:
Quoting "Mike Fabre"<mike+luv@fabre.id.au>:
Hi, I have a postfix& dovecot server set up, and I have been given the task of making it put a arbitrary 5-10 minute delay for every email that comes through, whether it be for sent mail or received mail doesn't matter.
Does a configuration as described here work?
Postfix on a dialup machine http://www.postfix.org/STANDARD_CONFIGURATION_README.html#dialup
You could put one more relay in your chain and run the delivery
randomized, instead of in the dialup script.
Apologies if this was discussed before, I probably missed a handful of mails in the thread.
Brilliant, this works perfectly. Thanks, I'll use a cronjob to push all messages through every 5-10 minutes that should work well enough.
I was wondering about suggesting a similar method, using fetchmail on a 5 minute timer.. However, instead I could suggest an improvement to the above method. Start by disabling spontaneous delivery, as above. Write a little Perl script or something to scan the mail queue of pending messages, and capture the id for all messages that have been waiting for at least 5 minutes. Then pass just that list of ids to postqueue -i $id rather than calling -f to flush the lot.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 14/03/2012 12:12 PM, Toby Corkindale wrote:
On 14/03/12 15:08, Mike Fabre wrote:
On Wed, Mar 14, 2012 at 02:27:42PM +1100, Peter Ross wrote:
Quoting "Mike Fabre"<mike+luv@fabre.id.au>:
Hi, I have a postfix& dovecot server set up, and I have been given the task of making it put a arbitrary 5-10 minute delay for every email that comes through, whether it be for sent mail or received mail doesn't matter.
Does a configuration as described here work?
Postfix on a dialup machine http://www.postfix.org/STANDARD_CONFIGURATION_README.html#dialup
You could put one more relay in your chain and run the delivery
randomized, instead of in the dialup script.
Apologies if this was discussed before, I probably missed a handful of mails in the thread.
Brilliant, this works perfectly. Thanks, I'll use a cronjob to push all messages through every 5-10 minutes that should work well enough.
I was wondering about suggesting a similar method, using fetchmail on a 5 minute timer..
However, instead I could suggest an improvement to the above method.
Start by disabling spontaneous delivery, as above. Write a little Perl script or something to scan the mail queue of pending messages, and capture the id for all messages that have been waiting for at least 5 minutes. Then pass just that list of ids to postqueue -i $id rather than calling -f to flush the lot. _______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main
Something that I'm sure a perl script could do would be to implement the timer in a variable manner. So that a longer email will get delayed less than a short 1-liner. Also, you could use it to keep track of how many emails have been sent or received in the last <time period of your choice> and give longer delays to those users with higher quantities sent or received. Some more food for thought... Cheers, Tim Lyth -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPYalEAAoJEENQGX7xOJnVXTEH/jtCHaFzMOeIh6iXVgtHF/Dj Nus2BAlfUpUqexUV8QczuZO/lIrTK1EXpXsWtDCmyqxvWaMfIeMORDtXr5ZtHH4n o407Fi5fkcGNv2CST7tPBRb2BcOC9BY/Tq8h6EQdzLTqnH6mpk6XPLw0JbXt3C+G opPPpxVcdU+bCk655B0NI5ww3yh0FygXH9WjsXrxW0yQY0zI29RArjCwgRF7VT4v RoMaerqZuK6teE7n8c3SfsUTnXZeBiAUHZ1b9+UdueG4XCUpvB0qYKlx9ZdkHvdk 1jGqzDu9cFVsBYCnYzpmbagC2hiW5pP7aWqa9tBl7zjyxjM5raRDQf+R7jT+K5Q= =7QtB -----END PGP SIGNATURE-----
participants (3)
-
Mike Fabre -
Tim Lyth -
Toby Corkindale