= Sourcehut Mail =

The '''Sourcehut''' software system uses email for user communication.

<<TableOfContents>>

----



== SMTP Connection ==

To route outbound email (i.e. automated notifications), Sourcehut needs to run alongside some [[Email/MTA|MTA]].

For an unencrypted connection, try:

{{{
[mail]
smtp-host=localhost
smtp-port=25
smtp-encryption=insecure
smtp-auth=none
}}}

For an encrypted connection, try:

{{{
smtp-encryption=starttls
}}}

For an authenticated connection, try:

{{{
smtp-auth=plain
smtp-user=myuser
smtp-password=mypassword
}}}

----



== Sending Mail ==

The sender address must be configured with a value taht the MTA will accept.

{{{
smtp-from=postmaster@localhost
}}}

A passwordless PGP key also needs to be made available, so that mail can be verified to be authentic.

{{{
pgp-privkey=/etc/sr.ht/pgp.key
pgp-pubkey=/etc/sr.ht/pgp.pubkey
pgp-key-id=KEYID
}}}

For instructions on exporting keys to files and removing passwords from keys, see [[Encryption/GPG#Usage|GPG]].

Error reports are generated automatically as emails. Configure the sender and recipient addresses.

{{{
error-to=me@example.com
error-from=postmaster@example.com
}}}

----



== LMTP Servers ==

The mailing list and bug tracker services use [[Email/LMTP|LMTP]] servers. Emails can be routed based on the destination address; all emails for `todo.example.com` should go to the corresponding socket.

The LMTP servers are designed to use either a [[Linux/Networking#Unix_Sockets|unix socket]] or a [[Protocols/TCP|TCP socket]] (i.e. a networking port), but my personal experience is that the unix sockets are more reliable.

{{{
sock=/tmp/todosrht-lmtp.sock
sock-group=mtauser
posting-domain=todo.example.com
}}}



----
CategoryRicottone