Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Matt 359 posts 842 karma points
    1 week ago
    Matt
    0

    Images not being displayed for external users

    Hello,

    I'm looking to get some advise.

    We have a website which is internal only for staff, we've installed the newsletter studio which displays fine for users internal on the network.

    However when sending emails to anyone outside of the organisation the images aren't being displayed, This is due to the website being hosted on an internal server which is not accessible from outside.

    Is there a work around for this? For a standard header and footer I can host the images external and just reference.

    But is there a way that any images that form part of the message can be displayed?

    Thanks

  • Markus Johansson 1939 posts 5867 karma points MVP 2x c-trib
    1 week ago
    Markus Johansson
    0

    Hi!

    Thanks for using the package!

    You could host public images where ever you want to and just insert an img-element that points to this URL.

    Hosting the sending server on an internal network does bring some potential issues around tracking and links (if you're using link tracking). E.g. with the default setup, any links included in the email would be rewritten to a URL that tracks the click before redirecting the recipient to the actual URL. In your scenario, this would point to the internal server and external readers would not be able to follow the link.

    In general, the package does not take this kind of scenario into consideration - it would be possible to get most things to work but it could limit the features you're able to use - especially if you are targeting both internal and external recipients.

    In practice, I guess maybe your internal users can read emails on other devices that are not connected to the network/VPN at all times? So even your "internal" recipients would potentially suffer from the same problems.

    The recommendation would be to consider finding a way to host the package on a publicly accessible URL (at least the /media and /__ns routes). Another potential solution would be to have some kind of forward proxy that only allows certain routes to go through to the internal server.

    // Markus

Please Sign in or register to post replies

Write your reply to:

Draft