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_map.cfg mappings ignored

hessian

In the past, I've routinely mapped email IDs to external addresses like so-n-so@yahoo.com for testing purposes then changed/deleted the mappings afterward. I've never had a problem doing so until now, using TS6.2.1 on Windows 2000. Can anyone hazard a guess as to why changed mappings are not being respected? No matter what I do, to email_map.cfg, email keeps getting sent to the ID's regular domain address.

Thanks in advance for advise...

Find more posts tagged with

Comments

lhdavis

First of all, did you mean TeamSite 6.1?

Secondly, are you editing the email_map.cfg under <iw-home>/local/config/wft or <iw-home>/local/config/wft/solutions? If you are using the solutions workflow, it will need to be the latter that you modify.

Third, what do you have set up for the path to the file in iw.cfg? That is, what is the "email_mapping_file" value under iwsend_mail.

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

Test1_report.rptdesign

hessian

Luke-

Thanks for trying to help.
I'm so used to typing a ".2" when referring to my TeamSite version I did it again even though I'm at a site that's on 6.1.0 now. Thought I had a new release no one heard of, eh? Alas, no.

Now that I've checked the fundamentals for a third time I can assure myself and all others that iw.cfg has the following set of entries...

[iwsend_mail]
maildomain=hess.com
mailserver=smtp.ihess.com
use_mapping_file=true
email_mapping_file=c:/iw-home/local/config/wft/email_map.cfg
debug_output=c:/temp/iwsend_mail_debug

... and that the file is indeed located where it's supposed to be.

Since the darn setup is sending emails I'm ruling out problems with the mail server. BTW... after tweaking the cfg file I routinely issue an "iwreset" and have even done "iwreset -ui" a couple times, more out of frustration than anything else.

Grrrrr...
-hessian

lhdavis

Sounds like your mail server is configured correctly then.

Where are you sending your e-mail from, custom CGI scripts, workflows, OpenDeploy?

If it is a solution workflow, then you have to update the other email_map.cfg file under the solutions subdirectory. There have been several threads about that in here.

Other than that, could there be some caching going on here for the incorrect e-mail addresses? But answer the previous question first about what functinality you are using to send e-mails.

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov
<edited by Lissa at Luke's request>

Edited by lissa on 07/12/04 10:57 AM (server time).

iwovGraduate

Already being asked -- Are you using solutions workflows ?
I think the solutions workflow uses the iw-home/local/config/wft/solutions/email_map.cfg file irrespective of what you specify in iw.cfg.

hessian

These emails are being sent via tasks in workflows.
I put copies of email_map.cfg in the solutions directory but mappings are still not being respected.
I even changed iw.cfg after the first shot failed to no avail.

hessian

Putting email_map.cfg didn't effect any mapping changes... thanks.

iwovGraduate

"Putting email_map.cfg didn't effect any mapping changes"

What exactly did you put ? Where ?

iwovGraduate

Again - Are you using OOTB solutions workflow ?

lhdavis

I do not think you can just overwrite the copy of email_map.cfg in the solutions directory with the "regular" one as they are formatted somewhat differentally. Hopefully you have the original solutions/email_map.cfg and can compare it with the email_map.cfg.example file.

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

Migrateduser

Isn't it fun helping people who don't help you help them?

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

hessian

Putting email_map.cfg into the iw-home/local/config/wft/solutions/ directory didn't effect mapping changes.

To anticipate a future helpful question....

the entries I have in email_map.cfg are like this:

ihess\iwoveditor1: a_test_id@yahoo.com
ihess\iwoveditor2: my_id@hess.com

THANKS!

iwovGraduate

nipper atleast gets the cheques. I don't get nothing.

Migrateduser

Dude, how are you performing the actual email itself? What mechanism are you using in your script? Perhaps you could post your email script - that might be helpful.

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

iwovGraduate

Again -
"Are you using solutions workflows ?"

If you don't know, thats fine. Post your workflow - .wft file.
Also see if c:/temp/iwsend_mail_debug file exists on your TS server. If so, post it as well.

lhdavis

As I mentioned, the format is different for the solutions version of email_map.cfg

Again, the format is different for the solutions version.

Did I mention the format is different for the solutions version of email_map.cfg? Smiley Happy

Try this:
<emailConf>
<user name="ihess\iwoveditor1" fullname="Editor One" email="a_test_id@yahoo.com"/>
<user name="ihess\iwoveditor2" fullname="Editor Two" email="my_id@hess.com"/>
</emailConf>

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

iwovGraduate

I think you forgot to mention that solutions workflows use a different format for email_map.cfg

lhdavis

Doggone it you're right.

Hey, BTW, the solutions email_map.cfg....who am I kidding. Hopefully you get the picture by now.

Would help to know if you're using the solutions workflows too though Smiley Happy

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

hessian

Sorry that the format difference didstinction did not sink in after you advised me of it. I'm trying to fulfill a higher priority commitment in another area while responding to these posts and performing half-baked checks and tweaks. I'll grok all this info and guidance tomorrow and post complete details ASAP. I'm still scratching my head, though, as to why I did not have to do anything other than edit the cfg file in a 5.5.2/Solaris environment.

Thanks again, Luke.

And, Smitty, tsk tsk... no reason to get snooty or sarcastic. I'd rather you NOT chime in if you think you can take a shot at me just because I don't respond fast enough to your posts. I've already got a wife for things like that. To be fair, maybe I should not have engaged folks on DevNet to chime in about my problem until I could focus on it 100% myself. However, the exchanges this afternoon have gotten things a lot more focused and I really don't think anybody's gotten bent out of shape. Sometimes the best approach to these things is a primitive boot-strapping approach starting with verification of the most fundamental who/what/where things and the nature of these exchanges is, basically, frustrating and painful until the "AHA!" experience occurs.

hessian

Not using an OOTB solutions workflow. I created my own subdir, wft/hess_internet, and am running a custom workflow from there.

Migrateduser

There's always a reason to be sarcastic. I think you'll find that the good folks, including myself, who try and help in DevNet will be better able to help you if you provide as much detail about your problem as possible. Everyone's time is precious, not just yours. If you want help, help others help you. It's really very simple.

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

hessian

Hmmmm. There was no copy of email_map.cfg in the solutions directory.

Adam Stoller

Howdy (I was on vacation last week, otherwise I would have chimed in sooner ;-)

I believe we've established that:
- you are using TeamSite 6.1 on W2K
- you are not using a "solutions" wft
- you are, in fact, using your own externaltask to send email
- that you have iw.cfg configured to use the IWHOME/local/config/wft/email_map.cfg
- that your .../email_map.cfg is formatted as:
userid: email@address

Is that all correct so far?

Assuming the above is correct:
- What script are you using from your externaltask to send email?
-- Are you using one of the OOTB scripts?
--- If so, which one?
--- If not, can you provide a copy of the script you *are* using for us to look at?

- Is the problem happening for all userids that are registered within the email_map.cfg or just some userids?
-- If the latter, can you narrow it down to userids that begin with certain letters (like 'b', 't', 'n', etc.)?

(note: iwreset is *not* required when making changes to the email_map.cfg file)

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

hessian

Sorry I didn't post a resolution message before you posted... thanks for chiming in anyway.

When all else fails -- like following the advice from lhdavis ("If it is workflows, then you have to update the other email_map.cfg file under the solutions subdirectory") -- I resolved to "Use The Source" and drill down into what was going on in iwsend_mail.ipl. Turns out that wft/email_map.cfg was being opened and parsed correctly. The problem had to deal with the fact that the "_convert_email function was comparing the domain\email_id from email_map.cfg to an email id without a domain (line 723: next unless("\L$key\E" eq "\L$email_address\E") Smiley Wink

. Adding a line of code to split $key into domain and email_id fixed the problem.

hessian

I think you've got to revise your advice-set regarding which email_map.cfg file to update when sending emails from workflows.

The problem was in iwsend_mail.ipl itself. Turns out that wft/email_map.cfg was being opened and parsed correctly. The problem stems from the fact that the "_convert_email function was comparing the domain\email_id from email_map.cfg to an email id without a domain (line 723: next unless("\L$key\E" eq "\L$email_address\E") Smiley Wink

. Adding a line of code to split $key into domain and email_id fixed the problem.

Just curious, can you point to any "official" reference or documentation that stipulates that email_map.cfg in the solutions dir had to be used if sending emails from workflows? Following up on that pronouncement turned out to be something of a wild goose chase and, in the end, turned out to be completely unfounded.