Webhook MS Teams not working
Hi,
I have an alert setup to notify via MS Teams.
However it doesn’t arrive.
When I run ./test_alert.php -dd -a 327 the webhook gives a 400 Bad Request
Testing with the same webhook with curl returns a “1”
curl -H "Content-Type: application/json" -d "{"text": "Hello World"}" https://outlook.office.com/webhook/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
1
[cid:image001.png@01D3435E.E47C3B10]
But Observium shows this:
SQL RUNTIME[0.00041604s]
o Notifying [webhook] Microsoft Teams:
{"url":"https://outlook.office.com/webhook/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"}
REQUEST[https://outlook.office.com/webhook/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx...]
REQUEST STATUS[FALSE]
REQUEST RUNTIME[0.1904s]
RESPONSE CODE[400 Bad Request]
RESPONSE[
]
$http_response_header /opt/observium/includes/common.inc.php:3585
array(
[0] => string(24) "HTTP/1.1 400 Bad Request"
[1] => string(23) "Cache-Control: no-cache"
[2] => string(16) "Pragma: no-cache"
[3] => string(18) "Content-Length: 28"
[4] => string(39) "Content-Type: text/plain; charset=utf-8"
[5] => string(11) "Expires: -1"
[6] => string(48) "request-id: xxxxxxxxxxxxxxxxxxxxxxxxxxx"
[7] => string(68) "X-CalculatedBETarget: AM5PR0102MB2723.eurprd01.prod.exchangelabs.com"
[8] => string(24) "X-BackEndHttpStatus: 400"
[9] => string(27) "X-AspNet-Version: 4.0.30319"
[10] => string(55) "X-CafeServer: AM5PR0201CA0013.EURPRD02.PROD.OUTLOOK.COM"
[11] => string(27) "X-BEServer: AM5PR0102MB2723"
[12] => string(21) "X-Powered-By: ASP.NET"
[13] => string(27) "X-FEServer: AM5PR0201CA0013"
[14] => string(100) "X-MSEdge-Ref: Ref A: XXXXXXXXXX9787B468 Ref B: AMSEDGE0313 Ref C: 2017-10-12T10:38:38Z"
[15] => string(35) "Date: Thu, 12 Oct 2017 10:38:38 GMT"
[16] => string(17) "Connection: close"
)
Epco Dijk Systems Administrator
Northpool B.V. 3e Binnenvestgracht 23 N 2312 NR Leiden The Netherlands Tel: +31 (0)88 2400300 Fax: +31 (0)88 2400399 E-mail: epco.dijk@northpool.nl Web: www.northpool.nl
[Logo Northpool]
This message and any attachments (the "message") are confidential and intended solely for the addressees. If you are not the addressee indicated in this message or if this message has been addressed to you by error, you may not copy or deliver this message to anyone but destroy it and kindly notify the sender by reply email. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Northpool bv shall not be liable for the message if altered, changed or falsified.
Hi Epco,
The "webhook" notifier is not an MS Teams transport - it is made for custom webhook use where you use a script on a web server to process Observium events.
Based on your example we could likely create a simple Teams transport, however I don't have access to a testing environment.
How do you set up such a webhook on Teams? Is xxxxx just a long identifier string?
Tom
On 18/10/2017 21:39, Epco Dijk wrote:
Hi,
I have an alert setup to notify via MS Teams.
However it doesn’t arrive.
When I run ./test_alert.php -dd -a 327 the webhook gives a 400 Bad Request
Testing with the same webhook with curl returns a “1”
curl -H "Content-Type: application/json" -d "{"text": "Hello World"}" https://outlook.office.com/webhook/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
1
But Observium shows this:
SQL RUNTIME[0.00041604s]
o Notifying [webhook] Microsoft Teams:
{"url":"https://outlook.office.com/webhook/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"}
REQUEST[https://outlook.office.com/webhook/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx...]
REQUEST STATUS[FALSE]
REQUEST RUNTIME[0.1904s]
RESPONSE CODE[400 Bad Request]
RESPONSE[
]
$http_response_header /opt/observium/includes/common.inc.php:3585
array(
[0] => string(24) "HTTP/1.1 400 Bad Request"
[1] => string(23) "Cache-Control: no-cache"
[2] => string(16) "Pragma: no-cache"
[3] => string(18) "Content-Length: 28"
[4] => string(39) "Content-Type: text/plain; charset=utf-8"
[5] => string(11) "Expires: -1"
[6] => string(48) "request-id: xxxxxxxxxxxxxxxxxxxxxxxxxxx"
[7] => string(68) "X-CalculatedBETarget: AM5PR0102MB2723.eurprd01.prod.exchangelabs.com"
[8] => string(24) "X-BackEndHttpStatus: 400"
[9] => string(27) "X-AspNet-Version: 4.0.30319"
[10] => string(55) "X-CafeServer: AM5PR0201CA0013.EURPRD02.PROD.OUTLOOK.COM"
[11] => string(27) "X-BEServer: AM5PR0102MB2723"
[12] => string(21) "X-Powered-By: ASP.NET"
[13] => string(27) "X-FEServer: AM5PR0201CA0013"
[14] => string(100) "X-MSEdge-Ref: Ref A: XXXXXXXXXX9787B468 Ref B: AMSEDGE0313 Ref C: 2017-10-12T10:38:38Z"
[15] => string(35) "Date: Thu, 12 Oct 2017 10:38:38 GMT"
[16] => string(17) "Connection: close"
)
Epco Dijk Systems Administrator
Northpool B.V. 3e Binnenvestgracht 23 N 2312 NR Leiden The Netherlands Tel: +31 (0)88 2400300 Fax: +31 (0)88 2400399 E-mail: epco.dijk@northpool.nl Web: www.northpool.nl
Logo Northpool
This message and any attachments (the "message") are confidential and intended solely for the addressees. If you are not the addressee indicated in this message or if this message has been addressed to you by error, you may not copy or deliver this message to anyone but destroy it and kindly notify the sender by reply email. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Northpool bv shall not be liable for the message if altered, changed or falsified.
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
There's a MS Teams transport in the repository now - not fully tested. Comments welcome!
Tom
On 18/10/2017 21:50, Tom Laermans wrote:
Hi Epco,
The "webhook" notifier is not an MS Teams transport - it is made for custom webhook use where you use a script on a web server to process Observium events.
Based on your example we could likely create a simple Teams transport, however I don't have access to a testing environment.
How do you set up such a webhook on Teams? Is xxxxx just a long identifier string?
Tom
On 18/10/2017 21:39, Epco Dijk wrote:
Hi,
I have an alert setup to notify via MS Teams.
However it doesn’t arrive.
When I run ./test_alert.php -dd -a 327 the webhook gives a 400 Bad Request
Testing with the same webhook with curl returns a “1”
curl -H "Content-Type: application/json" -d "{"text": "Hello World"}" https://outlook.office.com/webhook/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
1
But Observium shows this:
SQL RUNTIME[0.00041604s]
o Notifying [webhook] Microsoft Teams:
{"url":"https://outlook.office.com/webhook/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"}
REQUEST[https://outlook.office.com/webhook/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx...]
REQUEST STATUS[FALSE]
REQUEST RUNTIME[0.1904s]
RESPONSE CODE[400 Bad Request]
RESPONSE[
]
$http_response_header /opt/observium/includes/common.inc.php:3585
array(
[0] => string(24) "HTTP/1.1 400 Bad Request"
[1] => string(23) "Cache-Control: no-cache"
[2] => string(16) "Pragma: no-cache"
[3] => string(18) "Content-Length: 28"
[4] => string(39) "Content-Type: text/plain; charset=utf-8"
[5] => string(11) "Expires: -1"
[6] => string(48) "request-id: xxxxxxxxxxxxxxxxxxxxxxxxxxx"
[7] => string(68) "X-CalculatedBETarget: AM5PR0102MB2723.eurprd01.prod.exchangelabs.com"
[8] => string(24) "X-BackEndHttpStatus: 400"
[9] => string(27) "X-AspNet-Version: 4.0.30319"
[10] => string(55) "X-CafeServer: AM5PR0201CA0013.EURPRD02.PROD.OUTLOOK.COM"
[11] => string(27) "X-BEServer: AM5PR0102MB2723"
[12] => string(21) "X-Powered-By: ASP.NET"
[13] => string(27) "X-FEServer: AM5PR0201CA0013"
[14] => string(100) "X-MSEdge-Ref: Ref A: XXXXXXXXXX9787B468 Ref B: AMSEDGE0313 Ref C: 2017-10-12T10:38:38Z"
[15] => string(35) "Date: Thu, 12 Oct 2017 10:38:38 GMT"
[16] => string(17) "Connection: close"
)
Epco Dijk Systems Administrator
Northpool B.V. 3e Binnenvestgracht 23 N 2312 NR Leiden The Netherlands Tel: +31 (0)88 2400300 Fax: +31 (0)88 2400399 E-mail: epco.dijk@northpool.nl Web: www.northpool.nl
Logo Northpool
This message and any attachments (the "message") are confidential and intended solely for the addressees. If you are not the addressee indicated in this message or if this message has been addressed to you by error, you may not copy or deliver this message to anyone but destroy it and kindly notify the sender by reply email. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Northpool bv shall not be liable for the message if altered, changed or falsified.
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Just tried this out. Doesn’t seem to work? Can’t really say much other than that. Any troubleshooting tips that would help give more feedback?
Curl “Hello World” to Teams Webhook address works sends to Teams channel.
Observium alert with Teams Webhook as a destination contact fails?
Thanks
On 18 Oct 2017, at 23:39, Tom Laermans tom.laermans@powersource.cx wrote:
There's a MS Teams transport in the repository now - not fully tested. Comments welcome!
Tom
On 18/10/2017 21:50, Tom Laermans wrote: Hi Epco,
The "webhook" notifier is not an MS Teams transport - it is made for custom webhook use where you use a script on a web server to process Observium events.
Based on your example we could likely create a simple Teams transport, however I don't have access to a testing environment.
How do you set up such a webhook on Teams? Is xxxxx just a long identifier string?
Tom
On 18/10/2017 21:39, Epco Dijk wrote: Hi,
I have an alert setup to notify via MS Teams.
However it doesn’t arrive.
When I run ./test_alert.php -dd -a 327 the webhook gives a 400 Bad Request
Testing with the same webhook with curl returns a “1”
curl -H "Content-Type: application/json" -d "{"text": "Hello World"}" https://outlook.office.com/webhook/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
1
But Observium shows this:
SQL RUNTIME[0.00041604s] o Notifying [webhook] Microsoft Teams: {"url":"https://outlook.office.com/webhook/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"}
REQUEST[https://outlook.office.com/webhook/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx...] REQUEST STATUS[FALSE] REQUEST RUNTIME[0.1904s] RESPONSE CODE[400 Bad Request] RESPONSE[
]
$http_response_header /opt/observium/includes/common.inc.php:3585
array( [0] => string(24) "HTTP/1.1 400 Bad Request" [1] => string(23) "Cache-Control: no-cache" [2] => string(16) "Pragma: no-cache" [3] => string(18) "Content-Length: 28" [4] => string(39) "Content-Type: text/plain; charset=utf-8" [5] => string(11) "Expires: -1" [6] => string(48) "request-id: xxxxxxxxxxxxxxxxxxxxxxxxxxx" [7] => string(68) "X-CalculatedBETarget: AM5PR0102MB2723.eurprd01.prod.exchangelabs.com" [8] => string(24) "X-BackEndHttpStatus: 400" [9] => string(27) "X-AspNet-Version: 4.0.30319" [10] => string(55) "X-CafeServer: AM5PR0201CA0013.EURPRD02.PROD.OUTLOOK.COM" [11] => string(27) "X-BEServer: AM5PR0102MB2723" [12] => string(21) "X-Powered-By: ASP.NET" [13] => string(27) "X-FEServer: AM5PR0201CA0013" [14] => string(100) "X-MSEdge-Ref: Ref A: XXXXXXXXXX9787B468 Ref B: AMSEDGE0313 Ref C: 2017-10-12T10:38:38Z" [15] => string(35) "Date: Thu, 12 Oct 2017 10:38:38 GMT" [16] => string(17) "Connection: close" ) Epco Dijk Systems Administrator
Northpool B.V. 3e Binnenvestgracht 23 N 2312 NR Leiden The Netherlands Tel: +31 (0)88 2400300 Fax: +31 (0)88 2400399 E-mail: epco.dijk@northpool.nl Web: www.northpool.nl
This message and any attachments (the "message") are confidential and intended solely for the addressees. If you are not the addressee indicated in this message or if this message has been addressed to you by error, you may not copy or deliver this message to anyone but destroy it and kindly notify the sender by reply email. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Northpool bv shall not be liable for the message if altered, changed or falsified.
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
On 19 Oct 2017, at 14:27, Tim Cooper lists@coop3r.com wrote:
Just tried this out. Doesn’t seem to work? Can’t really say much other than that. Any troubleshooting tips that would help give more feedback?
Curl “Hello World” to Teams Webhook address works sends to Teams channel.
Observium alert with Teams Webhook as a destination contact fails?
Thanks
Going to take a stab in the dark here and the problem may be that the format of the message has to comply with the ‘Connector Card message’ format and possibly this is not currently the case? ( if I’m reading the test_alert verbose debug of the message correctly? )
https://blogs.msdn.microsoft.com/mvpawardprogram/2017/01/17/part-2-office-36...
Thanks
Hi Tim,
I've tested the JSON output against the "Connect Playground" site at MS. Unfortunately I can't really do much more... :-/
You can put an "echo $data_string;" on line 38 of includes/alerting/teams.inc.php and try to curl that, to try and find out what the issue is exactly...
Tom
On 10/19/2017 03:49 PM, Tim Cooper wrote:
On 19 Oct 2017, at 14:27, Tim Cooper <lists@coop3r.com mailto:lists@coop3r.com> wrote:
Just tried this out. Doesn’t seem to work? Can’t really say much other than that. Any troubleshooting tips that would help give more feedback?
Curl “Hello World” to Teams Webhook address works sends to Teams channel.
Observium alert with Teams Webhook as a destination contact fails?
Thanks
Going to take a stab in the dark here and the problem may be that the format of the message has to comply with the ‘Connector Card message’ format and possibly this is not currently the case? ( if I’m reading the test_alert verbose debug of the message correctly? )
https://blogs.msdn.microsoft.com/mvpawardprogram/2017/01/17/part-2-office-36...
Thanks
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
On 19 Oct 2017, at 14:56, Tom Laermans tom.laermans@powersource.cx wrote:
Hi Tim,
I've tested the JSON output against the "Connect Playground" site at MS. Unfortunately I can't really do much more... :-/
You can put an "echo $data_string;" on line 38 of includes/alerting/teams.inc.php and try to curl that, to try and find out what the issue is exactly... Tom
Tom,
There is an empty ‘[ ],’ section in the centre of the facts in the JSON, if I remove this from the test data it works?
On 19 Oct 2017, at 16:41, Tim Cooper lists@coop3r.com wrote:
On 19 Oct 2017, at 14:56, Tom Laermans tom.laermans@powersource.cx wrote:
Hi Tim,
I've tested the JSON output against the "Connect Playground" site at MS. Unfortunately I can't really do much more... :-/
You can put an "echo $data_string;" on line 38 of includes/alerting/teams.inc.php and try to curl that, to try and find out what the issue is exactly... Tom
Tom,
There is an empty ‘[ ],’ section in the centre of the facts in the JSON, if I remove this from the test data it works?
Commented out line 31 to remove this empty part from the PHP generated JSON output. Curl workspace expected with the out put now, test_alert.php still doesn’t. Will do some more digging.
Thanks
Hi Guys,
The empty section is an issue, but there’s also the Authorization: Bearer line in the headers, removing that and the empty section gets things to work.
Regards, Michael.
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Tim Cooper Sent: Friday, 20 October 2017 5:29 AM To: Observium observium@observium.org Subject: Re: [Observium] Webhook MS Teams not working
On 19 Oct 2017, at 16:41, Tim Cooper <lists@coop3r.commailto:lists@coop3r.com> wrote:
On 19 Oct 2017, at 14:56, Tom Laermans <tom.laermans@powersource.cxmailto:tom.laermans@powersource.cx> wrote:
Hi Tim,
I've tested the JSON output against the "Connect Playground" site at MS. Unfortunately I can't really do much more... :-/
You can put an "echo $data_string;" on line 38 of includes/alerting/teams.inc.php and try to curl that, to try and find out what the issue is exactly...
Tom Tom,
There is an empty ‘[ ],’ section in the centre of the facts in the JSON, if I remove this from the test data it works?
Commented out line 31 to remove this empty part from the PHP generated JSON output. Curl workspace expected with the out put now, test_alert.php still doesn’t. Will do some more digging.
Thanks This email is intended only for the person to which it is addressed and may contain confidential or legally privileged material. Any dissemination or other use of or taking of any action in reliance upon the content of this email by persons other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the email from any computer. Opinions and other information in this email that do not relate to the business of my employer are not given nor endorsed by it. Unencrypted email is not secure and may not be authentic. If you have any doubts as to the contents please telephone to confirm. Oceana Gold Corporation and its related entities accept no responsibility for changes made to this email or its attachments after transmission from Oceana Gold Corporation and its related entities and do not guarantee that this email or attachments are virus or error free.
On 20 Oct 2017, at 00:26, Michael Davies Michael.Davies@oceanagold.com wrote:
Hi Guys,
The empty section is an issue, but there’s also the Authorization: Bearer line in the headers, removing that and the empty section gets things to work.
Regards, Michael.
Spotted that when I was looking at this again late last night offline and was going to test this very thing this morning. Good to know that should fix it when we do!
Thanks Michael
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Tim Cooper Sent: Friday, 20 October 2017 5:29 AM To: Observium observium@observium.org Subject: Re: [Observium] Webhook MS Teams not working
On 19 Oct 2017, at 16:41, Tim Cooper lists@coop3r.com wrote:
On 19 Oct 2017, at 14:56, Tom Laermans tom.laermans@powersource.cx wrote:
Hi Tim,
I've tested the JSON output against the "Connect Playground" site at MS. Unfortunately I can't really do much more... :-/
You can put an "echo $data_string;" on line 38 of includes/alerting/teams.inc.php and try to curl that, to try and find out what the issue is exactly...
Tom
Tom,
There is an empty ‘[ ],’ section in the centre of the facts in the JSON, if I remove this from the test data it works?
Commented out line 31 to remove this empty part from the PHP generated JSON output. Curl workspace expected with the out put now, test_alert.php still doesn’t. Will do some more digging.
Thanks This email is intended only for the person to which it is addressed and may contain confidential or legally privileged material. Any dissemination or other use of or taking of any action in reliance upon the content of this email by persons other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the email from any computer. Opinions and other information in this email that do not relate to the business of my employer are not given nor endorsed by it. Unencrypted email is not secure and may not be authentic. If you have any doubts as to the contents please telephone to confirm. Oceana Gold Corporation and its related entities accept no responsibility for changes made to this email or its attachments after transmission from Oceana Gold Corporation and its related entities and do not guarantee that this email or attachments are virus or error free. _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Thanks both for looking into this, should be fixed now.
Tom
On 20/10/2017 08:16, Tim Cooper wrote:
On 20 Oct 2017, at 00:26, Michael Davies <Michael.Davies@oceanagold.com mailto:Michael.Davies@oceanagold.com> wrote:
Hi Guys,
The empty section is an issue, but there’s also the Authorization: Bearer line in the headers, removing that and the empty section gets things to work.
Regards,
Michael.
Hi,
I ran an test_alert again, but now failed with a 408:
SQL RUNTIME[0.00025296s]
o Notifying [teams] Observium Alerts Teams:
{"webhook_address":"https://outlook.office.com/webhook/35efe6c3-7319-485a-afd3-1865ffa3c4ed@3b850805-f971-474d-8f6c-bd17485bee17/IncomingWebhook/73c99acde6974e6bba0361a7e590c711/8b27cc7f-f000-4ca3-aff2-34f421e346e1"}
REQUEST[https://outlook.office.com/webhook/35efe6c3-7319-485a-afd3-1865ffa3c4ed@3b85...]
REQUEST STATUS[FALSE]
REQUEST RUNTIME[25.9535s]
RESPONSE CODE[408 Request Timeout]
SQL[UPDATE `notifications_queue` set `notification_locked` ='0',`endpoints` ='{"contact_id":"11","contact_descr":"Observium Alerts Teams","contact_method":"teams","contact_endpoint":"{\"webhook_address\":\"https:\\\/\\\/outlook.office.com\\\/webhook\\\/35efe6c3-7319-485a-afd3-1865ffa3c4ed@3b850805-f971-474d-8f6c-bd17485bee17\\\/IncomingWebhook\\\/73c99acde6974e6bba0361a7e590c711\\\/8b27cc7f-f000-4ca3-aff2-34f421e346e1\"}","contact_disabled":"0","contact_disabled_until":null,"webhook_address":"https:\/\/outlook.office.com\/webhook\/35efe6c3-7319-485a-afd3-1865ffa3c4ed@3b850805-f971-474d-8f6c-bd17485bee17\/IncomingWebhook\/73c99acde6974e6bba0361a7e590c711\/8b27cc7f-f000-4ca3-aff2-34f421e346e1"}' WHERE `notification_id` = '154']
SQL RUNTIME[0.00066400s]
root@kelvin:/opt/observium#
But...
It came through:
[cid:ef0148bc-43f2-4543-ac45-6967984058e4]
Thanks all for this great addition to Observium.
KR,
Epco
________________________________ Van: observium observium-bounces@observium.org namens Tom Laermans tom.laermans@powersource.cx Verzonden: zaterdag 21 oktober 2017 00:50:29 Aan: observium@observium.org Onderwerp: Re: [Observium] Webhook MS Teams not working
Thanks both for looking into this, should be fixed now.
Tom
On 20/10/2017 08:16, Tim Cooper wrote:
On 20 Oct 2017, at 00:26, Michael Davies <Michael.Davies@oceanagold.commailto:Michael.Davies@oceanagold.com> wrote:
Hi Guys,
The empty section is an issue, but there’s also the Authorization: Bearer line in the headers, removing that and the empty section gets things to work.
Regards, Michael.
Epco Dijk Systems Administrator
Northpool B.V. 3e Binnenvestgracht 23 N 2312 NR Leiden The Netherlands Tel: +31 (0)88 2400300 Fax: +31 (0)88 2400399 E-mail: epco.dijk@northpool.nl Web: www.northpool.nl
[Logo Northpool]
This message and any attachments (the "message") are confidential and intended solely for the addressees. If you are not the addressee indicated in this message or if this message has been addressed to you by error, you may not copy or deliver this message to anyone but destroy it and kindly notify the sender by reply email. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Northpool bv shall not be liable for the message if altered, changed or falsified.
participants (4)
-
Epco Dijk -
Michael Davies -
Tim Cooper -
Tom Laermans