QP encoding is used to “encode” certain characters into “safe” sequences that can be transmitted over MIME and then “decoded” later back into the characters you had originally. What you see is perfectly legal and correct. If you QP decode your data you will see it looks fine:
Content-Type: text/calendar; method=EPLY"; charset=TF-8"
Content-Transfer-Encoding: quoted-printable
BEGIN:VCALENDAR
X-LOTUS-CHARSET:UTF-8
VERSION:2.0
PRODID:-//Lotus Development Corporation//NONSGML Notes 9.0.1//EN_C
METHOD:REPLY
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:19501029T020000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;BYMINUTE=0;BYHOUR=2;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19500326T020000
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;BYMINUTE=0;BYHOUR=2;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=“W. Europe Standard Time”:20141028T120000
DTEND;TZID=“W. Europe Standard Time”:20141028T130000
TRANSP:OPAQUE
DTSTAMP:20141028T104902Z
SEQUENCE:0
ATTACH:CID:FFFF__=4EBBF7ECDFA8EDEA8f9e8a93df938690918c4EB@ CID:FFFF__=4EBBF7ECDFA8EDEA8f9e8a93df938690918c4EB@
ATTENDEE;PARTSTAT=ACCEPTED;CN=“Manfred Pausch/XXX/YYY/ZZZ”
;RSVP=FALSE:mailto:Manfred.Pausch@our-domain.tldmailto:Manfred.Pausch@our-domain.tld
CLASS:PUBLIC
SUMMARY:Test-Meeting
LOCATION:Test
ORGANIZER;CN=“InvitationSender”:mailto:InvitationSender@external-domain.tldmailto:InvitationSender@external-domain.tld
UID:040000008200E00074C5B7101A82E00800000000303DC18B9CF2CF01000000000000000010000000F8932970965C4F47822809BBDEAEB177
X-LOTUS-UPDATE-SEQ:1
X-LOTUS-NOTESVERSION:2
X-LOTUS-NOTICETYPE:A
X-LOTUS-APPTTYPE:3
X-LOTUS-CHILD-UID:1B3B9A7BCC1967EFC1257D7F003B6B7A
END:VEVENT
END:VCALENDAR