>From my research into this issue, the specific error messages listed in
this bug report are due to credential and/or certificate mismatches
between the server and client. It can indicate a misconfigured server,
but more commonly indicate a misbehaved mail client. Without seeing the
actual log files, and/or knowing the specific conditions that produced
them it's hard to figure out how to reproduce the exact failure.
However, I did work out how to configure couriertls and test logwatch's
handling of its error logs:
Install logwatch & couriertls
$ sudo apt-get install -y logwatch
$ sudo apt-get install -y courier-imap
• Create directories for web-based admin? No
• SSL cert generation required. Ok
• Courier MTA user:group changed to courier:courier. Ok
$ [optional] sudo apt-get install -y gamin
Setup postfix
$ sudo debconf-set-selections <<< "postfix postfix/mailname string <hostname>"
$ sudo debconf-set-selections <<< "postfix postfix/main_mailer_type string
'Local only'"
Setup courier
# In /etc/courier/imapd, set:
ADDRESS=127.0.0.1
#ADDRESS=0
$ sudo maildirmake /etc/skel/Maildir
$ sudo maildirmake /etc/skel/Maildir/.Drafts
$ sudo maildirmake /etc/skel/Maildir/.Sent
$ sudo maildirmake /etc/skel/Maildir/.Trash
$ sudo maildirmake /etc/skel/Maildir/.Templates
$ sudo cp -r /etc/skel/Maildir /home/${USER}/
$ sudo chown -R ${USER}:${USER} /home/${USER}/Maildir
$ sudo chmod -R 700 /home/${USER}/Maildir
$ sudo service courier-imap-authdaemon start
$ sudo service courier-imap start
$ sudo service courier-imap-ssl start
Verify installation is working
$ sudo service courier-imap status
[...]
Active: active (running) [...]
[...]
$ telnet localhost imap
...
* OK [CAPABILITY IMAP4rev1 ... ACL ACL2=UNION STARTTLS ENABLE UTF8=ACCEPT]
Courier-IMAP ready.[...]
01 login <USER> <PASSWORD>
01 OK LOGIN Ok.
02 select Inbox
* FLAGS (\Draft \Answered \Flagged \Deleted \Seen \Recent)
* OK [PERMANENTFLAGS (\* \Draft \Answered \Flagged \Deleted \Seen)] Limited
* 0 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 591130030] Ok
* OK [MYRIGHTS "acdilrsw"] ACL
02 OK [READ-WRITE] Ok
03 logout
* BYE Courier-IMAP server shutting down
03 OK LOGOUT completed
Send test email(s)
$ mail ${USER}@localhost
Cc:
Subject: Testing to localhost
test
^D
Run logwatch
+ sudo logwatch --detail Med --service imapd --service courier --range all
Like I mentioned above, I could not sort out how to get courier to emit the
exact error messages that the user reported. However, it's possible to inject
these into the mail log synthetically, and then check logwatch's behavior.
Download the 'fake_couriertls_entries.log' file attached to this bug report,
then:
$ sudo cat /tmp/fake_couriertls_entries.log >> /var/log/mail.log
$ sudo logwatch --detail High --service imapd --service courier --range "all"
This will show a number of **Unmatched Entries** shown in the imapd
section. Nothing gets shown in the courier section (except for some
authdaemond stuff, but think that's an orthogonal issue).
** Attachment added: "Example log file"
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1578004/+attachment/5380848/+files/fake_couriertls_entries.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578004
Title:
unmatched entries for courier
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1578004/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
