LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: khopkins

Hello everyone,

While creating a graph to produce scheduled data extracts for our business i have been creating additional functionality to email out if the scheduled graph has an error using the email node.
Whilst running this via the client connected to the LAE server the emails are generated when an error occurs.
However when the graph has been deployed to the server and is run from the shell script the email node fails with the below errors saying that the local host is refusing all email addresses.

Status
All e-mail addresses were refused by server "localhost". No e-mail messages were sent at all
Error pumping node (Traceback (most recent call last):
File "/usr/local/lavastorm-4.5.2/lib/python/lavastorm/brain/python1.py", line 913, in Run
while n.pump(quant):
File "/usr/local/lavastorm-4.5.2/db/../tmp/brain/Address_Information/2012.08.29_112422/temp.ttblael1.17310.104981.1346240852408.prop", line 161, in pump
raise BrainNodeException, "All e-mail addresses were refused by server \"%s\". No e-mail messages were sent at all" % self.smtpServerAddress
BrainNodeException: All e-mail addresses were refused by server "localhost". No e-mail messages were sent at all
)

Does anyone please have a pointer to what could be causing this issue?

Regards,

Keith

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: rpigneri

Dear Keith,

This error only occurs when every e-mail address to which you sent messages has a failure. In my experience, this most commonly happens because the server to which you are sending mail is not authorized to send mail to the address you have chosen. For example, let's say that you are using an LAE server to send an e-mail to a GMail account. Since the LAE server is an internal machine and the GMail server is outside of your company, it is possible that the IT Department has not yet set up the LAE server to relay e-mail from to outside your company.

Now, this issue is complicated by the fact that you are using "localhost" as your address. "localhost" refers to the machine on which the node is running, and the specific machine running the node can change on each run. These facts could create two different problematic situations. First, it is possible that the server that you are connecting to from BRE is different from the server to which your graph has been deployed. Second, if you are using a farm with multiple servers, it might be that only one server is allowed to send e-mail to the addresses you want while another server has been overlooked. If you would like to continue to use "localhost" as your mail server, I would suggest that you first check your server farms to ensure that they are the same. You can check your server farm for your BRE connection by double-clicking the name of your server farm in the toolbar in BRE (this is the third drop-down from the right). For the deployed version, you are going to have to speak with whoever wrote the shell script to confirm that you both are using the same server farm.

However, due to these complications, I would recommend changing your SmtpServerName parameter from "localhost" to a specific sever name that is known to work. This change will avoid this ambiguity and make it easier to deploy your graph.

Hope that helps,

Rocco

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: khopkins

Hi Rocco,

This error is confusing as on the local host using sendmail/mail/rmail etc will send emails without any problems as the permissions have been granted,also the client is connecting to only one server farm as only one is set-up.
However by checking the sendmail config files i have discovered that while localhost does not work when the graph is deployed localhost.localdomain does.
Also if i add in the actual smtp server name then the client has its request refused along with when deployed so i guess this is more of a sendmail configuration issue than a Lavastorm one.
Thanks for the help though.