- Mailtrain would not start if built-in ZoneMTA had to retry the startup
- Campaign list showed "Sending" instead of "Scheduled" for scheduled campaigns
ERR! Senders Sending message to 4:1 failed with error: shortid is not defined. Dropping the message.
verb ReferenceError: shortid is not defined
at html.replace (/home/mailtrain2/mailtrain/server/lib/message-sender.js:236:29)
at String.replace (<anonymous>)
at MessageSender._getMessage (/home/mailtrain2/mailtrain/server/lib/message-sender.js:235:25)
at MessageSender._sendMessage (/home/mailtrain2/mailtrain/server/lib/message-sender.js:345:34)
This fixes that triggered campaign e-mails are not reported in ui and so it's also possible to
create another triggered campaign on this first triggered one.
What i don't understand why their is a difference in handling of a triggered campaign and a normal one in sending.
Also i expected that a triggered campaign can only be send once to an user regardless which trigger fires the send.
But currently it's send for every trigger that is defined in a campaign.
Fix - message sent to a list not associated with a campaign couldn't be shown in archive - to know which message to show even if the list is not at the campaign, we store test messages in table test_messages
- More options how to send test emails.
- Fixed problems with pausing a campaign (#593)
- Started rework of transactional sender of templates (#606), however this contains functionality regression at the moment because it does not interpret templates as HBS. It needs HBS option for templates as described in https://github.com/Mailtrain-org/mailtrain/issues/611#issuecomment-502345227
TODO:
- detect sending errors connected to not able to contact the mailer and pause/retry campaing and queued sending - don't mark the recipients as BOUNCED
- add FAILED campaign state and fall into it if sending to campaign consistently fails (i.e. the error with sending is not temporary)
- if the same happends for queued email, delete the message
