User Tools

Site Tools


userdoc:mail

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
userdoc:mail [2014-09-02 19:39]
mricon [Sending outgoing mail]
userdoc:mail [2020-05-08 14:55] (current)
mricon
Line 1: Line 1:
 +~~REDIRECT>​https://​korg.docs.kernel.org/​mail.html~~
 +
 ====== Using your username@kernel.org alias ====== ====== Using your username@kernel.org alias ======
 We do not provide mailbox hosting to kernel.org members, but we do provide a redirect alias to the address you specified when requesting an account. The only other service we offer in addition to the redirect is outgoing mail SMTP. We do not provide mailbox hosting to kernel.org members, but we do provide a redirect alias to the address you specified when requesting an account. The only other service we offer in addition to the redirect is outgoing mail SMTP.
Line 39: Line 41:
 You should be able to use this output to configure any other client for authenticated SMTP sending. The automatically generated random password is not used for anything else, so there is little concern in leaving it cleartext in your configuration files. You should be able to use this output to configure any other client for authenticated SMTP sending. The automatically generated random password is not used for anything else, so there is little concern in leaving it cleartext in your configuration files.
  
-**Note**, that **you may use gmail or many other web services ​for sending ​your username@kernel.org ​mail** ​-- most of them do the right thing with envelope-sender, so even if we put SPF/DKIM records in place for kernel.org in the future, you should ​not be affected by various spam filters.+===== Adding a kernel.org UID to your PGP key ===== 
 + 
 +If you are sending PGP-signed mail using your username@kernel.org email addressyou should add that UID to the public key (should be the same key you used to apply for your kernel.org account). 
 + 
 +<​code>​ 
 +gpg2 --quick-add-uid [keyid] '​Firstname Lastname <username@kernel.org>'​ 
 +gpg2 --send-keys [keyid] 
 +</​code>​ 
 + 
 +To find out your keyid, you can run: 
 + 
 +<​code>​ 
 +gpg2 --list-secret-keys 
 +</​code>​ 
 + 
 +Your keyid (either ​the full fingerprint,​ or the last 16 characters) should be listed ​right under the sec line. 
 + 
 +==== The kernel.org Web Key Directory ==== 
 + 
 +We publish the [[https://​wiki.gnupg.org/​WKDHosting|Web Key Directory (WKD)]] for all accounts, so once you add the kernel.org uid to your public key, people will be able to obtain your key automatically ​if they use an email client that supports automatic WKD key retrieval. If they use the default TOFU trust mechanism, the key retrieved from kernel.org ​will be automatically marked as trusted. 
 + 
 +To check which key we have in the WKD, you can run the following command: 
 + 
 +<​code>​ 
 +GNUPGHOME=$(mktemp -d) gpg2 --auto-key-locate wkd --locate-keys [username]@kernel.org  
 +</​code>​ 
 + 
 +The output ​should ​display which key ID was retrieved from the WKD. If instead you see an error message like this: 
 + 
 +<​code>​ 
 +gpg: key [keygrip]: no valid user IDs 
 +gpg: Total number processed: 1 
 +gpg:           w/o user IDs: 1 
 +gpg: error retrieving '​[username]@kernel.org'​ via WKD: No fingerprint 
 +</​code>​ 
 + 
 +This means there is no corresponding username@kernel.org uid on the key retrieved from the directory. If you've just added the kernel.org uid to your key, it takes about 24 hours for the WKD to be regenerated. If you repeatedly get this error even after 24 hours, please contact [[userdoc:​support]]. 
  
 ===== Changing your forwarding address ===== ===== Changing your forwarding address =====
-Please submit ​pgp-signed ​request to [[userdoc:​support]] with your username and the new desired destination. ​Successful ​PGP signature verification is required step before we proceed with the change.+==== If you have kernel.org ssh account ==== 
 + 
 +You can self-administer your forwarding address if you have an active ssh account allowing you to access gitolite.kernel.org. To list your current forwarding address(es):​ 
 + 
 +<​code>​ 
 +ssh git@gitolite.kernel.org mailforward list 
 +</​code>​ 
 + 
 +To add another forwarding address in addition to what is already present: 
 + 
 +<​code>​ 
 +ssh git@gitolite.kernel.org mailforward add foo@example.com 
 +</​code>​ 
 + 
 +To replace your current forwarding address(es):​ 
 + 
 +<​code>​ 
 +ssh git@gitolite.kernel.org mailforward set foo@example.com 
 +</​code>​ 
 + 
 +For other commands and more information,​ run: 
 + 
 +<​code>​ 
 +ssh git@gitolite.kernel.org mailforward help 
 +</​code>​ 
 + 
 +==== If you don't have an active ssh account ==== 
 +Please send a request to [[userdoc:​support]] with your username and the new desired destination. 
 + 
 +:!: The new address must match one of the UIDs on your PGP key and exist on keyservers. See the section above for instructions on how to add UID to your PGP key. 
 + 
 +We can also forward to multiple destinations. Follow ​the same procedure to request additional destinations. 
 + 
 +===== Topical addresses ===== 
 +We support using ''​+topic''​ addressing, so you can use any number of ''​username+topic@kernel.org''​ addresses when doing things like subscribing to mailing lists. E.g.: 
 + 
 +  - username+lkml@kernel.org
  
 +They will be correctly delivered to your forwarding address.
userdoc/mail.1409686748.txt.gz · Last modified: 2014-09-02 19:39 by mricon