Run our own email (IMAP/POP3/SMTP) server for automated tests
- Assignee changed from anonym to intrigeri
- QA Check deleted (
anonym, how urgent is that?
Considering it's not the last source of problems on Jenkins, not very.
Can it wait until the 3.1 or 3.2 cycle? I'm really not sure I can commit to anything better.
Absolutely! I let you set the target version.
#6 Updated by intrigeri about 1 month ago
Some implementation ideas to start with, as notes to myself and also to groente who expressed interest in this topic:
- Just like we have
tails::tester::support::sshclasses, we would create a
tails::tester::support::emailclass (that can possibly itself include
tails::tester::support::postfixif it gets too big or badly structured).
- We can apply this new class on misc.lizard: it currently runs Postfix (like all our systems) that only listens on port 127.0.0.1:25. We could run another Postfix instance that listens on
127.0.0.2:587(for the test suite trying to send email).
- In Stretch, the Postfix systemd integration has multi-instance support which makes it easy to isolate that 2nd Postfix instance from the one we already have. See
tails::whisperback::relayfor an example.
- Regarding imaps/pop3s, I would expect that the default dovecot configuration will do something very close to what we want. I would use the
passdb, pointing to
/etc/dovecot/userdb, but YMMV :)
- I'm not sure what we should do about X.509 certificates. The easiest solution might be to use the snakeoil auto-generated keypair + cert, add support to our test suite for importing an arbitrary cert into the Thunderbird, and use that on isotesterN.lizard. Suggestions welcome!