11/25/2021 1:40 AM | |
Joined: 6/4/2008 Last visit: 9/15/2024 Posts: 1497 Rating: (324) |
Hi all, We are attempting to use TMail_C to e-mail via Gmail.com and before I lose all my hair, I though I would reach out for some assistance. Been following the guidance in the 12/2020 document: https://support.industry.siemens.com/cs/ww/en/view/46817803 We are using an S7-1515TF-2 PN (MLFB=6ES7 515-2UM01-0AB0) Firmware version V2.8.3 No CP card is fitted Safety is disabled TIA version is V16 Upd4 From what I understand, this CPU and this FW version should now be capable of using SMTPS e-mail via the integrated PN ports, at least according to the table 3-2 in the pdf document above This particular iteration of our attempt uses the TMail_QDN_SEC data type See screenshot of the connection DB settings (I ensured the online values matched) For obvious reasons, the email address and passwords are substituted, but keep the form of the original Apart from occasional error messages of 8030 which is unlisted, I keep seeing 16#80E1 which suggests the following may be wrong. 80E1 - Error during the handshake. Possible causes: Abort by the user Security not high enough Renewed negotiation is not supported SSL/TLS version is not supported. Decryption error See watch table result screenshot, I expanded the instance DB and saw it definitely comes from the TMail_C call, but I noticed that in the instance DB that the To_S and various other parameters are not visible. I'm not sure if these are only there for 1 scan for example, or if they are not actually viewable, but it seemed strange to me so I took a screenshot of this The hardware ID for the integrated PN Port 1 was set to 64 as per the System constant. I checked the current certificate on my Gmail account and this was reported as GTS CA 1C3, so I downloaded the GTS CA 1C3 cert from https://pki.goog (I also tried loading in the GTS Root R2 into the Trusted and root certs and changing the certificate ID when testing it) This was loaded in the global certificate manager and later, locally as a partner device certificate (ID set in the connection as 3 to match the certificate ID) I also tried enabling the ExtTLSCapabilities as a test, but this made no difference. The IP of the PLC and that of my router are on the same subnet, I also added the router address as a DNS server address. Is there anything obvious that I'm missing? Would be grateful for any help. Regards, Graeme Attachmentscreenshots.zip (499 Downloads) |
Last edited by: Jen_Moderator at: 11/25/2021 10:38:18Optimized link. Edited text for better reading. |
|
12/21/2021 4:20 PM | |
Joined: 3/28/2020 Last visit: 7/24/2024 Posts: 2 Rating: (0) |
Hi there, Did you ever get a solution to this? I am having exactly the same issue trying to send emails Thanks |
6/9/2022 11:05 AM | |
Joined: 10/21/2015 Last visit: 8/23/2024 Posts: 16 Rating: (0) |
Hi guys! Did you solve your problem with sending mail? What mail provider did you use? |
Follow us on