Discussions of development and use of the Sup email client
 help / color / mirror / Atom feed

From: Robert Winkler <robert.winkler.mail@gmail.com>
To: Iain Parris <ipv2.lst@parris.org>
Cc: supmua <supmua@googlegroups.com>
Subject: Re: [sup] Sup Autogenerated Fake Sender
Date: Thu, 09 Jul 2020 14:01:01 -0500	[thread overview]
Message-ID: <1594320920-sup-9158@rob-Lenovo-Y720-15IKB> (raw)
In-Reply-To: <1594316951-sup-6796@ceres>

Hi Iain,

Thanks for the explication. Thus, this is an error notice of failed sending.

Using "V" the mails seem to be completely empty. Well I suppose, they come from
messages that did not arrive (at least 2; but in both cases they were
important enough that I was "reminded" ;-)).

For now, I will not worry and set-up more important functions (the Spam
filtering..). I keep observing the issue.

Best regards, 

Robert 


Excerpts from Iain Parris's message of 2020-07-09 18:59:42 +0100:
> Hi Robert,
> 
> Excerpts from Robert Winkler's message of 2020-07-09 09:50:48 -0700:
> > 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?
> 
> If the email is malformed and missing its "From" header, then the
> default "From" header value used by Sup is "Sup Auto-generated Fake
> Sender <sup@fake.sender.example.com>". See:
> <https://github.com/sup-heliotrope/sup/blob/a2b953743f3f18bfcdcf93678183d135cb45be14/lib/sup/message.rb#L96>
> 
> I wouldn't expect you to see many of these - it's extremely unusual for
> an email to be so malformed that it's missing a From header.
> 
> If you open one of these malformed emails in Sup and press "V", then Sup
> will show you the raw email message. (Press "x" to return to the normal
> view.)
> 
> This should then help you to track down the origin of these malformed
> emails.
> 
> Kind regards,
> Iain
> 

next prev parent reply	other threads:[~2020-07-10  7:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09 16:50 Robert Winkler
2020-07-09 17:59 ` [sup] " Iain Parris
2020-07-09 19:01   ` Robert Winkler [this message]
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=1594320920-sup-9158@rob-Lenovo-Y720-15IKB \
    --to=robert.winkler.mail@gmail.com \
    --cc=ipv2.lst@parris.org \
    --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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox