On 09/07/2015 04:06 PM, [email protected] wrote:
> Thanks for the friendly and helpful replies and thanks for considering
> the persistency, forgot to test that (doh!)
Ah, I thought you already had considered it. In that case I'll probably
save you some time by giving you something to start with. It's written
mostly from the top of my head, and may be incomplete. You have been
warned! Here goes:
First users must setup persistence and enable the APT Lists and APT
Packages persistence presets, and then reboot. When Tails boots, an
administration password must be set in the Greeter, and then these
commands should be run in a root terminal:
apt-get update
apt-get install icedove enigmail xul-ext-torbirdy/jessie
for p in icedove enigmail xul-ext-torbirdy/jessie; do
echo "${p}" >>
/live/persistence/TailsData_unlocked/live-additional-software.conf
done
echo "/home/amnesia/.icedove source=icedove" >>
/live/persistence/TailsData_unlocked/persistence.conf
And then a last reboot. From now on, no administration password or
further configuration should be needed. When they boot Tails *and*
enable persistence, then Icedove will install automatically (which will
slowdown the login process somewhat) and any ~/.icedove profile should
be persistent too. Around 100 MiB extra RAM will be used, though, since
Icedove and the other packages (but not ~/.icdove) will be installed in
a RAM-based filesystem.
Disclaimer: I'm unsure how much help our front desk team will be able to
supply you with further help, if needed.
> Yes we'll write a step-by-step guide and provide direct support.
> We'll publish here the link of the guide as soon as it is ready :)
Great! Since your users would be a bit like experimental users for a
future Tails feature, I think we'd like to hear about any general
feedback you get about Icedove (excluding things related to installing
it and the persistence stuff, but certainly including stuff related to
configuration of new accounts etc.) in Tails in general. In that case,
post it to our development list, <[email protected]>.
Lastly, I did a quick test of your service using Icedove + Torbirdy, but
outside of Tails and this highlighted an issue for me: Torbirdy will
guess some pretty sane defaults during account creation that will work
with most ISPs, but notably not with yours. Given
[email protected] it will guess:
POP/IMAP/SMTP user name: some_account
IMAP server: imap.ruggedinbox.com
POP server: pop.ruggedinbox.com
SMTP server: smtp.ruggedinbox.com
but you require:
POP/IMAP/SMTP user name: [email protected]
IMAP server: mail.ruggedinbox.com
POP server: mail.ruggedinbox.com
SMTP server: mail.ruggedinbox.com
If possible, please make {pop,imap,smtp}.ruggedinbox.com resolve to the
same host as mail.ruggedinbox.com, and (not sure how feasible this is)
make both [email protected] and some_account (or switch to
the latter, which likely will piss of most existing users :P) work as
the POP/IMAP/SMTP user names. Then you can just go with Torbirdy's
defaults, which will save you and your users a lot of pain. :)
Cheers!
_______________________________________________
tails-support mailing list
[email protected]
https://mailman.boum.org/listinfo/tails-support
To unsubscribe from this list, send an empty email to
[email protected].
