Intralink 3.4 e-mail

[JWayman]

Hello,
We are in the process of setting up an Intralink 3.4 installation.
Previously, in our 3.3 installation, we have not used e-mail notification to alert users that they have RTP forms to deal with. We would now like to use this feature.
However, in the manuals, we can find no details of how to set up the e-mail address of the Intralink server.
Does the software have its own e-mail address (something like intralink@intralink_server_thales.com<),">mailto:intralink@intralink_server_thales.com>), or do we have to set up an Outlook client on the server itself to act as the source of the e-mail for the rest of the world?
I'm only a humble Mechanical Engineer, so I realise my terminology is not necessarily quite up to scratch, but I hope my quandary is clear.

Any assistance will be gratefully received.

currently:
Ilink 3.3, WF2

soon to be:
Ilink 3.4, WF4

Thanks,



This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[iceblink1]

John,

The intralink server only sends emails, it does not read replies.
The point of the emails is only to make people aware of what is
happening in Intralink.
It is one way traffic, from Intralink to your users.

The sender-address should either be:
* the email address of someone in your organisation that will read
replies, i.e. john_smith@yourplace.com where John Smith is the Intralink
administrator (or perhaps the release coordinator?)
* a dummy email address that will serve as a black hole, i.e.
no_reply@yourplace.com so that it is clear to the users that there is
no point in replying to these messages.
The choice is up to you. What do you want your information process to
look like.

Technically email is just a piece of text being delivered to a mailbox
by computers. The software just needs to be able to connect to a mail
server so it can pass on the message. So the software needs to know the
local SMTP mail server, and the addressee. The only thing making this
more complex is that nowadays most mail servers have spam prevention
measures in place. So talk to your local IT dept to check if the SMTP
server will accept connections from the Intralink sendmail utility.

Best regards,
Patrick Asselman