question about email automation
Hello,
this is unrelated to using mm itself but was wondering if anyone here had any insight they could share;
i run a mailing list on mm 2.x. periodically i send out an event opening email to the list. this is typically followed by a conclusion email at the end of a specific period. in the interim period i would like to send out reminders of the event to the list but would like to automate this task. i want the reminders to be triggered by my opening email and end with my conclusion email.
has anyone done this and how? i've looked at ifttt and zapier but wasn't sure. thanks.
--
Fabian S.
OpenPGP:
0xA1250C2112D2D0E53E5BD964BBB5B16CFB701CD7
Fabian A. Santiago writes:
i run a mailing list on mm 2.x. periodically i send out an event opening email to the list. this is typically followed by a conclusion email at the end of a specific period. in the interim period i would like to send out reminders of the event to the list but would like to automate this task. i want the reminders to be triggered by my opening email and end with my conclusion email.
Mailman 2 depends on cron for periodic activity. How to set up a cron job depends on your system. I'd guess the 'ifttt' and 'zapier' utilities depend on cron as well, but I've never heard of them before.
Even if the scripting described below sounds painful, perhaps a description of the process will help make sense of the utilities you mentioned.
There are two basic ways to do this, one of which involves Mailman itself, and one which does not. The one that does not involves creating a script, which you attach to a specific mailbox (this is MTA specific). Then you send the announcement mail to that mailbox, which invokes the script. The script places the reminder message in a specific place (formatted as a reply to the announcement message), and sends the announcement mail to the list address. Then the cron job triggers periodically, and sends out any messages that are in the specific place (this is MTA specific, but "sendmail -t < message" works on most systems). You also send the conclusion email to that place, as a reply to the announcement message. The script parses out the In-Reply-To message-id, scans the specific place for messages that are replies to that message-id, and deletes them. Then it sends the conclusion email to the list address.
The other is basically the same, except that you send the announcement and conclusion mails to the list address, marked as one of your announcements in some way. Basically the same code as above, with the addition of first checking if the message is an announcement or a conclusion (if not, it does nothing), is added to Mailman as a Handler. (This can be done globally, or in a list-specific way.)
Perhaps one of the utilities you mentioned can provide the script or even much of the MTA and cron interfacing.
The scripting itself can be pretty simple, or it could be medium complex, depending on how customized the reminder message should be for a given announcement, and how free-form the announcements are. In the simplest case, the reminder message is just the original announcement message with the Message-ID copied to the In-Reply-To field and the Message-ID field deleted (either Mailman or the MTA will add one).
Steve
On 5/30/19 8:04 AM, Fabian A. Santiago wrote:
Hello,
Hi,
i run a mailing list on mm 2.x. periodically i send out an event opening email to the list. this is typically followed by a conclusion email at the end of a specific period.
How specific is the period? Is the end known at the start, i.e. 3 months, or is it dependent on when a project completes?
in the interim period i would like to send out reminders of the event to the list but would like to automate this task. i want the reminders to be triggered by my opening email and end with my conclusion email.
I don't know if it really matters, but please clarify if you're talking about one list that multiple events are discussed on or if it's a different list per event.
has anyone done this and how?
I have not.
I think one list for multiple events would be simpler from an automation point of view. I say this because I'd subscribe a utility account that would receive copies of all messages and be able to parse them for specific keywords (event <bla> starts <date>, etc.).
I would likely have this script set up (Unix) at jobs (vs cron) as I think programmatically scheduling them might be easier. The at job can send the emails (typical script sending email) at the specified times.
If the duration of the project is known ahead of time, you can pre-schedule multiple at jobs and be done with it.
If the duration of the project is not known ahead of time, I think you will need to have each reminder iteration schedule the next at job. You will also need to have the utility account be a bit smarter and look for the end of job / event / project announcements. - In this case, I'd likely enhance the at job to look for a (flag) file or contents to determine if it should send the reminder or not. That way, you can finish a job / even / project and make sure that there's not accidentally spurious reminders that get sent or worry about cleaning them up by simply removing the (flag) file or changing it's contents.
I know that it's crude. But it will get the job done.
i've looked at ifttt and zapier but wasn't sure. thanks.
I'm not familiar with them. Sorry.
-- Grant. . . . unix || die
participants (3)
-
Fabian A. Santiago
-
Grant Taylor
-
Stephen J. Turnbull