verbose logging using docker image

[tszpinda]

Loving the project!

Is there a way to make docker image not to print content of attachments into the logs? as it gets very verbose with bigger attachments.

[ian-kent]

Thanks @tszpinda

No configurable way of changing log output at the moment (from MailHog) - a temporary workaround would be to pipe the output to /dev/null or something like that.

I'll have a look at making MailHog log output a bit more configurable!

[mjsisley]

+1

[esiqveland]

Any news on this? It makes it very verbose when printing entire data contents of every email.

[ian-kent]

Sorry for the delay - I'll get something done asap.

[fredleger]

+1
i used it as a production solution but the container is very agressive on cpu when priting every byte received in attachement ...

[talawahtech]

FYI, this is the docker ENTRYPOINT directive that I used to get MailHog to stop filling up my logs:

["/bin/sh", "-c", "MailHog &>/dev/null"]

Of course, if you are having trouble with something and actually need to look at the logs you will have remove this hack first. Would be great if we could get a verbosity flag for this.

[vchaptsev]

docker-compose:

mailhog:
  image: mailhog/mailhog
  logging:
    driver: 'none'  # disable saving logs
  ports:
    - '8025:8025'

[savinov]

Why don't you use your own go-log everywhere in MailHog, but only in main.go?
https://github.com/ian-kent/go-log

[rhnewtron]

We use mailhog as target for load tests for html mails. We use Openshift and collect logs to the integrated EFK stacks for all containers. Right now a single Mailhog instance fills gigabytes of logs. For now we disabled logs completely. However a logging verbosity system would be a great feature:

• Warn: Warnings and Errors only
• Info: Minimal Metadata (Mail Received with Headers atc)
• Debug: Metadata (Mail Received with Headers atc)
• Trace: Current Log

+1

[natearn]

docker-compose:

mailhog:
  image: mailhog/mailhog
  logging:
    driver: 'none'  # disable saving logs
  ports:
    - '8025:8025'

I'm confused and surprised to learn that doing this causes the mailhog container to hang when sending a PDF attachment. It took me a while to narrow it down to the logging driver specifically.

[gt-novelt]

docker-compose:

mailhog:
  image: mailhog/mailhog
  logging:
    driver: 'none'  # disable saving logs
  ports:
    - '8025:8025'

also breaks docker compose logs -f

Error response from daemon: configured logging driver does not support reading

[egor83]

I wanted to disable logging altogether without building Mailhog's image, so I combined @fnep's solution in #353 and @talawahtech's solution (thanks for these!) a bit, editing docker-compose.yml as follows:

mailhog:
  ...
  entrypoint: ["/bin/sh", "-c", "MailHog &>/dev/null"]