sieve filter generated email- sent folder
dovecot 2.3.21 pigeonhole 0.5.21. Filters created via roundcube.
Attempting to have filters detect certain email, send a notification text message to mobile via email, and copy that notification email to "Sent" folder.
Filter(s) detect condition, move the email to desired folder and appear, as note in logs outside of dovecot, to sent the notification email. The notification email is not recorded in "Sent" folder and is not received by mobile device.
Is this a "do-able" thing in dovecot/pigeonhole?
If so, how? Docs available?
Let me rephrase this question:
The "mailto:" function does not seem to place a copy of the sent message in the "Sent" folder. In the (snipped) example below the text message is received but no copy is seen in the Sent folder. Is there a setting I have missed or is that expected behavior for the "mailto:" function?
Example: "notify :importance "1" :message "You got pinged - Sent via My Filer" "mailto:123-456-7890@text.some_provider.net";"
Thanks.
joe a.
On 1/25/2024 16:28:38, joe a wrote:
dovecot 2.3.21 pigeonhole 0.5.21. Filters created via roundcube.
Attempting to have filters detect certain email, send a notification text message to mobile via email, and copy that notification email to "Sent" folder.
Filter(s) detect condition, move the email to desired folder and appear, as note in logs outside of dovecot, to sent the notification email. The notification email is not recorded in "Sent" folder and is not received by mobile device.
Is this a "do-able" thing in dovecot/pigeonhole?
If so, how? Docs available?
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
On 2024-01-26 1:05 p.m., joe a wrote:
The "mailto:" function does not seem to place a copy of the sent message in the "Sent" folder. In the (snipped) example below the text message is received but no copy is seen in the Sent folder. Is there a setting I have missed or is that expected behavior for the "mailto:" function?
AFAIK, the copying of outgoing emails to Sent folders is done by email clients, not by the server.
On 1/26/2024 14:31:04, Oscar del Rio wrote:
On 2024-01-26 1:05 p.m., joe a wrote:
The "mailto:" function does not seem to place a copy of the sent message in the "Sent" folder. In the (snipped) example below the text message is received but no copy is seen in the Sent folder. Is there a setting I have missed or is that expected behavior for the "mailto:" function?
AFAIK, the copying of outgoing emails to Sent folders is done by email clients, not by the server.
Ah, I guess you are right.
Still, I hoped there was some way to make it happen, so a mailbox owner might have a ready means to track messages potentially sent under their name.
On 1/26/2024 3:02 PM, joe a wrote:
The "mailto:" function does not seem to place a copy of the sent message in the "Sent" folder. ...so a mailbox owner might have a ready means to track messages potentially sent under their name.
The notify action has a specific purpose - it sends a notification. Outside that scope you can use whatever means that are available to (hint) notify the mailbox owner that they sent a notification.
Good news ... there are a number of ways to skin this cat.
First, the mailto: scheme of the URI supports a 'cc' parameter: mailto:a@a.com?subject=...&cc=b@b.com;c@c.com So, just ad the current user's own email address as a cc back to himself.
From what I see in the enotify code, "bcc" is not supported, but I could be wrong. Note the delimiter between multiple CC's, the semicolon. As I was looking that up it seems different platforms support different delimiters. If you need this and semicolon doesn't work, try a simple comma, or a hex comma+space: b@b.com%2c$20c@c.com
Another way is to notify the current user (as sender) is to simply add another "notify "mailto:${current_user_notification_address}..." right after your first one. Then have Those inbound notification messages filtered into a dedicated "Sent Notifications" folder.
Here is a note from the 2019 Dovecot List by Stephan Bosch that's related to this topic: https://dovecot.org/list/dovecot/2019-October/117341.html That refers to RFC 8580 to do exactly what you're asking without a "loopback" email, File Carbon Copy (FCC) - ;TL/DR; it's not implemented in Dovecot/Pidegonhole (yet). https://datatracker.ietf.org/doc/html/rfc8580
While the 'mailto:' scheme is the most common, the decades-old "trick" of emailing a phone provider to send an SMS is really fragile and easily subject to failure. Personally I'd prefer using Twilio or a similar service to completely eliminate that problem. I'd also try using the "tel:" schema, but that doesn't appear to be implemented in the enotify extension.
Another option for email-to-SMS notifications is to http: or mailto: a service like IFTTT or Zapier, and have them redirect the message to wherever the user actually prefers their messaging - maybe Slack or Skype or flashing the lights in their office.
I hope that helps.
participants (3)
-
dovecot-4tg＠freakin.rocks
-
joe a
-
Oscar del Rio