mailcatcher
mailcatcher copied to clipboard
sj26
Catches mail and serves it through a dream.
``` Starting MailCatcher v0.8.2 ==> smtp://0.0.0.0:1025 ==> http://0.0.0.0:1080 *** Error receiving message: {:sender=>"[email protected]", :recipients=>["[email protected]"]} Exception: undefined method `length' for nil:NilClass Backtrace: mailcatcher (0.8.2) lib/mail_catcher/mail.rb:48:in `add_message' mailcatcher (0.8.2) lib/mail_catcher/smtp.rb:58:in `receive_message' eventmachine...
I just tried to run a simple test, using version 0.8,2, to ensure that the recipient is correctly set. According to mailcatchers `Source` tab, everything looks fine: ```yml To: Max...
Many users seems to be confused by this clear button thinking that it will clears the search bar. I propose to change the label to avoid any confusion.
I added an HTML source view because I needed to look at the HTML sources and it was so much faster to use this than the browser's developer tools. For...
These changes bring the number of attachments for each message on the message list. This is how it looks after these changes: Resolves #523.
For my testing, it would be invaluable to see the number of attachments for each message already on the message list without having to click and open each of them...
Environment: OS: macOS Sonoma 14.4.1 Ruby: 3.3.2 MailCatcher: 0.10.0 Browser: Google Chrome (125.0.6422.114) and Mozilla Firefox (126.0.1) The `.js` and `.css` files from `/assets` are resolving with an incorrect `content-type`...
I don't know why I am experiencing an internal server error on mailcatcher.I am running ruby on rails on webpack with vue.This was my installation process: 1. Installed mail checker...
Detected by [Grype](https://github.com/anchore/grype) in Docker image `sj26/mailcatcher:v0.10.0`: ``` NAME INSTALLED FIXED-IN TYPE VULNERABILITY SEVERITY busybox 1.36.1-r28 1.36.1-r29 apk CVE-2023-42365 Medium busybox 1.36.1-r28 1.36.1-r29 apk CVE-2023-42364 Medium busybox-binsh 1.36.1-r28 1.36.1-r29 apk...
The `rack` dependency version, `~>2.2`, causes conflicts with modern `rackup` versions (e.g. `2.1.0`); it should be verified and upgraded to a modern version (e.g. `~>3.1`).
