GithubHelp home page GithubHelp logo

Comments (9)

ian-kent avatar ian-kent commented on June 27, 2024

Thanks @rosstimson, i'll investigate asap!

from mailhog.

rcrowe avatar rcrowe commented on June 27, 2024

I can also replicate this issue if it's of any help.

from mailhog.

stevebelicha avatar stevebelicha commented on June 27, 2024

Yes I can replicate it too

from mailhog.

ian-kent avatar ian-kent commented on June 27, 2024

thanks all, and sorry, haven't had a chance to look at this yet - hopefully will soon! (but PR's welcome if anyone does has a fix)

from mailhog.

jygastaud avatar jygastaud commented on June 27, 2024

Bug confirmed here too.

@ian-kent any news regarding that issue? Can you drive us where to look at to try to fix it?

from mailhog.

ian-kent avatar ian-kent commented on June 27, 2024

Sorry its taken a while to get around to looking at this - could anyone provide some example content please?

Just tried to reproduce it, but with a basic HTML e-mail it works as expected:

Subject: HTML test message
From: Foo <[email protected]>
To: Bar <[email protected]>
Mime-Version: 1.0
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<html>
<body>
<a href="http://iankent.uk/some_test_link">important link</a>
</body>
</html>

Wondering if it might be something to do with content encoding

from mailhog.

slonoed avatar slonoed commented on June 27, 2024

@ian-kent seems like problem in HTML renderer.

I use send to mailhog your html, and in Plan Text tab all OK

<html>
<body>
<a href=3D"http://iankent.uk/some_test_link">important link</a>
</body>
</html>

But in HTML tab

<html><head></head><body>
<a href="http://iankent.uk/some test link">important link</a>

</body></html>

from mailhog.

ian-kent avatar ian-kent commented on June 27, 2024

Thanks @slonoed - can you provide the full SMTP message you used, I can't reproduce the bug with just the headers in the example I gave

from mailhog.

ian-kent avatar ian-kent commented on June 27, 2024

I think this is fixed now - RFC2047 encoding was replacing a "_" with a " " before decoding, which is correct when applied to headers, but not the message body.

Please reopen if it hasn't been fixed 😄

from mailhog.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.