Groups keyboard shortcuts have been updated
Dismiss
See shortcuts
Sup Autogenerated Fake Sender
12 views
Skip to first unread message
Robert Winkler
Jul 9, 2020, 12:50:48 PM7/9/20
to The Sup email client
Hi, I am getting mails from the Sup Autogenerated Fake Sender <s...@fake.sender.example.com>
What are they good for and where can they be switched off?
Best regards,
Robert
Iain Parris
Jul 9, 2020, 1:59:48 PM7/9/20
to supmua
Hi Robert,
Excerpts from Robert Winkler's message of 2020-07-09 09:50:48 -0700:
default "From" header value used by Sup is "Sup Auto-generated Fake
Sender <s...@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
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
> <s...@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
> <s...@fake.sender.example.com>
> What are they good for and where can they be switched off?
default "From" header value used by Sup is "Sup Auto-generated Fake
Sender <s...@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
Iain Parris
Jul 9, 2020, 3:15:50 PM7/9/20
to supmua
Hi Robert,
Excerpts from Robert Winkler's message of 2020-07-09 14:01:01 -0500:
> Thanks for the explication. Thus, this is an error notice of failed
> sending.
Yes, I believe so - or perhaps of failed retrieval (if you are
downloading a copy of emails from a server).
> 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" ;-)).
That's odd. Are the mail files empty (zero byte files) in your Maildir?
You could try to identify empty files with something like:
find ~/Mail -size 0
The root cause, though, is the malformed email files, rather than a bug
in Sup.
Kind regards,
Iain
Excerpts from Robert Winkler's message of 2020-07-09 14:01:01 -0500:
> Thanks for the explication. Thus, this is an error notice of failed
> sending.
Yes, I believe so - or perhaps of failed retrieval (if you are
downloading a copy of emails from a server).
> 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" ;-)).
That's odd. Are the mail files empty (zero byte files) in your Maildir?
You could try to identify empty files with something like:
find ~/Mail -size 0
The root cause, though, is the malformed email files, rather than a bug
in Sup.
Kind regards,
Iain
Dan Callaghan
Jul 10, 2020, 12:30:49 AM7/10/20
to supmua
Excerpts from Iain Parris's message of 2020-07-09 20:15:46 +01:00:
procmail to open the destination file in the maildir but then fail to
process the mail and discard it (thus leaving a 0 byte file behind).
I guess more generally, any error inside your MDA could be causing this.
--
Dan Callaghan <d...@djc.id.au>
> Excerpts from Robert Winkler's message of 2020-07-09 14:01:01 -0500:
> > 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" ;-)).
>
> That's odd. Are the mail files empty (zero byte files) in your Maildir?
> You could try to identify empty files with something like:
>
> find ~/Mail -size 0
>
> The root cause, though, is the malformed email files, rather than a bug
> in Sup.
I have seen this happen when I misconfigured my .procmailrc causing
> > they come from messages that did not arrive (at least 2; but in both
> > cases they were important enough that I was "reminded" ;-)).
>
> That's odd. Are the mail files empty (zero byte files) in your Maildir?
> You could try to identify empty files with something like:
>
> find ~/Mail -size 0
>
> The root cause, though, is the malformed email files, rather than a bug
> in Sup.
procmail to open the destination file in the maildir but then fail to
process the mail and discard it (thus leaving a 0 byte file behind).
I guess more generally, any error inside your MDA could be causing this.
--
Dan Callaghan <d...@djc.id.au>
Robert Winkler
Jul 10, 2020, 3:02:15 AM7/10/20
to Iain Parris, supmua
Hi Iain,
Thanks for the explication. Thus, this is an error notice of failed sending.
filtering..). I keep observing the issue.
Best regards,
Robert
Excerpts from Iain Parris's message of 2020-07-09 18:59:42 +0100:
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
messages that did not arrive (at least 2; but in both cases they were
important enough that I was "reminded" ;-)).
filtering..). I keep observing the issue.
Best regards,
Robert
Excerpts from Iain Parris's message of 2020-07-09 18:59:42 +0100:
Reply all
Reply to author
Forward
0 new messages