[rt-users] Issue with Fetchmail

Borngunners borngunners at aol.com
Tue Jun 26 12:06:57 EDT 2012 

So, I change the username to helpdesk at ticket.co.it and I got these after running the same debug command. Looks like something is happening. The only issue is, I am not sure whether it is working like it is suppose to because it keeps appending zimbra.ticket.co.it at the end of the username... Please see below:

root at 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...
 * Pidfile not found! Is fetchmail running?
/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 zimbra.ticket.co.it: <empty>
fetchmail: Scratch list of UIDs: <empty>
fetchmail: starting fetchmail 6.3.21 daemon
fetchmail: 6.3.21 querying zimbra.ticket.co.it (protocol POP3) at Tue 26 Jun 2012 10:22:25 AM EDT: poll started
fetchmail: Trying to connect to 192.168.222.30/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: zimbra.ticket.co.it key fingerprint: 70:02:AF:9B:46:02:C1:12:F0:52:69:0D:EE:99:3A:EC
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: zimbra.ticket.co.it: upgrade to TLS succeeded.
fetchmail: POP3> USER helpdesk at ticket.co.it
fetchmail: POP3< +OK hello helpdesk at ticket.co.it, please enter your password
fetchmail: POP3> PASS *
fetchmail: POP3< +OK server ready
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 8 328373
fetchmail: POP3> LAST
fetchmail: POP3< -ERR unknown command
fetchmail: unknown command
fetchmail: POP3> UIDL
fetchmail: POP3< +OK 8 messages
fetchmail: POP3< 1 17720.IRidbzHeI6bzOWLayy2p7HWtDHM=
fetchmail: 1 is unseen
fetchmail: POP3< 2 17723.SHuBiaCWYg,0,9nWQnSrbPaE21M=
fetchmail: 2 is unseen
fetchmail: POP3< 3 17760.RrBL,aEkKUF38ObqE5RyxA8Fj3I=
fetchmail: 3 is unseen
fetchmail: POP3< 4 17780.xSV1x6jv0HRhe4TB7Cn29caKUEk=
fetchmail: 4 is unseen
fetchmail: POP3< 5 17800.zfe5R,i4,UY+UlWCiKW9BizFC7Q=
fetchmail: 5 is unseen
fetchmail: POP3< 6 17801.pv7zeMc0OwOMn1H9sMm2,2WHBoY=
fetchmail: 6 is unseen
fetchmail: POP3< 7 17803.WXLHYsVB4uK9qAHGychge,2EKmc=
fetchmail: 7 is unseen
fetchmail: POP3< 8 17820.l9qMWjsYiHOL+BMlCLMvhtcl6rY=
fetchmail: 8 is unseen
fetchmail: POP3< .
fetchmail: 8 messages for helpdesk at ticket.co.it at zimbra.ticket.co.it (328373 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 4492
fetchmail: POP3> TOP 1 99999999
fetchmail: POP3< +OK message top follows
fetchmail: reading message helpdesk at ticket.co.it@zimbra.ticket.co.it:1 of 8 (4492 octets) About to rewrite Return-Path: jane at ticket.co.it...
...rewritten version is Return-Path: jane at ticket.co.it.
fetchmail: About to rewrite From: Jane jane <jane at ticket.co.it>...
...rewritten version is From: Jane jane <jane at ticket.co.it>.
fetchmail: About to rewrite To: Help Desk <helpdesk at ticket.co.it>, ...
...rewritten version is To: Help Desk <helpdesk at ticket.co.it>, .
fetchmail: About to rewrite Cc: Lope Phatter <lphatter at ticket.co.it>, ...
...rewritten version is Cc: Lope Phatter <lphatter at ticket.co.it>, .
fetchmail: about to deliver with: /opt/rt4/bin/mailgate --queue general --action correspond --url http://helpdesks.ticket.co.it/
#*************************************.***************.***********sh: 1: /opt/rt4/bin/mailgate: not found
fetchmail: MDA returned nonzero status 127
fetchmail:  not flushed
fetchmail: POP3> LIST 3
fetchmail: POP3< +OK 3 85746
fetchmail: POP3> TOP 3 99999999
fetchmail: POP3< +OK message top follows
fetchmail: reading message helpdesk at ticket.co.it@zimbra.ticket.co.it:3 of 8 (85746 octets) About to rewrite Return-Path: young at ticket.co.it...
...rewritten version is Return-Path: young at ticket.co.it.
fetchmail: About to rewrite From: Moses young <young at ticket.co.it>...
...rewritten version is From: Moses young <young at ticket.co.it>.
fetchmail: About to rewrite Reply-To: Moses young <young at ticket.co.it>...
...rewritten version is Reply-To: Moses young <young at ticket.co.it>.
fetchmail: About to rewrite To: helpdesk at ticket.co.it...
...rewritten version is To: helpdesk at ticket.co.it.
fetchmail: about to deliver with: /opt/rt4/bin/mailgate --queue general --action correspond --url http://helpdesks.ticket.co.it/
#******************************************************.***********************.*************.**************.**************.*************.******************.*************.*************.*************.*************.*************.*************.*************.**************.*************.*************.*********sh: 1: ****.***/opt/rt4/bin/mailgate: not found
*******fetchmail: error writing message text
fetchmail: POP3> QUIT
fetchmail: POP3< SBldFGSPL8BlAm/SBHz+b9H9BVH1k6TfVj2eq6v7WA6pr2OB2uf6FdlvtPoVXW+yi27ZXd/g1Lqf
fetchmail: MDA error while fetching from helpdesk at ticket.co.it@zimbra.ticket.co.it
fetchmail: 6.3.21 querying zimbra.ticket.co.it (protocol POP3) at Tue 26 Jun 2012 10:22:25 AM EDT: poll completed
fetchmail: Merged UID list from zimbra.ticket.co.it: 17720.IRidbzHeI6bzOWLayy2p7HWtDHM= = UNSEEN, 17723.SHuBiaCWYg,0,9nWQnSrbPaE21M= = UNSEEN, 17760.RrBL,aEkKUF38ObqE5RyxA8Fj3I= = UNSEEN, 17780.xSV1x6jv0HRhe4TB7Cn29caKUEk= = UNSEEN, 17800.zfe5R,i4,UY+UlWCiKW9BizFC7Q= = UNSEEN, 17801.pv7zeMc0OwOMn1H9sMm2,2WHBoY= = UNSEEN, 17803.WXLHYsVB4uK9qAHGychge,2EKmc= = UNSEEN, 17820.l9qMWjsYiHOL+BMlCLMvhtcl6rY= = UNSEEN
fetchmail: discarding new UID list
fetchmail: Query status=6 (IOERR)
fetchmail: sleeping at Tue 26 Jun 2012 10:22:25 AM EDT for 60 seconds



 

 

 

-----Original Message-----
From: 20/20 Lab <lab at pacbell.net>
To: rt-users <rt-users at lists.bestpractical.com>
Sent: Mon, Jun 25, 2012 4:35 pm
Subject: Re: [rt-users] Issue with Fetchmail


              
On 06/25/2012 11:31 AM, Borngunners      wrote:
    
    
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 at 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
          
    Still looks like your using helpdesk and not helpdesk at ticket.co.it
  
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20120626/6ca3a4de/attachment.htm>

More information about the rt-users mailing list