#7488 closed enhancement (wontfix)
Regarding Encrypted/Signed Outbound Notifications
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | general | Version: | |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
We have a customer requirement for all outbound notifications to be both signed (by trac) and encrypted for the recipient.
We did the following… Route all notifications to a local delivery agent (.forward → procmail). This was done by changing the behavior of get_smtp_address in trac/notification.py
def get_smtp_address(self, address): if not address: return None position = address.find('@') if position < 0: return address + '@localhost' return address[:position] + '@localhost'
This works well for us.
Attachments (0)
Change History (4)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Milestone: | → 0.13 |
---|
This could be part of the enhanced notification architecture scheduled for 0.13.
comment:3 by , 14 years ago
Milestone: | next-major-0.1X |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
This can now be done in a plugin, by implementing the IEmailSender
interface.
comment:4 by , 14 years ago
I have a similar use case and already tried to solve it.
You may have a look at the GnuPG support added to th:wiki:AnnouncerPlugin trunk lately. It would be great to get feedback from you. Have a look at http://trac-hacks.org/wiki/AnnouncerPlugin/MessageEncryption for development notes.
Incidentally, I am looking at using procmail to update tickets using inbound email. Possibly using email2trac or writing something a little more specialized using TracDev/DataModels