How do I get troubleshooting information when reporting an email tracking pixel?

[mullbird]

If you are opening an issue in this repository, I am wondering if you are required to include troubleshooting information.
If you open an HTML file delivered via email in a web browser, you are opening local HTML and will not get the troubleshooting information.
How should I describe this when opening an issue?

[Yuki2718]

Do you use an email client? If you use a webmail, you can use that url for reporting.

[Yuki2718]

Hmm, in that case it's impossible to get the Troubleshooting information and I'm not sure what will be the best. Maybe other members would have opinions.

[gorhill]

Typically we need to reproduce. If the issue is "images within email client", then this won't be addressed because email clients such as Thunderbird have the ability to block connections to remote servers when they render messages.

The issue here is too bespoke, it's not something that affect other users, and we don't add filters which are beneficial for only one user because of issues arising as a result of their custom configuration. Best is to just add the filter in your own filterset.

[Yuki2718]

The same email pixel will be sent to webmails too though. I reproduced some past cases with either Gmail or Outlook. Of course I first had to allow images, but this is not something too strange as otherwise all the images are blocked, which makes the emails half-broken.

[gorhill]

The same email pixel will be sent to webmails too though

Maybe, maybe not, we don't know. The scenario provided here is not that of a webmail client. If this can be reproduced with a webmail client, then of course we will take care of it.

[gorhill]

Anyway, my stance regarding this is to not further burden list maintainers with issues with very special configurations, but if list maintainers themselves don't mind then it's all up to you, I won't object.