Email Service Snap-in setup email forwarding verification email not appearing as ticket
ART-3207_KNOWLEDGE_NODE-47
**Primary Use Case** is **Tickets**, go to **Support** > **Tickets** in the DevRev app; otherwise, if the **Primary Use Case** is **Conversation** go to **Inbox**. Find and open your verification message here.\n6. Open the given link to confirm the request. Make sure you click the link that allows your support address to be forwarded to v\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_@hooks.devrev.ai.\n7. Go back to your Gmail forwarding settings, select **Forward a copy of incoming mail** and **Save
Email snap-in configuration | Email | Integrate | Snap-ins | DevRev
ART-3207_KNOWLEDGE_NODE-55
test email to your configured address from the deliverability tool and confirm that a conversation or ticket is created.\n2. Respond from the test conversation or ticket in DevRev to the address mentioned in the deliverability check tool.\n\nYou need to add the address as a contact, which can be done in the email composer page.\n\n1. Check the status of the email sent by coming back to the chosen tool.\n\nIf the **DMARC Compliance checks** on the tool pass, then DevRev email is
Email snap-in configuration | Email | Integrate | Snap-ins | DevRev
ART-1284_KNOWLEDGE_NODE-41
forwarding address is `v1.abc.xyz@hooks.devrev.ai`, you should set up email\nforwarding from `test@company.com` to `v1.abc.xyz@hooks.devrev.ai`.\n\n##### \n\nOnly emails forwarded from the allowlist of emails/domains are emitted as events. Hence, this event source should be used for email forwarding only, not as a direct mailbox to which anyone can send their emails. Emails received (either directly or by forwarding) from senders who aren\xe2\x80\x99t in the allowlist are dropped. There are a
Event sources | DevRev | Docs
ART-3207_KNOWLEDGE_NODE-49
select **Forward all emails sent to this mailbox**, enter the forwarding address v\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_@hooks.devrev.ai, and choose whether you want to keep a copy of forwarded emails. If you don\'t see this option, make sure a license is assigned to the user account. Select **Save changes**.\n\nOnce added, an invitation is sent to the hooks address. The invitation appears as a conversation in your inbox in the DevRev app. However, note that the conversation comment might not be
Email snap-in configuration | Email | Integrate | Snap-ins | DevRev
ART-1478_KNOWLEDGE_NODE-46
event source is deployed, the instructions show a unique email address. You have to set up forwarding in your original email inbox or Google Group to this email address. In the example above, if the forwarding address is `v1.abc.xyz@hooks.devrev.ai`, you should set up email forwarding from `test@company.com` to `v1.abc.xyz@hooks.devrev.ai`.\n\n#####\n\nOnly emails forwarded from the allowlist of emails/domains are emitted as events. Hence, this event source should be used for email forwarding
Event sources — DevRev | Docs
ART-1284_KNOWLEDGE_NODE-42
few exceptions to this like Google\xe2\x80\x99s forwarding confirmation emails.\n\nThe allowlist can either contain an email address or an entire domain. Strict matching is done for domains, meaning that subdomains are not included.\n\n##### \n\nThe email protocol regarding forwarding is not very well defined. We\xe2\x80\x99ve tested forwarding from common sources like Gmail, Google Groups, and Outlook Inbox. However, if you\xe2\x80\x99re having issues with email forwarding on other providers,
Event sources | DevRev | Docs
ART-1478_KNOWLEDGE_NODE-45
sample of the YAML is shown below:\n\n[code]\n\n      - name: email-event-source  \n    ---  \n        description: Event source which emits an event when an email is received.  \n        display_name: Email events listener  \n        type:  email-forward  \n        config:  \n          allowlist:  \n            - "test@company.com"  \n            - "mycompanydomain"\n[/code]  \n  \nThe event type of the events emitted by this event source is `email.receive`.\n\nWhen a snap-in using such an
Event sources — DevRev | Docs
ART-2027_KNOWLEDGE_NODE-28
email address that messages to it create either a conversation or a ticket, but not both simultaneously. Whether to create a conversation or a ticket depends on the nature of the emails received at a specific email address.\n\nRead more about [conversations](../product/conversation) and [tickets](../product/tickets) to decide which is more suitable for your use case.\n\nWhen needed, you can link a conversation to a ticket. This is particularly useful if you decide to use conversations for all
Email | Integrate | Snap-ins | DevRev
ART-1478_KNOWLEDGE_NODE-47
only, not as a direct mailbox to which anyone can send their emails. Emails received (either directly or by forwarding) from senders who aren\xe2\x80\x99t in the allowlist are dropped. There are a few exceptions to this like Google\xe2\x80\x99s forwarding confirmation emails.\n\nThe allowlist can either contain an email address or an entire domain. Strict matching is done for domains, meaning that subdomains are not included.\n\n#####\n\nThe email protocol regarding forwarding is not very well
Event sources — DevRev | Docs
ART-3207_KNOWLEDGE_NODE-51
an invitation is sent to the hooks address. The invitation appears as a conversation in your inbox in the DevRev app. However, note that the conversation comment might not be rendered correctly as HTML, making the invite button inaccessible directly. To accept the invitation, you\'ll need to download the email.eml attachment and open it in your preferred mail client. From there, you can click **Accept invite**.\n\nZoho Mail\n\nTo enable forwarding, add the
Email snap-in configuration | Email | Integrate | Snap-ins | DevRev