https://bugs.kde.org/show_bug.cgi?id=359603
--- Comment #32 from Pali Rohár <pali.ro...@gmail.com> --- 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 had to make in email both here and on > lists as well. I'm old enough to remember a time before spammers, believe it > or > not. Now that they produce between 75 and 95% of all the mail sent, the old > RFCs have had to be left behind. Hi Valorie! Two important things: 1) Email clients implement those email RFCs (RFC2822 resp. RFC5322 and others for MIME). RFC5322 is not old for sure and you cannot ignore it or drop it. They are "email standards". 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 regular non-spam messages. Same as sending all emails to /dev/null. It is absolute anti-spam protection but totally useless. > Please believe that our sysadmin team is doing all they can to support our > developers in every way they can. They have sweat blood over these changes, > and > do not welcome repeated pleas to "go back to the old way" -- a way that did > not > work for a large percentage of our developers. I believe that. But I as person who working with emails, working on application which parse, archive, view... incoming emails cannot accept something which mangle emails or fill useless and incorrect info to email headers. Also as I'm (and probably other people) filtering emails by From header it basically means that I cannot longer do it. Plus I need to totally drop information from From header as it contains useless, incorrect and invalid information also for *regular* (non-spam) emails. By filtering I mean also active filter or search rule, not just applying them on incoming emails. If such anti-spam protection mangle emails, damage emails or is inconsistent to "email standards", then that it cause problems to all email clients which are compliant to "email standards". Doing such thing really complicates everything for me for developing. I cannot use anymore filter/search functionality on emails from KDE bugzilla and so those emails have very low value. And bugzilla emails for Kopete project what what I used, which means that I do not have any relevant tool which works for Kopete bugs. > We are all going to have to accept reality, and use the tools we have to > assist > us in our work. So instead of making KDE bugzilla to be compliant for "email standards" which is implemented by email clients and what they expect (and e.g. what I use for my work and tracking of Kopete bugs), you chose to support two/three provides of email-like services gmail, yahoo, aol (which are incompatible for normal emails). This is that reality? I cannot accept such thing! It means that indirectly you are forcing all KDE people (including developer!) to use one of that email-like service and stop using email applications which expect "standard emails". I'm really not happy with this situation it just means that tools for KDE developers are going to be only "gmail" compatible. -- You are receiving this mail because: You are watching all bug changes.
