New email logging beta - problems!

TM-OML
Colaborador

Hi

 

I have tried to submit this via the Feedback function in the Product Updates section but I keep getting a message saying "Failed to Submit Feedback" - unhelpful!

Has anyone else tried the new Email Logging function to log all connected emails not just outbound and replies?

 

This should be brilliant, however in the hour since I've switched it on, our users keep (at different times) being made contact owner of a contact created called noreply@notifications.hubspot.com (presumably because they've forwarded a response or just received an email from the noficiations address), and this then leads to them receiving literally HUNDREDS of notifications in just a few minutes when any notification is sent to any user, with the notification type being "A contact was logged on records you're following"

 

I have switched off the functionality until Hubspot get this resolved as it seems to be a significant bug.

 

Has anyone else tried this beta yet?

Tom

0 Me gusta
2 Soluciones aceptadas
karstenkoehler
Solución
Miembro del salón de la fama | Partner
Miembro del salón de la fama | Partner

Hi @TM-OML,

 

If the feedback option throws an error for you, I'd recommend reaching out to HubSpot support directly to flag it. This is the user-to-user part of the community, so options for troubleshooting bugs are limited.

 

Best regards!

Karsten Köhler
HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer

Beratungstermin mit Karsten vereinbaren

 

Did my post help answer your query? Help the community by marking it as a solution.

Ver la solución en mensaje original publicado

0 Me gusta
TM-OML
Solución
Colaborador

In case anyone else experiences this, the fix seems to be to add HubSpot’s notification sender domain to the global Never log list so these messages are ignored by logging. *@notifications.hubspot.com

 

Then remove the new noreply@ contact that was created, or at the very least unset whoever the unfortunate contact owner is!

Ver la solución en mensaje original publicado

0 Me gusta
2 Respuestas 2
TM-OML
Solución
Colaborador

In case anyone else experiences this, the fix seems to be to add HubSpot’s notification sender domain to the global Never log list so these messages are ignored by logging. *@notifications.hubspot.com

 

Then remove the new noreply@ contact that was created, or at the very least unset whoever the unfortunate contact owner is!

0 Me gusta
karstenkoehler
Solución
Miembro del salón de la fama | Partner
Miembro del salón de la fama | Partner

Hi @TM-OML,

 

If the feedback option throws an error for you, I'd recommend reaching out to HubSpot support directly to flag it. This is the user-to-user part of the community, so options for troubleshooting bugs are limited.

 

Best regards!

Karsten Köhler
HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer

Beratungstermin mit Karsten vereinbaren

 

Did my post help answer your query? Help the community by marking it as a solution.

0 Me gusta