Re: Mail::Vacation abondoned?
Adam Monsen writes: I need a vacation autoresponder that can (at least) be used within ~/.procmailrc. I'll write one unless someone knows of a useful one. I'd like to take over the Mail::Vacation namespace and fill it with some code that works. If you're writing a new e-mail-related module, it's worth liaising with Simon and Casey who have recently been doing much good work in the Email:: namespace, writing a bunch of simple-to-use modules that work well together (along the lines of how others have been doing in the DateTime:: namespace). It would be good for your code to work with theirs. Smylers
Re: Mail::Vacation abondoned?
I like Mail::AutoReply. Any objections? My plan is to use this namespace for code for email autoresponders, ie: vacation autoresponders. Mail::AutoReply will be usable from within a ~/.procmailrc file, an Email::Audit plugin, etc. On Fri, 13 Aug 2004 18:30:22 -0400, Randy W. Sims [EMAIL PROTECTED] wrote: Adam Monsen wrote: (this was originally posted in comp.lang.perl.modules, but received no response) I need a vacation autoresponder that can (at least) be used within ~/.procmailrc. I'll write one unless someone knows of a useful one. Features I need: * doesn't respond to mailing lists * doesn't send to the same email more than once in a user-configurable time period * simple, useful interface (any other suggestions?) I'd like to take over the Mail::Vacation namespace and fill it with some code that works. The tests fail, it won't install, and I tried to contact the author 10 days ago and haven't heard back. Would someone please advise me on this? Would there be a better mailing list to try, module-authors possibly? If getting ownership of the namespace is just hassle, I could certainly create a new one. I am just trying to proceed thoughtfully. How about abstracting it to a general autoreply module; It's applicable to a lot of situations other than vacation. (Mail::AutoReply) Filtering based on header fields is a must, primarily for the reason you mention above, but also as a general autoreply users might want to selectively respond to messages meeting certain criteria. Another idea that comes to mind is letting it monitor remote mail (POP3) or run as a proxy in addition to running as a filter, although that might arguably be left to other modules so users can assemble them anyway they wish depending on the functionality desired??? Just some ideas, Randy. -- Adam Monsen [EMAIL PROTECTED] http://adammonsen.com/
Re: Mail::Vacation abondoned?
Hmm, maybe Email::AutoReply would be better? I would also use Email::Filter::AutoReply for the Email::Filter plugin. On Sat, 14 Aug 2004 17:30:00 -0700, Adam Monsen [EMAIL PROTECTED] wrote: I like Mail::AutoReply. Any objections? My plan is to use this namespace for code for email autoresponders, ie: vacation autoresponders. Mail::AutoReply will be usable from within a ~/.procmailrc file, an Email::Audit plugin, etc. On Fri, 13 Aug 2004 18:30:22 -0400, Randy W. Sims [EMAIL PROTECTED] wrote: Adam Monsen wrote: (this was originally posted in comp.lang.perl.modules, but received no response) I need a vacation autoresponder that can (at least) be used within ~/.procmailrc. I'll write one unless someone knows of a useful one. Features I need: * doesn't respond to mailing lists * doesn't send to the same email more than once in a user-configurable time period * simple, useful interface (any other suggestions?) I'd like to take over the Mail::Vacation namespace and fill it with some code that works. The tests fail, it won't install, and I tried to contact the author 10 days ago and haven't heard back. Would someone please advise me on this? Would there be a better mailing list to try, module-authors possibly? If getting ownership of the namespace is just hassle, I could certainly create a new one. I am just trying to proceed thoughtfully. How about abstracting it to a general autoreply module; It's applicable to a lot of situations other than vacation. (Mail::AutoReply) Filtering based on header fields is a must, primarily for the reason you mention above, but also as a general autoreply users might want to selectively respond to messages meeting certain criteria. Another idea that comes to mind is letting it monitor remote mail (POP3) or run as a proxy in addition to running as a filter, although that might arguably be left to other modules so users can assemble them anyway they wish depending on the functionality desired??? Just some ideas, Randy. -- Adam Monsen [EMAIL PROTECTED] http://adammonsen.com/ -- Adam Monsen [EMAIL PROTECTED] http://adammonsen.com/
