Recently I've split the location of mutt and Zimbra, and found out there was a certificate problem during email delivery.
mutt is awaiting confirmation to accept or reject a certificate, and if it runs without interactivity, it automatically rejects the certificate. [this is my assumption of the behavior]
Here is an updated .muttrc:
set from="IP Address Information <ip-no-reply@xxx>" set folder="imaps://username:password@zimbra_or_postfix_server" set mask="!^\\.[^.]" set record="+IPInfo" set postponed="+Drafts" set spoolfile="+INBOX" set edit_headers=yes set certificate_file=.mutt-certs set ssl_starttls=yes set ssl_force_tls=yes set smtp_url = "smtp://username:password@zimbra_or_postfix_server:587"
I was looking for the solution to this problem, and found the answer here: http://www.seas.upenn.edu/cets/answers/mutt-certificates.html which explained that I have to add set certificate_file
directive to a file.
After letting mutt save the self-signed certificate, the script can once more deliver email to the MTA. But when I check to the mailbox of the account in use for the delivery, there is a folder named 'IPInfo' that follows the set record
directive. And therefore I assume that the solution to my original problem is to let mutt save the self-signed certificate.
I hope this helps anyone who is looking for the similar answer.