Email workflow

we r trying to send an email to our server thru a workflow. In our iw.cfg.........we have specified the IP address of our mail server.............and domain as well...........but it is giving the following error:
To: xyz@company.com
From: ABC
Subject: Develop Media Task Notification (3305)
Number of addresses: 1
iwsend_html_email.ipl script complete
connect() failed: Connection refusedEnd of output

so i guess we need to specify the user name and the password in order to get connected.........

but we don't know how to specify the user name and the password in the iw.cfg file........................

thanking u in anticipation

Find more posts tagged with

Comments

Adam Stoller

Are you sure you're providing the correct IP address of your mail server, and that your mail server supports SMTP? (i.e. can you telnet to port 25 on that IP address and interact with the SMTP server?)

From the error message, it sounds like the connection to the SMTP server is being refused - if so, you may have to work with your company's IT staff to figure out why that is happening.

--fish
(Interwoven Senior Technical Consultant)

vinylrecord

hi,
yes, i have telnet on the ip address specified, on port 25, its connecting from there.but still the problem remains the same, it says connection refused.

so, whats the next step.

its an imp. issue, plz help me to resolve it.

Adam Stoller

The next step is you get your IT people involved so that they can track the information directly on the SMTP server to see why it is not accepting the connection from the script.

One other possibility comes to mind... If this is a Unix TeamSite server - make sure you configured the settings in the correct iw.cfg file (the one in /etc/ not iw-home/etc/)

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

I don't understand why everybody uses these scripts. It is so easy to just write a temp file and mail it with a command line tool (mail/mailx/blat/etc.), or SMTP in the language of your choice. And you have full control. I guess if you want to support every possible email client there may be some value in the scripts. But I think a good number of the posts on devnet are on issues with them. Personally I have never seen them work but I have been able to do pretty cool things with mail, and have never heard of a problem with any email client accepting them.

Of course, if you use blat I recommend not using the one that ships with TeamSite - it is pretty old.

vinylrecord

hi
thanks a lot, it worked.

thanks a million

Adam Stoller

The only difference between what you are suggesting and what is provided in the scripts such as iwsend_mail.ipl - is the final means of communicating to the SMTP server. 95% of the scripts are written to generate the message and determine the parameters for the sending of that message. Only about 5% is actually inovlved in sending it.

So I don't think you gain that much by using mail/mailx/blat/etc - other than the lack of portability perhaps...

iwsend_mail.ipl is not meant to support "every possible email client" - it is meant to support connecting to a mail server and sending an email, which might be HTML formatted, and thus might not work on every possible email client (for example, HTML formatted email doesn't work very well in Eudora on Mac's, though it works just fine in Eudora on Windows).

The iw_solutions_email.ipl script was a different take on the same concept - the main thrust of that script is to make use of TeamSite Templating's presentation template engine to extract information from an XML document (the workflow information) and to format it for presentation purposes. I, personally, have less experience using this script - but I've seen nicely presented emails generated by it from Interwoven's own internal use of it.

As for the old version of blat in the TeamSite distribution - yeah, that is old (yikes) - I'll put in a request to have it either updated or removed from the distribution

--fish
(Interwoven Senior Technical Consultant)

Adam Stoller

thanks a lot, it worked.

For the viewers at home (me included) - can you elaborate on what worked?

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

I disagree about the only difference - the difference to me is full control, which means that without modifying the base product and maintaining that modification with upgrades I can maintain my custom system for logging and sending mail. The original poster was debugging an issue with Interwoven code - if he had written the code, he probably wouldn't be looking for support. SMTP is an open, well-documented standard. iw*.ipl is not.

On the portability issue, if you use SMTP calls it should be portable (right?), if you use CLTs you would just have a switch on the OS that called blat with appropriate params for one, mailx or whatever for the other (right?).

I expect 99.9% of developers already have code that sends email following corporate standards. I don't see why they would use Perl to do it with TeamSite instead of their prexisting code. But whatever works for each client is good for that client.

vinylrecord

hi
my email workflow is able to send mails, the problem was the same as u had suggested, the /etc file need to be corrected.