Outlook Integration Error: Email Delivery Failed Solution Needed | Lindy Community

Outlook Integration Error: Email Delivery Failed Solution Needed

Hey, whenever i use the outlook integration for automatic influencer outreach i get this error "Delivery has failed to these recipients or groups: Your message wasn't delivered because the recipient's email provider rejected it." Does anyone have a solution for this?

👀1

10 comments

Marvin A.
·
·
interesting… can you share the task URL with me? happy to take a look 🙏🏾
Marvin A.
·
·
How to share your Lindy task URL: 1. Click your Lindy agent → click “tasks” 2. Find the task you need help with 3. Click the specific task (you should see the full execution) 4. Copy that page URL from your browser 5. Paste the URL in your support request Note: The URL should include “task” followed by a number Screenshots are also helpful!
Alan T.
·
·
Marvin A. had the same issue, here is my task URL: https://chat.lindy.ai/alan-tebuevs-workspace/lindy/realtor-reach-out-684a19c9ef7366d0f013a1bb/tasks?task=684a244a0db643e3bc663f71 Seems like Lindy might not have good way to ensure deliverability and bypass email firewalls
Marvin A.
·
·
hey Alan T. I am confused.. the task shows that the email was sent successfully?!
Alan T.
·
·
Lindy claims it was sent, but the recipient’s mailbox rejected it
Alan T.
·
·
Marvin A.
Westpoint C.
·
·
Yup, same happening to me
➕1
Marvin A.
·
·
Interesting, talking to the engineers to investigate!
🔥1
Alan T.
·
·
Is Lindy supposed to be able to bypass all recipient mailbox firewalls?
Marvin A.
·
·
So I talked to both our engineers and the eng team from our integrations partner. Alan T. & Westpoint C. the “recipient rejected” error happens on the receiving end after the email is successfully sent. usually it’s their spam filters or domain reputation issues with bulk outreach. quick fixes to try:
warm up your domain with smaller volumes first
personalize content to avoid looking automated
check your SPF/DKIM records
use a separate sending domain
this isn’t something we can fix on our end since it happens after the email leaves our system