//mycomp

Options

Property	Default	Description
`host`		The host name or IP address to connect to.
`port`	See DefaultPorts	The TCP port number to connect on.
`username`		The user name on the e mail server.
`password`	`null`	The password on the email server.
`ignoreUriScheme`	`false`	If `false`, Camel uses the scheme to determine the transport protocol (POP, IMAP, SMTP etc.)
`defaultEncoding`	`null`	The default encoding to use for Mime Messages.
`contentType`	`text/plain`	The mail message content type. Use `text/html` for HTML mails.
`folderName`	`INBOX`	The folder to poll.
`destination`	`username@host`	@deprecated Use the `to` option instead. The `TO` recipients (receivers of the email).
`to`	`username@host`	The TO recipients (the receivers of the mail). Separate multiple email addresses with a comma.
`replyTo`	`alias@host`	As of Camel 2.8.4, 2.9.1+, the Reply-To recipients (the receivers of the response mail). Separate multiple email addresses with a comma.
`CC`	`null`	The CC recipients (the receivers of the mail). Separate multiple email addresses with a comma.
`BCC`	`null`	The BCC recipients (the receivers of the mail). Separate multiple email addresses with a comma.
`from`	`camel@localhost`	The FROM email address.
`subject`		As of Camel 2.3, the Subject of the message being sent. Note: Setting the subject in the header takes precedence over this option.
`delete`	`false`	Deletes the messages after they have been processed. This is done by setting the `DELETED` flag on the mail message. If `false`, the `SEEN` flag is set instead. As of Camel 2.10 you can override this configuration option by setting a h eader with the key `delete` to determine if the mail should be deleted or not.
`unseen`	`true`	It is possible to configure a consumer endpoint so that it processes only unseen messages (that is, new messages) or all messages. Note that Camel always skips deleted messages. The default option of `true` will filter to only unseen messages. POP3 does not support the `SEEN` flag, so this option is not supported in POP3; use IMAP instead.
`copyTo`	`null`	Camel 2.10: Consumer only. After processing a mail message, it can be copied to a mail folder with the given name. You can override this configuration value, with a header with the key `copyTo`, allowing you to copy messages to folder names configured at runtime.
`fetchSize`	`-1`	Sets the maximum number of messages to consume during a poll. This can be used to avoid overloading a mail server, if a mailbox folder contains a lot of messages. Default value of `-1` means no fetch size and all messages will be consumed. Setting the value to 0 is a special corner case, where Camel will not consume any messages at all.
`alternativeBodyHeader`	`CamelMailAlternativeBody`	Specifies the key to an IN message header that contains an alternative email body. For example, if you send emails in `text/html` format and want to provide an alternative mail body for non-HTML email clients, set the alternative mail body with this key as a header.
`debugMode`	`false`	Enable debug mode on the underlying mail framework. The SUN Mail framework logs the debug messages to `System.out` by default.
`connectionTimeout`	`30000`	The connection timeout in milliseconds. Default is 30 seconds.
`consumer.initialDelay`	`1000`	Milliseconds before the polling starts.
`consumer.delay`	`60000`	Camel will poll the mailbox only once a minute by default to avoid overloading the mail server.
`consumer.useFixedDelay`	`false`	Set to `true` to use a fixed delay between polls, otherwise fixed rate is used. See ScheduledExecutorService in JDK for details.
`disconnect`	`false`	Camel 2.8.3/2.9: Whether the consumer should disconnect after polling. If enabled this forces Camel to connect on each poll.
`mail.XXX`	`null`	Set any additional java mail properties. For instance if you want to set a special property when using POP3 you can now provide the option directly in the URI such as: `mail.pop3.forgettopheaders=true`. You can set multiple such options, for example: `mail.pop3.forgettopheaders=true&mail.mime.encodefilename=true`.
`mapMailMessage`	`true`	Camel 2.8: Specifies whether Camel should map the received mail message to Camel body/headers. If set to true, the body of the mail message is mapped to the body of the Camel IN message and the mail headers are mapped to IN headers. If this option is set to false then the IN message contains a raw `javax.mail.Message`. You can retrieve this raw message by calling `exchange.getIn().getBody(javax.mail.Message.class)`.
`maxMessagesPerPoll`	`0`	Specifies the maximum number of messages to gather per poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to avoid downloading thousands of files when the server starts up. Set a value of 0 or negative to disable this option.
`javaMailSender`	`null`	Specifies a pluggable `org.springframework.mail.javamail.JavaMailSender` instance in order to use a custom email implementation. If none provided, Camel uses the default `org.springframework.mail.javamail.JavaMailSenderImpl`.
`ignoreUnsupportedCharset`	`false`	Option to let Camel ignore unsupported charset in the local JVM when sending mails. If the charset is unsupported then `charset=XXX` (where `XXX` represents the unsupported charset) is removed from the `content-type< /tt> and it relies on the platform default instead.`
`sslContextParameters`	`null`	Camel 2.10: Reference to a `org.apache.camel.util.jsse.SSLContextParameters` in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility.
`searchTerm`	`null`	Camel 2.11: Refers to a `javax.mail.search.S earchTerm` which allows to filter mails based on search criteria such as subject, body, from, sent after a certain date etc. See further below for examples.
`searchTerm.xxx`	`null`	Camel 2.11: To configure search terms directly from the endpoint uri, which supports a limited number of terms defined by the `org.apache.camel.component.mail.SimpleSearchTerm` class. See further below for examples.

Property	Default	Description
`host`		The host name or IP address to connect to.
`port`	See DefaultPorts	The TCP port number to connect on.
`username`		The user name on the e mail server.
`password`	`null`	The password on the email server.
`ignoreUriScheme`	`false`	If `false`, Camel uses the scheme to determine the transport protocol (POP, IMAP, SMTP etc.)
`defaultEncoding`	`null`	The default encoding to use for Mime Messages.
`contentType`	`text/plain`	The mail message content type. Use `text/html` for HTML mails.
`folderName`	`INBOX`	The folder to poll.
`destination`	`username@host`	@deprecated Use the `to` option instead. The `TO` recipients (receivers of the email).
`to`	`username@host`	The TO recipients (the receivers of the mail). Separate multiple email addresses with a comma.
`replyTo`	`alias@host`	As of Camel 2.8.4, 2.9.1+, the Reply-To recipients (the receivers of the response mail). Separate multiple email addresses with a comma.
`CC`	`null`	The CC recipients (the receivers of the mail). Separate multiple email addresses with a comma.
`BCC`	`null`	The BCC recipients (the receivers of the mail). Separate multiple email addresses with a comma.
`from`	`camel@localhost`	The FROM email address.
`subject`		As of Camel 2.3, the Subject of the message being sent. Note: Setting the subject in the header takes precedence over this option.
`delete`	`false`	Deletes the messages after they have been processed. This is done by setting the `DELETED` flag on the mail message. If `false`, the `SEEN` flag is set instead. As of Camel 2.10 you can override this configuration option by setting a h eader with the key `delete` to determine if the mail should be deleted or not.
`unseen`	`true`	It is possible to configure a consumer endpoint so that it processes only unseen messages (that is, new messages) or all messages. Note that Camel always skips deleted messages. The default option of `true` will filter to only unseen messages. POP3 does not support the `SEEN` flag, so this option is not supported in POP3; use IMAP instead.
`copyTo`	`null`	Camel 2.10: Consumer only. After processing a mail message, it can be copied to a mail folder with the given name. You can override this configuration value, with a header with the key `copyTo`, allowing you to copy messages to folder names configured at runtime.
`fetchSize`	`-1`	Sets the maximum number of messages to consume during a poll. This can be used to avoid overloading a mail server, if a mailbox folder contains a lot of messages. Default value of `-1` means no fetch size and all messages will be consumed. Setting the value to 0 is a special corner case, where Camel will not consume any messages at all.
`alternativeBodyHeader`	`CamelMailAlternativeBody`	Specifies the key to an IN message header that contains an alternative email body. For example, if you send emails in `text/html` format and want to provide an alternative mail body for non-HTML email clients, set the alternative mail body with this key as a header.
`debugMode`	`false`	Enable debug mode on the underlying mail framework. The SUN Mail framework logs the debug messages to `System.out` by default.
`connectionTimeout`	`30000`	The connection timeout in milliseconds. Default is 30 seconds.
`consumer.initialDelay`	`1000`	Milliseconds before the polling starts.
`consumer.delay`	`60000`	Camel will poll the mailbox only once a minute by default to avoid overloading the mail server.
`consumer.useFixedDelay`	`false`	Set to `true` to use a fixed delay between polls, otherwise fixed rate is used. See ScheduledExecutorService in JDK for details.
`disconnect`	`false`	Camel 2.8.3/2.9: Whether the consumer should disconnect after polling. If enabled this forces Camel to connect on each poll.
`closeFolder`	`true`	Camel 2.10.4: Whether the consumer should close the folder after polling. Setting this option to `false` and having `disconnect=false` as well, then the consumer keep the folder open between polls.
`mail.XXX`	`null`	Set any additional java mail properties. For instance if you want to set a special property when using POP3 you can now provide the option directly in the URI such as: `mail.pop3.forgettopheaders=true`. You can set multiple such options, for example: `mail.pop3.forgettopheaders=true&mail.mime.encodefilename=true`.
`mapMailMessage`	`true`	Camel 2.8: Specifies whether Camel should map the received mail message to Camel body/headers. If set to true, the body of the mail message is mapped to the body of the Camel IN message and the mail headers are mapped to IN headers. If this option is set to false then the IN message contains a raw `javax.mail.Message`. You can retrieve this raw message by calling `exchange.getI n().getBody(javax.mail.Message.class)`.
`maxMessagesPerPoll`	`0`	Specifies the maximum number of messages to gather per poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to avoid downloading thousands of files when the server starts up. Set a value of 0 or negative to disable this option.
`javaMailSender`	`null`	Specifies a pluggable `org.springframework.mail.javamail.JavaMailSender` instance in order to use a custom email implementation. If none provided, Camel uses the default `org.springframework.mail.javamail.JavaMailSenderImpl`.
`ignoreUnsupportedCharset`	`false`	Option to let Camel ignore unsupported charset in the local JVM when sending mails. If the charset is unsupported then `charset=XXX` (where `XXX` represents the unsupported charset) is removed from the `content-type` and it relies on the platform default instead.
`sslContextParameters`	`null`	Camel 2.10: Reference to a `org.apache.camel.util.jsse.SSLContextParameters` in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility.
`searchTerm`	`null`	Camel 2.11: Refers to a `javax.mail.search.SearchTerm` which allows to filter mails based on search criteria such as subject, body, from, sent after a certain date etc. See further below for examples.
`searchTerm.xxx`	`null`	Camel 2.11: To configure search terms directly from the endpoint uri, which supports a limited number of terms defined by the `org.apache.camel.component.mail.SimpleSearchTerm class. See further below for examples.`

Modified: websites/production/camel/content/book-in-one-page.html ============================================================================== --- websites/production/camel/content/book-in-one-page.html (original) +++ websites/production/camel/content/book-in-one-page.html Sun Feb 3 10:25:41 2013 @@ -31135,7 +31135,7 @@ smtp://mycomp

Options

-< td colspan="1" rowspan="1" class="confluenceTd"> replyTo

Property	Default	Description
`host`		The host name or IP address to connect to.
`port`	See DefaultPorts	The TCP port number to connect on.
`username`		The user name on the email ser ver.
`password`	`null`	The password on the email server.
`ignoreUriScheme`	`false`	If `false`, Camel uses the scheme to determine the transport protocol (POP, IMAP, SMTP etc.)
`defaultEncoding`	`null`	The default encoding to use for Mime Messages.
`contentType`	`text/plain`	The mail message content type. Use `text/html` for HTML mails.
`folderName`	`INBOX`	The folder to poll.
`destination`	`username@host`	@deprecated Use the `to` option instead. The `TO` recipients (receivers of the email).
`to`	`username@host`	The TO recipients (the receivers of the mail). Separate multiple email addresses with a comma.
`alias@host`	As of Camel 2.8.4, 2.9.1+, the Reply-To recipients (the receivers of the response mail). Separate multiple email addresses with a comma.
`CC`	`null`	The CC recipients (the receivers of the mail). Separate multiple email addresses with a comma.
`BCC`	`null`	The BCC recipients (the receivers of the mail). Separate multiple email addresses with a comma.
`from`	`camel@localhost`	The FROM email address.
`subject`		As of Camel 2.3, the Subject of the message being sent. Note: Setting the subject in the header takes precedence over this option.
`delete`	`false`	Deletes the messages after they have been processed. This is done by setting the `DELETED` flag on the mail message. If `false`, the `SEEN` flag is set instead. As of Camel 2.10 you can override this configuration option by setting a header wi th the key `delete` to determine if the mail should be deleted or not.
`unseen`	`true`	It is possible to configure a consumer endpoint so that it processes only unseen messages (that is, new messages) or all messages. Note that Camel always skips deleted messages. The default option of `true` will filter to only unseen messages. POP3 does not support the `SEEN` flag, so this option is not supported in POP3; use IMAP instead.
`copyTo`	`null`	Camel 2.10: Consumer only. After processing a mail message, it can be copied to a mail folder with the given name. You can override this co nfiguration value, with a header with the key `copyTo`, allowing you to copy messages to folder names configured at runtime.
`fetchSize`	`-1`	Sets the maximum number of messages to consume during a poll. This can be used to avoid overloading a mail server, if a mailbox folder contains a lot of messages. Default value of `-1` means no fetch size and all messages will be consumed. Setting the value to 0 is a special corner case, where Camel will not consume any messages at all.
`alternativeBodyHeader`	`CamelMailAlternativeBody`	Specifies the key to an IN message header that contains an alternat ive email body. For example, if you send emails in `text/html` format and want to provide an alternative mail body for non-HTML email clients, set the alternative mail body with this key as a header.
`debugMode`	`false`	Enable debug mode on the underlying mail framework. The SUN Mail framework logs the debug messages to `System.out` by default.
`connectionTimeout`	`30000`	The connection timeout in milliseconds. Default is 30 seconds.
`consumer.initialDelay`	`1000`	Milliseconds before the polling starts.
`consumer.delay`	`60000`	Camel will poll the mailbox only once a minute by default to avoid overloading the mail server.
`consumer.useFixedDelay`	`false`	Set to `true` to use a fixed delay between polls, otherwise fixed rate is used. See ScheduledExecutorService in JDK for details.
`di sconnect`	`false`	Camel 2.8.3/2.9: Whether the consumer should disconnect after polling. If enabled this forces Camel to connect on each poll.
`mail.XXX`	`null`	Set any additional java mail properties. For instance if you want to set a special property when using POP3 you can now provide the option directly in the URI such as: `mail.pop3.forgettopheaders=true`. You can set multiple such options, for example: `mail.pop3.forgettopheaders=true&mail.mime.encodefilename=true`.
`mapMailMessage`	`true`	Camel 2.8: Specifies whether Camel should map the received mail message to Camel body/headers. If set to true, the body of the mail message is mapped to the body of the Camel IN message and the mail headers are mapped to IN headers. If this option is set to false then the IN message contains a raw `javax.mail.Message`. You can retrieve this raw message by calling `exchange.getIn().getBody(javax.mail.Message.class)`.
`maxMessagesPerPoll`	`0`	Specifies the maximum number of messages to gather per poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to avoid downloading thousands of files when th e server starts up. Set a value of 0 or negative to disable this option.
`javaMailSender`	`null`	Specifies a pluggable `org.springframework.mail.javamail.JavaMailSender` instance in order to use a custom email implementation. If none provided, Camel uses the default `org.springframework.mail.javamail.JavaMailSenderImpl`.
`ignoreUnsupportedCharset`	`false`	Option to let Camel ignore unsupported charset in the local JVM when sending mails. If the charset is unsupported then `charset=XXX` (where `XXX` represents the unsupported charset) is removed from the `content-type` and it relies on the platform default instead.
`sslContextParameters`	`null`	Camel 2.10: Reference to a `org.apache.camel.util.jsse.SSLContextParameters` in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility.
`searchTerm`	`null`	Camel 2.11: Refers to a `javax.mail.search.SearchTer m` which allows to filter mails based on search criteria such as subject, body, from, sent after a certain date etc. See further below for examples.
`searchTerm.xxx`	`null`	Camel 2.11: To configure search terms directly from the endpoint uri, which supports a limited number of terms defined by the `org.apache.camel.component.mail.SimpleSearchTerm` class. See further below for examples.

+< td colspan="1" rowspan="1" class="confluenceTd"> replyTo

Property	Default	Description
`host`		The host name or IP address to connect to.
`port`	See DefaultPorts	The TCP port number to connect on.
`username`		The user name on the email ser ver.
`password`	`null`	The password on the email server.
`ignoreUriScheme`	`false`	If `false`, Camel uses the scheme to determine the transport protocol (POP, IMAP, SMTP etc.)
`defaultEncoding`	`null`	The default encoding to use for Mime Messages.
`contentType`	`text/plain`	The mail message content type. Use `text/html` for HTML mails.
`folderName`	`INBOX`	The folder to poll.
`destination`	`username@host`	@deprecated Use the `to` option instead. The `TO` recipients (receivers of the email).
`to`	`username@host`	The TO recipients (the receivers of the mail). Separate multiple email addresses with a comma.
`alias@host`	As of Camel 2.8.4, 2.9.1+, the Reply-To recipients (the receivers of the response mail). Separate multiple email addresses with a comma.
`CC`	`null`	The CC recipients (the receivers of the mail). Separate multiple email addresses with a comma.
`BCC`	`null`	The BCC recipients (the receivers of the mail). Separate multiple email addresses with a comma.
`from`	`camel@localhost`	The FROM email address.
`subject`		As of Camel 2.3, the Subject of the message being sent. Note: Setting the subject in the header takes precedence over this option.
`delete`	`false`	Deletes the messages after they have been processed. This is done by setting the `DELETED` flag on the mail message. If `false`, the `SEEN` flag is set instead. As of Camel 2.10 you can override this configuration option by setting a header wi th the key `delete` to determine if the mail should be deleted or not.
`unseen`	`true`	It is possible to configure a consumer endpoint so that it processes only unseen messages (that is, new messages) or all messages. Note that Camel always skips deleted messages. The default option of `true` will filter to only unseen messages. POP3 does not support the `SEEN` flag, so this option is not supported in POP3; use IMAP instead.
`copyTo`	`null`	Camel 2.10: Consumer only. After processing a mail message, it can be copied to a mail folder with the given name. You can override this co nfiguration value, with a header with the key `copyTo`, allowing you to copy messages to folder names configured at runtime.
`fetchSize`	`-1`	Sets the maximum number of messages to consume during a poll. This can be used to avoid overloading a mail server, if a mailbox folder contains a lot of messages. Default value of `-1` means no fetch size and all messages will be consumed. Setting the value to 0 is a special corner case, where Camel will not consume any messages at all.
`alternativeBodyHeader`	`CamelMailAlternativeBody`	Specifies the key to an IN message header that contains an alternat ive email body. For example, if you send emails in `text/html` format and want to provide an alternative mail body for non-HTML email clients, set the alternative mail body with this key as a header.
`debugMode`	`false`	Enable debug mode on the underlying mail framework. The SUN Mail framework logs the debug messages to `System.out` by default.
`connectionTimeout`	`30000`	The connection timeout in milliseconds. Default is 30 seconds.
`consumer.initialDelay`	`1000`	Milliseconds before the polling starts.
`consumer.delay`	`60000`	Camel will poll the mailbox only once a minute by default to avoid overloading the mail server.
`consumer.useFixedDelay`	`false`	Set to `true` to use a fixed delay between polls, otherwise fixed rate is used. See ScheduledExecutorService in JDK for details.
`di sconnect`	`false`	Camel 2.8.3/2.9: Whether the consumer should disconnect after polling. If enabled this forces Camel to connect on each poll.
`closeFolder`	`true`	Camel 2.10.4: Whether the consumer should close the folder after polling. Setting this option to `false` and having `disconnect=false` as well, then the consumer keep the folder open between polls.
`mail.XXX`	`null`	Set any additional java mail properties. For instance if you want to set a special property when using POP3 you can now provide the option directly in the URI such as: `mail.pop3.forgettopheaders=true`. You can set multiple such options, for example: `mail.pop3.forgettopheaders=true&mail.mime.encodefilename=true`.
`mapMailMessage`	`true`	Camel 2.8: Specifies whether Camel should map the received mail message to Camel body/headers. If set to true, the body of the mail message is mapped to the body of the Camel IN message and the mail headers are mapped to IN headers. If this option is set to false then the IN message contains a raw `javax.mail.Message`. You can retrieve this raw message by calling `exchange.getIn().getB ody(javax.mail.Message.class)`.
`maxMessagesPerPoll`	`0`	Specifies the maximum number of messages to gather per poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to avoid downloading thousands of files when the server starts up. Set a value of 0 or negative to disable this option.
`javaMailSender`	`null`	Specifies a pluggable `org.springframework.mail.javamail.JavaMailSender` instance in order to use a custom email implementation. If none provided, Camel uses the default `org.springframework.mail.javamail.JavaMailSenderImpl`.
`ignoreUnsupportedCharset`	`false`	Option to let Camel ignore unsupported charset in the local JVM when sending mails. If the charset is unsupported then `charset=XXX` (where `XXX` represents the unsupported charset) is removed from the `content-type` and it relies on the platform default instead.
`sslContextParameters`	`null`	Camel 2.10: Reference to a `org.apache.camel.util.jsse.SSLContextParameters` in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility.
`searchTerm`	`null`	Camel 2.11: Refers to a `javax.mail.search.SearchTerm` which allows to filter mails based on search criteria such as subject, body, from, sent after a certain date etc. See further below for examples.
`searchTerm.xxx`	`null`	Camel 2.11: To configure search terms directly from the endpoint uri, which supports a limited number of terms defined by the `org.apache.camel.component.mail.SimpleSearchTerm` class . See further below for examples.

Modified: websites/production/camel/content/cache/main.pageCache ============================================================================== Binary files - no diff available. Modified: websites/production/camel/content/mail.html ============================================================================== --- websites/production/camel/content/mail.html (original) +++ websites/production/camel/content/mail.html Sun Feb 3 10:25:41 2013 @@ -158,7 +158,7 @@ smtp://mycomp

Options

-< td colspan="1" rowspan="1" class="confluenceTd"> Milliseconds before the polling starts.

Property	Default	Description
`host`		The host name or IP address to connect to.
`port`	See DefaultPorts	The TCP port number to connect on.
`username`		The user name on the email server.
`password`	`null`	The password on the email server.
`ignoreUriScheme`	`false`	If `false`, Camel uses the scheme to determine the transport protocol (POP, IMAP, SMTP etc.)
`defaultEncoding`	`null`	The default encoding to use for Mime Messages.
`contentType`	`text/plain`	The mail message content type. Use `text/html` for HTML mails.
`folderName`	`INBOX`	The folder to poll.
`destination`	`username@host`	@deprecated Use the `to` option instead. The `TO` recipients (receivers of the email).
`to`	`username@host`	The TO recipients (the receivers of the mail). Separate multiple email addresses with a comma.
`replyTo`	`alias@host`	As of Camel 2.8.4, 2.9.1+, the Reply-To recipients (the receivers of the response mail). Separate multiple email addresses with a comma.
`CC`	`null`	The CC recipients (the receivers of the mail). Separate multiple email addresses with a comma.
`BCC`	`null`	The BCC recipients (the receivers of the mail). Separate multiple email addresses with a comma.
`from`	`camel@localhost`	The FROM email address.
`subject`		As of Camel 2.3, the Subject of the message being sent. Note: Setting the subject in the header takes precedence over this option.
`delete`	`false`	Deletes the messages after they have been processed. This is done by setting the `DELETED` flag on the mail message. If `false`, the `SEEN` flag is set instead. As of Camel 2.10 you can override this configuration option by setting a header with the ke y `delete` to determine if the mail should be deleted or not.
`unseen`	`true`	It is possible to configure a consumer endpoint so that it processes only unseen messages (that is, new messages) or all messages. Note that Camel always skips deleted messages. The default option of `true` will filter to only unseen messages. POP3 does not support the `SEEN` flag, so this option is not supported in POP3; use IMAP instead.
`copyTo`	`null`	Camel 2.10: Consumer only. After processing a mail message, it can be copied to a mail folder with the given name. You can override this configurati on value, with a header with the key `copyTo`, allowing you to copy messages to folder names configured at runtime.
`fetchSize`	`-1`	Sets the maximum number of messages to consume during a poll. This can be used to avoid overloading a mail server, if a mailbox folder contains a lot of messages. Default value of `-1` means no fetch size and all messages will be consumed. Setting the value to 0 is a special corner case, where Camel will not consume any messages at all.
`alternativeBodyHeader`	`CamelMailAlternativeBody`	Specifies the key to an IN message header that contains an alternative email body. For example, if you send emails in `text/html` format and want to provide an alternative mail body for non-HTML email clients, set the alternative mail body with this key as a header.
`debugMode`	`false`	Enable debug mode on the underlying mail framework. The SUN Mail framework logs the debug messages to `System.out` by default.
`connectionTimeout`	`30000`	The connection timeout in milliseconds. Default is 30 seconds.
`consumer.initialDelay`	`1000`
`consumer.delay`	`60000`	Camel will poll the mailbox only once a minute by default to avoid overloading the mail server.
`consumer.useFixedDelay`	`false`	Set to `true` to use a fixed delay between polls, otherwise fixed rate is used. See ScheduledExecutorService in JDK for details.
`disconnect< /tt>`	`false`	Camel 2.8.3/2.9: Whether the consumer should disconnect after polling. If enabled this forces Camel to connect on each poll.
`mail.XXX`	`null`	Set any additional java mail properties. For instance if you want to set a special property when using POP3 you can now provide the option directly in the URI such as: `mail.pop3.forgettopheaders=true`. You can set multiple such options, for example: `mail.pop3.forgettopheaders=true&mail.mime.encodefilename=true`.
< tt>mapMailMessage	`true`	Camel 2.8: Specifies whether Camel should map the received mail message to Camel body/headers. If set to true, the body of the mail message is mapped to the body of the Camel IN message and the mail headers are mapped to IN headers. If this option is set to false then the IN message contains a raw `javax.mail.Message`. You can retrieve this raw message by calling `exchange.getIn().getBody(javax.mail.Message.class)`.
`maxMessagesPerPoll`	`0`	Specifies the maximum number of messages to gather per poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to avoid downloading thousands of files when the server starts up. Set a value of 0 or negative to disable this option.
`javaMailSender`	`null`	Specifies a pluggable `org.springframework.mail.javamail.JavaMailSender` instance in order to use a custom email implementation. If none provided, Camel uses the default `org.springframework.mail.javamail.JavaMailSenderImpl`.
`ignoreUnsupportedCharset`	`false`	Option to let Camel ignore unsupported charset in the local JVM when sending mails. If the charset is unsupported then `charset=XXX` (where `XXX` represents the unsupported charset) is removed from the `content-type` and it relie s on the platform default instead.
`sslContextParameters`	`null`	Camel 2.10: Reference to a `org.apache.camel.util.jsse.SSLContextParameters` in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility.
`searchTerm`	`null`	Camel 2.11: Refers to a `javax.mail.search.SearchTerm` wh ich allows to filter mails based on search criteria such as subject, body, from, sent after a certain date etc. See further below for examples.
`searchTerm.xxx`	`null`	Camel 2.11: To configure search terms directly from the endpoint uri, which supports a limited number of terms defined by the `org.apache.camel.component.mail.SimpleSearchTerm` class. See further below for examples.

+< td colspan="1" rowspan="1" class="confluenceTd"> Milliseconds before the polling starts.

Property	Default	Description
`host`		The host name or IP address to connect to.
`port`	See DefaultPorts	The TCP port number to connect on.
`username`		The user name on the email server.
`password`	`null`	The password on the email server.
`ignoreUriScheme`	`false`	If `false`, Camel uses the scheme to determine the transport protocol (POP, IMAP, SMTP etc.)
`defaultEncoding`	`null`	The default encoding to use for Mime Messages.
`contentType`	`text/plain`	The mail message content type. Use `text/html` for HTML mails.
`folderName`	`INBOX`	The folder to poll.
`destination`	`username@host`	@deprecated Use the `to` option instead. The `TO` recipients (receivers of the email).
`to`	`username@host`	The TO recipients (the receivers of the mail). Separate multiple email addresses with a comma.
`replyTo`	`alias@host`	As of Camel 2.8.4, 2.9.1+, the Reply-To recipients (the receivers of the response mail). Separate multiple email addresses with a comma.
`CC`	`null`	The CC recipients (the receivers of the mail). Separate multiple email addresses with a comma.
`BCC`	`null`	The BCC recipients (the receivers of the mail). Separate multiple email addresses with a comma.
`from`	`camel@localhost`	The FROM email address.
`subject`		As of Camel 2.3, the Subject of the message being sent. Note: Setting the subject in the header takes precedence over this option.
`delete`	`false`	Deletes the messages after they have been processed. This is done by setting the `DELETED` flag on the mail message. If `false`, the `SEEN` flag is set instead. As of Camel 2.10 you can override this configuration option by setting a header with the ke y `delete` to determine if the mail should be deleted or not.
`unseen`	`true`	It is possible to configure a consumer endpoint so that it processes only unseen messages (that is, new messages) or all messages. Note that Camel always skips deleted messages. The default option of `true` will filter to only unseen messages. POP3 does not support the `SEEN` flag, so this option is not supported in POP3; use IMAP instead.
`copyTo`	`null`	Camel 2.10: Consumer only. After processing a mail message, it can be copied to a mail folder with the given name. You can override this configurati on value, with a header with the key `copyTo`, allowing you to copy messages to folder names configured at runtime.
`fetchSize`	`-1`	Sets the maximum number of messages to consume during a poll. This can be used to avoid overloading a mail server, if a mailbox folder contains a lot of messages. Default value of `-1` means no fetch size and all messages will be consumed. Setting the value to 0 is a special corner case, where Camel will not consume any messages at all.
`alternativeBodyHeader`	`CamelMailAlternativeBody`	Specifies the key to an IN message header that contains an alternative email body. For example, if you send emails in `text/html` format and want to provide an alternative mail body for non-HTML email clients, set the alternative mail body with this key as a header.
`debugMode`	`false`	Enable debug mode on the underlying mail framework. The SUN Mail framework logs the debug messages to `System.out` by default.
`connectionTimeout`	`30000`	The connection timeout in milliseconds. Default is 30 seconds.
`consumer.initialDelay`	`1000`
`consumer.delay`	`60000`	Camel will poll the mailbox only once a minute by default to avoid overloading the mail server.
`consumer.useFixedDelay`	`false`	Set to `true` to use a fixed delay between polls, otherwise fixed rate is used. See ScheduledExecutorService in JDK for details.
`disconnect< /tt>`	`false`	Camel 2.8.3/2.9: Whether the consumer should disconnect after polling. If enabled this forces Camel to connect on each poll.
`closeFolder`	`true`	Camel 2.10.4: Whether the consumer should close the folder after polling. Setting this option to `false` and having `disconnect=false` as well, then the consumer keep the folder open between polls.
`mail.XXX`	`null`	Set any additional java mail properties. For instance if you want to set a special property when using POP3 you can now provide the option directly in the URI such as: `mail.pop3.forgettopheaders=true`. You can set multiple such options, for example: `mail.pop3.forgettopheaders=true&mail.mime.encodefilename=true`.
`mapMailMessage`	`true`	Camel 2.8: Specifies whether Camel should map the received mail message to Camel body/headers. If set to true, the body of the mail message is mapped to the body of the Camel IN message and the mail headers are mapped to IN headers. If this option is set to false then the IN message contains a raw `javax.mail.Message`. You can retrieve this raw message by calling `exchange.getIn().getBody(javax .mail.Message.class)`.
`maxMessagesPerPoll`	`0`	Specifies the maximum number of messages to gather per poll. By default, no maximum is set. Can be used to set a limit of e.g. 1000 to avoid downloading thousands of files when the server starts up. Set a value of 0 or negative to disable this option.
`javaMailSender`	`null`	Specifies a pluggable `org.springframework.mail.javamail.JavaMailSender` instance in order to use a custom email implementation. If none provided, Camel uses the default `org.springframework.mail.javamail.JavaMailSenderImpl`.
`ignoreUnsupportedCharset`	`false`	Option to let Camel ignore unsupported charset in the local JVM when sending mails. If the charset is unsupported then `charset=XXX` (where `XXX` represents the unsupported charset) is removed from the `content-type` and it relies on the platform default instead.
`sslContextParameters`	`null`	Camel 2.10: Reference to a `org.apache.camel.util.jsse.SSLContextParameters` in the Registry. This reference overrides any configured SSLContextParameters at the component level. See Using the JSSE Configuration Utility.
`searchTerm`	`null`	Camel 2.11: Refers to a `javax.mail.search.SearchTerm` which allows to filter mails based on search criteria such as subject, body, from, sent after a certain date etc. See further below for examples.
`searchTerm.xxx`	`null`	Camel 2.11: To configure search terms directly from the endpoint uri, which supports a limited number of terms defined by the `org.apache.camel.component.mail.SimpleSearchTerm` class. See fur ther below for examples.