Hmm, yes, the boilerplate reply sounds like quite a good idea, although this doesn't come up quite often enough for it to seem worth the effort (though it does come up just often enough for me to wonder about it).
Thinking about it further, I suppose that provided the opening email at least mentions PuTTY (which they do generally manage to, and that's one of the ways I decide they're not spam) it does at least avoid the risk of the sender typing up a huge project description and then finding they've sent it to completely the wrong address by mistake. Though in that situation you'd think they could easily enough recover it from their outgoing mail archive and send it to the right address instead...
The other thing that might be good is a FAQ bit re suggestions. ie: Feature suggestion: this has been suggested already and is a nice to have but extremely technically difficult and timeconsuming so low-priority unless you want to fund this.. *grin*.
You probably get lots of the same suggestions over and over again...
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Thinking about it further, I suppose that provided the opening email at least mentions PuTTY (which they do generally manage to, and that's one of the ways I decide they're not spam) it does at least avoid the risk of the sender typing up a huge project description and then finding they've sent it to completely the wrong address by mistake. Though in that situation you'd think they could easily enough recover it from their outgoing mail archive and send it to the right address instead...
ie: Feature suggestion: this has been suggested already and is a nice to have but extremely technically difficult and timeconsuming so low-priority unless you want to fund this.. *grin*.
You probably get lots of the same suggestions over and over again...
-grue-