Ticket #675 (closed enhancement: fixed)

Opened 6 years ago

Last modified 21 months ago

Generic mail capability for FAS

Reported by: pfrields Owned by: toshio
Priority: major Milestone:
Component: Development Version:
Severity: Normal Keywords:
Cc: sysadmin-devel Blocked By:
Blocking: Sensitive:

Description

FAS needs a generic email capability. This capability could be used and built upon by other components, so that specific events trigger email.

An example would be the voting application -- at the time the election begins, that event triggers email to eligible voters as defined by the particular election. Another event might be, say, two days before the voting closes.

This capability, though, shouldn't be tied to the voting app, but rather available for any app using FAS. I'm sure there are tons of other use cases for this enhancement.

Change History

comment:1 Changed 6 years ago by mmcgrath

This might be more a thing for the message bus system in ticket #151

comment:2 Changed 6 years ago by mmcgrath

  • Cc sysadmin-devel added

Just so I'm clear about what we're talking about we want a spammer? So the screen would include, perhaps, a list of all the groups in Fedora with check boxes next to them followed by an empty textbox. The would be spammer / emailer would type the text into this box and click submit.

Would we also be including opt-out for people? I'm assuming once the stuff is in place we could easily enable an xmlrpc / json interface to it.

I vote this to be a plugin FWIW, not part of the core of FAS.

comment:3 Changed 6 years ago by pfrields

I suppose we should offer an opt-out, but we also need to be able to override the opt-out in specific cases (like notifications about a Privacy Policy change, for instance). That could be constrained only to people in specific groups. We don't want to turn this into a redundant channel for mailing list email, but we do need some way of contacting every account holder in a specific group regardless of his ML subscriptions.

comment:4 Changed 3 years ago by toshio

This is old and I'm wondering if we maybe fixed this another way --

I vaguely recall talking about GROUP-member@… aliases. Did you know about them? Do they fit the use case you wanted?

comment:5 Changed 21 months ago by edvm

What happened with this ? any news about this ticket ? :-)

comment:6 Changed 21 months ago by toshio

  • Resolution set to fixed
  • Status changed from new to closed

I think that we decided not to proceed with the ticket as written. The GROUP-member aliases may work instead.

Closing.

Note: See TracTickets for help on using tickets.