https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #48 from Nicolás Alvarez ---
Since we're not going to write and maintain a custom patch to deal with this,
please take this problem to upstream Bugzilla. I'm sure you would be interested
in not having this problem
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #47 from Pali Rohár ---
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 ---
> This will be
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #46 from Ben Cooksley ---
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
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #45 from Valorie Zimmerman ---
(In reply to Pali Rohár from comment #44)
> On Tuesday 17 May 2016 09:29:17 Ben Cooksley via KDE Bugzilla wrote:
> > This isn't a bug - it's intended behaviour and conforms with
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #44 from Pali Rohár ---
On Tuesday 17 May 2016 09:29:17 Ben Cooksley via KDE Bugzilla wrote:
> This isn't a bug - it's intended behaviour and conforms with what email
> providers these days expect. It therefore won't
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #43 from Ben Cooksley ---
This isn't a bug - it's intended behaviour and conforms with what email
providers these days expect. It therefore won't be changing.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #41 from Ben Cooksley ---
Adding custom code will still add a maintenance burden, especially as our
database schema will differ from upstream. It will also create unexpected
behaviour and create a support burden.
We
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #40 from Pali Rohár ---
Ok, and what about option which do not check DNS records when user
change it? That will not lock bugzilla...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #39 from Ben Cooksley ---
In regards to DNS queries, Bugzilla doesn't execute those. Bugzilla passes the
email off to the local mail server, which then handles things at it's
discretion. This maximises the performance
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #38 from Pali Rohár ---
On Saturday 23 April 2016 01:55:21 Ben Cooksley via KDE Bugzilla wrote:
> Detection of DMARC enforcement would involve making DNS queries everytime an
> action takes place on Bugzilla (for every
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #37 from Ben Cooksley ---
Detection of DMARC enforcement would involve making DNS queries everytime an
action takes place on Bugzilla (for every single recipient none the less),
which would make the system unnecessarily
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #35 from Pali Rohár ---
Any response/objections/comments about my idea?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #34 from Pali Rohár ---
On Saturday 26 March 2016 19:13:24 Nicolás Alvarez via KDE Bugzilla
wrote:
> https://bugs.kde.org/show_bug.cgi?id=359603
>
> --- Comment #33 from Nicolás Alvarez
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #33 from Nicolás Alvarez ---
(In reply to Pali Rohár from comment #32)
> 2) If such anti-spam protection drops more than 30% of non-spam emails
> then it is not only useless but must be avoided because it drop
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #32 from Pali Rohár ---
On Monday 21 March 2016 06:02:49 Valorie Zimmerman via KDE Bugzilla wrote:
> Pali, the points you make have also been made by others, so you are not alone
> in your dismay with the changes we've
https://bugs.kde.org/show_bug.cgi?id=359603
Ben Cooksley changed:
What|Removed |Added
Status|REOPENED|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #29 from Pali Rohár ---
Ok, so in this case it is not problem with Gmail service...
Anyway... I still do not understand your decision. You broke all emails which
are sent from Bugzilla, made them non-filter-able and
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #23 from Ben Cooksley ---
Probably better would be to tweak the name to either lack the "via KDE
Bugzilla" (simpler) or say "Anonymous via KDE Bugzilla" / "Unknown via KDE
Bugzilla" when we don't know the name.
In terms
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #18 from Pali Rohár ---
Please do something with this bug! Just having string "via KDE Bugzilla"
in From header without any other information about sender/creator makes
my work with bugzilla really hard. I --- as
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #22 from Pali Rohár ---
Nicolás, thank you! Please at least do that.
Anyway, I still do not understand, why problem is with Bugzilla and not
with (KDE) mailing lists?? I see that KDE mailing lists servers set
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #21 from Nicolás Alvarez ---
Then maybe we should tweak Bugzilla to use the email address if there is no
name.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #20 from Pali Rohár ---
Nicolás: This is independent to email client. Email notification from this bug
contain "From: NAME via KDE Bugzilla " header, but
email notifications from e.g. bug
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #28 from Ben Cooksley ---
The rejection of 3rd party originated email for a domain will depend on the
policies of that domain. Yahoo and AOL are the only ones at this stage who have
set aggressive rejection DMARC
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #24 from Pali Rohár ---
Ben, but there is no difference between email sent by Bugzilla and email sent
by kde.org list (both with d=kde.org DKIM signature). In both cases that email
is sent by outgoing kde.org SMTP
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #27 from Pali Rohár ---
Alright, I missed that second DKIM-Signarure header (from google). So yes,
there are two DKIM signartures, one from google and one from kde.
But it still does not explain, why emails from other
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #26 from Nicolás Alvarez ---
(In reply to Pali Rohár from comment #24)
> Ben, but there is no difference between email sent by Bugzilla and email
> sent by kde.org list (both with d=kde.org DKIM signature). In
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #17 from Pali Rohár ---
Maybe I have knowledge how email should like, but I have absolutely no
knowledge of bugzilla and its code, so I'm not able to develop it...
I can only test implementation if it send correctly
https://bugs.kde.org/show_bug.cgi?id=359603
Christoph Feck changed:
What|Removed |Added
CC||cf...@kde.org
--
You are
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #16 from Frédéric Sheedy ---
No such feature exists in Bugzilla.
But you seem to have technical knowledge to develop it.
Do no hesitate to contribute.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #15 from Pali Rohár ---
So that DMARC is broken by design...
And one more reason for per-bugzilla-account option to enable/disable removing
>From header.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #14 from Nicolás Alvarez ---
"DMARC protects the domain name of the RFC5322:From field against spoofing"
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #13 from Pali Rohár ---
And for exactly such situation there is defined Sender header in RFC 5322 where
should be specified kde.org address and signed by kde key.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #12 from Nicolás Alvarez ---
People are sending DKIM-signed messages from their respective providers into
our mailing lists, and we're forwarding them without modifying anything that
would break the DKIM
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #11 from Pali Rohár ---
And one more thing... Via kde.org domain are running more mailing list servers.
I do not see any discarding of From header in emails send to mailing list. So
why are you doing it for bugzilla
https://bugs.kde.org/show_bug.cgi?id=359603
Ben Cooksley changed:
What|Removed |Added
CC||bcooks...@kde.org
---
https://bugs.kde.org/show_bug.cgi?id=359603
Pali Rohár changed:
What|Removed |Added
Resolution|WONTFIX |---
https://bugs.kde.org/show_bug.cgi?id=359603
Ben Cooksley changed:
What|Removed |Added
Resolution|--- |WONTFIX
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #7 from Nicolás Alvarez ---
Will *you* explain to all our GMail and Yahoo user that it is "their problem"
if every bugzilla message arrives to their spam folder?
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #6 from Pali Rohár ---
I do not agree.
If somebody put correct and RFC-compliant message with meaningful headers
suitable for processing and parsing into spam folder it is his problem.
But if server generates
https://bugs.kde.org/show_bug.cgi?id=359603
Nicolás Alvarez changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #4 from Pali Rohár ---
But if you ignore RFC 5322 how email structure must looks like, you are
breaking email message itself. It means that every email client which is RFC
5322 compliant just show incorrect or less
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #3 from Ben Cooksley ---
Ignore the RFC, it isn't helpful here.
DKIM/DMARC are standards for verifying the email was legitimately sent. In
particular, they operate to ensure headers and the message body originate from
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #2 from Pali Rohár ---
Why it does now work? RFC 5322 says:
The "From:" field specifies the author(s) of the message, that is, the
mailbox(es) of the person(s) or system(s) responsible for the writing of the
message.
https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #1 from Ben Cooksley ---
The change was made due to DKIM/DMARC issues. You can no longer set "From" to
be the person who you are representing - it just does not work.
--
You are receiving this mail because:
You are
44 matches
Mail list logo