From: Robert Winkler <robert.winkler.mail@gmail.com>
To: The Sup email client <supmua@googlegroups.com>
Subject: Sup Autogenerated Fake Sender
Date: Thu, 9 Jul 2020 09:50:48 -0700 (PDT) [thread overview]
Message-ID: <3f5174fe-8cd1-4fb9-95ce-2691c0809f42o@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 176 bytes --]
Hi, I am getting mails from the Sup Autogenerated Fake Sender
<sup@fake.sender.example.com>
What are they good for and where can they be switched off?
Best regards,
Robert
[-- Attachment #1.2: Type: text/html, Size: 261 bytes --]
next reply other threads:[~2020-07-09 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 16:50 Robert Winkler [this message]
2020-07-09 17:59 ` [sup] " Iain Parris
2020-07-09 19:01 ` Robert Winkler
2020-07-09 19:15 ` Iain Parris
2020-07-10 4:30 ` Dan Callaghan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3f5174fe-8cd1-4fb9-95ce-2691c0809f42o@googlegroups.com \
--to=robert.winkler.mail@gmail.com \
--cc=supmua@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox