Re: [9front] /mail/lib: cleanup proposal

[sirjofri+ml-9front@sirjofri.de]

Hey ori,

> I've also rewritten remotemail, so that it uses factotum to figure
> out where to send to. That means that configuring mail is adding
>
> upasname=user@server.com
>
> to your environment, and adding an 'email=user@server.com' to your
> smtp factotum key so we can decide which smtp server to use:
>
> echo 'key proto=pass server=server.com ' \
> 'service=smtp user=user >>email=user@server.com<< !password=12345'
>
> Here's the rewritten remotemail:
>
> #!/bin/rc
>
> # allow users to do their own mail setup
> if(test -x $home/lib/mail/remotemail)
> exec $home/mail/lib/remotemail
>
> sender=$2
> svcpat='[   ]service=smtp[  ]'
> addrpat='[  ]email='$2'[  ]'
> config=`{grep -e $svcpat -e $addrpat /mnt/factotum/ctl}
> if(~ $#config 0)
> exit 'no server'
> for(kv in $config){
> parts=`'='{echo -n $kv}
> switch($parts(1)){
> case server;  server=$parts(2)
> case user;  login=$parts(2)
> }
> }
>
> exec /bin/upas/smtp -as -u $login $server $addr $sender $*(4-)

I like the changes. Also may I suggest that you add my patch for smtp? 
Then unrecognized certificates during smtp can be ignored using a flag 
resulting in encrypted mails. Modern providers like this, although it 
makes mails somewhat unsecure (mails are encrypted which is more secure, 
but no one can ensure you're talking to the right server). Otherwise we 
need to handle certificates better (maybe trust on first use?)

Also since my patch provides a flag server admins can choose which 
security feature they want.

sirjofri