Can we configure our instance/POP Reader to NOT delete email from the server after its been retrieved/downloaded/pulled? SummaryThe email reader on the instance adheres to pop3 or IMAP protocols. The reader reads 20 emails (by default or a different number as defined in the system property com.glide.email.max_read) at a cycle. Once those emails are read into the instance it sends a delete command to the email server to delete those read emails from the email server, then the next 20 are read and deletes are sent for those and so on until all of the emails are processed. Even though there is a property for the Email Reader job (fdLeaveMessages=false|true) that will keep messages in the mailbox, this is not something that should be modified. Even though this property will keep messages in the mailbox, the next time the job executes, it will grab the same records, and process them again. The reader job will pick up 20 emails, so if you keep this emails around, only 20 records will ever be processed, and it will always be the same 20 records. The suggestion is to have emails copied into another location, and configure the reader to pickup from one account, and use the other for your archive/auditing. The email admin team should be able to create a rule to make the copies of your email for archival.