This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
reference:user_autoresponder [2012/03/30 13:41] – [Autoresponder Rules] paul | reference:user_autoresponder [2013/01/18 09:00] – [Creating or editing an autoresponder] paul | ||
---|---|---|---|
Line 1: | Line 1: | ||
======Autoresponder====== | ======Autoresponder====== | ||
+ | |||
+ | An autoresponder is a way of automatically replying to messages as they arrive in a user's mailbox. | ||
+ | |||
+ | In VPOP3, an incoming message //must// arrive in a user's mailbox for the autoresponder to trigger. If you use forwards, assistants, mappings, etc to divert a message before it arrives in the mailbox, the autoresponder will never trigger. If you want to use an autoresponder, | ||
+ | |||
+ | |||
+ | =====Configuring Autoresponders===== | ||
+ | |||
For Versions 3 and 4 see [[Autoresponders v3 & v4]] | For Versions 3 and 4 see [[Autoresponders v3 & v4]] | ||
Line 14: | Line 22: | ||
{{: | {{: | ||
- | In the **Autoresponders: | + | In the **Autoresponders: |
+ | |||
+ | Note that this drop-down only selects which autoresponder you are currently editing. It does not select which autoresponder is used; all the defined autoresponders are used, depending on the rules defined for the autoresponders. | ||
====Autoresponder definition==== | ====Autoresponder definition==== | ||
Line 49: | Line 60: | ||
{{: | {{: | ||
+ | |||
+ | * **Rule name** is a name you give the rule for your own reference, eg " | ||
+ | * **Respond if this rule matches** tells VPOP3 whether to send the response when this rule matches. Usually this will be checked, but by not checking it it lets you specify exceptions to the other rules. Note that this does //not// disable this rule, the rule still applies, but if it matches, then no autoresponse will be sent. | ||
+ | * **Prevent user changes** - this stops the user from changing the rule via their Webmail access | ||
+ | * **Priority** - this lets you put the rules in a suitable order (higher priorities are processed first) | ||
+ | |||
+ | ===Conditions=== | ||
+ | * **Dates** - specify dates between which the autoresponder will trigger | ||
+ | * **Times** - specify times between which the autoresponder will trigger | ||
+ | * **Date/ | ||
+ | * **Days of the Week** - specify which days of the week the autoresponder will trigger on | ||
+ | * **Sender** - specify a substring match for the original message sender to make the autoresponder trigger | ||
+ | * **Subject** - specify a substring match for the original message subject to make the autoresponder trigger | ||
+ | |||
+ | If you leave any (or all) of the conditions blank (except for 'Days of the Week' | ||
+ | |||
+ | The Dates, Times and Date/Time settings are sometimes a bit confusing because people may think that Dates + Times is equivalent to Date/Time, but they are different. | ||
+ | |||
+ | If you have Dates of //1 March 2012 - 7 March 2012// and Times of //10:00 - 14:00//, then the autoresponder will trigger between 10am and 2pm on each day between 1st and 7th March (inclusive) | ||
+ | |||
+ | However, if you have Date/Times of //1 March 2012 10:00 - 7 March 2012 14:00//, then the autoresponder will trigger from 10am on 1st March to 2pm on 7th March. | ||
+ | |||
+ | You can use Dates, Times and Date/Times in the same rule. | ||