Still having problems with fetchmail after migrating to RT 4.05 and wanted to use the fetchmail option to get email sent to our helpdesk system instead of users logging into rt to create a ticket... This is the log from running this command
root@helpdesks:~# /etc/init.d/fetchmail debug-run /etc/init.d/fetchmail: Initiating debug run of system-wide fetchmail service... /etc/init.d/fetchmail: script will be run in debug mode, all output to forced to /etc/init.d/fetchmail: stdout. This is not enough to debug failures that only /etc/init.d/fetchmail: happen in daemon mode. /etc/init.d/fetchmail: You might want to direct output to a file, and tail -f it. /etc/init.d/fetchmail: Stopping the service... * Stopping mail retriever agent: [ OK ] /etc/init.d/fetchmail: exit status of service stop was: 0 /etc/init.d/fetchmail: RUNUSER is fetchmail /etc/init.d/fetchmail: OPTIONS would be -f /etc/fetchmailrc --pidfile /var/run/fetchmail/fetchmail.pid /etc/init.d/fetchmail: Starting service in nodetach mode, hit ^C (SIGINT/intr) to finish run... fetchmail: Old UID list from ticket.co.it: <empty> fetchmail: Scratch list of UIDs: <empty> fetchmail: starting fetchmail 6.3.21 daemon fetchmail: 6.3.21 querying ticket.co.it (protocol POP3) at Mon 25 Jun 2012 02:13:50 PM EDT: poll started fetchmail: Trying to connect to 128.8.222.167/110...connected. fetchmail: POP3< +OK zimbra.ticket.co.it Zimbra POP3 server ready fetchmail: POP3> CAPA fetchmail: POP3< +OK Capability list follows fetchmail: POP3< TOP fetchmail: POP3< USER fetchmail: POP3< UIDL fetchmail: POP3< STLS fetchmail: POP3< SASL PLAIN X-ZIMBRA fetchmail: POP3< EXPIRE 31 USER fetchmail: POP3< XOIP fetchmail: POP3< IMPLEMENTATION ZimbraInc fetchmail: POP3< . fetchmail: POP3> STLS fetchmail: POP3< +OK Begin TLS negotiation fetchmail: Certificate chain, from root to peer, starting at depth 3: fetchmail: Issuer Organization: GTE Corporation fetchmail: Issuer CommonName: GTE CyberTrust Global Root fetchmail: Subject CommonName: GTE CyberTrust Global Root fetchmail: Certificate at depth 2: fetchmail: Issuer Organization: GTE Corporation fetchmail: Issuer CommonName: GTE CyberTrust Global Root fetchmail: Subject CommonName: DigiCert High Assurance EV Root CA fetchmail: Certificate at depth 1: fetchmail: Issuer Organization: DigiCert Inc fetchmail: Issuer CommonName: DigiCert High Assurance EV Root CA fetchmail: Subject CommonName: DigiCert High Assurance CA-3 fetchmail: Server certificate: fetchmail: Issuer Organization: DigiCert Inc fetchmail: Issuer CommonName: DigiCert High Assurance CA-3 fetchmail: Subject CommonName: zimbra.ticket.co.it fetchmail: Subject Alternative Name: zimbra.ticket.co.it fetchmail: Server CommonName mismatch: zimbra.ticket.co.it != ticket.co.it fetchmail: ticket.co.it key fingerprint: 70:02:AF:9B:46:02:C1:12:F0:52:69:0D:EE:99:3A:EC fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!) fetchmail: POP3> CAPA fetchmail: POP3< +OK Capability list follows fetchmail: POP3< TOP fetchmail: POP3< USER fetchmail: POP3< UIDL fetchmail: POP3< STLS fetchmail: POP3< SASL PLAIN X-ZIMBRA fetchmail: POP3< EXPIRE 31 USER fetchmail: POP3< XOIP fetchmail: POP3< IMPLEMENTATION ZimbraInc fetchmail: POP3< . fetchmail: ticket.co.it: upgrade to TLS succeeded. fetchmail: POP3> USER helpdesk fetchmail: POP3< +OK hello helpdesk, please enter your password fetchmail: POP3> PASS * fetchmail: POP3< -ERR invalid username/password fetchmail: invalid username/password fetchmail: Authorization failure on helpd...@ticket.co.it fetchmail: For help, see http://www.fetchmail.info/fetchmail-FAQ.html#R15 fetchmail: POP3> QUIT fetchmail: POP3< +OK zimbra.ticket.co.it Zimbra POP3 server closing connection fetchmail: 6.3.21 querying ticket.co.it (protocol POP3) at Mon 25 Jun 2012 02:13:50 PM EDT: poll completed fetchmail: Merged UID list from ticket.co.it: <empty> fetchmail: Query status=3 (AUTHFAIL) fetchmail: sleeping at Mon 25 Jun 2012 02:13:50 PM EDT for 60 seconds Please help