nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Email Task Error

syim

We are using TeamSite 5.5.2 for windows.
In my workflow I used Email Task to send email. Following is the element in my workflow file:

<externaltask name = "Email"
owner = "__TAG__('iw_user');"
retry = "f" start = "f"
description = "Deployment Failed.">
<areavpath v = "__TAG__('iw_workarea');"/>
<successors>
<successorset description = "Go to EndTask">
<succ v = "End"/>
</successorset>
</successors>
__INSERT__( iw_get_mail_cmd('iwsend_mail','', 'test@cucbc.com') );
</externaltask>

When this task is invoked, the email log indicated following error:

Failure to send Email: Bad file descriptor at

\PROGRA~1\INTERW~1\TeamSite\iw-perl\site\lib/Mail/Mailer.pm line 267.

Any idea how can I fix this problem?

Find more posts tagged with

Comments

Adam Stoller

Have you properly configured the mailserver setting under the [iwsend_mail] section of the iw.cfg file?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

Where are your <command> tags for your externaltask?

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

syim

I did specify the mailserver under [iwsend_mail] in the iw.cfg file.

Edited by syim on 02/02/04 08:49 AM (server time).

syim

The "iw_get_mail_cmd" inserted the <command> tag. Following is the function generated by the Workflow Builder:

sub iw_get_mail_cmd {
# NT lacks the ability to bind a script executor with a
# script on a 'shebang' line (eg: #!/blah/blah/iwperl)
# Instead it uses the assoc/ftype mechanism which employs
# the use of environment variables that are not always
# available (cf: IIS's metabasse, which replicates the
# extention-based association scheme on its own). Therefore,
# we need to spoon-feed iwperl the script like this for now:

my($type, $taskName, $addr) = @_;
return(sprintf("<command v='%s$iwhome/bin/%s %s'/>",
($^O eq "MSWin32") ? "$iwhome/iw-perl/bin/iwperl " : "",
($type eq "iwsend_mail") ?
"$type.ipl" : "iwsend_servlet_mail.ipl",
($taskName eq "" ) ? $addr: "$taskName $addr"));
}

Migrateduser

Workflow Builder is a terrible tool. If you have to do anything remotely useful in workflow, you have to code things up yourself. It would be such a benefit to you to take the workflow training through Interwoven, if at all possible. Using Workflow Builder is the wrong way to approach workflow development, in my humble opinion.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

syim

From my workflow debug file, I can see "__INSERT__( iw_get_mail_cmd('iwsend_mail','', 'test@cucbc.com') );" is converted into following <command> tag:

<command v='D:/PROGRA~1/INTERW~1/TeamSite/iw-perl/bin/iwperl

/PROGRA~1/INTERW~1/TeamSite/bin/iwsend_mail.ipl test@cucbc.com'/>

Are you suggesting that I should not use "iwsend_mail.ipl" to send email? I should write my own Perl script to send email?

Migrateduser

I'm not suggesting you do anything other than learn workflow via the standard training. Trying to debug a workflow after using Workflow Builder to create the workflow is an exercise in futility. If iwsend_mail.ipl works for you, then use it. I don't use Windows for TeamSite, so if that command line looks correct, then the problem lies elsewhere. I'm guessing that ghoti was more on the right track and something is set up incorrectly with your mail server setup.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

JonathonG

Are you sure the mailserver you specified in iw.cfg will accept SMTP connections? I'm fairly certain SMTP is the default protocol in iwsend_mail.ipl (although its been awhile since I looked). There error message your getting would seem to indicate a failure in establishing the SMTP connection. So, I'd check again on the mailserver setting in iw.cfg. Then, try establishing an SMTP connection outside of the workflow. From a command prompt on the TeamSite server try telnetting in to the SMTP port (port 25) of the mailserver you have configured:

C:\>telnet yourmailserver 25

HTH,

Jonathon
Independent Interwoven Contractor

syim

Thanks a lot. It was the network settings caused the problem.

PageIn.jpg

JonathonG

If you don't mind me asking, what network settings were at issue? I like to have some ideas of what to check when I get these kinds of failures.

Jonathon
Independent Interwoven Contractor

pagein.png

syim

I believe the port number was blocked off by firewall.

JonathonG

Ok, that would do it Smiley Happy

Thanks,

Jonathon
Independent Interwoven Contractor

check.jpg