It is actually very simple if you understand the mechanism.
To send email from a program livelink you will need a SMTP server simpler all corporate entitieshave a SMTP that is why you can send email. Functionality like Notifications or WFstep that send you email in livelink is just executing OScript code which invokes a login to a SMTP client and sending you that message.
To receive email you have to have a much more complicated infrastructure, here the mail travels through specified protocols ,sites will explain mail sending but I am saying things for a layman for e.g if you send an email to firstname.lastname@example.org the internet mechanism through its labyrinth of connected mail and DNS servers will try to locate the @part which is gmail.com,once it is delivered to an IMAP or POP server or many other technologies that have evolved after that it is received by the gmail server,then all it has to do is basically store the message in its database and check if a user exists there.You open up your favorite mail client and lo and behold .Note email and internet transfer existed way before internet and other things as part of Unix operating systems or even before that but common man thinks only when big players like Windows, Apple and Google has made it more popular and affordable, however the RFC's and protocols were well established before that.When we come into livelink and its eLink module this is a typical user scenario, because there's more than one way to skin this cat. What is being described is a typical company with AD and Exchange as mail providers and Livelink on simple IIS/Windows OS
• Livelink Administrator Chore
Installs the ELINK oscript module ,now maybe installed by default, also installs the eLink Server which is a free to license SendMail Daemon, which OT licenses
• Mail Administrator Chore Creates a Virtual Hosting by allowing a subdomain.In most livelink/elink operations this is the most disconnect as Mail admins will never know and will get extremely paranoid when thy hear the sendmail daemon.Thir job is to just make sure a MX record exists in their mail system,so if your company domain was email@example.com the LL team may want to call their subdomain firstname.lastname@example.org.Once you get this done in AD and exchange which is usually a 30 min job.
If you have this done and working then half the battle is won.Note this product cannot be completely done and going without the LL team and Mail team collaborating for your benefit,the Notifications and other aspects are SMTP driven this does not require your to talk to your mail team,if you are allowed to use a published SMTP server.It confuses a whole lot for starting people when they mysteriously see livelink can send mail but it cannot recive email.
Now when somebody sends a email to email@example.com if you are inside your compnay mail or ouside your company email this part is evaluated elink.mycompany.comand mail will come to your mail server,at which point the mail server looks up its MX records and say hey I have a envelop to elink.mycompany.com and it will forward it to the elink server(java/sendmail service) .If elink is to be used only inside the company then the outside world is blocked form this MX record,Simply put if you send email in such address from your gmail client you will get an error from gmail that says the address is unknown to me,if the MX record was public gmail will try to deliver
True to many of the automagic that OT delivers and a lot of people never understanding livelink scheduled agents a scheduled agent(5000) wakes up every 5 minute or so logging on to this POP server and finds a mail to be delivered to firstname.lastname@example.org .So the livelink checks works like this do I have a email alias in dtree for that object ,and does the sender have add item/add version capabilities on the Object [ https://appukili.wordpress.com/2015/05/03/general-...] email@example.com is a technical user who like Admin has SA privileges and you cannot delete that account.Discussions allow anonymous posting which means post it as that user because in LL only people allowed on objects can do anything. elinklias stores the objects dataid to whatever friendly name you choose.
In my 19 years of working with eLink there has never been a smooth mail/livelink admin interaction.The only time I had eLink configured and running was when our LL team and our Mail team was under the same manager :)