Project

General

Profile

Feature #12277

Run our own email (IMAP/POP3/SMTP) server for automated tests

Added by intrigeri 8 months ago. Updated 25 days ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Continuous Integration
Target version:
Start date:
03/02/2017
Due date:
% Done:

0%

QA Check:
Feature Branch:
Type of work:
Sysadmin
Blueprint:
Easy:
Affected tool:
Email Client

Description

See #11890#note-17 and #11890#note-18 for more detailed specs.


Related issues

Blocks Tails - Bug #11890: Checking credentials in Icedove autoconfig wizard sometimes fails in the test suite Confirmed 10/31/2016

History

#1 Updated by intrigeri 8 months ago

  • Assignee changed from intrigeri to anonym
  • QA Check set to Info Needed

anonym, how urgent is that? Can it wait until the 3.1 or 3.2 cycle? I'm really not sure I can commit to anything better.

#2 Updated by intrigeri 8 months ago

  • Blocks Bug #11890: Checking credentials in Icedove autoconfig wizard sometimes fails in the test suite added

#3 Updated by anonym 8 months ago

  • Assignee changed from anonym to intrigeri
  • QA Check deleted (Info Needed)

intrigeri wrote:

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.

#4 Updated by intrigeri 8 months ago

  • Target version set to Tails_3.2

#5 Updated by intrigeri about 1 month ago

  • Description updated (diff)

#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::sftp and tails::tester::support::ssh classes, we would create a tails::tester::support::email class (that can possibly itself include tails::tester::support::email::dovecot and tails::tester::support::postfix if 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::relay for 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 passwd-file driver for userdb and 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!

#7 Updated by intrigeri 25 days ago

  • Target version changed from Tails_3.2 to Tails_3.3

Also available in: Atom PDF