[
https://issues.apache.org/jira/browse/JAMES-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521948
]
Stefano Bagnara commented on JAMES-809:
---------------------------------------
Then you have to add a wait in your mailet initialization.
Adding a wait to fetchmail is not a solution. Fetchmail is in no way related to
the SpoolManager. They both work with the Spool. And the mailet could be called
for any mail being in the spool. If you stop the server while mail are in the
spool and not yet processed they will be processed at the next startup without
the need for the fetchmail to be running.
I simply see no point in adding a delay to the fetchmail service: your problem
is that a specific mailet does not work until a given service is started, so
the correct solution is to add synchronization between the mailet and the
service, or simply add a delay in the mailet initialization. Changing the
behaviour for fetchmail is not correct and will not fix your issue in all the
cases.
> Add initialDelay parameter
> --------------------------
>
> Key: JAMES-809
> URL: https://issues.apache.org/jira/browse/JAMES-809
> Project: James
> Issue Type: New Feature
> Components: FetchMail
> Affects Versions: 2.3.1
> Reporter: David Dossot
> Priority: Minor
>
> It would be useful to have an "initialDelay" parameter that would define the
> time before Fetchmail starts fetching mails.
> Reason: I have a Mailet that takes 15 seconds to initialize and this
> initialization is done by a background thread. I would like to start fetching
> only after a certain delay.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
