* Sup Autogenerated Fake Sender
@ 2020-07-09 16:50 Robert Winkler
2020-07-09 17:59 ` [sup] " Iain Parris
0 siblings, 1 reply; 5+ messages in thread
From: Robert Winkler @ 2020-07-09 16:50 UTC (permalink / raw)
To: The Sup email client
[-- 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 --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [sup] Sup Autogenerated Fake Sender
2020-07-09 16:50 Sup Autogenerated Fake Sender Robert Winkler
@ 2020-07-09 17:59 ` Iain Parris
2020-07-09 19:01 ` Robert Winkler
0 siblings, 1 reply; 5+ messages in thread
From: Iain Parris @ 2020-07-09 17:59 UTC (permalink / raw)
To: supmua
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [sup] Sup Autogenerated Fake Sender
2020-07-09 17:59 ` [sup] " Iain Parris
@ 2020-07-09 19:01 ` Robert Winkler
2020-07-09 19:15 ` Iain Parris
0 siblings, 1 reply; 5+ messages in thread
From: Robert Winkler @ 2020-07-09 19:01 UTC (permalink / raw)
To: Iain Parris; +Cc: supmua
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
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [sup] Sup Autogenerated Fake Sender
2020-07-09 19:01 ` Robert Winkler
@ 2020-07-09 19:15 ` Iain Parris
2020-07-10 4:30 ` Dan Callaghan
0 siblings, 1 reply; 5+ messages in thread
From: Iain Parris @ 2020-07-09 19:15 UTC (permalink / raw)
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
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [sup] Sup Autogenerated Fake Sender
2020-07-09 19:15 ` Iain Parris
@ 2020-07-10 4:30 ` Dan Callaghan
0 siblings, 0 replies; 5+ messages in thread
From: Dan Callaghan @ 2020-07-10 4:30 UTC (permalink / raw)
To: supmua
Excerpts from Iain Parris's message of 2020-07-09 20:15:46 +01:00:
> 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
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 <djc@djc.id.au>
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2020-07-10 7:02 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-09 16:50 Sup Autogenerated Fake Sender Robert Winkler
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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox