English
Chinese (Simplified)
French
German
Italian
Japanese
Russian
Spanish
Vietnamese
Wishlist: AutoResponder-Only Accounts
-
When we have someone who leaves the company, especially if they were higher up, we like to have an autoresponder continue for a fair length of time, but we don't want to keep their whole account active.
We'd like to see something that would allow an AutoResponder Only list -- a list of emails and corresponding auto-response files for each email. Emails coming in to one of the addresses on the list would get an autoresponse, but the incoming email would be discarded. It would also keep from eating up an account license for a non-existant user. It would basically be a mailing list, where anyone could email to it, but the email would be discarded after the autoresponder macros were processed and the response sent.
Thanks,
Dave
-
This can already be done using the content filter and aliases.
- Delete the account in question, we will call it olduser@domain.com.
- Create an alias for olduser@domain.com that points to a valid local account
- Create a content filter rule like the following:
[Rule048]
RuleName=Send A Note and Delete
Enable=Yes
ThisRuleCondition=All
ProcessQueue=BOTH
Condition01=X-MDRcpt-To|contains|AND|olduser@domain.com|
Action01=send note|"to <$SENDER$>","from <MDaemon@domain.com>","subject <Re: $SUBJECT$>","x-flag=attach <$COPYOFMESSAGE$, MIME> -X","","Hello,","","This address is no longer valid, your message will be deleted."
Action02=delete|Anytime a message is sent to olduser@domain.com a message will be sent back to the sender, and the message will be deleted.
-
Arron:
Ok, thanks. Will give that a try.
A slightly related question: Why does the autoresponder for a frozen account attempt to send a response, only to have that response end up in the holding queue, where it cannot be released because the sender isn't authorized to send? And the holding queue just builds up and builds up. For instance, we might have student interns that are here for the summer, then back over Christmas break, so we freeze their account -- but if there's an autoresponder set....
I would be fine if a frozen account COULD send an autoresponse -- for instance, the intern may have been corresponding w/ somone on a project, and the autoresponder could say "hey, I'm unavailable -- you need to email person X."
Dave
-
In some cases an account being frozen is very temporary. Meaning it could last for minutes. If there is an autoresponder enabled, we leave it enabled so messages that arrive when the account is frozen also receive the auto response. After the account is thawed the next time MDaemon reprocesses the holding queue the messages will be sent out.
If you want an account to be able to send an autoresponse, I'd try adjusting the mail and web services settings. To simplify the process, I'd suggest createding a group that configurs the desired settings and then just add the user account to that group. This will allow you to prevent access, while still allowing the autoresponder to work. Make sure the priority on the group is set low enough to over-ride all other groups the account may be a member of.
-
Ooooh! Great idea... Thanks!
Dave
-
@Arron Hi Arron, sorry to OP for hijacking this post.
This is fantastic as we were looking to acheive exactly this. I have this working without having any aliases in place though! Should this content filter still work with no aliases and if so are there any negative side effects to not having the aliases? Seems pointless to have them if they are not needed?
-
The point of the alias was so that the original account (olduser@domain.com) could be deleted and MDaemon will still accept the mail for olduser@domain.com. If you have MDaemon configured to accept mail for addresses that don't exist, you wouldn't need the alias, but I wouldn't reccomend this setup as it can lead to lots of mail being accetped and then bounced.
You also wouldn't need the alias if the olduser@domain.com account still existed.
