Mail Forward Rule - Any Ideas Would Be Helpful

We developed an application in a mailin database, where in the form that a user selects an email address that they want to email the form contents from to a vendor. The vendor will only accept email address that come from this form. No matter what hard-coding we put into the email functionality we coded into the form “submit” button, the email always comes from the user name specifically (although we have been successful in hard-coding the memo form to at least send it from the database name, but it is a generic database and we don’t want that). We have tried hardcoding Principal, NetiPrincipal, Altfrom, Dispfrom,etc., none work).- Is there another field that we can hard code into either the Submit functionality in the form, or within the Memo form itself that will send from the email address the user selected in the form?

As a workaround, since we are able to force it to send from the database name, we could set up a database for each of the potentially selected addresses (not great because that would be 20 or so). Then, based on what the user selects as the From email address, it will send an email to the appropriate secondary database. We would like to set up a mail rule that would forward it on to the vendor. There is only a Send Copy To rule, and this just sends an identical email from the first database with the from still being from the User, not the secondary database name.

  • Is there some coding we could put into a mail rule that will Forward, not Send Copy To

  • We don’t want to do a scheduled agent, because the From then becomes the email address of the person who signed it, again, not the person we want.

A final idea set up a database for each of the email addresses and have the users go to the correct database (this isn’t very effective), but then we would have to maintain the exact same form in each database and would become a Change Management nightmare.

Any ideas or help would be greatly appreciated.

Subject: try another email api to send.

Other than creating 20 similar agents saved individually by the 20 or so ID’s that matches the acceptable ID’s by your vendor, it is very difficult to spoof or change the identify of a lotus notes author. Each agent will have to check if a particular name is requested, then call the mail.send on the incoming. I think that would be a big mess after 5 ID’s–I could not imaagine the set up with 20+.

Another effort is to use a java agent and embedd the javamail libraries. Then create the message with javamail api. You should be able to put override the “from” address. If not java, I suspect you can use mapi on windows (just look in the Outlook / Exchange forums on how people are sending emails messages). In each case, I think you may need to connect to a mail server. Note, if you connect to a server that has an open mail relay, some mail-security products will not accept responses if your mail server is on the open-relay list.

-Kyle Huang

Subject: use an agent to send

Do this:When the user hits send, the message is actually just saved to a view in the db that acts as a queue.

Have an agent (signed by the server) then copy the desired sendername into (all those fields like Principal, Sender, inetfrom, From, etc) and copy the message to the mail.box.