Think Tank Workspaces


Well to make this short. You can just follow the FQA for email

Its almost exact. However I kind of added a few additional things.

SMTP requires @gmail symbol

echo 'key proto=pass service=smtp !password=123456'>/mnt/factotum/ctl

IMAP requires symbol

echo 'key proto=pass service=imap !password=123456'>/mnt/factotum/ctl

This can be slow when you are doing the testing for the first time for debugging

upas/fs -f /imaps/

It will force you to authenticate and tell you that a cert is not recognized.

Test mail with acme in same mount session

echo open /imaps/ mbox >/mail/fs/ctl

basic command to add to $home/lib/profile

upas/fs -n

x509 commands

echo 'x509 sha256=asdfasdf' >/sys/lib/tls/mail
echo 'x509 sha256=asdfasdf' >/sys/lib/tls/smtp

Debug mail

tail -f /sys/log/smtp
tail -f /sys/log/mail
echo hello | mail -s foobar

Lastly you will need to go to google and select a 'less secure apps'. Otherwise everything is dropped.

  1. Open your Google Admin console (
  2. Click Security > Basic settings.
  3. Under Less secure apps, select Go to settings for less secure apps.
  4. In the subwindow, select the Enforce access to less secure apps for all users radio button. ...
  5. Click the Save button.


I got tired of typing in passwords so I used ipso.

echo test | auth/aescbc -e >$home/lib/fact.keys
aescbc key:

You just saved your first key called test chmod 600 $homelib/fact.keys

now add keys to the secrets file (y,n,x) pick 'y'

Any time you want to make a change you run the following. I belive my plumber is set for sam when using ipso.

ipso -a $home/lib/fact.keys
	Warning: the editor will display the secret contents of
	your aescbc files in the clear
aescbc password:
aescbc key:

add the following to $home/lib/profile

if(test -f $home/lib/fact.keys)
	auth/aescbc -d < $home/lib/fact.keys | read -m >/mnt/factotum/ctl

To post a comment you need to login first.