Only Direct Auto Responder Option

timoto shared this idea 4 years ago
Open Discussion

cPanel needs an option to force autoresponders to only respond from mails sent directly to an account instead of forwarded to an account.

Currently if contact@domain.com is forwarded to john@domain.com the autoresponder for john@domain.com is sent instead of the autoresponder setup for contact@domain.com.

This is both confusing and revealing of potentially sensitive information to the person receiving the autoresponder.

For example if a serious business query is made from smithers@rich.com to contact@domain.com and john@domain.com has a more personal autoresponder "on a madcap holiday bungee jumping off cliffs, back in a month, maybe". What is smithers@rich.com to think, he doesn't know who john@domain.com is, never sent an email to john@domain.com and doesn't/shouldn't need/want to know about the forthcoming holiday of john@domain.com.

This is not the official response that the company wants to give to smithers@rich.com

The company would prefer an option to force only direct autoresponders such that smithers@rich.com will only see an autoresponder from contact@domain.com such as "we are dealing with your request and will respond shortly"

Comments (6)

photo
4

I support this request. I'd tweak it though. Whilst I agree with the scenario outlined above, there's also the case where John users an alias address john.smith@domain.com. In this case he *does* want the auto-responder to fire for anything sent to john@ or john.smith@, but no to fire for e-mail sent to contact@.

What would be ideal is that, when setting-up forwarding in cpanel, you can specify whether this forward triggers an auto-response or not. The setting would be Yes for john.smith@, but would be No for contact@.

photo
1

That sounds wise! Thanks!

Please cPanel, do consider and implement this.

Any chance we could get it any time soon? When?

Thanks,

photo
1

Yes please.

We had a client switch to us and ran into issues because their previous host had the auto-responders implemented in that way and they rely on it.

Their general information e-mail is info@domain.com. Everything is also forwarded to owner@domain.com so she can keep an eye on things.

Now she went on a trip and put an auto-responder on her owner@domain.com and everyone e-mailing to info@domain.com got her auto-responder - from her e-mail address of course - that she is out of the office and only checks the e-mail sporadically.

Not good.

photo
2

I found a workaround for now.

Keep having public@domain forward to secret@domain.com.

For secret@domain.com set up an user-level filter:

Rules:

"Any Header" "contains" "Envelope-to: public@domain"

Action:

"Deliver to Folder" "/INBOX"

It seems that cPanel adds that additional header into the e-mail when forwarding.

Now, I don't know if "equals", "begins with" or "ends with" works as well. It was a users' account and I didn't want to play around too much with her autoresponder while she wasn't actually on vacation - especially since she was already unhappy about previous tries to working properly in the end while it worked that way on her previous host (not cPanel).

Also as a note - I tried the built in "Filter Test" and it did NOT catch it. Actual e-mails do work though.

I guess cPanel doesn't recognize "Envelope-to" as a header in the test box.

photo
1

I very much second this feature request: the ability to toggle auto-responders per forwarder would allow e.g. to create a forwarder (public@domain) that can be used to register on mailing lists, which forwards to a personal email address (secret@domain). If secret@domain has set an auto-responder but public@domain doesn't generate auto-responders, then messages sent via mailing lists to public@domain won't receive auto-responders.

In response to Mark's workaround: when including "Envelope-to" in the test string, it doesn't work for me. When omitting "Envelope to:", it does, however.

I've tried to generalize that rule a bit, so that it only triggers the filter when the sender's address hasn't been listed explicitly in any recipient field (to/cc/bcc):

Filter: "mute auto-responder for forwarders"

Rules:

"Any Header" does not contain "secret@domain"

Action:

"Deliver to Folder" "/INBOX"

So far, so good, but this means that if the SpamBox option of SpamAssassin is switched on, this filter will effectively bypass it, and all spam sent to public@domain will still end up in secret@domain's inbox (instead of the spam folder). Therefore, an additional filter needs to be configured and executed for secret@domain, prior to the "mute auto-responder for forwarders" filter:

Filter: "re-create SpamAssassin's SpamBox"

Rules:

"Spam Bar" contains "+++"

Actions:

"Deliver to Folder" "/spam"

"Stop Processing Rules"

The order of both filters is important:

  1. "re-create SpamAssassin's SpamBox"
  2. "mute auto-responder for forwarders"

Of course, this overrides the global SpamBox settings, and would require both filters to be set up for every email account, which is a hassle.

The option to toggle auto-responders per forwarder would be much more elegant and efficient!

photo
1

Ok, I can improve my own workaround: what bothered me is that the explicit setting of "Spam Bar" in the filter duplicates the SpamBox settings, meaning that if the spam score in SpamBox settings changes (to e.g. a minimal score of 1), this filter gets 'out of sync' (if it is left at a score of '+++' for the Spam Bar header).

Instead, the 'Spam Status' header does seem to follow the SpamBox threshold: if it is set to 3, this will cause messages with a higher spam score (and "Spam Bar" header "+++") to be flagged with the "Spam Status" header as "Yes, score=3.1". On the other hand, if the same message is being received with a lower SpamBox threshold of 5, it will still have the same "Spam Score" and "Spam Bar" headers, but (due to the higher threshold value) the "Spam Status" header will be "No, score=3.1".

This means that the spam check in this filter can be made dynamic, so it follows the SpamBox settings. The filters in my previous suggestion can hence be refined to (in the correct order, which still matters):

Filter: "re-create SpamAssassin's SpamBox"

Rules:

"Spam Status" begins with "Yes"

Actions:

"Deliver to Folder" "/spam"

"Stop Processing Rules"

Filter: "mute auto-responder for forwarders"

Rules:

"Any Header" does not contain "secret@domain"

Action:

"Deliver to Folder" "/INBOX"