Re: [rt-users] Issue with Fetchmail
On 06/26/2012 11:19 AM, Borngunners wrote: I made the correction to your suggestion and RT seems to be fetching tickets from helpd...@health.umd.edu, but I get this message after looking into the log: root@helpdesks:/var/tmp/rt-4.0.5# tail .f /var/log/fetchmail.log tail: cannot open `.f' for reading: No such file or directory ==> /var/log/fetchmail.log <== sh: 1: /opt/rt4/bin/mailgate: not found fetchmail: reading message helpd...@ticket.co.it@zimbra.ticket.co.it:2 of 8 (7944 octets) (log message incomplete) fetchmail: MDA returned nonzero status 127 fetchmail: not flushed sh: 1: /opt/rt4/bin/mailgate: not found fetchmail: reading message helpd...@ticket.co.it@zimbra.ticket.co.it:3 of 8 (85746 octets) (log message incomplete) fetchmail: error writing message text fetchmail: MDA error while fetching from helpd...@ticket.co.it@zimbra.ticket.co.it fetchmail: Query status=6 (IOERR) fetchmail: terminated with signal 15 Anyway that this message can be cleared. Thanks -Original Message- From: 20/20 Lab To: Borngunners Cc: rt-users Sent: Tue, Jun 26, 2012 12:15 pm Subject: Re: [rt-users] Issue with Fetchmail --snip-- 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 --snip-- Ok, your username is fixed and your authenticating correctly. However, its /opt/rt4/bin/rt-mailgate, not /opt/rt4/bin/mailgate. Just change that in your fetchmailrc file and you should be good to go. -Matt Still looks like fetchmail is trying to route your messeges through /opt/rt4/bin/mailgate. Somewhere in your fetchmailrc(s) you have /opt/rt4/bin/mailgate. It needs to be /opt/rt4/bin/*rt-*mailgate. altho, a not advisable, you could run 'sudo ln /opt/rt4/bin/rt-mailgate -s /opt/rt4/bin/mailgate' It'll create a link that fetchmail can follow. It wont fix the problem with your fetchmail, but it'll allow fetchmail to pipe your messages correctly. -Matt -Matt
Re: [rt-users] Issue with Fetchmail
I made the correction to your suggestion and RT seems to be fetching tickets from helpd...@health.umd.edu, but I get this message after looking into the log: root@helpdesks:/var/tmp/rt-4.0.5# tail .f /var/log/fetchmail.log tail: cannot open `.f' for reading: No such file or directory ==> /var/log/fetchmail.log <== sh: 1: /opt/rt4/bin/mailgate: not found fetchmail: reading message helpd...@ticket.co.it@zimbra.ticket.co.it:2 of 8 (7944 octets) (log message incomplete) fetchmail: MDA returned nonzero status 127 fetchmail: not flushed sh: 1: /opt/rt4/bin/mailgate: not found fetchmail: reading message helpd...@ticket.co.it@zimbra.ticket.co.it:3 of 8 (85746 octets) (log message incomplete) fetchmail: error writing message text fetchmail: MDA error while fetching from helpd...@ticket.co.it@zimbra.ticket.co.it fetchmail: Query status=6 (IOERR) fetchmail: terminated with signal 15 Anyway that this message can be cleared. Thanks -Original Message- From: 20/20 Lab To: Borngunners Cc: rt-users Sent: Tue, Jun 26, 2012 12:15 pm Subject: Re: [rt-users] Issue with Fetchmail --snip-- 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 --snip-- Ok, your username is fixed and your authenticating correctly. However, its /opt/rt4/bin/rt-mailgate, not /opt/rt4/bin/mailgate. Just change that in your fetchmailrc file and you should be good togo. -Matt
Re: [rt-users] Issue with Fetchmail
--snip-- 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 --snip-- Ok, your username is fixed and your authenticating correctly. However, its /opt/rt4/bin/rt-mailgate, not /opt/rt4/bin/mailgate. Just change that in your fetchmailrc file and you should be good to go. -Matt
Re: [rt-users] Issue with Fetchmail
is To: Help Desk , . fetchmail: About to rewrite Cc: Lope Phatter , ... ...rewritten version is Cc: Lope Phatter , . 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 fetchmail: POP3< +OK message top follows fetchmail: reading message helpd...@ticket.co.it@zimbra.ticket.co.it:3 of 8 (85746 octets) About to rewrite Return-Path: yo...@ticket.co.it... ...rewritten version is Return-Path: yo...@ticket.co.it. fetchmail: About to rewrite From: Moses young ... ...rewritten version is From: Moses young . fetchmail: About to rewrite Reply-To: Moses young ... ...rewritten version is Reply-To: Moses young . fetchmail: About to rewrite To: helpd...@ticket.co.it... ...rewritten version is To: helpd...@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 helpd...@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 To: rt-users 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 fetchmailafter migrating to RT 4.05 and wanted to use the fetchmailoption to get email sent to our helpdesk system instead ofusers logging into rt to create a ticket... This is the logfrom 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 retrieveragent: [ 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: fetchmail: Scratch list of UIDs: 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 fetchm
Re: [rt-users] Issue with Fetchmail
The issue I am having is, if I use the username as helpd...@ticket.co.it, will end up having helpd...@ticket.co.it@ticket.co.it, which is not ok for it to authenticate. Now, rt and my email server are on 2 separate box and my email domain name is different from the server. My email SMTP incoming server is zimbra.ticket.co.it and my email domain is ticket.co.it... How do I setup fetchmail to work in this case?
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@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: fetchmail: Scratch list of UIDs: 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 helpd...@ticket.co.it
[rt-users] Issue with Fetchmail
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: fetchmail: Scratch list of UIDs: 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: fetchmail: Query status=3 (AUTHFAIL) fetchmail: sleeping at Mon 25 Jun 2012 02:13:50 PM EDT for 60 seconds Please help
[rt-users] Issue with Fetchmail
Hi All, Having issue with configuring email accounts with fetchmail. I'm keep on getting the following issue: C:\Program Files\OurInternet\Common\fetchmail\bin>type ..\rt-mailgate.conf | etchmail.exe -N -d 300 -f - fetchmail: removing stale lockfile fetchmail: starting fetchmail 6.2.5 daemon fetchmail: Authorization failure on [EMAIL PROTECTED] fetchmail: Query status=3 (AUTHFAIL) fetchmail: sleeping at Mon Aug 6 12:26:01 2007 And I configured the rt-mailgate.conf as following poll mail.xyz.com proto pop3: username contactus password X mda "c:/Progra~1/OurInternet/Common/perl/bin/perl.exe c:/Progra~1/Ourinternet/Reques~1/rt/bin/rt-mailgate.in --url http://localhost:8284/ --queue xyz --action correspond" I'm using windows based rt server. Please help me am I doing any wrong? For your information I'm having different mail domain on the same server. Thanks and regards, Sridhar Adabala. - Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out.___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
