Project

General

Profile

Feature #5729

Monitor WhisperBack SMTP relays

Added by Tails about 6 years ago. Updated over 2 years ago.

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

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:
Starter:
No
Affected tool:

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 queueResolved


Related issues

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

History

#1 Updated by intrigeri about 6 years ago

  • Category set to Infrastructure
  • Starter set to No

#2 Updated by BitingBird over 5 years ago

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

#3 Updated by bertagaz over 4 years ago

Shouldn't this issue be a child of #5734?

#4 Updated by intrigeri over 4 years ago

Shouldn't this issue be a child of #5734?

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

#5 Updated by sajolida almost 3 years ago

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

#6 Updated by sajolida almost 3 years ago

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

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

Seeing #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 almost 3 years ago

Seeing #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 #12086 that should have a waaaay better cost/benefit ratio.

#8 Updated by intrigeri almost 3 years ago

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

#9 Updated by intrigeri over 2 years ago

  • Description updated (diff)

Also available in: Atom PDF