Hi, I used to use spamgourmet many, many years ago, but then I found mailnull and sneakemail and have been using the two of those. The reasons I switched away are:
(1) Message cap. I want to use my email hiding service to join mailing lists and other services where I expect to receive many messages in the future, yet be able to quickly and cleanly cut them off as soon as I get any spam from them. I can continually reset my message count, but that's impractical.
(2) Automatic creation of addresses. I've gotten plenty of spam via generated addresses on all of my @spamgourmet.com addresses. (You guys ought to adjust your answer on the FAQ; the current answer is rather disingenous on your part.) I could resort to watchwords, but that adds garbage to the address. What I ended up doing to emulate explicit address creation (before I switched away) was to enforce watchwords; when I needed a new address, I'd disable watchwords, choose whatever name I wanted, and reinforce watchwords.
Anyway, I'm now visiting this forum again because I'm hoping that I can convince the devs to implement these changes, and because of some gripes with mailnull/sneakemail. These wouldn't interfere with the existing approach; I'm requesting non-default options to enable explicit address creating and message cap removal.
I'm a dev too, but I don't have time to work on spamgourmet - that's why I switched away, rather than hack. Even if I did, it would take me much longer to implement the requested changes than the current devs due to codebase familiarity.
Thanks for hearing me in.
In case you're curious, my gripes with the other services are as follows; neither of these is anywhere as serious as the message cap limitation, however:
- mailnull has no outgoing addresses
- sneakemail has a bandwidth cap + address munging