From time to time there's an email you want to let through without turning maillog completely off. I propose adding the ability to let messages through on a case-by-case basis. I think the ability makes sense in two places: 1) In the message right after an email is suppressed and 2) from the logs, as depicted below.
The ability to resend a message (from the logs) seems valuable even if you're not suppressing email—in case you accidentally delete a message from your mail server or client and need another copy of it or are testing another aspect of your email functionality (like a spam filter) that may have blocked delivery.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | resend.patch | 17.97 KB | danielbeeke2 |
| maillog-screenshots.gif | 6.7 KB | traviscarden |
Comments
Comment #1
miro_dietikerI like the idea.
Possibly we should add new data about a mail:
- flag if mail was sent
- date when really sent
- send count
Alternatively a 1:n table with n possible send events per mail.
A little more ui state would be great. Send, resend.
However, we should consider the original system class on resend/ delayed send to allow the message to take the same path.
There might be some additional options here and the D7 tools are not yet complete.
Comment #2
danielbeeke2 commentedHere is a starting point for the drupal 6 version:
I added the resend link in the default view
I added a resend function that sends it directly via mail()
I also changed the database table to have a column realsend_date
This is the flag and the send date
Comment #3
anjjriit commented+1 for @TravisCarden and i like #1 idea.
Comment #4
damienmckennaThis needs to be updated after #2655872: Update Views definition is committed.
It's an interesting idea, but I wonder if another module would be better off handling it, e.g. the SMTP module?
Comment #5
damienmckennaBerdir & miro_dietiker: What do you think of this as a feature request? Is it ok or should we push this functionality to something like SMTP?
Comment #6
miro_dietikerIMHO the module that logs, possibly suppresses sending, is the only party that can then trigger sending again.
Thus if it is needed, maillog would need to support it.
The feature should be transport agnostic to allow resend no matter what transport (sendmail, SMTP, cloud provider) you use.