On Fri, Jan 30, 2015 at 11:06 AM, Mark Constable <[email protected]> wrote:
> I've been meaning to do this for the past decade...
>
> #!/bin/bash
> # autoreply 20150130 (C) Mark Constable <[email protected]> (AGPL-3.0)
> #
> # A simple vacation autoreply script for courier-mta based mailservers.
>
I'm not sure that sharing this script is wise, as it will – unless I
misunderstood something – generate an automatic response to absolutely
everything, every single time.
If I haven't misunderstood, then this script is going to create problems
for anyone using it.
I urge you to read RFC 3834 and check that your script complies with not
only what kind of messages to send autoresponses to, but also how
frequently.
Also, please preserve the original subject. Autoresponders that don't give
any clue regarding what the original message was about are not merely
annoying and problematic, they're also useless.
Imagine getting an autoresponse from every participant on courier-users,
but with no indication that it was about what you sent to courier-users,
every time you sent a message, but due to delivery differences, you won't
know which of your messages sent to courier-users (or indeed, whether it
was just someone joe-jobbing you), caused the autoresponse.
Imagine being a recipient of this, and trying to make the flood stop.
--
Jan
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
