ok tryed some things with the mule imap:connector and its kinda cool… and its kinda crap… a few functions are really cool, but dont work as expected…
imap:connector
- checkFrequency: milliseconds to try getting new mails on the imap-server
- deleteReadMessage: deletes the message, after read
- backupEnabled / bachupFolder: backups the read mail to the folder… the folder is localy, not on the imap-server (partly crap)
- moveToFolder: moves the mail to the given folder after processing. if deleteReadMessage is true, the moved message is flagged deleted too (crap), if deleteReadMessage is false, the move is a copy (crap)
imap:inbound-endpoint
- user (is containing a @, use %40 instead)
- password
- host
- port
all in all it is a really powerful connector, which reads the mailbox frequently and can be used as perfect flow starter… additionally it returns an MimeMessage, with all the Headers and so on… but on the other hand, it cant handle the mails on the imap server… it looks like the handling on the server needs to be implemented with a POJO… if this is the way to go is a complete new question…