service/email.md

@@ -30,7 +30,7 @@ password". For this, you need to update your account in LDAP:
 
  1. head towards <https://db.torproject.org/update.cgi>
  2. login with your LDAP credentials (here's how to do a [password
-    reset](howto/ldap#password-reset) if you lost that)
+    reset](service/ldap#password-reset) if you lost that)
  3. be careful to hit the "Update my info" button (not the "Full
     search")
  4. enter a new, *strong* password in the `Change mail password:`
@@ -734,7 +734,7 @@ There is currently no easy way to turn this into a highly available / redundant
 SASL authentication is delegated to a dummy
 Dovecot server which is *only* used for authentication (i.e. it
 doesn't provide IMAP or POP storage). Username/password pairs are
-deployed by [ud-ldap](howto/ldap) into `/etc/dovecot/private/mail-passwords`.
+deployed by [ud-ldap](service/ldap) into `/etc/dovecot/private/mail-passwords`.
 
 The LDAP server stores those passwords in a `mailPassword` field and
 the web interface is used to modify those passwords. Passwords are
@@ -961,7 +961,7 @@ than the "smtps" port (465), but both are supported. Lately, the
 documentation has been changed for suggest port 465 first instead.
 
 The TLS server is authenticated using the regular Let's Encrypt CA
-(see [TLS documentation](howto/tls)).
+(see [TLS documentation](service/tls)).
 
 ## Storage
 
@@ -988,7 +988,7 @@ commandline interface.
 On the submission server, SASL authentication is delegated to a dummy
 Dovecot server which is *only* used for authentication (i.e. it
 doesn't provide IMAP or POP storage). Username/password pairs are
-deployed by [ud-ldap](howto/ldap) into `/etc/dovecot/private/mail-passwords`.
+deployed by [ud-ldap](service/ldap) into `/etc/dovecot/private/mail-passwords`.
 
 The LDAP server stores those passwords in a `mailPassword` field and
 the web interface is used to modify those passwords. Passwords are
@@ -1003,7 +1003,7 @@ Most software in this space is written in C (Postfix, Dovecot, OpenDKIM).
 ## Related services
 
 The submission and mail forwarding services both rely on the [LDAP
-service](howto/ldap), for secrets and aliases, respectively.
+service](service/ldap), for secrets and aliases, respectively.
 
 The [mailing list service](services/lists) and [schleuder](service/schleuder) both depend on basic
 email services for their normal operations. The [CiviCRM service](service/crm)
@@ -1040,7 +1040,7 @@ built by anarcat, and is maintained by TPA.
 
 Some parts of the mail services (the submission service, in
 particular) depends on patches on `userdir-ldap` that were partially
-merged in the upstream, see [LDAP docs](howto/ldap#maintainer-users-and-upstream) for details.
+merged in the upstream, see [LDAP docs](service/ldap#maintainer-users-and-upstream) for details.
 
 ## Users
 
@@ -1292,7 +1292,7 @@ Stockholm meeting.
 
 ### Proposed Solution
 
-The proposed design is to setup a new email server in the [howto/ganeti](howto/ganeti)
+The proposed design is to setup a new email server in the [service/ganeti](service/ganeti)
 cluster (currently `gnt-fsn`) with the user list synchronized from
 LDAP, using a new password field (named `mailPassword`). The access
 would therefore be granted only to LDAP users, and LDAP accounts would