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

Why don't use sieve auto responder mechanize instead cron + mail reader ? #1

Open
harobed opened this issue Jun 12, 2015 · 4 comments

Comments

@harobed
Copy link

harobed commented Jun 12, 2015

Why don't use sieve auto responder mechanize instead cron + mail reader ?

@dirkgroenen
Copy link
Owner

For starters, I haven't created Goldfish, only republished it. I was looking for an auto-reply and didn't had that much time. When I stumbled on Goldfish I decided to go for it, since it was easy to implement, combined with my current setup and was easy to integrate in Roundcube.

@harobed
Copy link
Author

harobed commented Jun 15, 2015

Ok because dovecot + sieve isn't too hard to configure. I suggest you to append this note in your README. http://wiki2.dovecot.org/Pigeonhole/Sieve/Examples#Vacation_auto-reply

@dirkgroenen
Copy link
Owner

In my opinion placing that code in the README ain't related to Goldfish.

Might explore Sieve's possibilities somewhere in the future and create a own project for it. In that case it could be worthy to link to that repo in the README as an alternative.

@jaapjansma
Copy link

I have just installed Sieve as I wanted a filter mechanism for the e-mails and also a vaction message. It looks quite good. I used this tutorial: https://www.rosehosting.com/blog/how-to-set-up-server-side-email-filtering-with-dovecot-sieve-and-roundcube-on-a-centos-6-vps/

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

No branches or pull requests

3 participants