https://bugs.kde.org/show_bug.cgi?id=359603

--- Comment #47 from Pali Rohár <pali.ro...@gmail.com> ---
On Wednesday 18 May 2016 09:27:25 Ben Cooksley via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=359603
> 
> --- Comment #46 from Ben Cooksley <bcooks...@kde.org> ---
> This will be my very final correspondence on this issue.
> 
> In regards to email standards, they're not relevant here. What
> commonly used email providers dictate as being required is relevant,
> as what people care about is getting their email in a readable form.
> The RFCs and other material are just a guideline towards that. Oh,
> and DMARC is an RFC, so it's part of the standards. GMail, followed
> by Yahoo are our top destinations for email delivery. So they set
> the rules.

Your words basically means: "I do not care about anybody except Gmail & 
Yahoo providers which set and dictate rules how emails could work". 
Sorry, but in open community and for free & open source projects, I 
cannot accept this statement.

If you are doing such thing, please explicitly write to KDE webpages:
We are not supporting email service and appreciate standards anymore. We 
only supports Gmail & Yahoo services and due to our limits we ignore all 
requests for supporting standard email service. Our users are restricted 
to use Gmail or Yahoo otherwise our service will not work correctly.

If you are *not* doing such thing, you cannot mark this report as 
INVALID. As INVALID means "we do not care about non Gmail users".

So I really would like to know what is current state. I really cannot 
accept community which declare themselves as free & open source 
software, but follow big corporations which "set the rules".

> In regards to the solutions you proposed, they either:
> a) Impacted upon the reliability of Bugzilla service; or
> b) Significantly increased the maintenance burden Sysadmin would face
> to maintain Bugzilla. And we have enough maintenance workload as it
> stands. Plus we'd have to author the change in the first place, and
> Bugzilla is written in Perl.

If you need I can help with Perl, this is something which I know.

I proposed solutions, because nobody else proposed anything. And I 
wanted to see this bug fixed. So I did everything which I could.

> And in case you are wondering - every other bug tracking system out
> there, including vanilla Bugzilla, follows the behaviour we follow
> now. Our previous behaviour was a hack, added in many, many years
> ago, and which is not able to be continued with, due to the issues
> noted previously.
> 
> This issue is far from being ignored. It has been looked into and
> discussed here for a very long time. The behaviour the system now
> follows is known, and is the desired and correct behaviour.
> 
> I have no idea why your workflow requires / demands filtering based
> on commenter/reporter email address (in which case, may I suggest
> headers in the email which Bugzilla includes), but it is no longer
> something we can accommodate using the From field in an email.

Reason is quite obvious. Every and I'm sure every one email client show 
3 important headers to user: From, To and Subject. Lot of email clients 
(and those web based too) have some index view, where is list of emails, 
e.g. clickable one email per line and on that line show again only 
From/To and Subject (sometimes also Date). And based on this information 
user open/select email.

Email headers From and To are there for 20+ years and they are not going 
to be changed. All existing email software is based on them and once you 
start rewriting them or mangling, you just broke email support...

And I'm using this information in From, To and Subject headers to 
quickly filter emails and mark what is important and what not. Also for 
searching for comments from specific people, etc...

====

And problem via total nonsense in From header

"From: via KDE Bugzilla <bugzilla_nore...@kde.org>"

is still there and did not hear anybody how and when to fix it. In 
comment 10 you wrote that this is when somebody does entered name at 
all. Should I interpret your last comment, that you are ignoring also 
this problem?

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to