This feature request is set to Archived again. Why wasn't it solved the first time it went archived and people brought it up again? Why wasn't it solved the second time it went archived and people brought it up again. This is hardly the only time it has been brought up.
And this isn't the sort of thing that should require a consensus or a vote. This is an obvious feedback loop for a common setup for contact forms. I have 8 different contact forms set up like this for our subsidiary companies, covering 9 different employees. For Chinese New Year, each of those 9 employees gets a holiday autoresponder.
If one instance of the contact form gets triggered, it causes an exponential explosion at the server level, which gets us a warning.
I've got workarounds in place, but the main account is of course my own, so I simply can't use an autoresponder for my own email account.
Email goes to
[email protected], both via direct query and via contact form.
Email gets forwarded to
[email protected] and
[email protected],
[email protected],
[email protected], etc.
Responder1 goes on vacation. Sets holiday autoresponder.
Autoresponder holiday notification gets sent to
[email protected].
Email gets forwarded to everyone in the network, including
[email protected].
Autoresponder holiday notification gets sent to
[email protected].
Email gets forwarded to everyone in the network, including
[email protected].
Autoresponder holiday notification gets sent to
[email protected].
Email gets forwarded to everyone in the network, including
[email protected].
When the office is closed and the entire staff has an autoresponder, it is much worse.
This has been default behavior for this for so many years.
How is this not fixed yet? This is not a rare or unusual setup.