I am working with a customer to interace with HubSpot on an IBM i (AS400) system. I created an email token, got the user and password, and tried to send an email using that information. All logs connecting to the HubSpot SMTP relay say the email was accepted and queued for delivery, but I didn’t receive it (yes, I checked spam as well). I also don’t see a history of the email in the dashboard for the account. Here’s a log of the communications: Attempting to connect to server smtp.hubapi.com on port 587.... Waiting for connection... Connection to server smtp.hubapi.com on port 587 succeeded! 220 smtp.hubapi.com ESMTP R6H7kfThjW17s7df6K-Bj-0 - hssmtp Sending EHLO command to smtp.hubapi.com. EHLO xxxxx 250-smtp.hubapi.com at your service, [/172.16.31.222:25234] Sending STARTTLS command. STARTTLS 220 2.0.0 Ready to start TLS R6H7kfThjW17s7df6K-Bj-0 - hssmtp SSL handshake succeeded! Sending EHLO command to smtp.hubapi.com. EHLO xxxxxxx 250-smtp.hubapi.com at your service, [/172.16.31.222:25234] Sending AUTH LOGIN command. AUTH LOGIN Sending User ID. 334 VXNlcm5hbWU6 R6H7kfThjW17s7df6K-Bj-0 - hssmtp [user removed] 334 UGFzc3dvcmQ6 R6H7kfThjW17s7df6K-Bj-0 - hssmtp Sending Password. [password removed] 235 2.0.0 Authentication successful. R6H7kfThjW17s7df6K-Bj-0 - hssmtp MAIL FROM: 250 2.0.0 Sender address accepted. R6H7kfThjW17s7df6K-Bj-0 - hssmtp RCPT TO: 250 2.0.0 250 Recipient address accepted. R6H7kfThjW17s7df6K-Bj-0 - hssmtp Sending to start message. DATA 354 Continue R6H7kfThjW17s7df6K-Bj-0 - hssmtp Sending to end message. . 250 2.0.0 Ok queued as 1549549116344/e719b4af-6e4b-4cd3-94d3-a1491efa0c36 R6H7kfThjW17s7df6K-Bj-0 - hssmtp Sending QUIT command to smtp.hubapi.com. QUIT 221 2.0.0 cheers R6H7kfThjW17s7df6K-Bj-0 - hssmtp

Hi, @cjbaker. Sincere apologies for the delayed response. I appreciate your patience while our team investigated your reports. We checked our logs for the messages we discussed above. In both cases, we recorded a “Missing at least one required body: ‘html’ or ‘text’” message, which indicates the message either lacked content or wasn’t formatted properly. Could you confirm that you included content for the email’s body and provide an example of a message you passed to the SMTP API?

@IsaacTakushi, It was an email address that was used. I don’t believe it’s set up as a contact in my customer’s account. I didn’t want to post the email here for spambots to collect. :slightly_smiling_face: [redacted]

Totally fair, @bvstone. Thanks for sharing. I’ve redacted the email so there’s even less risk of that [16x16_smiley-wink.png.png] Could you still specify your client’s Hub ID, though?

Hey, @bvstone. Apologies for the delayed response. My internal tool is showing 4 successful transactional email deliveries from account 2618299 to the email you specified on Thursday, 7 February 2019. Indeed, all four messages were opened at one point, so they were delivered to someone.

@IsaacTakushi, those emails you mentioned were sent using the Single Send Email api, not the SMTP API. The Single Send API I have working just fine. With the SMTP API (which this post is about) you send email by directing your email client to use the server and credentials specified by HubSpot after setting up credentials/SMTP tokens for a user. As you can see in the original post, that is the connection that was made, the user and password that was set up was used, and the mail server accepted the email for delivery.

Sorry about that, @bvstone. I forgot we were discussing the SMTP API. I’ll dig into this further.

Thanks for your continued patience, @bvstone. I haven’t been able to uncover the issue yet, but I wanted to confirm whether you’ve tried resetting your SMTP token yet? Could you go ahead and do that and let me know if you receive the same response but no tracking? If you’re still experiencing the issue after this step, I’ll loop in one of our email deliverability consults for further investigation.

@IsaacTakushi I did just try resetting the token/password. I tried again. The SMTP server reported: 02/13/2019 14:25:57 - 250 2.0.0 Ok queued as 1550090317383/ba5ae739-d697-483c-925f-bcf80df98e1e R6H8vWS5JW5gnfLG7GHX6L0 - hssmtp Just as before, it says the email is queued for delivery, but it’s never sent. Does the email need to come from a specific allowlisted IP address, or something else?

Thanks for confirming, @bvstone. I don’t believe it needs to come from a allowlisted IP address if you have the correct token and password. I’ll investigate further with my team. Am I correct in believing you tested again with the same contact as earlier?

@IsaacTakushi yes… the email was sent to bvstone at bvstools dot com. The last message I sent had an email ID that you should be able to find in your SMTP server’s logs. If not and you need to turn on some debugging, let me know and I can send another test.

SMTP API Not delivering Email

Develop, Build & Integrate APIs & Integrations

IsaacTakushi February 14, 2019, 10:21pm 17

Thanks for all this information, @cjbaker.

The one part I need to investigate further is the contact’s email address. If you send me a link to the contact in your account, that’ll be enough.

Topic		Replies	Views
SMTP: Email is queued for delivery, but is never received. APIs & Integrations email	8	13192	July 4, 2024
How to check email events/status for every email we are sending to the users. APIs & Integrations email	5	5305	November 1, 2021
Clarity on the SMTP API APIs & Integrations email	4	2982	January 22, 2021
SMTP API For Emails APIs & Integrations professional	1	2827	August 16, 2023
SMTP API: Drop the content of the email at the Hubspot contact. APIs & Integrations email	0	655	September 22, 2023

SMTP API Not delivering Email

Related topics