Sending a message to the seedlist: Difference between revisions
Created page with "Category:InboxSys Category:Configuration Category:E-Mail_analysis Category:Seeds <strong>Sending a message to the seedlist</strong> Campaigns are analysed in InboxSys app by sending them to a seedlist. This list consists of 2 parts: * The trigger - this is an address ending with @app.inboxsys.com. * The ISP seeds - those are the ISP seeds that are sent to Gmail, Outlook.com, Yahoo, Orange.fr and many others. You can find your personal seedlist in your..." |
No edit summary |
||
| Line 5: | Line 5: | ||
<strong>Sending a message to the seedlist</strong> | <strong>Sending a message to the seedlist</strong> | ||
Campaigns are analysed in InboxSys app by sending them to a seedlist. This list consists of 2 parts: | Campaigns are analysed in [[:Category:InboxSys|InboxSys]] app by sending them to a [[:Category:Seeds|seedlist]]. This list consists of 2 parts: | ||
* The trigger - this is an address ending with @app.inboxsys.com. | * The trigger - this is an address ending with @app.inboxsys.com. | ||
* The ISP seeds - those are the ISP seeds that are sent to Gmail, Outlook.com, Yahoo, Orange.fr and many others. | * The [[:Category:Reputation|ISP]] seeds - those are the ISP seeds that are sent to Gmail, Outlook.com, Yahoo, Orange.fr and many others. | ||
You can find your personal seedlist in your InboxSys account by clicking on the cogwheels icon in the far right top. | You can find your personal seedlist in your InboxSys account by clicking on the cogwheels icon in the far right top. | ||
The ISP seeds are showing in the "Inbox Delivery"-section on the individual campaign results. This section shows if the seeds have arrived to the inbox, the spam-folder, or somewhere else. For all mails received, it is possible to show full mail headers. | The ISP seeds are showing in the "Inbox Delivery"-section on the individual campaign results. This section shows if the seeds have arrived to the inbox, the [[spam]]-folder, or somewhere else. For all mails received, it is possible to show full mail headers. | ||
Messages to the trigger address are the messages that get actually analysed. A message that is not sent to the trigger address, will not be displayed in InboxSys at all. Messages sent to the trigger address only will arrive, but show all ISP seeds as "missing". | Messages to the trigger address are the messages that get actually [[:Category:E-Mail_analysis|analysed]]. A message that is not sent to the trigger address, will not be displayed in InboxSys at all. Messages sent to the trigger address only will arrive, but show all ISP seeds as "missing". | ||
Messages to the seedlist should be sent as list - in single messages. Adding seeds to CC or BCC will distort the final analysis. If you don't have access to an ESP, you can use [https://support.microsoft.com/en-us/office/use-mail-merge-for-bulk-email-letters-labels-and-envelopes-f488ed5b-b849-4c11-9cff-932c49474705 Mail Merge for Microsoft] or [https://addons.thunderbird.net/en-US/thunderbird/addon/mail-merge/ Mail Merge for Thunderbird] to simulate list-sending. | Messages to the seedlist should be sent as list - in single messages. Adding seeds to CC or BCC will distort the final analysis. If you don't have access to an ESP, you can use [https://support.microsoft.com/en-us/office/use-mail-merge-for-bulk-email-letters-labels-and-envelopes-f488ed5b-b849-4c11-9cff-932c49474705 Mail Merge for Microsoft] or [https://addons.thunderbird.net/en-US/thunderbird/addon/mail-merge/ Mail Merge for Thunderbird] to simulate list-sending. | ||
Because seeds are matched based on the | Because seeds are matched based on the [[subject]]line, it is important that all subjectlines are exactly the same. If [[personalisation]] on the subjectline is being used, personalization variables for each address in the seedlist should have the same content. | ||
In case you would like to test delivery to any ISP not on the list, please don't hesitate to create a [https://support.inboxsys.com/login?back_url=https%3A%2F%2Fsupport.inboxsys.com%2Fissues%2Fnew support ticket]. | In case you would like to test delivery to any ISP not on the list, please don't hesitate to create a [https://support.inboxsys.com/login?back_url=https%3A%2F%2Fsupport.inboxsys.com%2Fissues%2Fnew support ticket]. | ||
=InboxSys trigger seed unsubscribes= | |||
InboxSys calls the headers of all links in all seeds, in order to test if links work. InboxSys is not calling the ''body'' of that link! If this little check unsubscribes immediately, that indicates a few severe flaws in the unsubscribe mechanism. | |||
First of all, no-one uses a single-click [[unsubscribe]] in the bottom of an E-Mail. It's legally allowed to use a dual-click unsubscribe, so that is the common standard. When you click on an unsusbscribe link, the landing page should show a confirmation dialog. Otherwise, you get bot-unsubscribes! That is basically what we have here: a bot-unsubscribe. | |||
Secondly, we are calling the header of the page, but not the body. Even if there is no dialog, calling the header should only send back header information, but not execute actions that are typically taken ''after'' the ''full page'' has loaded. | |||
An immediate unsubscribe upon only calling the header of a page looks symptomatic to a List-Unsubscribe link. LU have opposite requirements and best practices from standard unsubscribe links. InboxSys never calls a List-Unsubscribe link, for this exact, obvious reason. | |||
==Troubleshooting unsubscribes== | |||
* Check your logs to see the reason for the unsubscription | |||
* Request Information from your ESP to explain why this has happened | |||
* InboxSys can assist to converse with ESP to see if their approach can be changed | |||
* Ensure the InboxSys trigger seed is safe-listed | |||
Revision as of 02:47, 9 June 2023
Sending a message to the seedlist
Campaigns are analysed in InboxSys app by sending them to a seedlist. This list consists of 2 parts:
- The trigger - this is an address ending with @app.inboxsys.com.
- The ISP seeds - those are the ISP seeds that are sent to Gmail, Outlook.com, Yahoo, Orange.fr and many others.
You can find your personal seedlist in your InboxSys account by clicking on the cogwheels icon in the far right top.
The ISP seeds are showing in the "Inbox Delivery"-section on the individual campaign results. This section shows if the seeds have arrived to the inbox, the spam-folder, or somewhere else. For all mails received, it is possible to show full mail headers.
Messages to the trigger address are the messages that get actually analysed. A message that is not sent to the trigger address, will not be displayed in InboxSys at all. Messages sent to the trigger address only will arrive, but show all ISP seeds as "missing".
Messages to the seedlist should be sent as list - in single messages. Adding seeds to CC or BCC will distort the final analysis. If you don't have access to an ESP, you can use Mail Merge for Microsoft or Mail Merge for Thunderbird to simulate list-sending.
Because seeds are matched based on the subjectline, it is important that all subjectlines are exactly the same. If personalisation on the subjectline is being used, personalization variables for each address in the seedlist should have the same content.
In case you would like to test delivery to any ISP not on the list, please don't hesitate to create a support ticket.
InboxSys trigger seed unsubscribes
InboxSys calls the headers of all links in all seeds, in order to test if links work. InboxSys is not calling the body of that link! If this little check unsubscribes immediately, that indicates a few severe flaws in the unsubscribe mechanism.
First of all, no-one uses a single-click unsubscribe in the bottom of an E-Mail. It's legally allowed to use a dual-click unsubscribe, so that is the common standard. When you click on an unsusbscribe link, the landing page should show a confirmation dialog. Otherwise, you get bot-unsubscribes! That is basically what we have here: a bot-unsubscribe.
Secondly, we are calling the header of the page, but not the body. Even if there is no dialog, calling the header should only send back header information, but not execute actions that are typically taken after the full page has loaded.
An immediate unsubscribe upon only calling the header of a page looks symptomatic to a List-Unsubscribe link. LU have opposite requirements and best practices from standard unsubscribe links. InboxSys never calls a List-Unsubscribe link, for this exact, obvious reason.
Troubleshooting unsubscribes
- Check your logs to see the reason for the unsubscription
- Request Information from your ESP to explain why this has happened
- InboxSys can assist to converse with ESP to see if their approach can be changed
- Ensure the InboxSys trigger seed is safe-listed