Changes between Version 14 and Version 16 of Ticket #30608


Ignore:
Timestamp:
Nov 14, 2019, 7:37:38 PM (2 months ago)
Author:
anarcat
Comment:

reorder the checklist. i don't think having a mail gateway interface is a priority because in all likelyhood people will have *trouble* talking to the interface in the first place if they do need to talk to it. best to work on the web interface instead. furthermore, we should probably setup a server before we start distributing the password file.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #30608 – Description

    v14 v16  
    77It would honestly be of a great help if we could simply have an authenticated SMTP server that I could use with let say my LDAP account for sending emails with my @tpo and not being worried that it gets dropped...
    88
     9----
     10
    911The steps required for this change are:
    1012
    1113 1. [x] create a new field (`emailPassword`?) in the LDAP schema (done)
    12  2. [ ] update the mail gateway to support changes to the field
    13  3. [ ] update the web interface (to support changing the field as well?)
    14  4. [ ] optionally, setup a separate email server to accept submissions and keep mail servers aware that not only eugeni sends email
    15  5. [ ] hook up the password field as authentication in Postfix in the server (probably through ud-generate?)
    16  4. [ ] do tests with the users in this ticket, and if this works, propagate to all current LDAP users
    17  5. [ ] create LDAP accounts for more users who want to use the system
     14 2. [ ] setup a separate email server to accept submissions and keep mail servers aware that not only eugeni sends email
     15 3. [ ] hook up the password field as authentication in Postfix in the server (probably through ud-generate?)
     16 4. [ ] test with TPA users that can modify their own password directly through LDAP
     17 5. [ ] update the web interface (to support changing the field as well?)
     18 6. [ ] optionally, update the mail gateway to support changes to the field
     19 7. [ ] do tests with the users in this ticket, and if this works, propagate to all current LDAP users
     20 8. [ ] create LDAP accounts for more users who want to use the system
    1821
    1922We should also make a design document to follow along.