<font color='black' size='2' face='Arial, Helvetica, sans-serif'>So<font color="black" face="Arial, Helvetica, sans-serif" size="2">, I change the username to helpdesk@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:<br>
<br>
root@helpdesks:~# /etc/init.d/fetchmail debug-run<br>
<br>
/etc/init.d/fetchmail: Initiating debug run of system-wide fetchmail service...<br>
/etc/init.d/fetchmail: script will be run in debug mode, all output to forced to<br>
/etc/init.d/fetchmail: stdout. This is not enough to debug failures that only<br>
/etc/init.d/fetchmail: happen in daemon mode.<br>
/etc/init.d/fetchmail: You might want to direct output to a file, and tail -f it.<br>
/etc/init.d/fetchmail: Stopping the service...<br>
* Pidfile not found! Is fetchmail running?<br>
/etc/init.d/fetchmail: exit status of service stop was: 0<br>
/etc/init.d/fetchmail: RUNUSER is fetchmail<br>
/etc/init.d/fetchmail: OPTIONS would be -f /etc/fetchmailrc --pidfile /var/run/fetchmail/fetchmail.pid<br>
/etc/init.d/fetchmail: Starting service in nodetach mode, hit ^C (SIGINT/intr) to finish run...<br>
fetchmail: Old UID list from zimbra.ticket.co.it: <empty><br>
fetchmail: Scratch list of UIDs: <empty><br>
fetchmail: starting fetchmail 6.3.21 daemon<br>
fetchmail: 6.3.21 querying zimbra.ticket.co.it (protocol POP3) at Tue 26 Jun 2012 10:22:25 AM EDT: poll started<br>
fetchmail: Trying to connect to 192.168.222.30/110...connected.<br>
fetchmail: POP3< +OK zimbra.ticket.co.it Zimbra POP3 server ready<br>
fetchmail: POP3> CAPA<br>
fetchmail: POP3< +OK Capability list follows<br>
fetchmail: POP3< TOP<br>
fetchmail: POP3< USER<br>
fetchmail: POP3< UIDL<br>
fetchmail: POP3< STLS<br>
fetchmail: POP3< SASL PLAIN X-ZIMBRA<br>
fetchmail: POP3< EXPIRE 31 USER<br>
fetchmail: POP3< XOIP<br>
fetchmail: POP3< IMPLEMENTATION ZimbraInc<br>
fetchmail: POP3< .<br>
fetchmail: POP3> STLS<br>
fetchmail: POP3< +OK Begin TLS negotiation<br>
fetchmail: Certificate chain, from root to peer, starting at depth 3:<br>
fetchmail: Issuer Organization: GTE Corporation<br>
fetchmail: Issuer CommonName: GTE CyberTrust Global Root<br>
fetchmail: Subject CommonName: GTE CyberTrust Global Root<br>
fetchmail: Certificate at depth 2:<br>
fetchmail: Issuer Organization: GTE Corporation<br>
fetchmail: Issuer CommonName: GTE CyberTrust Global Root<br>
fetchmail: Subject CommonName: DigiCert High Assurance EV Root CA<br>
fetchmail: Certificate at depth 1:<br>
fetchmail: Issuer Organization: DigiCert Inc<br>
fetchmail: Issuer CommonName: DigiCert High Assurance EV Root CA<br>
fetchmail: Subject CommonName: DigiCert High Assurance CA-3<br>
fetchmail: Server certificate:<br>
fetchmail: Issuer Organization: DigiCert Inc<br>
fetchmail: Issuer CommonName: DigiCert High Assurance CA-3<br>
fetchmail: Subject CommonName: zimbra.ticket.co.it<br>
fetchmail: Subject Alternative Name: zimbra.ticket.co.it<br>
fetchmail: zimbra.ticket.co.it key fingerprint: 70:02:AF:9B:46:02:C1:12:F0:52:69:0D:EE:99:3A:EC<br>
fetchmail: POP3> CAPA<br>
fetchmail: POP3< +OK Capability list follows<br>
fetchmail: POP3< TOP<br>
fetchmail: POP3< USER<br>
fetchmail: POP3< UIDL<br>
fetchmail: POP3< STLS<br>
fetchmail: POP3< SASL PLAIN X-ZIMBRA<br>
fetchmail: POP3< EXPIRE 31 USER<br>
fetchmail: POP3< XOIP<br>
fetchmail: POP3< IMPLEMENTATION ZimbraInc<br>
fetchmail: POP3< .<br>
fetchmail: zimbra.ticket.co.it: upgrade to TLS succeeded.<br>
fetchmail: POP3> USER helpdesk@ticket.co.it<br>
fetchmail: POP3< +OK hello helpdesk@ticket.co.it, please enter your password<br>
fetchmail: POP3> PASS *<br>
fetchmail: POP3< +OK server ready<br>
fetchmail: selecting or re-polling default folder<br>
fetchmail: POP3> STAT<br>
fetchmail: POP3< +OK 8 328373<br>
fetchmail: POP3> LAST<br>
fetchmail: POP3< -ERR unknown command<br>
fetchmail: unknown command<br>
fetchmail: POP3> UIDL<br>
fetchmail: POP3< +OK 8 messages<br>
fetchmail: POP3< 1 17720.IRidbzHeI6bzOWLayy2p7HWtDHM=<br>
fetchmail: 1 is unseen<br>
fetchmail: POP3< 2 17723.SHuBiaCWYg,0,9nWQnSrbPaE21M=<br>
fetchmail: 2 is unseen<br>
fetchmail: POP3< 3 17760.RrBL,aEkKUF38ObqE5RyxA8Fj3I=<br>
fetchmail: 3 is unseen<br>
fetchmail: POP3< 4 17780.xSV1x6jv0HRhe4TB7Cn29caKUEk=<br>
fetchmail: 4 is unseen<br>
fetchmail: POP3< 5 17800.zfe5R,i4,UY+UlWCiKW9BizFC7Q=<br>
fetchmail: 5 is unseen<br>
fetchmail: POP3< 6 17801.pv7zeMc0OwOMn1H9sMm2,2WHBoY=<br>
fetchmail: 6 is unseen<br>
fetchmail: POP3< 7 17803.WXLHYsVB4uK9qAHGychge,2EKmc=<br>
fetchmail: 7 is unseen<br>
fetchmail: POP3< 8 17820.l9qMWjsYiHOL+BMlCLMvhtcl6rY=<br>
fetchmail: 8 is unseen<br>
fetchmail: POP3< .<br>
fetchmail: 8 messages for helpdesk@ticket.co.it at zimbra.ticket.co.it (328373 octets).<br>
fetchmail: POP3> LIST 1<br>
fetchmail: POP3< +OK 1 4492<br>
fetchmail: POP3> TOP 1 99999999<br>
fetchmail: POP3< +OK message top follows<br>
fetchmail: reading message<font color="blue"><b> helpdesk@ticket.co.it@zimbra.ticket.co.it</b></font>:1 of 8 (4492 octets) About to rewrite Return-Path: jane@ticket.co.it...<br>
...rewritten version is Return-Path: jane@ticket.co.it.<br>
fetchmail: About to rewrite From: Jane jane <jane@ticket.co.it>...<br>
...rewritten version is From: Jane jane <jane@ticket.co.it>.<br>
fetchmail: About to rewrite To: Help Desk <helpdesk@ticket.co.it>, ...<br>
...rewritten version is To: Help Desk <helpdesk@ticket.co.it>, .<br>
fetchmail: About to rewrite Cc: Lope Phatter <lphatter@ticket.co.it>, ...<br>
...rewritten version is Cc: Lope Phatter <lphatter@ticket.co.it>, .<br>
fetchmail: about to deliver with: /opt/rt4/bin/mailgate --queue general --action correspond --url http://</font><font color="black" face="Arial, Helvetica, sans-serif" size="2">helpdesks.ticket.co.it</font><font color="black" face="Arial, Helvetica, sans-serif" size="2">/<br>
#*************************************.***************.***********sh: 1: /opt/rt4/bin/mailgate: not found<br>
fetchmail: MDA returned nonzero status 127<br>
fetchmail: not flushed<br>
fetchmail: POP3> LIST 3<br>
fetchmail: POP3< +OK 3 85746<br>
fetchmail: POP3> TOP 3 99999999<br>
fetchmail: POP3< +OK message top follows<br>
fetchmail: reading message <b><font color="blue">helpdesk@ticket.co.it@zimbra.ticket.co.it</font></b>:3 of 8 (85746 octets) About to rewrite Return-Path: young@ticket.co.it...<br>
...rewritten version is Return-Path: young@ticket.co.it.<br>
fetchmail: About to rewrite From: Moses young <young@ticket.co.it>...<br>
...rewritten version is From: Moses young <young@ticket.co.it>.<br>
fetchmail: About to rewrite Reply-To: Moses young <young@ticket.co.it>...<br>
...rewritten version is Reply-To: Moses young <young@ticket.co.it>.<br>
fetchmail: About to rewrite To: helpdesk@ticket.co.it...<br>
...rewritten version is To: helpdesk@ticket.co.it.<br>
fetchmail: about to deliver with: /opt/rt4/bin/mailgate --queue general --action correspond --url http://helpdesks.ticket.co.it/<br>
#******************************************************.***********************.*************.**************.**************.*************.******************.*************.*************.*************.*************.*************.*************.*************.**************.*************.*************.*********sh: 1: ****.***/opt/rt4/bin/mailgate: not found<br>
*******fetchmail: error writing message text<br>
fetchmail: POP3> QUIT<br>
fetchmail: POP3< SBldFGSPL8BlAm/SBHz+b9H9BVH1k6TfVj2eq6v7WA6pr2OB2uf6FdlvtPoVXW+yi27ZXd/g1Lqf<br>
fetchmail: MDA error while fetching from<font color="red"><b> <font color="blue">helpdesk@ticket.co.it@zimbra.ticket.co.it</font></b></font><br>
fetchmail: 6.3.21 querying zimbra.ticket.co.it (protocol POP3) at Tue 26 Jun 2012 10:22:25 AM EDT: poll completed<br>
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<br>
fetchmail: discarding new UID list<br>
fetchmail: Query status=6 (IOERR)<br>
fetchmail: sleeping at Tue 26 Jun 2012 10:22:25 AM EDT for 60 seconds<br>
<br>
<br>
<div> <br>
</div>
<div> <br>
</div>
<div> <br>
</div>
<div style="font-family:arial,helvetica;font-size:10pt;color:black">-----Original Message-----<br>
From: 20/20 Lab <lab@pacbell.net><br>
To: rt-users <rt-users@lists.bestpractical.com><br>
Sent: Mon, Jun 25, 2012 4:35 pm<br>
Subject: Re: [rt-users] Issue with Fetchmail<br>
<br>
<div id="AOLMsgPart_1_49029500-12b3-427f-a18b-96a7f8ba49ab">
<div class="moz-cite-prefix">On 06/25/2012 11:31 AM, Borngunners
wrote:<br>
</div>
<blockquote type="cite"><font color="black" face="Arial, Helvetica, sans-serif" size="2"><font size="2"><font face="Arial, Helvetica, sans-serif">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<br>
<br>
root@helpdesks:~# /etc/init.d/fetchmail debug-run<br>
<br>
/etc/init.d/fetchmail: Initiating debug run of system-wide
fetchmail service...<br>
/etc/init.d/fetchmail: script will be run in debug mode, all
output to forced to<br>
/etc/init.d/fetchmail: stdout. This is not enough to debug
failures that only<br>
/etc/init.d/fetchmail: happen in daemon mode.<br>
/etc/init.d/fetchmail: You might want to direct output to a
file, and tail -f it.<br>
/etc/init.d/fetchmail: Stopping the service...<br>
* Stopping mail retriever
agent:
[ OK ]<br>
/etc/init.d/fetchmail: exit status of service stop was: 0<br>
/etc/init.d/fetchmail: RUNUSER is fetchmail<br>
/etc/init.d/fetchmail: OPTIONS would be -f /etc/fetchmailrc
--pidfile /var/run/fetchmail/fetchmail.pid<br>
/etc/init.d/fetchmail: Starting service in nodetach mode,
hit ^C (SIGINT/intr) to finish run...<br>
fetchmail: Old UID list from ticket.co.it: <empty><br>
fetchmail: Scratch list of UIDs: <empty><br>
fetchmail: starting fetchmail 6.3.21 daemon<br>
fetchmail: 6.3.21 querying ticket.co.it (protocol POP3) at
Mon 25 Jun 2012 02:13:50 PM EDT: poll started<br>
fetchmail: Trying to connect to
128.8.222.167/110...connected.<br>
fetchmail: POP3< +OK zimbra.ticket.co.it Zimbra POP3
server ready<br>
fetchmail: POP3> CAPA<br>
fetchmail: POP3< +OK Capability list follows<br>
fetchmail: POP3< TOP<br>
fetchmail: POP3< USER<br>
fetchmail: POP3< UIDL<br>
fetchmail: POP3< STLS<br>
fetchmail: POP3< SASL PLAIN X-ZIMBRA<br>
fetchmail: POP3< EXPIRE 31 USER<br>
fetchmail: POP3< XOIP<br>
fetchmail: POP3< IMPLEMENTATION ZimbraInc<br>
fetchmail: POP3< .<br>
fetchmail: POP3> STLS<br>
fetchmail: POP3< +OK Begin TLS negotiation<br>
fetchmail: Certificate chain, from root to peer, starting at
depth 3:<br>
fetchmail: Issuer Organization: GTE Corporation<br>
fetchmail: Issuer CommonName: GTE CyberTrust Global Root<br>
fetchmail: Subject CommonName: GTE CyberTrust Global Root<br>
fetchmail: Certificate at depth 2:<br>
fetchmail: Issuer Organization: GTE Corporation<br>
fetchmail: Issuer CommonName: GTE CyberTrust Global Root<br>
fetchmail: Subject CommonName: DigiCert High Assurance EV
Root CA<br>
fetchmail: Certificate at depth 1:<br>
fetchmail: Issuer Organization: DigiCert Inc<br>
fetchmail: Issuer CommonName: DigiCert High Assurance EV
Root CA<br>
fetchmail: Subject CommonName: DigiCert High Assurance CA-3<br>
fetchmail: Server certificate:<br>
fetchmail: Issuer Organization: DigiCert Inc<br>
fetchmail: Issuer CommonName: DigiCert High Assurance CA-3<br>
fetchmail: Subject CommonName: zimbra.ticket.co.it<br>
fetchmail: Subject Alternative Name: zimbra.ticket.co.it<br>
fetchmail: Server CommonName mismatch: zimbra.ticket.co.it
!= ticket.co.it<br>
fetchmail: ticket.co.it key fingerprint:
70:02:AF:9B:46:02:C1:12:F0:52:69:0D:EE:99:3A:EC<br>
fetchmail: Warning: the connection is insecure, continuing
anyways. (Better use --sslcertck!)<br>
fetchmail: POP3> CAPA<br>
fetchmail: POP3< +OK Capability list follows<br>
fetchmail: POP3< TOP<br>
fetchmail: POP3< USER<br>
fetchmail: POP3< UIDL<br>
fetchmail: POP3< STLS<br>
fetchmail: POP3< SASL PLAIN X-ZIMBRA<br>
fetchmail: POP3< EXPIRE 31 USER<br>
fetchmail: POP3< XOIP<br>
fetchmail: POP3< IMPLEMENTATION ZimbraInc<br>
fetchmail: POP3< .<br>
fetchmail: ticket.co.it: upgrade to TLS succeeded.<br>
fetchmail: POP3> USER helpdesk<br>
fetchmail: POP3< +OK hello helpdesk, please enter your
password<br>
</font></font></font></blockquote>
Still looks like your using helpdesk and not <a class="moz-txt-link-abbreviated" __removedlink__1066319525__href="mailto:helpdesk@ticket.co.it">helpdesk@ticket.co.it</a><br>
</div>
<!-- end of AOLMsgPart_1_49029500-12b3-427f-a18b-96a7f8ba49ab -->
</div>
</font></font>