Blocked Senders

Stop repeat offenders with one command. When you block a sender, their future emails are silently dropped β€” no issue created, no notification sent, no disruption to your team.

Blocking a sender

On any issue or discussion created from an email, add a comment:

/block-sender

Scitor extracts the sender’s email address from the issue metadata and adds it to the block list. The sender’s email is stored as a SHA-256 hash for privacy.

Unblocking a sender

To remove a sender from the block list:

/unblock-sender

What happens when a blocked sender emails

Emails from blocked senders are quietly discarded:

  • No issue or discussion is created
  • The sender receives no notification or bounce message
  • Your team is never interrupted

Warning

Blocked senders will not know they’ve been blocked. Their emails are quietly discarded without any bounce or error message.

Privacy

  • Email addresses are never stored in plain text
  • Only a SHA-256 hash is kept in the blocks table
  • The hash cannot be reversed to reveal the original email address
  • Block lists are per-installation (per repository)

You can still reply

Blocking only affects inbound emails. You can still use /send to reply to a blocked sender on existing issues that were created before the block.

Scitor β€” Turn GitHub into your support platform