Changes between Version 2 and Version 3 of AnnouncerPlugin/Concerns


Ignore:
Timestamp:
Jan 12, 2008, 8:52:48 PM (7 years ago)
Author:
ixokai
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AnnouncerPlugin/Concerns

    v2 v3  
    33  * Optional verification? This would require sending a message asking the person if they can receive mails, and until they say yes, never sending the notices. An external module to 'get' email would be required.
    44  * Be sure apostrophes in names work okay.
    5   * Should be able to plug-into an email address discovery system; e.g. if 'bob' is authenticated, get their address.
    6    * It may be sufficient to add an '@address.com' to the end of an authenticated user in the case of an intranet, but not always. As figuring this out may be slightly complicated, the delivery system should perhaps allow a pluggable
     5  * ~~Should be able to plug-into an email address discovery system; e.g. if 'bob' is authenticated, get their address.~~
     6   * ~~It may be sufficient to add an '@address.com' to the end of an authenticated user in the case of an intranet, but not always. As figuring this out may be slightly complicated, the delivery system should perhaps allow a pluggable~~
    77  * Allow multiple email addresses per user?
    88 * Delivery
    99  * Use a subprocess to prevent blocking and not require threads.
    10   * Test plain text format mailing for proportional font
    11   * Add some X-Trac-* headers for filtering perhaps?
    12   * Email URL syntax: Ticket URL: <URL:http://developer.pidgin.im/ticket/1428#comment:2>
     10  * ~~Test plain text format mailing for proportional font~~
     11  * ~~Add some X-Trac-* headers for filtering perhaps?~~
     12  * ~~Email URL syntax: Ticket URL: <URL:http://developer.pidgin.im/ticket/1428#comment:2>~~
    1313  * Allow for an email's Sender field to specify the user who made the change?
    1414  * A /usr/bin/sendmail IAnnouncementDelivererererer module.