Author Topic: SMTP MIME How do I achieve them  (Read 954 times)

0 Members and 1 Guest are viewing this topic.

Offline MrSpecialist

  • Sr. Member
  • *
  • Posts: 348
  • Karma: +1/-0
  • I'm an expert!
    • View Profile
SMTP MIME How do I achieve them
« on: November 27, 2008, 02:15:04 AM »
SMTP MIME How do I achieve them

Hi All,

I have an agent which is scheduled to run on a server. The agent shoots out a few mails everyday.

For testing the agent, I run it on my local client. When run on the client, the following code works perfectly. (Thanks to a few posts on the community). The mails are generated in SMTP format.

Code: [Select]
Call maildoc.ReplaceItemValue("Form","Bookmark")
Call maildoc.ReplaceItemValue("Principal","Aditya Jois")
Call maildoc.ReplaceItemValue("DisplaySent","Aditya Jois")

so, when the user receives the mail, s/he will see the It with the name Aditya Jois in the Inbox and Sent By as Aditya Jois

This is fine, but, when the agent is run on server, the mails generated are in MIME format and all this code is a waste and does not work as intended.

Another problem is that, when I embed a doclink, it works fine in SMTP but not in MIME. So, I came up with this code

Code: [Select]
If notesag.ServerName <> "" Then
Call rtitem.AppendText(doclink.NotesURL)
Call rtitem.AddNewline(2)
Call rtitem.AppendDocLink(doclink,CurrDB.Title)
End If
i.e. if it is running on a server, I embed the NotesURL else I attach the doclink.

Does anyone have an alternative solution? Any help would be appreciated.


Techronnati | where technology never sleeps

SMTP MIME How do I achieve them
« on: November 27, 2008, 02:15:04 AM »

Mountain View


Posting Disclaimer: Any individual may post a message in this forum and may do so anonymously. Therefore, the sole author is exclusively and entirely responsible for all opinions in that message. They do not represent the official opinions of Techronnati, its administrators or moderators or the Techronnati Management. Techronnati is merely acting as an impartial conduit for constitutionally protected free speech and is not responsible and will not be held liable for the content of such messages. All images and service logos are trademarks of their respective owners.