Author |
Message
|
newToMB1234 |
Posted: Wed Dec 23, 2009 2:15 pm Post subject: EmaiOutput node issue - Please help |
|
|
Newbie
Joined: 23 Dec 2009 Posts: 3
|
Hello all,
I had a request to use EmailOutput node to send an Email with invisible information to receiver. I need use this information to set the retry times in case the email bounced back. Could anybody tell me how to do that? Or it's impossible to do it. Thanks!
Have a great holiday! |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Dec 23, 2009 2:24 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
It's unreasonable to expect that any part of an email message will be invisible to the receiver.
If you can be *much* more specific about what you have been asked to do, you can probably get assistance on setting an X header in the email or on setting some other property that might accomplish what you need.
But please understand. The EmailOutput node *will* not a) retry messages, b) process bounced email and return information to the flow.
The *only* time you will get anything back from the EmailOutput node is if the connection to the SMTP server fails or if the SMTP server you are directly talking to rejects the email or the connection for some reason. I.e. if it returns an error to the node. |
|
Back to top |
|
 |
newToMB1234 |
Posted: Wed Dec 23, 2009 2:41 pm Post subject: |
|
|
Newbie
Joined: 23 Dec 2009 Posts: 3
|
Thank you very much.
The request is use EmailOutput node to send message. Another flow will check the inbox for any bounced back message, and try to re-send the email up to three times. If still fail, then put message to error queue. So I need a field to held the retry counter information within send out email, so when I parse the bounced back email, I can check the retry times. But I don't want to this field visible to receiver. |
|
Back to top |
|
 |
smdavies99 |
Posted: Wed Dec 23, 2009 11:01 pm Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
One possible solution
Try using the Zipnode support Pack to zip up the contents of the email. I can't remember if the node allows you to add a password to the file.
I'm not sure about the use of this support pack on V7. I emailed the author some time ago but I've not had any response so far. IT works fine on V6 _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Dec 24, 2009 5:12 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
I'm not sure where the Zipnode would help, really?
newToMB1234 - you need to set a header on the email message. You probably want to start it with X-. Something like "Set OutputRoot.EmailOutputHeader."X-MyRetryCount"=0"
This won't be "invisible" to the end user, but it won't in general be visible unless they want to look at all the email headers. But as I said, there's no way to make it "invisible" to the end user.
There might be an existing mail header that already contains the retry count.
You could also look at using the message id that's returned in WrittenDestination and using that to keep track of the retry count. I forget if bounced emails have the same id or not, but the original message ID should be in there. |
|
Back to top |
|
 |
smdavies99 |
Posted: Thu Dec 24, 2009 6:33 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
mqjeff wrote: |
I'm not sure where the Zipnode would help, really?
|
I should have clarified it a bit better.
I was thinking about using the zipnode to make the text in the body invisible to a normal user. If you used a password on it then that is an added (Allbeit not very much) way to keep the text of the email out of prying eyes. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
newToMB1234 |
Posted: Thu Dec 24, 2009 9:11 am Post subject: |
|
|
Newbie
Joined: 23 Dec 2009 Posts: 3
|
Thanks all, I will try use X header first, if it's not work, I will store the information into a table.
Happy holiday to all |
|
Back to top |
|
 |
rkford11 |
Posted: Thu Dec 24, 2009 9:12 am Post subject: |
|
|
Partisan
Joined: 06 Jun 2004 Posts: 316
|
Current version of Zipnode supports only v5 & v6 of Message broker. is there new version of Zipnode that supports v6.1 of the message broker.
Thanks |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Dec 24, 2009 9:53 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
rkford11 wrote: |
Current version of Zipnode supports only v5 & v6 of Message broker. is there new version of Zipnode that supports v6.1 of the message broker. |
It runs in v6.1. |
|
Back to top |
|
 |
|