I am sooo close to getting RT up and running. I used RT heavily in my last
organization and I’m trying to implement here. We are entirely a Windows
shop (before, we ran under Linux).
I downloaded rt-3.0.10.exe and installed.
I have things working with fetchmail to retrieve from Server. However, I am
getting an error that I am having a really hard time tracking down.
Fetchmail sees the messages and tried to grab it, that’s when things fail.
1). When I use POP3, I get a message that the message size is not as
expected. I read that this is a known issue and I don’t think this causes
any problems.
-
Again, using POP3
“MDA returned nonzero status 127”
“not flushed”
-
Trying IMAP, I get this error message (this is listed as a better way to
work with Server)
“SIGPIPE thrown from an MDA or stream socket error”
“socket error while fetching from (IP address)”
Query status = 2 (SOCKET)
This is the start command I am using
“C:\Program Files\OURINT~1\COMMON\FETCHM~1\bin\FETCHM~1.EXE” -f
…/rt-mailgate.conf -N -d 30 -v -v -a
In both cases, this is the config file (rt-mailgate.conf) (obviously,
changing pop3 to imap)
defaults proto pop3
poll xxx.xxx.xxx.xxx:
auth password username “rtadmin” password “xxxxxx” 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 General --action correspond”
Looking at c:/progra~1/ourinternet/reques~1/rt/bin/rt-mailgate.in I don’t
see anything jumps out and grabs my attention as needing fixed or
customized.
Any help would be greatly appreciated. Others here are getting very
fustrated that this is being difficult to get going, but I believe this is
the best product for our needs.
Looking at rt-mailgate.in more closely, this looks more like a page on how
to set things up with testing scripts rather then the completed MDA file to
be used with fetchmail.
Does anyone have a sample file that I could use to jumpstart this? Getting
RT to suck in email to create new tickets is the last thing that we need to
set up.
Thanks!
-
Again, using POP3
“MDA returned nonzero status 127”
“not flushed”
-
Trying IMAP, I get this error message (this is listed as a better
way to work with Server)
“SIGPIPE thrown from an MDA or stream socket error”
“socket error while fetching from (IP address)”
Query status = 2 (SOCKET)
Looks like the error is in rt-mailgate, not in fetchmail. To verify
this, run rt-mailgate directly and with debug output enabled: put a
message (headers and all) in a file, then run something like
“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 General --action correspond --debug <
message.txt”
This should either create a ticket, or give some error output.
Sebastian
Sebastian Flothow
sebastian@flothow.de
Because it reverses the logical flow of conversation.
Looking at rt-mailgate.in more closely, this looks more like a page on
how
to set things up with testing scripts rather then the completed MDA
file to be used with fetchmail.
You should look at it even more closely - the first 400 or so lines are
test cases indeed, but then it says “=end testing” and that’s where the
actual script begins.
Sebastian
Sebastian Flothow
sebastian@flothow.de
Because it reverses the logical flow of conversation.
Thanks for the hint. Doing as you suggest does indeed create a ticket, which
suggests that rt-mailgate is OK.
Is there someway to debug rt-mailgate when used with Fetchmail as you do
below?
It is possible that the email has a different config when retrieved from the
exchange server versus when I save the email as a file and read it in.
Doing as you suggest does indeed create a ticket, which
suggests that rt-mailgate is OK.
Does it provide any interesting output?
Is there someway to debug rt-mailgate when used with Fetchmail as you
do
below?
You can add the --debug option to the rt-mailgate call in
rt-mailgate.conf and see if you get more useful output when running
fetchmail.
Otherwise, you could have fetchmail output the retrieved message to a
file, which you can examine afterwards.
Sebastian
Sebastian Flothow
sebastian@flothow.de
Because it reverses the logical flow of conversation.
Interesting, when I dump the email to a file and then try to read it in, it
succeeds, but the requestor, subject, etc don’t come through.
The email in the file looks like
MAIL FROM: BrettB@hkusa.com
RCPT TO: BrettB@localhost
DATA
Received: from xxx.xxx.xxx.xxx [xxx.xxx.xxx.xxx]
by localhost with POP3 (fetchmail-6.2.5)
for BrettB@localhost (single-drop); Fri, 28 May 2004 09:48:36 -0500 (CDT)
Received: by EXCHANGE4
id 01C444C2.57574DA0@EXCHANGE4; Fri, 28 May 2004 09:44:55 -0500
Message-ID: 2E8440B99F0D1B4F9D4F3099A3778FB507179D0E@EXCHANGE4From: Brett Barnhart BrettB@hkusa.com
To: rtadmin RT Testing rtadmin@hkusa.com
Subject: test again
Date: Fri, 28 May 2004 09:44:55 -0500
MIME-Version: 1.0
Content-Type: text/plain;
charset=“iso-8859-1”
Another test
.
The only thing created in the rt is
Another test
.
So, it looks like things aren’t be parsed out correctly.
If I remove all the header information down to ‘From:’ it works correctly.
-----Original Message-----
From: Sebastian Flothow [mailto:lists@flothow.de]
Sent: Friday, May 28, 2004 6:13 AM
To: Brett Barnhart
Cc: ‘rt-users@lists.bestpractical.com’
Subject: Re: [rt-users] Retrieving mail from Outlook Server
Am 27. Mai 2004 um 16:56 Uhr schrieb Brett Barnhart:
Doing as you suggest does indeed create a ticket, which
suggests that rt-mailgate is OK.
Does it provide any interesting output?
Is there someway to debug rt-mailgate when used with
Fetchmail as you
do
below?
You can add the --debug option to the rt-mailgate call in
rt-mailgate.conf and see if you get more useful output when running
fetchmail.
Otherwise, you could have fetchmail output the retrieved message to a
file, which you can examine afterwards.
Sebastian
–
Sebastian Flothow
sebastian@flothow.de
Because it reverses the logical flow of conversation.
Why is top posting frowned upon?
Interesting, when I dump the email to a file and then try to read it
in, it succeeds, but the requestor, subject, etc don’t come through.
The email in the file looks like
MAIL FROM: BrettB@hkusa.com
RCPT TO: BrettB@localhost
DATA
Received: from xxx.xxx.xxx.xxx [xxx.xxx.xxx.xxx]
by localhost with POP3 (fetchmail-6.2.5)
for BrettB@localhost (single-drop); Fri, 28 May 2004 09:48:36 -0500
(CDT)
Received: by EXCHANGE4
id 01C444C2.57574DA0@EXCHANGE4; Fri, 28 May 2004 09:44:55 -0500
Message-ID: 2E8440B99F0D1B4F9D4F3099A3778FB507179D0E@EXCHANGE4
From: Brett Barnhart BrettB@hkusa.com
To: rtadmin RT Testing rtadmin@hkusa.com
Subject: test again
Date: Fri, 28 May 2004 09:44:55 -0500
MIME-Version: 1.0
Content-Type: text/plain;
charset=“iso-8859-1”
Another test
.
The only thing created in the rt is
Another test
.
So, it looks like things aren’t be parsed out correctly.
If I remove all the header information down to ‘From:’ it works
correctly.
I suppose this is caused by the first three lines, as these are SMTP
commands rather than message headers. How did you dump this message to
the file?
Sebastian
Sebastian Flothow
sebastian@flothow.de
Because it reverses the logical flow of conversation.
I reinstalled the RT and poof… everything works fine. Go figure.
Thanks for all your help!