(08-28-2019, 07:16 PM)ccMcBride Wrote: misnamed field name. NOT my structure, but is the structure being used.
enable_ssl is actually 'use encryption' and
flags is actually the method of encryption (0 being none)
Still looks odd to me, but OK.
(08-28-2019, 07:16 PM)ccMcBride Wrote: code for adding the ics:
Where are you setting the TIdMessage.ContentType when using the TIdMessage.MessageParts?
Why are you setting the TIdAttachment.ContentDisposition to 'inline' instead of 'attachment'? And you are STILL setting the ExtraHeaders['Content-ID'] header when you shouldn't be.
(08-28-2019, 07:16 PM)ccMcBride Wrote: mail.txt: (this one blows up when I use outlook365 as my SMTP email server)
Define "blows up" exactly.
(08-28-2019, 07:16 PM)ccMcBride Wrote: and the only difference between the two is this line:
not working: (throws recipient error when sent through outlook smtp, but works when I use gmail smtp server)
ORGANIZER;CN=3DConnie M.:mailto:conniem@provantagesoftware.com
Works:
ORGANIZER;MAILTO:conniem@provantagesoftware.com
I have tried putting the CN part in quotes, and tried putting it in double quotes, but I still get the same error.
That difference is merely in the content of the "ORGANIZER" field, regardless of how that content is being transported via email. One email is using "CN=<name>:mailto:<email>" (ignore the changing of '=' characters to '=3D', that is just the Quoted-Printable encoding at play during transport - any MIME-compliant receiver will decode '=3D' back to '=' before processing the ICS data), whereas the other email is using "MAILTO:<email>" instead. That has absolutely nothing to do with Indy, and if the receiver can't handle the added "CN" value, that is not Indy's fault.
That being said, if you find that the receiver is simply not handling the Quoted-Printable encoding properly, you CAN disable it (though I would not recommend that) by setting the TIdText.ContentTransfer property to either '7bit', 'base64', '8bit', or 'binary' instead ('quoted-printable' is the default if left blank).
(08-28-2019, 07:16 PM)ccMcBride Wrote: so, is the message still malformed?
There is an extra 'text/plain' MIME part that is present in your emails that doesn't belong there (it should not be causing problems for iCalendar-aware receivers, though), but I don't see your code adding a TIdText for that text, and Indy should not be generating a blank text MIME part like that (if it is, that will have to be addressed).