Bug 207012

Summary: KMail: Define custom headers doesn't seem to change anything
Product: [Applications] kmail Reporter: Jeffrey <eljefedelito>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: kollix, sgh
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Changes to KMails headers

Description Jeffrey 2009-09-10 23:57:51 UTC
Version:            (using KDE 4.3.1)
OS:                Linux
Installed from:    Debian testing/unstable Packages

The bug itself is:
Why are the headers not being updated correctly per the changes I made to Compose > Headers (as shown in the image at http://imagebin.ca/view/qjHzvM.html and soon to be attached to the bug report)

Long story short, my emails at work were being rejected by a ticketing system.  I looked into the issue and it seems that my KMail Headers were giving this:

> Content-Type: multipart/signed;

when I would sign with a GPG key, and as

> Content-Type: Text/Plain;

when I wouldn't sign.  Either way I was being rejected by the system, and I never sent any HTML-formatted emails at all.  Other people's emails were showing, in lowercase:

> Content-Type: text/plain;

I changed the custom headers per this image:
> http://imagebin.ca/view/qjHzvM.html
and my headers are pretty much the same, except:

1.  My work's ticketing system is no longer rejecting me, no matter how much HTML etc I put into an email, and

2.  The changes aren't actually happening in the headers for new emails, and I don't know why nor do I know why the system would start accepting my emails.

What would be different?  Here are the headers themselves:


Old headers:

From: XXX X XXX <XXX.XXX@company.com>
 Organization: XXXXXXXX
 X-KMail-Transport: Scalix Server
 To: "W/O System" <workmanager@company.com>
 Subject: test email [W0025295]
 Date: Thu, 10 Sep 2009 10:31:07 -0500
 User-Agent: KMail/1.12.1 (Linux/2.6.30-1-686; KDE/4.3.1; i686; ; )
 X-KMail-QuotePrefix: >
 MIME-Version: 1.0
 Content-Type: multipart/signed;
   boundary="nextPart3575412.Q8i8Slnan2";
   protocol="application/pgp-signature";
   micalg=pgp-sha1
 Content-Transfer-Encoding: 7bit
 Message-Id: <200909101031.08042.XXX.XXX@company.com>
 Status: RO
 X-Status: RS
 X-KMail-EncryptionState: N
 X-KMail-SignatureState: F
 X-KMail-MDN-Sent: 
 X-UID: 84401


New headers after changes per the image at http://imagebin.ca/view/qjHzvM.html

To: Work Manager <Work.Manager@company.com>,
 Subject: test six as HTML [W0025295]
 From: XXX X XXX <XXX.XXX@company.com>
 Organization: XXXXXXX
 X-KMail-Transport: Scalix Server
 Date: Thu, 10 Sep 2009 10:56:43 -0500
 X-KMail-QuotePrefix: >
 X-KMail-Markup: true
 MIME-Version: 1.0
 Content-Type: multipart/signed;
   boundary="nextPart1359458.HvMZTtbvDf";
   protocol="application/pgp-signature";
   micalg=pgp-sha1
 Content-Transfer-Encoding: 7bit
 Message-Id: <200909101056.43656.XXX.XXX@company.com>
 Status: RO
 X-Status: RS
 X-KMail-EncryptionState: N
 X-KMail-SignatureState: F
 X-KMail-MDN-Sent: 
 X-UID: 84456
Comment 1 Jeffrey 2009-09-10 23:59:19 UTC
Created attachment 36851 [details]
Changes to KMails headers

Changes to headers as show in image don't actually change the headers in outgoing emails.
Comment 2 Jeffrey 2009-09-11 00:04:47 UTC
Per conversations on Freenode #kontact, this is not meant to rewrite the headers, just add additional headers.  Which is fine but that isn't happening either.
Comment 3 Martin Koller 2009-09-11 22:13:21 UTC
if your bug report is now about new headers not being added, I have to close this report with WORKSFORME.
I added a header named "BLAAA" with value "Hallo" and the sent mail now has:
...
X-KMail-QuotePrefix: >
X-KMail-Identity: 511735207
BLAAA: Hallo
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="utf-8"
...

So it works for me.
Comment 4 Søren Holm 2011-09-04 20:02:50 UTC
Please reopen. KMail 4.7.0 does not adde extra headers.