Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Email catch-all: Delete entries within control center #754

Closed
fkaminski opened this issue Nov 19, 2020 · 6 comments
Closed

Email catch-all: Delete entries within control center #754

fkaminski opened this issue Nov 19, 2020 · 6 comments
Assignees
Labels
Milestone

Comments

@fkaminski
Copy link

It would be nice if we could delete one or all e-mail entries directly from the control center (instead manually in the console/shell).

@fkaminski
Copy link
Author

Maybe leave a hint in the documentation for manually deleting mails too;

bash shell.sh
cd ../../var/mail
ls -a
rm devilbox
exit

@stale
Copy link

stale bot commented Jun 4, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the issue:stale This issue has become stale and is marked for auto-close label Jun 4, 2021
@stale stale bot closed this as completed Jul 8, 2021
@fkaminski
Copy link
Author

Would still be a nice feature ...

@cytopia
Copy link
Owner

cytopia commented Jul 8, 2021

Agree

@cytopia cytopia reopened this Jul 8, 2021
@stale stale bot removed issue:stale This issue has become stale and is marked for auto-close labels Jul 8, 2021
@llaville
Copy link
Contributor

Probably you didn't notice yet but Mailhog is able to delete one or all messages in a GUI.
Of course as the default storage is in-memory, we have to configure it to use maildir storage (see https://github.com/mailhog/MailHog/blob/master/docs/CONFIG.md, the MH_STORAGE env variable).

Devilbox documentation about Mailhog is available at https://devilbox.readthedocs.io/en/latest/custom-container/enable-mailhog.html

And here is what the current service become when we use maildir storage with devilbox backups/mailhog directory (for example).

# vim: set ft=yaml:
---
version: '2.3'

services:

  # -----------------------------------------------------------------------------------------------
  # MailHog
  # -----------------------------------------------------------------------------------------------
  mailhog:
    image: mailhog/mailhog:${MAILHOG_SERVER:-latest}
    hostname: mailhog
    ports:
      - "${LOCAL_LISTEN_ADDR}${HOST_PORT_MAILHOG:-8025}:8025"
    environment:
      MH_STORAGE: "maildir"
      MH_MAILDIR_PATH: /tmp/mailhog
    networks:
      app_net:
        ipv4_address: 172.16.238.201
    depends_on:
      - bind
      - php
      - httpd
    volumes:
      - ./backups/mailhog:/tmp/mailhog      

Usage of Mailhog allow to bypass issue #798. Remember that native devilbox mail support use a solution around PEAR that is a bit outdated now !

@cytopia cytopia self-assigned this Jan 30, 2022
@cytopia cytopia added this to the v1.10.1 milestone Jan 30, 2022
@cytopia
Copy link
Owner

cytopia commented Jan 30, 2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants