Feature #5729

Monitor WhisperBack SMTP relays

Added by Tails 2013-07-18 07:45:10 . Updated 2017-02-15 12:46:10 .

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
2016-12-26
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

We should monitor WhisperBack SMTP relays, e.g. using Nagios. We already monitor 1. whether the WhisperBack SMTP relay is up and answers SMTP commands; 2. whether the WhisperBack SMTP relay has email queued for delivery.

What’s left to do is an end-to-end test of the entire system, which is hard to implement.

Subtasks

Bug #12086: Monitor the size of WhisperBack SMTP relay's queue Resolved

100

Related issues

Related to Tails - Bug #12085: "Unable to connect to the server" when sending WhisperBack report Resolved 2016-12-26

History

#1 Updated by intrigeri 2013-10-04 06:47:44

  • Category set to Infrastructure
  • Starter set to No

#2 Updated by BitingBird 2014-06-09 11:04:05

  • Subject changed from monitor WhisperBack SMTP relays to Monitor WhisperBack SMTP relays

#3 Updated by bertagaz 2015-06-25 03:21:38

Shouldn’t this issue be a child of Feature #5734?

#4 Updated by intrigeri 2015-06-28 04:12:21

> Shouldn’t this issue be a child of Feature #5734?

Possibly, but it depends on the outcome of Feature #8649. Once that one is closed, then we’ll need a bunch of new tickets anyway.

#5 Updated by sajolida 2016-12-26 11:36:08

  • related to Bug #12085: "Unable to connect to the server" when sending WhisperBack report added

#6 Updated by sajolida 2016-12-26 11:40:04

  • Assignee set to bertagaz
  • QA Check set to Info Needed

Could you clarify here why was this not part of Feature #5734 in the end?

Seeing Bug #12085 and that similar things happens pretty much every year, it seems “a high-priority service” to me and marked as “HIGH” in https://tails.boum.org/blueprint/monitor_servers/#index21h2.

#7 Updated by intrigeri 2016-12-26 12:14:30

> Seeing Bug #12085 and that similar things happens pretty much every year, it seems “a high-priority service” to me and marked as “HIGH” in https://tails.boum.org/blueprint/monitor_servers/#index21h2.

The complete version is:

* HIGH: SMTP server is up
* MEDIUM: email is actually relayed (would be truly good to have, but hard
to implement, so the cost/benefit ratio is likely to be pretty bad)

… which is exactly what was implemented. We do have a check for “SMTP server is up”.

Regarding the other (MEDIUM) check, we explained on the blueprint why it didn’t make it.
But I’ve just filed Bug #12086 that should have a waaaay better cost/benefit ratio.

#8 Updated by intrigeri 2016-12-26 12:15:01

  • Assignee deleted (bertagaz)
  • QA Check deleted (Info Needed)

#9 Updated by intrigeri 2017-02-15 12:46:10

  • Description updated