This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
reference:schedule [2011/07/12 08:30] – created paul | reference:schedule [2018/11/14 10:45] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 11: | Line 11: | ||
=====Pausing Scheduling===== | =====Pausing Scheduling===== | ||
At the top of the page you can **Pause** or **Resume** scheduling. Normal operation occurs when schedule is active (resumed). If you want to stop VPOP3 sending or collecting mail, then you can pause the scheduling. In this case, the only time it will connect to send/ | At the top of the page you can **Pause** or **Resume** scheduling. Normal operation occurs when schedule is active (resumed). If you want to stop VPOP3 sending or collecting mail, then you can pause the scheduling. In this case, the only time it will connect to send/ | ||
+ | |||
+ | =====Manual overrides===== | ||
+ | You can tell VPOP3 to connect from the VPOP3 [[Status Monitor]] or from the [[Status]] page | ||
+ | |||
+ | If you create a file called **CONNECT.NOW** in the VPOP3 installation directory, VPOP3 will immediately connect to the ' | ||
+ | |||
+ | If you create a file called **CONNECT.PAUSE** in the VPOP3 installation (in v6.1 and later), VPOP3 will not perform scheduled connections. This can be useful if you wish to start VPOP3 ' | ||
=====Schedules===== | =====Schedules===== | ||
Line 16: | Line 23: | ||
You can click in the **Enable** column to enable or disable an individual schedule. Each time you click here it toggles whether the schedule is enabled or not. | You can click in the **Enable** column to enable or disable an individual schedule. Each time you click here it toggles whether the schedule is enabled or not. | ||
+ | |||
+ | ====Caution with multiple connections===== | ||
+ | Note that if you have multiple connections configured, then each time the scheduler ' | ||
+ | |||
+ | This means that if you have the schedule connecting every 1 minute, and you have it set to use 10 connections, | ||
+ | - connection 1 | ||
+ | - connection 2 | ||
+ | - (schedule triggers, marking connection 1 and 2 to connect again) | ||
+ | - connection 1 | ||
+ | - connection 2 | ||
+ | - connection 3 | ||
+ | - (schedule triggers, marking connections 1 to 3 to connect again) | ||
+ | - etc | ||
+ | |||
+ | To prevent this happening, you should increase the time between the scheduled connections. | ||
=====Extra Settings===== | =====Extra Settings===== |