|Deletions are marked like this.||Additions are marked like this.|
|Line 161:||Line 161:|
|Line 174:||Line 175:|
|ssh -2 -i "$HOME/.ssh/id-bsmtp-$HOST" -C "$HOST" bsmtp-pull-server "$HOST" > "$HOST"||ssh -2 -i "$HOME/.ssh/id-bsmtp-$HOST" -C "$HOST" bsmtp-pull-server "$VHOST" > "$HOST"|
|Line 186:||Line 187:|
|$ ln -f id-dsa id-bsmtp-<yourname>.debian.net||$ ln -f id_dsa id-bsmtp-<yourname>.debian.net|
|Line 194:||Line 195:|
|$ ~/bin/bsmtp-pull <yourname>.debian.net||$ ~/bin/bsmtp-pull <yourname>@people.debian.org <yourname>.debian.net|
Debian Services for the Debian Developper
Following is not tested contents. This is under contraction.
When we became Debian Developper (DD), we knew we obtained few privilages:
- your GPG key in official Debian keyring (This is your source of power)
- package upload privilage,
a cute debian.org mail address, like <username>@debian.org, on MX=master.debian.org
subscription to firstname.lastname@example.org mailing list
- shell accounts on many fast/strange architecture machines.
Well, there is more to it. Let me go through them step-by-step to set up Debian services.
Step 1: New password
You must set your new password through [http://db.debian.org/doc-mail.html mail gateway] first.
$ echo "Please change my Debian password" | gpg --clearsign | mail email@example.com
After validating the request the daemon will generate a new random password, set it in the LDAP directory and respond with an encrypted message containing the new password. (The password can be changed using one of the other interface methods later.)
Please note many of the Debian service have similar [http://db.debian.org/doc-mail.html mail based configuration].
Step 2: Set up your Debian account LDAP data
Configuration of your Debian account can be done through the web interface of [https://db.debian.org/login.html LDAP Debian server] after loging in with your password with "Update my info" button.
- Change password
- Street address
- Postal code
- Latitude / Longitude
- ICQ UIN
- Jabber ID
- Preferred shell
- email forwarded to
- debian-private subscript addr
- IRC nickname
- Web page
- Vacation message
Here you can set your password to a momorable one.
Since Debian does not supply POP3 service, you may think that mails sent to "<yourname>@debian.org" and the "debian-private" mailing list subscription must be picked up at external mail address. This is not the case. You can keep direct secure access to these mail address using Debian services.
I will explain this neat tricks following the information described in [http://lists.debian.org/debian-devel/2001/debian-devel-200102/msg00965.html BSMTP on debian.net] .
Step 3: Set up your shell accounts
Debian offers shell accounts to the developer using SSH service. See sshd(8) and set up your SSH setup locally on your PC.
The virtual .ssh/authorized_keys file for each user can be set by the Debian LDAP server. Probably the most common way to use this function will be:
$ gpg --clearsign < .ssh/id_dsa.pub | mail firstname.lastname@example.org
which will set the authentication key to the identity you are using. Multiple keys per user are supported, but they must all be sent at once.
Step 4: Set up your <yourname>.debian.net domain for mail
Although there seems to be no explicit rule on what 3rd level domain name we can pick, the common sense is to use your Debian account name. Let's set up osamu.debian.net, for example , by creating a text file osamu.txt:
$ cat osamu.txt osamu IN MX 10 gluck.debian.org. osamu IN TXT "Osamu Aoki <email@example.com>" osamu IN TXT "PGP 253A 4076 6A3B CCE2 A426 DEF5 E80F C4C1 A806 1F32" $ gpg --clearsign <osamu.txt | mail firstname.lastname@example.org
Here please note that
- there is no debian.net after osamu, and
- there is a "." (period) after "gluck.debian.org".
Please be considerate to avoid using other DD's account name for the 3rd level sub-domain name.
If you also want a web service on the domain, you can set it by adding your host IP (e.g. 22.214.171.124):
$ cat osamu.txt osamu IN A 126.96.36.199 osamu IN MX 10 gluck.debian.org. osamu IN TXT "Osamu Aoki <email@example.com>" osamu IN TXT "PGP 253A 4076 6A3B CCE2 A426 DEF5 E80F C4C1 A806 1F32" $ gpg --clearsign <osamu.txt | mail firstname.lastname@example.org
Step 5: Set up your PC to accept mail to <yourname>.debian.net domain
You need to set your local PC to accept mails addressed to "<yourname>.debian.net" including ones for "root".
See exim4 configuration.
$ sudo dpkg-reconfigure exim-config
Then, under "Configuring Exim v4 (exim4-config)" menu, you add "<yourname>.debian.net" to the list separated by colon.
Step 6: Set up script to do BSMTP
You obtain BSMTP script run on Debian server from:
I have modified it to be host name neutral ($FILE can be set from argument).
set -e DIR="$HOME/bsmtp" FILE="$1" TRANSIT="$FILE.transit" cd "$DIR" || exit 0 # Is there anything to send? [ -s "$FILE" ] || exit 0 lockfile-create "$FILE" lockfile-touch "$FILE" & TOUCH="$!" trap 'kill "$TOUCH"; lockfile-remove "$FILE"' EXIT ERR HUP INT QUIT TERM if [ -f "$TRANSIT" ]; then cat "$FILE" >> "$TRANSIT" && rm -f "$FILE" else mv -f "$FILE" "$TRANSIT" fi cat "$TRANSIT" rm -f "$TRANSIT" exit 0
You obtain BSMTP script run on your local PC from:
Here I adjusted to match above change.
# Depends: lockfile-progs, ssh set -e if [ -z "$1" ]; then echo "Usage: $0 hostname" 2>&1 exit 1 fi DIR="$HOME/tmp/.bsmtp" mkdir -p "$DIR" cd "$DIR" HOST="$1" VHOST="$2" # TODO: Note that this scheme may currently lose mail if the local disk # fills up! This is obviously very bad. Fix this. # By default, lockfile-create gives up after three minutes, so don't cron # this any more frequently than that without supplying a --retry argument. lockfile-create "$HOST" # Race condition pointed out by pjb: this doesn't guarantee that the lock is # held before the critical section starts. lockfile-touch "$HOST" & TOUCH="$!" trap 'kill "$TOUCH"; lockfile-remove "$HOST"' EXIT ERR HUP INT QUIT TERM ssh -2 -i "$HOME/.ssh/id-bsmtp-$HOST" -C "$HOST" bsmtp-pull-server "$VHOST" > "$HOST" [ -s "$HOST" ] || exit 0 /usr/sbin/sendmail -bS -odq < "$HOST" rm -f "$HOST" exit 0
Since above script is designed to work with SSH key named "$HOME/.ssh/id-bsmtp-$HOST", we make link:
$ cd ~/.ssh $ ln -f id_dsa id-bsmtp-<yourname>.debian.net
Here I assumed you have set up $HOME/id_dsa.pub as the SSH public key described in Step 3. If you make custom SSH keys for Debian activity, that is even better.
Now you can invoke following to retrieve your message.
$ ~/bin/bsmtp-pull <yourname>@people.debian.org <yourname>.debian.net
Now you have mail address on which you do not rely any external resorces.
These days, the value of this setup has been more for the security and stability.
If it is just to get subscription to high volume Debian ML, I would use free (commercial) service such as gmail.com.
Step 7: Alternative mail addresses
Although "<yourname>@debian.org" is most common e-mail address used by the DD on Debian system, there are many available mail addresses for you.
<yourname>@debian.org on MX=master.debian.org
<yourname>-<suffix>@debian.org on MX=master.debian.org
<yourname>@people.debian.org on MX=people.debian.org
See /etc/exim4/* on master.debian.org and people.debian.org:
... # Special Features for users: # .forward-foo - is understood as an extension address for email@example.com # .forward-default - is understood to be a catch all for firstname.lastname@example.org # .procmailrc - with no .forward file invokes procmail for delivery # automatically. # For virtual domains the first lookup is done against a linear text # database called 'aliases', then .forward files are consulted. Exim # filtering is available for these .forward files only. .forward-default # is the universal catch all for everything not handled. # For virtual domains the first lookup is done against a linear text # database called 'aliases', then .forward files are consulted. Exim # filtering is available for these .forward files only. .forward-default # is the universal catch all for everything not handled. ...
See also [http://db.debian.org/forward.html Debian GNU/Linux -- Email Forwarding] and Debian DNS set up to figure out exactly how you use all these.
Let's login to debian machine to see how other people are doing. (Here, people.debian.org.)
Let's see how people uses this host for BSMTP by "cat /etc/exim/bsmtp" and check their domain set up. (I am not publishing exact content of these and hiding some contents here Try these command yourself.):
osamu@gluck:exim$ cat bsmtp r****.debian.net: user=d** group=Debian file=/home/d**/bsmtp/r*****.debian.net s*****.debian.net: user=b** group=Debian file=/home/b**/bsmtp/s*****.debian.net ... r***.debian.net: user=c******* group=Debian file=/home/c*******/bsmtp/r***.debian.net ... osamu@gluck:exim$ dig r***.debian.net ANY ... ;; QUESTION SECTION: ;r***.debian.net. IN ANY ;; ANSWER SECTION: r***.debian.net. 3600 IN MX 0 gluck.debian.org. ... osamu@gluck:exim$ dig s*****.debian.net ANY ... ;; QUESTION SECTION: ;s*****.debian.net. IN ANY ;; ANSWER SECTION: s*****.debian.net. 3600 IN MX 10 s*****.a****.org .au. s*****.debian.net. 3600 IN MX 20 s*****.m****** u*****.com.au. s*****.debian.net. 3600 IN MX 30 alts*****.m***** o*********.com.au. s*****.debian.net. 3600 IN MX 0 gluck.debian.org. s*****.debian.net. 3600 IN TXT "PGP ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** ** **" s*****.debian.net. 3600 IN TXT "PGP **** **** **** **** **** **** **** **** ****" s*****.debian.net. 3600 IN TXT "******** <email@example.com>" s*****.debian.net. 3600 IN A 2**.1**.1**.8* ...
The first one is for one with just fast internet connection without any SMTP mail hosts to get BSMTP service via Debian host as described above.
The second one is for you with semi-stable fixed IP SMTP mail hosts. This ensures mail delivary to the home PC on Cable/DSL/Optical connection (with some risk).
[:OsamuAoki: Osamu Aoki]