2. IMAP Connector
■ The IMAP Connector, which is configurable only as an inbound endpoint (also known
as a message source) with a one-way exchange pattern, implements a transport
channel that enables your Mule application to retrieve email from an IMAP email
server.
■ IMAP is similar to POP3, except IMAP supports both online and offline modes. For
instance, IMAP users can leave email messages on the IMAP server until they explicitly
delete them. Like POP3, IMAP cannot send email; for that, you must implement an
SMTP outbound endpoint.
3. Configuration
■ IMAP endpoint configuration consists of two stages:
■ Place your IMAP endpoint at the head of the sequence of building blocks that make up
your Mule flow. Since it must serve as the message source for your flow, it cannot
occupy any other position. (You can also use the Composite Sourcescope to wrap the
IMAP endpoint along with the POP3 endpoint so that your flow can receive email
through multiple transport channels).
■ Configure the IMAP endpoint by providing values for the fields on the various tabs on
the properties editor, which you open by double-clicking the IMAP endpoint icon on
the Message Flow canvas.