Re: [rt-users] rt-mailgate https - problem

[DD DD]

on old and new server there runs 4.0.7

new machine:

root@rt:~# wget https://127.0.0.1/rt
--2014-06-30 12:24:15--  https://127.0.0.1/rt

Connecting to 127.0.0.1:443... connected.
The certificate's owner does not match hostname `127.0.0.1'
root@rt:~# wget https://localhost/rt
--2014-06-30 12:28:22--  https://localhost/rt
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:443... connected.

GnuTLS: A TLS warning alert has been received.
Unable to establish SSL connection.
root@rt:~#

Why occurs a TLS warning? This comes not from the certificate (I also tried
it with --no-check-certificate)


2014-06-30 12:21 GMT+02:00 Christian Loos :

> Please keep replies to the list.
>
> Which RT version are you using?
>
> Because your apache making a redirect and rt-mailgate following
> redirects only in RT 4.2.4 and newer.
>
> Chris
>
> Am 30.06.2014 12:09, schrieb DD DD:
> > root@rt:~# wget https://HIDDEN/rt
> > --2014-06-30 12:04:42--  https://HIDDEN/rt
> > Resolving HIDDEN (HIDDEN)... HIDDEN
> > Connecting to HIDDEN (HIDDEN)|HIDDEN|:443... connected.
> > HTTP request sent, awaiting response... 301 Moved Permanently
> > Location: https://HIDDEN/rt/ [following]
> > --2014-06-30 12:04:42--  https://HIDDEN/rt/
> > Reusing existing connection to HIDDEN:443.
> > HTTP request sent, awaiting response... 200 OK
> > Length: unspecified [text/html]
> > Saving to: `rt'
> >
> > [
> > <=>
> > ] 4,064   --.-K/s   in 0.01
> >
> > 2014-06-30 12:04:43 (324 KB/s) - `rt' saved [4064]
> >
> > root@rt:~#
> >
> > It seems that Apache doesn't listen correct, but the hosts entry is
> correct.
>
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] rt-mailgate: Permission denied

[Matt Brennan]

On my system, the application is world executable. I don't recall if that's
the default or I changed it. I'm sure someone here will say that's a bad
idea, security wise.

At a minimum, it needs to be executable by whatever user ID postfix is
running as. If you want to lock down the executable, you'd need to check
what user ID you have postfix running as and set the group to one which
contains that user ID (you'd also need to make sure it's group executable).


On Tue, Jun 16, 2015 at 11:33 AM, Jeff Melton  wrote:

> I'm setting up a new RT server, and I'm having some trouble getting
> rt-mailgate to accept email piped from postfix.
> `Command output: local: fatal: execvp /opt/rt4/bin/rt-mailgate:
> Permission denied`
>
> Best I can tell, it's likely to be a permissions issue. What owner, group
> and mode should RT be using? Are there any other gotchas I need to be
> looking at? (I've configured role, group and user permissions in the RT
> GUI.)
>
> JM
>

Re: [rt-users] rt-mailgate: Permission denied

[Jeff Melton]

On Tue, Jun 16, 2015 at 11:54:52AM -0400, Matt Brennan wrote:

On my system, the application is world executable. I don't recall if that's
the default or I changed it. I'm sure someone here will say that's a bad
idea, security wise.

At a minimum, it needs to be executable by whatever user ID postfix is
running as. If you want to lock down the executable, you'd need to check
what user ID you have postfix running as and set the group to one which
contains that user ID (you'd also need to make sure it's group executable).


Thanks! The whole of /opt/rt4 is 755 right now, with everything executed by 
root. The postfix master process is owned by root; qmgr and pickup are owned by 
postfix. /opt/rt4 is root:www-data right now, but I've tried it root:root as 
well. I've tried adding the postfix user to the root and www-data groups, and 
that has no effect.



On Tue, Jun 16, 2015 at 11:33 AM, Jeff Melton  wrote:


I'm setting up a new RT server, and I'm having some trouble getting
rt-mailgate to accept email piped from postfix.
`Command output: local: fatal: execvp /opt/rt4/bin/rt-mailgate:
Permission denied`

Best I can tell, it's likely to be a permissions issue. What owner, group
and mode should RT be using? Are there any other gotchas I need to be
looking at? (I've configured role, group and user permissions in the RT
GUI.)

JM

Re: [rt-users] rt-mailgate: Permission denied

[Joop]

On 16-6-2015 17:33, Jeff Melton wrote:
> I'm setting up a new RT server, and I'm having some trouble getting
> rt-mailgate to accept email piped from postfix.
> `Command output: local: fatal: execvp /opt/rt4/bin/rt-mailgate:
> Permission denied`
>
You don't state which OS you're using but if you're using CentOS/Rhel
base/derived you could be facing a SELinux problem. Check
/var/log/messages /var/log/audit or see what happens if you run
setenforce 0.

Regards,

Joop

Re: [rt-users] rt-mailgate: Permission denied

[Jeff Melton]

It's Debian Wheezy. No SELinux in this case.

On Tue, Jun 16, 2015 at 09:25:02PM +0200, Joop wrote:

On 16-6-2015 17:33, Jeff Melton wrote:

I'm setting up a new RT server, and I'm having some trouble getting
rt-mailgate to accept email piped from postfix.
`Command output: local: fatal: execvp /opt/rt4/bin/rt-mailgate:
Permission denied`


You don't state which OS you're using but if you're using CentOS/Rhel
base/derived you could be facing a SELinux problem. Check
/var/log/messages /var/log/audit or see what happens if you run
setenforce 0.

Regards,

Joop

Re: [rt-users] rt-mailgate: Permission denied

[Aaron C. de Bruyn]

AppArmor?  (Or is that just Ubuntu?)

Also, is the postfix process running in a chroot?
Check /etc/postfix/master.cf to see if the service that is doing the
rt-mailgate delivery has a 'y' in the chroot column.

-A

On Tue, Jun 16, 2015 at 12:29 PM, Jeff Melton  wrote:
> It's Debian Wheezy. No SELinux in this case.
>
>
> On Tue, Jun 16, 2015 at 09:25:02PM +0200, Joop wrote:
>>
>> On 16-6-2015 17:33, Jeff Melton wrote:
>>>
>>> I'm setting up a new RT server, and I'm having some trouble getting
>>> rt-mailgate to accept email piped from postfix.
>>> `Command output: local: fatal: execvp /opt/rt4/bin/rt-mailgate:
>>> Permission denied`
>>>
>> You don't state which OS you're using but if you're using CentOS/Rhel
>> base/derived you could be facing a SELinux problem. Check
>> /var/log/messages /var/log/audit or see what happens if you run
>> setenforce 0.
>>
>> Regards,
>>
>> Joop
>>
>

Re: [rt-users] rt-mailgate: Permission denied

[Jeff Melton]

It is chrooted, but when I s/-/n for all the chrooted processes in master.cf 
and restarted postfix, it didn't make any difference. I just swapped the 
original master.cf back in.

I'll update to add that my aliases were quoted incorrectly to begin with, and 
having changed that, the full error output now reads:

Command died with status 126: "/opt/rt4/bin/rt-mailgate --queue 'Network 
Support' --action correspond --url http://rt.ifworld.com";. Command output: sh: 1: 
/opt/rt4/bin/rt-mailgate: Permission denied

On Tue, Jun 16, 2015 at 12:39:15PM -0700, Aaron C. de Bruyn wrote:

AppArmor?  (Or is that just Ubuntu?)

Also, is the postfix process running in a chroot?
Check /etc/postfix/master.cf to see if the service that is doing the
rt-mailgate delivery has a 'y' in the chroot column.

-A

On Tue, Jun 16, 2015 at 12:29 PM, Jeff Melton  wrote:

It's Debian Wheezy. No SELinux in this case.


On Tue, Jun 16, 2015 at 09:25:02PM +0200, Joop wrote:


On 16-6-2015 17:33, Jeff Melton wrote:


I'm setting up a new RT server, and I'm having some trouble getting
rt-mailgate to accept email piped from postfix.
`Command output: local: fatal: execvp /opt/rt4/bin/rt-mailgate:
Permission denied`


You don't state which OS you're using but if you're using CentOS/Rhel
base/derived you could be facing a SELinux problem. Check
/var/log/messages /var/log/audit or see what happens if you run
setenforce 0.

Regards,

Joop

Re: [rt-users] rt-mailgate: Permission denied

[Jeff Melton]

I figured this out. I was using this project as an opportunity to try out 
plenv, but used /root/.plenv to set global Perl. When we set /root +x, it 
started working. Now I just need to figure out how best to fix it long-term.

Thanks, all.

On Tue, Jun 16, 2015 at 12:39:15PM -0700, Aaron C. de Bruyn wrote:

AppArmor?  (Or is that just Ubuntu?)

Also, is the postfix process running in a chroot?
Check /etc/postfix/master.cf to see if the service that is doing the
rt-mailgate delivery has a 'y' in the chroot column.

-A

On Tue, Jun 16, 2015 at 12:29 PM, Jeff Melton  wrote:

It's Debian Wheezy. No SELinux in this case.


On Tue, Jun 16, 2015 at 09:25:02PM +0200, Joop wrote:


On 16-6-2015 17:33, Jeff Melton wrote:


I'm setting up a new RT server, and I'm having some trouble getting
rt-mailgate to accept email piped from postfix.
`Command output: local: fatal: execvp /opt/rt4/bin/rt-mailgate:
Permission denied`


You don't state which OS you're using but if you're using CentOS/Rhel
base/derived you could be facing a SELinux problem. Check
/var/log/messages /var/log/audit or see what happens if you run
setenforce 0.

Regards,

Joop

Re: [rt-users] rt-mailgate rejects incoming email

[Giuseppe Sollazzo]

Just a question... had the user authenticated at least once?
If they aren't in the db or imported from ldap, there's no mention of 
them in the RT users db hence incoming e-mails can't create tickets.


Giuseppe

On 04/03/11 17:46, Brandon Olszewski wrote:


I have a new install of RT 3.8.9 running on SLES11, and I cannot get 
incoming emails to update/create tickets.  I'm using postfix for email 
routing.  Outgoing mail works (all mail routed to an Exchange 
smarthost).  I put a debug switch in my aliases file and the error 
generated by an incoming email is:


[error] Couldn't find sender's address 
(/opt/rt3/bin/../lib/RT/Interface/Email/Auth/MailFrom/pm:67)


[error] Could not record email: Could not load a valid user 
(/opt/rt3/share/html/REST/1.0/noAuth/mail-gateway:75)


From what I understand, this error means that postfix received the 
email properly and passed it to rt-mailgate, which failed to parse a 
valid FROM email address from the headers thus rejecting the message.


The only instance I've found of this error happing was resolved by 
adding "CreateTicket" permissions to the "Everyone" group in RT -- 
I've done this to no avail.


Linux version: 2.6.32.27-0.2-default

Perl version: 5.10.0 built for x86_64-linux-thread-multi

Non-standard configurations:

Default http site redirects to https

Additional module RT::Authen::ExternalAuth 0.08_01 -- authenticates 
via LDAP against Active Directory -- is working properly.


Any advice would be much appreciated!



The information transmitted is intended only for the person or entity 
to which it is addressed and may contain confidential and privileged 
material. Unauthorized review, use, disclosure, or distribution is 
prohibited. If you receive this material/information in error, please 
contact the sender and destroy the material/information.


Email is not a secure form of communication and should not be used to 
transmit personal or confidential information such as account numbers, 
balance information, or wire transfer requests. The PrivateBank is not 
responsible for the security of sensitive information received by email.



--


Giuseppe Sollazzo
Senior Systems Analyst
Computing Services
Information Services
St. George's, University Of London
Cranmer Terrace
London SW17 0RE

Email: gsoll...@sgul.ac.uk
Direct Dial: +44 20 8725 5160
Fax: +44 20 8725 3583

Re: [rt-users] rt-mailgate rejects incoming email

[Thomas Sibley]

On 04 Mar 2011 12:56, Giuseppe Sollazzo wrote:
> 
> Just a question... had the user authenticated at least once?
> If they aren't in the db or imported from ldap, there's no mention of
> them in the RT users db hence incoming e-mails can't create tickets.

That's not entirely correct.  RT autocreates unprivileged users who send
in email if the Everyone or Unprivileged system groups have the
appropriate rights (CreateTicket or Comment/ReplyToTicket).

Thomas

Re: [rt-users] rt-mailgate rejects incoming email

[Brandon Olszewski]

Yes - the user has authenticated a number of times, and opened a ticket via the 
web interface.  I did verify that the proper email address was imported from AD 
to the RT database.

From: Giuseppe Sollazzo [mailto:gsoll...@sgul.ac.uk]
Sent: Friday, March 04, 2011 11:57 AM
To: Brandon Olszewski
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] rt-mailgate rejects incoming email


Just a question... had the user authenticated at least once?
If they aren't in the db or imported from ldap, there's no mention of them in 
the RT users db hence incoming e-mails can't create tickets.

Giuseppe

On 04/03/11 17:46, Brandon Olszewski wrote:
I have a new install of RT 3.8.9 running on SLES11, and I cannot get incoming 
emails to update/create tickets.  I'm using postfix for email routing.  
Outgoing mail works (all mail routed to an Exchange smarthost).  I put a debug 
switch in my aliases file and the error generated by an incoming email is:

[error] Couldn't find sender's address 
(/opt/rt3/bin/../lib/RT/Interface/Email/Auth/MailFrom/pm:67)
[error] Could not record email: Could not load a valid user 
(/opt/rt3/share/html/REST/1.0/noAuth/mail-gateway:75)

>From what I understand, this error means that postfix received the email 
>properly and passed it to rt-mailgate, which failed to parse a valid FROM 
>email address from the headers thus rejecting the message.

The only instance I've found of this error happing was resolved by adding 
"CreateTicket" permissions to the "Everyone" group in RT - I've done this to no 
avail.

Linux version: 2.6.32.27-0.2-default
Perl version: 5.10.0 built for x86_64-linux-thread-multi


Non-standard configurations:

Default http site redirects to https

Additional module RT::Authen::ExternalAuth 0.08_01 - authenticates via LDAP 
against Active Directory - is working properly.


Any advice would be much appreciated!


The information transmitted is intended only for the person or entity to which 
it is addressed and may contain confidential and privileged material. 
Unauthorized review, use, disclosure, or distribution is prohibited. If you 
receive this material/information in error, please contact the sender and 
destroy the material/information.

Email is not a secure form of communication and should not be used to transmit 
personal or confidential information such as account numbers, balance 
information, or wire transfer requests. The PrivateBank is not responsible for 
the security of sensitive information received by email.




--





Giuseppe Sollazzo

Senior Systems Analyst

Computing Services

Information Services

St. George's, University Of London

Cranmer Terrace

London SW17 0RE



Email: gsoll...@sgul.ac.uk<mailto:gsoll...@sgul.ac.uk>

Direct Dial: +44 20 8725 5160

Fax: +44 20 8725 3583




The information transmitted is intended only for the person or entity to which 
it is addressed and may contain confidential and privileged material. 
Unauthorized review, use, disclosure, or distribution is prohibited. If you 
receive this material/information in error, please contact the sender and 
destroy the material/information.

Email is not a secure form of communication and should not be used to transmit 
personal or confidential information such as account numbers, balance 
information, or wire transfer requests. The PrivateBank is not responsible for 
the security of sensitive information received by email.

[rt-users] rt-mailgate and command by mail

[Albert Shih]

Hi all 


I've exact same probleme as 


http://www.mail-archive.com/rt-users@lists.bestpractical.com/msg08421.html

Do you've any news idea ?

Regards.

JAS
-- 
Albert SHIH
DIO batiment 15
Observatoire de Paris Meudon
5 Place Jules Janssen
92195 Meudon Cedex
Téléphone : 01 45 07 76 26/06 86 69 95 71
Heure local/Local time:
mar 19 avr 2011 10:02:15 CEST

[rt-users] rt-mailgate stopped workng please help

[Matthew Simpson]

Hi all,

I'm using Centos 4.5 and use the RT yum repo to install RT 3. Over the 
last week I have noticed this error in the mailog for sendmail:


sendmail[7784]: m3H2xC0A007792: to=|"/etc/smrsh/rt-mailgate --queue 
care-shifts --action correspond --url http://care.domain.com/";, 
ctladdr=<[EMAIL PROTECTED]> (8/0), delay=04:13:07, 
xdelay=00:00:00, mailer=prog, pri=483216, dsn=4.0.0, stat=Deferred: prog 
mailer (/usr/sbin/smrsh) exited with EX_TEMPFAIL


Delivery Fail:

   - Transcript of session follows -
RT server error.

The RT server which handled your email did not behave as expected. It
said:

Can't locate object method "tmp_recycling" via package "MIME::Parser" at 
/usr/lib/rt/RT/EmailParser.pm line 616.

Stack:
  [/usr/lib/rt/RT/EmailParser.pm:616]
  [/usr/lib/rt/RT/EmailParser.pm:225]
  [/usr/lib/rt/RT/EmailParser.pm:177]
  [/usr/lib/rt/RT/EmailParser.pm:137]
  [/usr/lib/rt/RT/Interface/Email.pm:523]
  [/var/rt/html/REST/1.0/NoAuth/mail-gateway:58]

|"/etc/smrsh/rt-mailgate --queue care-shifts --action correspond --url 
http://care.mattysimpson.com/";... Deferred: 421 4.4.2 sv2-2.per.domain.com 
Error: timeout exceeded
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old


What has happened? Please help?



Matt


___
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

[rt-users] rt-mailgate stopped working please help

[Matthew Simpson]

Hi all,

I'm using Centos 4.5 and use the RT yum repo to install RT 3. Over the 
last week I have noticed this error in the mailog for sendmail:


sendmail[7784]: m3H2xC0A007792: to=|"/etc/smrsh/rt-mailgate --queue 
care-shifts --action correspond --url http://care.domain.com/";, 
ctladdr=<[EMAIL PROTECTED]> (8/0), delay=04:13:07, 
xdelay=00:00:00, mailer=prog, pri=483216, dsn=4.0.0, stat=Deferred: prog 
mailer (/usr/sbin/smrsh) exited with EX_TEMPFAIL


Delivery Fail:

   - Transcript of session follows -
RT server error.

The RT server which handled your email did not behave as expected. It
said:

Can't locate object method "tmp_recycling" via package "MIME::Parser" at 
/usr/lib/rt/RT/EmailParser.pm line 616.

Stack:
  [/usr/lib/rt/RT/EmailParser.pm:616]
  [/usr/lib/rt/RT/EmailParser.pm:225]
  [/usr/lib/rt/RT/EmailParser.pm:177]
  [/usr/lib/rt/RT/EmailParser.pm:137]
  [/usr/lib/rt/RT/Interface/Email.pm:523]
  [/var/rt/html/REST/1.0/NoAuth/mail-gateway:58]

|"/etc/smrsh/rt-mailgate --queue care-shifts --action correspond --url 
http://care.domain.com/";... Deferred: 421 4.4.2 sv2-2.per.domain.com 
Error: timeout exceeded
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old


What has happened? Please help?



Matt




___
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

[rt-users] [rt-mailgate] "--action comment" not commenting

[Tyler Knappe]

Hi all,

I am running RT 3.6.3 using fetchmail to retrieve messages from our mail 
server. I have two email addresses setup to receive mail, [EMAIL PROTECTED] and 
[EMAIL PROTECTED]  Within the fetchmail config file [EMAIL PROTECTED] correctly 
uses '--action correspond' to make a ticket within RT.  However, when 
sending mail to [EMAIL PROTECTED] it doesn't seem to correctly use the 
'--action comment' to comment on tickets, rather it never comments and 
only corresponds, creating new tickets.

Though rt-mailgate shows this:

=item Action

The action being performed. At the moment, it's one of "comment" or 
"correspond"

I've isolated it to rt-mailgate, ruling out the mail server and 
fetchmail.  Any ideas?

Thanks,
-Tyler

-- 
Tyler Knappe  |  IT Assistant  |  VisionLink  |  First National Center  |  3101 
Iris Avenue, Suite 240  |  Boulder CO, 80301  |  303.402.0170 ext. 124 

___
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

Re: [rt-users] rt-mailgate requests from 127.0.1.1?

[Jesse Vincent]

On Thu, Apr 01, 2010 at 11:23:47AM -0700, Nick Irvine wrote:
> Setting up rt-mailgate, and was getting "403 Forbidden" errors.
> Checked Apache logs, and request was coming from 127.0.1.1 instead
> of 0.1.  If I do a wget or w3m for the same /REST... address, it
> comes from 127.0.0.1 and works.  Just a minor change to
> apache2-modperl from "Allow from 127.0.0.1" to "Allow from 127" and
> it's fixed...
> 
> Can anyone tell me why requests from rt-mailgate would come from
> 127.0.1.1?  Maybe it's a Perl thing?

Can you send your /etc/hosts?



> -- 
> Nick Irvine
> IT and Network Administrator
> Artona Group
> 
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com

-- 

Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Re: [rt-users] rt-mailgate requests from 127.0.1.1?

[Nick Irvine]

Wow, you're good:

127.0.0.1 localhost
127.0.1.1 hostname.domain.tld hostname

# plus some IPv6 stuff

So RT prefers the FQDN to using localhost?

Nick Irvine
IT and Network Administrator
Artona Group

On 04/01/10 12:38, Jesse Vincent wrote:




On Thu, Apr 01, 2010 at 11:23:47AM -0700, Nick Irvine wrote:

Setting up rt-mailgate, and was getting "403 Forbidden" errors.
Checked Apache logs, and request was coming from 127.0.1.1 instead
of 0.1.  If I do a wget or w3m for the same /REST... address, it
comes from 127.0.0.1 and works.  Just a minor change to
apache2-modperl from "Allow from 127.0.0.1" to "Allow from 127" and
it's fixed...

Can anyone tell me why requests from rt-mailgate would come from
127.0.1.1?  Maybe it's a Perl thing?


Can you send your /etc/hosts?




--
Nick Irvine
IT and Network Administrator
Artona Group

Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com




Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Re: [rt-users] rt-mailgate requests from 127.0.1.1?

[Jesse Vincent]

On Thu, Apr 01, 2010 at 12:52:00PM -0700, Nick Irvine wrote:
> Wow, you're good:
> 
> 127.0.0.1 localhost
> 127.0.1.1 hostname.domain.tld hostname
> 
> # plus some IPv6 stuff
> 
> So RT prefers the FQDN to using localhost?

Next up, what's in /etc/aliases?

> 
> Nick Irvine
> IT and Network Administrator
> Artona Group
> 
> On 04/01/10 12:38, Jesse Vincent wrote:
> >
> >
> >
> >On Thu, Apr 01, 2010 at 11:23:47AM -0700, Nick Irvine wrote:
> >>Setting up rt-mailgate, and was getting "403 Forbidden" errors.
> >>Checked Apache logs, and request was coming from 127.0.1.1 instead
> >>of 0.1.  If I do a wget or w3m for the same /REST... address, it
> >>comes from 127.0.0.1 and works.  Just a minor change to
> >>apache2-modperl from "Allow from 127.0.0.1" to "Allow from 127" and
> >>it's fixed...
> >>
> >>Can anyone tell me why requests from rt-mailgate would come from
> >>127.0.1.1?  Maybe it's a Perl thing?
> >
> >Can you send your /etc/hosts?
> >
> >
> >
> >>--
> >>Nick Irvine
> >>IT and Network Administrator
> >>Artona Group
> >>
> >>Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> >>Buy a copy at http://rtbook.bestpractical.com
> >

-- 

Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Re: [rt-users] rt-mailgate requests from 127.0.1.1?

[Nick Irvine]

# /etc/aliases
mailer-daemon: postmaster
postmaster: root
nobody: root
hostmaster: root
usenet: root
news: root
webmaster: root
www: root
ftp: root
abuse: root
noc: root
security: root
root: administrator

But I'm using fetchmail actually:

#/etc/fetchmailrc
poll mail.domain.tld proto imap auth password
user helpd...@domain.tld pass password mda "rt-mailgate --url 
http://hostname/rt --queue General --action correspond"


Thanks,

Nick Irvine
IT and Network Administrator
Artona Group

On 04/01/10 12:58, Jesse Vincent wrote:




On Thu, Apr 01, 2010 at 12:52:00PM -0700, Nick Irvine wrote:

Wow, you're good:

127.0.0.1 localhost
127.0.1.1 hostname.domain.tld hostname

# plus some IPv6 stuff

So RT prefers the FQDN to using localhost?


Next up, what's in /etc/aliases?



Nick Irvine
IT and Network Administrator
Artona Group

On 04/01/10 12:38, Jesse Vincent wrote:




On Thu, Apr 01, 2010 at 11:23:47AM -0700, Nick Irvine wrote:

Setting up rt-mailgate, and was getting "403 Forbidden" errors.
Checked Apache logs, and request was coming from 127.0.1.1 instead
of 0.1.  If I do a wget or w3m for the same /REST... address, it
comes from 127.0.0.1 and works.  Just a minor change to
apache2-modperl from "Allow from 127.0.0.1" to "Allow from 127" and
it's fixed...

Can anyone tell me why requests from rt-mailgate would come from
127.0.1.1?  Maybe it's a Perl thing?


Can you send your /etc/hosts?




--
Nick Irvine
IT and Network Administrator
Artona Group

Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com






Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Re: [rt-users] rt-mailgate requests from 127.0.1.1?

[Jesse Vincent]

On Thu, Apr 01, 2010 at 01:23:28PM -0700, Nick Irvine wrote:
> 
> Can anyone tell me why requests from rt-mailgate would come from 
> 127.0.1.1? 

> >>127.0.1.1 hostname.domain.tld hostname

> poll mail.domain.tld proto imap auth password user helpd...@domain.tld pass 
> password mda "rt-mailgate --url http://hostname/rt --queue General --action 
> correspond"
 
I presume it's now obvious. :)

Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Re: [rt-users] rt-mailgate requests from 127.0.1.1?

[Nick Irvine]

Yeah, thanks!

Nick Irvine
IT and Network Administrator
Artona Group

On 04/01/10 13:52, Jesse Vincent wrote:




On Thu, Apr 01, 2010 at 01:23:28PM -0700, Nick Irvine wrote:



Can anyone tell me why requests from rt-mailgate would come from 127.0.1.1?



127.0.1.1 hostname.domain.tld hostname



poll mail.domain.tld proto imap auth password user helpd...@domain.tld pass password mda 
"rt-mailgate --url http://hostname/rt --queue General --action correspond"


I presume it's now obvious. :)


Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Re: [rt-users] rt-mailgate: change timeout default

[Torsten Brumm]

Hi Björn,
try at the mailgate command: --timeout=seconds

Torsten

2010/4/9 Bjoern Schulz 

> Hi RT Users,
>
> I try to change the rt-mailgate timeout default without changing the
> source?
>
> I don't find this in RT_Config.
>
> Any hints or suggestions?
>
> Best regards,
>  Björn
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com
>



-- 
MFG

Torsten Brumm

http://www.brumm.me
http://www.elektrofeld.de

Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Re: [rt-users] rt-mailgate: change timeout default

[Bjoern Schulz]

Hi Torsten,

Am 09.04.2010 14:13, schrieb Torsten Brumm:

Hi Björn,
try at the mailgate command: --timeout=seconds


I know that, but I like to change the default (180s to 360s) ;-)
I don't like to change all my procmail rc's...

Schönes Wochenende und geniesse das feine Wetter in Hamburg,
  Björn

Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Re: [rt-users] rt-mailgate: change timeout default

[Torsten Brumm]

OK, open rt-mailgate and navigate to:

127 $ua->timeout( exists( $opts{'timeout'} )? $opts{'timeout'}: 180 );
128 my $r = $ua->post( $full_url, \%args, Content_Type => 'form-data' );
129 check_failure($r);

i think here you can change this for your slow postfix ;-)

Schönes Wochenende

Torsten

2010/4/9 Bjoern Schulz 

> Hi Torsten,
>
> Am 09.04.2010 14:13, schrieb Torsten Brumm:
>
>  Hi Björn,
>> try at the mailgate command: --timeout=seconds
>>
>
> I know that, but I like to change the default (180s to 360s) ;-)
> I don't like to change all my procmail rc's...
>
> Schönes Wochenende und geniesse das feine Wetter in Hamburg,
>  Björn
>



-- 
MFG

Torsten Brumm

http://www.brumm.me
http://www.elektrofeld.de

Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Re: [rt-users] rt-mailgate: change timeout default

[Bjoern Schulz]

Hi Exim-Guy!

Am 09.04.2010 14:56, schrieb Torsten Brumm:

OK, open rt-mailgate and navigate to:

127 $ua->timeout( exists( $opts{'timeout'} )? $opts{'timeout'}: 180 );
128 my $r = $ua->post( $full_url, \%args, Content_Type => 'form-data' );
129 check_failure($r);


OK I know that, I don't like to change the source ( as you, if I 
remember correctly)




i think here you can change this for your slow postfix ;-)


Maybe it's mysql but who knows... Postfix is not the problem, gell



Schönes Wochenende


Danke und grüße zu Hause!

Postfix-Björn

Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

[rt-users] RT mailgate loop revisited - last chapter

[Kenneth Crocker]

Kevin,

I did a complete scan of our rt.log and found the following:

[Wed Aug  4 22:23:42 2010] [info]:
RT::Authen::ExternalAuth::CanonicalizeUserInfo returning Comments:
Autocreated on ticket submission, Disabled: 0, EmailAddress:
jja...@motio.com, Name: jja...@motio.com, Password: , Privileged: 0,
RealName: Jonathan James
(/opt/rt3/local/plugins/RT-Authen-ExternalAuth/lib/RT/Authen/ExternalAuth.pm:536)



[Wed Aug  4 22:23:42 2010] [crit]: User creation failed in mailgateway:
Could not set user info (/opt/rt3/bin/../lib/RT/Interface/Email.pm:244)



[Wed Aug  4 22:23:42 2010] [warning]: Couldn't load user
'jja...@motio.com'.giving
up (/opt/rt3/bin/../lib/RT/Interface/Email.pm:932)



[Wed Aug  4 22:23:42 2010] [crit]: User  'jja...@motio.com' could not be
loaded in the mail gateway (/opt/rt3/bin/../lib/RT/Interface/Email.pm:244)



[Wed Aug  4 22:23:42 2010] [warning]: Use of uninitialized value in
concatenation (.) or string at
/opt/rt3/local/plugins/RT-Extension-CommandByMail/lib/RT/Interface/Email/Filter/TakeAction.pm
line 184.
(/opt/rt3/local/plugins/RT-Extension-CommandByMail/lib/RT/Interface/Email/Filter/TakeAction.pm:184)


[Wed Aug  4 22:23:42 2010] [error]: Couldn't get principal for not loaded
object (/opt/rt3/bin/../lib/RT/User_Overlay.pm:1181)

This set of logs repeats every 15 minutes.

It was initially initiated by an email from a user that is NOT on our LDAP
list of approved users and we have our RT_SiteConfig.pm settings to NOT add
new (email) Users automatically unless they pass the LDAP muster. Our Config
settings for the Mail Gateway are as follows:

Set($OwnerEmail, 'kfcroc...@lbl.gov');

Set($LoopsToRTOwner, 1);

Set($StoreLoops, undef);

Set($TruncateLongAttachments, 1);

Set($ParseNewMessageForTicketCcs , undef);

Set($RTAddressRegexp , '.*\stuff');

Set($LookupSenderInExternalDatabase, 1);# not actually functional -alinc

Set($SenderMustExistInExternalDatabase, 1);

Set($ValidateUserEmailAddresses, 1);

Set(@MailPlugins, (qw(Auth::MailFrom Filter::TakeAction)));

Set($MailCommand , 'sendmailpipe');

Set($SetOutgoingMailFrom, 0);

Set($SendmailArguments , "-oi -t");

Set($SendmailBounceArguments , '-f "<>"');

Set($SendmailPath, "/usr/lib/sendmail");

Set($SMTPServer, undef);

Set($SMTPFrom, undef);

Set(@MailParams, ());

Set($CorrespondAddress , '');

Set($CommentAddress , '');

Set($UseFriendlyFromLine, 0);

Set($UseFriendlyToLine, 0);

Set($NotifyActor, 0);

Set($RecordOutgoingEmail, 1);

Set($ForwardFromUser, 0);

Set($RedistributeAutoGeneratedMessages, 'privileged');

Set($WebExternalAuth , undef);

Set($WebExternalAuthContinuous, 0);

Set($WebFallbackToInternalAuth , undef);

Set($WebExternalAuto , 0);
Set($AutoCreate, undef);

Our “reply” and “Comment” addresses are the same on a Queue-by-Queue basis,
ALL ending with the same “stuff” which is in the “RTAddressRegexp” setting.

Now, from what I understand from the comments/instructions in the
RT_Config.pm file is that *if we do NOT set* <$ParseNewMessageForTicketCcs>,
then we *shouldn't need to set* the "$RTAddressRegexp" setting, which we
didn't. *When I DID set it*, the  loop disappeared.

If the Mail Gateway is set to NOT auto add *OR* if LDAP authorization
failures are also going to cause a loop, should there be an instruction
about this in the RT_Config.pm file?

The only thing I can figure is that one or more of the settings shown above
is causing RT to initiate a mail loop every 15 minutes. Does RT go to the
incoming mail server to look for "new" mail every 15 minutes? If so, why 15
minutes? Where does that setting exist? Is there something in one of the
settings above that tells RT to keep re-trying to add this guy?

Anyway, that's about all I have for now.

Any more in a direction to look would be extremely helpful.

Thanks a WHOLE BUNCH!

Kenn
LBNL
RT Training in Washington DC, USA on Oct 25 & 26 2010
Last one this year -- Learn how to get the most out of RT!

[rt-users] rt-mailgate problem - certificate verify failure ?

[Ethier, Michael]

Hello,

The rt-mailgate program acts differently between v 3.8.8 and v 4.0.6. The v 
3.8.8 version works
fine using https, and even when I have v 4.0.6 running with the /etc/aliases 
point to the v 3.8.8 version of rtmailgate, email
get sent to the queue. But the v 4.0.6 version fails with certificate verify 
failed, output from mailq:

(temporary failure. Command output: An Error Occurred =  500 
Can't connect to testrt.rc.fas.harvard.edu:443 (certificate verify failed))
 r...@testrt.rc.fas.harvard.edu

Any ideas as to the verification of my RT/ssl setup,  on how to fix this ? 
Apparently the RT 4.0.6 is less forgiving about the ssl setup and config.
I ran RT configure with the --enable-ssl-mailgate option and installed all perl 
modules required with "make fixdeps" in RT 4.0.6.

Thanks,
Mike

This is in /etc/aliases:
# rt3
rt: "|/opt/rt-3.8.8/bin/rt-mailgate --queue 'General' --action correspond --url 
https://testrt.rc.fas.harvard.edu/";
rt-comment: "|/opt/rt-3.8.8/bin/rt-mailgate --queue 'General' --action comment 
--url https://testrt.rc.fas.harvard.edu/";

# rt4
#rt: "|/opt/rt4/bin/rt-mailgate --queue 'General' --ca-file 
/etc/pki/tls/certs/ca-bundle.crt --action correspond --url 
https://testrt.rc.fas.harvard.edu/";
#rt-comment: "|/opt/rt4/bin/rt-mailgate --queue 'General' --ca-file 
/etc/pki/tls/certs/ca-bundle.crt --action comment --url 
https://testrt.rc.fas.harvard.edu/";

Re: [rt-users] rt-mailgate: undefined server error

[Thomas Sibley]

On 12/03/2012 01:27 AM, Carlos Fuentes Bermejo wrote:
> Hiya folks,
> 
> Since a few days ago I'm having the following error:
> 
> rt-mailgate: connecting to
> http://xxx.xxx.xxx.xxx//REST/1.0/NoAuth/mail-gateway An Error
> Occurred =  500 read timeout
> /path/to/my/rt/bin/rt-mailgate: undefined server error
> 
> This is happening since I did migrate to RT 4.0.8, and not with all
> the incoming mail, just with mails which have attachments.
> 
> Any ideas??? I forgot something to configure???

The error implies that rt-mailgate times out while waiting for a
response from the RT server.  Is there anything in your web server logs?

We're hiring! http://bestpractical.com/jobs

Re: [rt-users] rt-mailgate: undefined server error

[Carlos Fuentes Bermejo]

Hi Thomas,

Nothing on the web server logs.

Cheers,
Carlos

El 03/12/2012, a las 19:53, Thomas Sibley escribió:

> On 12/03/2012 01:27 AM, Carlos Fuentes Bermejo wrote:
>> Hiya folks,
>> 
>> Since a few days ago I'm having the following error:
>> 
>> rt-mailgate: connecting to
>> http://xxx.xxx.xxx.xxx//REST/1.0/NoAuth/mail-gateway An Error
>> Occurred =  500 read timeout
>> /path/to/my/rt/bin/rt-mailgate: undefined server error
>> 
>> This is happening since I did migrate to RT 4.0.8, and not with all
>> the incoming mail, just with mails which have attachments.
>> 
>> Any ideas??? I forgot something to configure???
> 
> The error implies that rt-mailgate times out while waiting for a
> response from the RT server.  Is there anything in your web server logs?
> 
> We're hiring! http://bestpractical.com/jobs

--
Carlos Fuentes Bermejo 
Security Specialist - IRIS-CERT 
RedIRIS/Red.es
Tel: 91 212 76 20/25 Ext: 5583
www.rediris.es - http://www.rediris.es/cert
PGP key: http://www.rediris.es/keyserver





We're hiring! http://bestpractical.com/jobs

[rt-users] rt-mailgate and web based authentication

[Thomas Misilo]

Hi,

I am switched from using LDAP to CAS for authentication, and now because it 
redirects to the login screen, mailgate isn't working. I was wondering if 
anyone had a workaround or solution to this?

Thanks,

Tom

Re: [rt-users] rt-mailgate issue with postfix

[Tim Wiley]

On 07/23/2013 04:53 AM, Rajat toshniwal wrote:

Hi Folks

We have just installed RT4.0.13 in our environment. Our foremost
requirement is ticket creation via email. In our setup we already have
postfix running on separate server.
On RT we are having exim which is acting as relay server and using
postfix mail server as master.
Now I want to integrate my RT server with that mailbox.
In order to do that I installed rt-mailgate on my mail server and
created below mentioned entries in /etc/aliases

*rt-database: "|/opt/rt4/bin/rt-mailgate --queue database
--action correspond --url http://rt.xyz.com/";
rt-database-comment: "|/opt/rt4/bin/rt-mailgate --queue database
--action comment --url http://rt.xyz.com/";
*
I have database queue configured on my RT box with the above mentioned
email-address. I have also given create-ticket rights to everyone.
Both the email-ids rt-datab...@gml.com and rt-database-comm...@gml.com
are configured on my AD.

But whenever i am trying to create ticket, I get the below mentioned
error from mail.log

Jul 23 07:23:17 mail postfix/smtpd[7389]: connect from localhost[127.0.0.1]
Jul 23 07:23:17 mail postfix/smtpd[7389]: DC0DC45C61:
client=localhost[127.0.0.1]
Jul 23 07:23:17 mail postfix/cleanup[7369]: DC0DC45C61:
message-id=
Jul 23 07:23:17 mail postfix/qmgr[5870]: DC0DC45C61:
from=, size=1448, nrcpt=1 (queue active)
Jul 23 07:23:17 mail postfix/smtpd[7389]: disconnect from
localhost[127.0.0.1]
Jul 23 07:23:17 mail amavis[5064]: (05064-04) Passed CLEAN,
[192.168.10.24]  -> <"|/opt/rt4/bin/rt-mailgate --queue
database --action correspond --url http://rt.tekmindz.com/"@gml.com>,
Message-ID: , mail_id: qXkzuLb1TZ4M, Hits: -1,
size: 854, queued_as: DC0DC45C61, 28311 ms
Jul 23 07:23:17 mail postfix/smtp[7386]: 8553245C65:
to=<|/opt/rt4/bin/rt-mailgate --queue database --action correspond --url
http://rt.tekmindz.com/@gml.com>, relay=127.0.0.1[127.0.0.1]:10024,
delay=28, delays=0.11/0.03/0.01/28, dsn=2.0.0, status=sent (250 2.0.0
Ok, id=05064-04, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as
DC0DC45C61)
Jul 23 07:23:17 mail postfix/qmgr[5870]: 8553245C65: removed
Jul 23 07:23:18 mail postfix/virtual[7390]: DC0DC45C61:
to=<|/opt/rt4/bin/rt-mailgate --queue database --action correspond --url
http://rt.tekmindz.com/@gml.com>, relay=virtual, delay=0.17,
delays=0.06/0.05/0/0.06, dsn=5.1.1, status=bounced (unknown user:
"|/opt/rt4/bin/rt-mailgate --queue database --action correspond --url
http://rt.tekmindz.com/@gml.com";)
Jul 23 07:23:18 mail postfix/cleanup[7369]: 106A845C64:
message-id=<20130723112318.106a845...@mail.gml.com>
Jul 23 07:23:18 mail postfix/qmgr[5870]: 106A845C64: from=<>, size=3673,
nrcpt=1 (queue active)
Jul 23 07:23:18 mail postfix/bounce[7391]: DC0DC45C61: sender
non-delivery notification: 106A845C64
Jul 23 07:23:18 mail postfix/qmgr[5870]: DC0DC45C61: removed
Jul 23 07:23:18 mail postfix/virtual[7390]: 106A845C64:
to=, relay=virtual, delay=0.12, delays=0.06/0.01/0/0.05,
dsn=2.0.0, status=sent (delivered to maildir)
Jul 23 07:23:18 mail postfix/qmgr[5870]: 106A845C64: removed
Jul 23 07:24:29 mail postfix/smtpd[7363]: idle timeout -- exiting

Actually whole rt-mailgate entry is treated like a user. Right now i am
clueless about what to do.
Kindly help me in troubleshooting this issue.

Regards


You didn't post your exim.conf, so I'm pretty much stabbing in the dark, 
but my guess is a lack of address_pipe transport configuration.


That said, if your postfix machine is only used for routing to/from the 
RT machine, you may want to consider eliminating that machine & running 
postfix on your RT box.  And even if your postfix box is used for other 
things, you may want to consider using postfix on your RT box as well to 
eliminate the confusion of running 2 different MTAs.

Fwd: [rt-users] rt mailgate reply to field

[SystemAdmin]

You set that in the Queue configuration..., Configuration, queues then select the queue and you can set Reply-To
 
 

On 4/25/06, Winn Johnston <
[EMAIL PROTECTED]> wrote: 




hello all,
 
i am working on a development box, and the last thing i have to do is test the rt-mailgate. It seems like everything is working except for the replyto field. It still refrences the old box.
 
example.
[EMAIL PROTECTED]
i need it to say
[EMAIL PROTECTED]
 
i am sure it is in the site config, but i just can't find it.
 
thanks in advance

winn johnston



Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. 
Great rates starting at 1¢/min. 


___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-usersCommunity 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.comWe're hiring! Come hack Perl for Best Practical: 
http://bestpractical.com/about/jobs.html
 
___
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


We're hiring! Come hack Perl for Best Practical: 
http://bestpractical.com/about/jobs.html

[rt-users] rt-mailgate ignoring --no-verify-ssl?

[Aaron C. de Bruyn]

Mailgate has been driving me nuts.  I downloaded 4.2.10 and set it up
on a bright, shiny new server.

I'm running fetchmail on my RT box using the following to send tickets to RT:

poll mail.mydomain.tld with protocol pop3
   username engineering password -redacted- mda
"/opt/rt4/bin/rt-mailgate --no-verify-ssl --queue engineering --action
correspond --url https://tickets.mydomain.tld --debug"

Fetchmail complains about the MDA erroring out.  Increasing fetchmail
debugging shows:

fetchmail: about to deliver with: /opt/rt4/bin/rt-mailgate
--no-verify-ssl --queue engineering --action correspond --url
https://tickets.mydomain.tld/ --debug
#***/opt/rt4/bin/rt-mailgate: temp file is '/tmp/Ax6Or2dgc1/23FBulXCfc'
/opt/rt4/bin/rt-mailgate: connecting to
https://tickets.mydomain.tld//REST/1.0/NoAuth/mail-gateway
HTTP request failed: 500 Can't connect to tickets.mydomain.tld:443
(certificate verify failed). Your webserver logs may have more
information or there may be a network problem.

/opt/rt4/bin/rt-mailgate: undefined server error
fetchmail: MDA returned nonzero status 75
 not flushed
fetchmail: POP3> QUIT


I even get an SSL error when running from the command line:

root@tickets:/opt# /opt/rt4/bin/rt-mailgate --no-verify-ssl --queue
engineering --action correspond --url https://tickets.mydomain.tld/
--debug
test 
/opt/rt4/bin/rt-mailgate: temp file is '/tmp/9vlYhx9C9X/kI4IQo0RRw'
/opt/rt4/bin/rt-mailgate: connecting to
https://tickets.mydomain.tld//REST/1.0/NoAuth/mail-gateway
HTTP request failed: 500 Can't connect to tickets.mydomain.tld:443
(certificate verify failed). Your webserver logs may have more
information or there may be a network problem.

/opt/rt4/bin/rt-mailgate: undefined server error
root@tickets:/opt#

It's acting like it's ignoring --no-verify-ssl.

Am I missing something?

Thanks,

-A

[rt-users] rt-mailgate needs http for comment

[Joseph D. Wagner]

I had apache set to allow rt over https only.  Trying over http would fail.

rt-mailgate was working perfectly fine over https when using "--action 
correspond".  However, when using "--action comment", it fails saying it 
is unable to connect.


When I changed my apache configuration to allow http on local 
connections, it started working.


I suspect there is some code in the comment path of rt-mailgate that is 
forcing it over the http connection, rather than properly deriving the 
connection from the url parameter.


Being new to rt, I am open to the possibility I misconfigured 
something.  Is anyone else able to reproduce this?


Joseph D. Wagner

[rt-users] rt-mailgate, --queue extension and disabled queues

[Aaron Ross]

Hi all,

Our users are reporting that before we upgraded to 3.8.8 queues that were
disabled did not continue to receive mails, but that post upgrade they are.
It's entirely possible we lost a local change in the upgrade.

I'm wondering if that (accepting mail for disabled queues) is an expected
behavior. And if so where the code that does the lookup actually lives.

Thanks in advance,
-- 
Aaron

Re: [rt-users] rt-mailgate and command by mail

[Albert Shih]

 Le 19/04/2011 à 10:03:43+0200, Albert Shih a écrit
> Hi all 
> 
> 
> I've exact same probleme as 
> 
>   
> http://www.mail-archive.com/rt-users@lists.bestpractical.com/msg08421.html
> 
> Do you've any news idea ?
> 

I don't fine a good solution, but find a «bad one» : 

Change this in TakeAction.pm : 

697c697
< my $ErrorsTo = RT->Config->Get('OwnerEmail');
---
> my $ErrorsTo = 
> RT::Interface::Email::ParseErrorsToAddressFromHead($args{'Message'}->head );

so the error-email is send to the admin of RT not to requestor (generally
the requestor don't understand anything about those error). 

Regards.

JAS

-- 
Albert SHIH
DIO batiment 15
Observatoire de Paris Meudon
5 Place Jules Janssen
92195 Meudon Cedex
Téléphone : 01 45 07 76 26/06 86 69 95 71
Heure local/Local time:
jeu 21 avr 2011 11:10:20 CEST

[rt-users] Rt-mailgate fails on emails from hotmail

[Michael Maxwell]

A little digging through the archives turned up some messages from 2000 or
so pertaining to this, but a solution remains forthcoming.

What we have:
RT 3.6.6
fetchmail pulling messages from our remote mail server via IMAP+SSL

So far, we've tested email for ticket creation and replies with various
different mail clients and source domains.  All have worked perfectly with
the exception of hotmail.

After doing a little detective work, I've traced it down to this function in
rt-mailgate:

my $r = $ua->post( $full_url, {%args} );

$ua is actually LWP::UserAgent's post() method.  So, I'm not sure if it's
really rt-mailgate itself that's to blame or if it's LWP::Useragent.

I turned on fetchmail's verbose option and pasted the relevant output below.
Domains have been replaced with "[DELETED]" for the purposes of this email.
Please note in particular the failure message returned by fetchmail:

An Error Occurred
=

500 Internal Server Error
fetchmail: MDA returned nonzero status 75
 not flushed

The end result is that tickets DO get created, but since rt-mailgate
apparently keeps trying to finish this transaction up until its default 180
second timeout, it keeps generating tickets.  So for ONE email sent from a
hotmail account, we'll end up with FIVE or so tickets (all identical).

If anyone has any tips on how to fix this, please let me know.  Thank you.


Fetchmail's verbose output posted below:


1 message for [EMAIL PROTECTED] at mail.[DELETED].com.
fetchmail: IMAP> A0006 FETCH 1 RFC822.SIZE
fetchmail: IMAP< * 1 FETCH (RFC822.SIZE 2440)
fetchmail: IMAP< A0006 OK FETCH completed.
fetchmail: IMAP> A0007 FETCH 1 RFC822.HEADER
fetchmail: IMAP< * 1 FETCH (RFC822.HEADER {1365}
reading message [EMAIL PROTECTED]:1 of 1 (1365 header
octets)
#
fetchmail: IMAP< )
fetchmail: IMAP< A0007 OK FETCH completed.
fetchmail: IMAP> A0008 FETCH 1 BODY.PEEK[TEXT]
fetchmail: IMAP< * 1 FETCH (BODY[TEXT] {1075}
 (1075 body octets) .***
fetchmail: IMAP< )
fetchmail: IMAP< A0008 OK FETCH completed.
An Error Occurred
=

500 Internal Server Error
fetchmail: MDA returned nonzero status 75
 not flushed
fetchmail: IMAP> A0009 LOGOUT
fetchmail: IMAP< * BYE Microsoft Exchange Server 2003 IMAP4rev1 server
version 6.5.7638.1 signing off.
fetchmail: IMAP< A0009 OK LOGOUT completed.
fetchmail: 6.2.5 querying mail.[DELETED].com (protocol IMAP) at Fri 30 May
2008 05:09:37 PM PDT: poll completed
fetchmail: normal termination, status 0



___
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

Re: [rt-users] [rt-mailgate] "--action comment" not commenting

[Tyler Knappe]

I would rather avoid upgrading at this time.  An upgrade is planned, but 
not at this time.  Plus this feature appears to have been working since 
at least RT 3.4.

http://wiki.bestpractical.com/view/UbuntuInstallGuide

One thing we noticed was that rt-mailgate defaults to correspond;

Note that C and C actions ignore message text if used
alone.  Include a  C or C action if you want RT
to record the incoming message.

The default action is C.

Jerrad, did you have to do anything special to your fetchmail setup to 
have mail correctly comment, other than the '--action comment'?

Also, how does rt-mailgate know which ticket to comment on?  Does it 
match the subject to an existing ticket?  If so, wouldn't things like 
'Re:' or 'Fwd:' break subject matching?  I can't seem to figure this out 
looking at the source code.

Thanks,
-Tyler

Jerrad Pierce wrote:
> On Wed, Aug 20, 2008 at 10:33, Tyler Knappe <[EMAIL PROTECTED] 
> > wrote:
>
> Hi all,
>
> I am running RT 3.6.3 using fetchmail to retrieve messages from
> our mail
> server. I have two email addresses setup to receive mail,
> [EMAIL PROTECTED]  and
> [EMAIL PROTECTED] .  Within the fetchmail
> config file [EMAIL PROTECTED]  correctly
> uses '--action correspond' to make a ticket within RT.  However, when
> sending mail to [EMAIL PROTECTED]  it doesn't
> seem to correctly use the
> '--action comment' to comment on tickets, rather it never comments and
> only corresponds, creating new tickets.
>
> Though rt-mailgate shows this:
>
> =item Action
>
> The action being performed. At the moment, it's one of "comment" or
> "correspond"
>
> I've isolated it to rt-mailgate, ruling out the mail server and
> fetchmail.  Any ideas?
>
> Upgrade? 3.8 works for me.
>
>
> -- 
> Cambridge Energy Alliance: Save money & the planet

-- 
Tyler Knappe  |  IT Assistant  |  VisionLink  |  First National Center  |  3101 
Iris Avenue, Suite 240  |  Boulder CO, 80301  |  303.402.0170 ext. 124 

___
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

[rt-users] RT-Mailgate hack to remove quoted replies

[Tom Lahti]

I am having an awful time with getting users to remove quoted text from
replies.  I've begun looking at rt-mailgate code to figure a way to remove
the " Original Message " and below it that Outlook creates when you
hit reply.

the write_down_message() function seems to either create a temp file or use
memory to take the message from STDIN.  I thought about stripping it down
during reading from STDIN but its being read in binmode 8k at a time, so the
" Original Message " might be broken across chunks.  So that won't work.

After write_down_message(), I could simply regex it into oblivion -- if its
in memory.  If its in the temp file... it doesn't seem like a scalable
solution to read the temp file and re-write it.  We've already written the
message to the temp file once.

What I'd like to do is go back to write_down_message() and look for the key
line, and do some sneaky read-ahead of a few bytes into the next buffer if
the end of the buffer _could_ be a broken "Original Message" line, and then
seek back to the beginning of that chunk if it isn't.

Finally,  I suspect that Outlook puts attachments after the body, in which
case an email reply that contains attachments would get the attachments
dropped unless I keep reading for a MIME boundary, in which case I have to
know what the boundary is in the first place, which means parsing the header.

Has anyone else done anything like this already, or am I venturing into
uncharted waters here?  Does my plan sound decent, or am I crazy for even
thinking of it?

-- 
-- 
   Tom Lahti
   BIT Statement LLC

   (425)251-0833 x 117
   http://www.bitstatement.net/
-- 
___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sa...@bestpractical.com


Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
Buy a copy at http://rtbook.bestpractical.com

Re: [rt-users] RT mailgate loop revisited - last chapter

[Kevin Falcone]

On Thu, Aug 12, 2010 at 12:37:01PM -0700, Kenneth Crocker wrote:
>The only thing I can figure is that one or more of the settings shown 
> above is causing RT to
>initiate a mail loop every 15 minutes. Does RT go to the incoming mail 
> server to look for
>"new" mail every 15 minutes? If so, why 15 minutes? Where does that 
> setting exist? Is there
>something in one of the settings above that tells RT to keep re-trying to 
> add this guy?

Kenn

RT does not query for new mail.  Your mail infrastructure does.

You have told RT to fail to create new users for people, make your
mail infrastructure respect that.

-kevin


pgpZ85iJ2pXqE.pgp
Description: PGP signature

RT Training in Washington DC, USA on Oct 25 & 26 2010
Last one this year -- Learn how to get the most out of RT!

Re: [rt-users] RT mailgate loop revisited - last chapter

[Kenneth Crocker]

Kevin,

OK. That settles it, then. I've *definitely* got to talk to our email
postmaster guys.

Thanks again for your time and patience.

Kenn
LBNL

On Tue, Aug 17, 2010 at 1:53 PM, Kevin Falcone wrote:

> On Thu, Aug 12, 2010 at 12:37:01PM -0700, Kenneth Crocker wrote:
> >The only thing I can figure is that one or more of the settings shown
> above is causing RT to
> >initiate a mail loop every 15 minutes. Does RT go to the incoming mail
> server to look for
> >"new" mail every 15 minutes? If so, why 15 minutes? Where does that
> setting exist? Is there
> >something in one of the settings above that tells RT to keep re-trying
> to add this guy?
>
> Kenn
>
> RT does not query for new mail.  Your mail infrastructure does.
>
> You have told RT to fail to create new users for people, make your
> mail infrastructure respect that.
>
> -kevin
>
>
> RT Training in Washington DC, USA on Oct 25 & 26 2010
> Last one this year -- Learn how to get the most out of RT!
>

RT Training in Washington DC, USA on Oct 25 & 26 2010
Last one this year -- Learn how to get the most out of RT!

[rt-users] rt-mailgate 302 Error. No, not Plack.

[Jourdan Perla]

Install of RT3.8 on Ubuntu 10.4 LTS.

I'm getting that pesky "302 Found" error as I'm trying to push mail into my 
queues using rt-mailqueue.

I've done the usual Googling and wiki hunts, and I've run out of options.
- Aliases are working fine, it's a rt-mailgate error.
- Plack is up to date (0.9985).
- There's no extra '/'. It's finding rt-mailgate fine.
- Not configured for SSL. That's on my to-do list, and if I need to bump that 
up, I will.

Command : /usr/bin/rt-mailgate --queue myqueue --action correspond --url 
http://myserver.com/rt -debug < test.msg
Output:
/usr/bin/rt-mailgate: temp file is '/tmp/TykSIIvN17'
/usr/bin/rt-mailgate: connecting to 
http://myserver.com/rt/REST/1.0/NoAuth/mail-gateway
An Error Occurred
=

302 Found

/usr/bin/rt-mailgate: undefined server error

Thoughts?

RT Training Sessions (http://bestpractical.com/services/training.html)
* Boston — March 5 & 6, 2012

Re: [rt-users] rt-mailgate problem - certificate verify failure ?

[Martin Drasar]

On 21.8.2012 15:59, Ethier, Michael wrote:
> Hello,
> 
>  
> 
> The rt-mailgate program acts differently between v 3.8.8 and v 4.0.6.
> The v 3.8.8 version works
> 
> fine using https, and even when I have v 4.0.6 running with the
> /etc/aliases point to the v 3.8.8 version of rtmailgate, email
> 
> get sent to the queue. But the v 4.0.6 version fails with certificate
> verify failed, output from mailq:
> 
>  
> 
> (temporary failure. Command output: An Error Occurred = 
> 500 Can't connect to testrt.rc.fas.harvard.edu:443 (certificate verify
> failed))
> 
>  r...@testrt.rc.fas.harvard.edu
> 
>  
> 
> Any ideas as to the verification of my RT/ssl setup,  on how to fix this
> ? Apparently the RT 4.0.6 is less forgiving about the ssl setup and config.
> 
> I ran RT configure with the --enable-ssl-mailgate option and installed
> all perl modules required with “make fixdeps” in RT 4.0.6.
> 
>  
> 
> Thanks,
> 
> Mike
> 
>  
> 
> This is in /etc/aliases:
> 
> # rt3
> 
> rt: "|/opt/rt-3.8.8/bin/rt-mailgate --queue 'General' --action
> correspond --url https://testrt.rc.fas.harvard.edu/";
> 
> rt-comment: "|/opt/rt-3.8.8/bin/rt-mailgate --queue 'General' --action
> comment --url https://testrt.rc.fas.harvard.edu/";
> 
>  
> 
> # rt4
> 
> #rt: "|/opt/rt4/bin/rt-mailgate --queue 'General' --ca-file
> /etc/pki/tls/certs/ca-bundle.crt --action correspond --url
> https://testrt.rc.fas.harvard.edu/";
> 
> #rt-comment: "|/opt/rt4/bin/rt-mailgate --queue 'General' --ca-file
> /etc/pki/tls/certs/ca-bundle.crt --action comment --url
> https://testrt.rc.fas.harvard.edu/";
> 

Hi Mike,

add this option to your aliases if you want to bypass certificate
validation: --no-verify-ssl

So your rt entry in /etc/aliases would look like this:

#rt: "|/opt/rt4/bin/rt-mailgate --queue 'General' --ca-file
/etc/pki/tls/certs/ca-bundle.crt --action correspond --url
https://testrt.rc.fas.harvard.edu/ --no-verify-ssl"

Martin

Re: [rt-users] rt-mailgate problem - certificate verify failure ?

[Ethier, Michael]

Hi Martin,

Thanks for the suggestion but if I enable --no-ssl I will be creating a security
vulnerability no ?

Thanks,
Mike

-Original Message-
From: rt-users-boun...@lists.bestpractical.com 
[mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Martin Drasar
Sent: Tuesday, August 21, 2012 10:11 AM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] rt-mailgate problem - certificate verify failure ?

On 21.8.2012 15:59, Ethier, Michael wrote:
> Hello,
> 
>  
> 
> The rt-mailgate program acts differently between v 3.8.8 and v 4.0.6.
> The v 3.8.8 version works
> 
> fine using https, and even when I have v 4.0.6 running with the 
> /etc/aliases point to the v 3.8.8 version of rtmailgate, email
> 
> get sent to the queue. But the v 4.0.6 version fails with certificate 
> verify failed, output from mailq:
> 
>  
> 
> (temporary failure. Command output: An Error Occurred 
> =
> 500 Can't connect to testrt.rc.fas.harvard.edu:443 (certificate verify
> failed))
> 
>  r...@testrt.rc.fas.harvard.edu
> 
>  
> 
> Any ideas as to the verification of my RT/ssl setup,  on how to fix 
> this ? Apparently the RT 4.0.6 is less forgiving about the ssl setup and 
> config.
> 
> I ran RT configure with the --enable-ssl-mailgate option and installed 
> all perl modules required with "make fixdeps" in RT 4.0.6.
> 
>  
> 
> Thanks,
> 
> Mike
> 
>  
> 
> This is in /etc/aliases:
> 
> # rt3
> 
> rt: "|/opt/rt-3.8.8/bin/rt-mailgate --queue 'General' --action 
> correspond --url https://testrt.rc.fas.harvard.edu/";
> 
> rt-comment: "|/opt/rt-3.8.8/bin/rt-mailgate --queue 'General' --action 
> comment --url https://testrt.rc.fas.harvard.edu/";
> 
>  
> 
> # rt4
> 
> #rt: "|/opt/rt4/bin/rt-mailgate --queue 'General' --ca-file 
> /etc/pki/tls/certs/ca-bundle.crt --action correspond --url 
> https://testrt.rc.fas.harvard.edu/";
> 
> #rt-comment: "|/opt/rt4/bin/rt-mailgate --queue 'General' --ca-file 
> /etc/pki/tls/certs/ca-bundle.crt --action comment --url 
> https://testrt.rc.fas.harvard.edu/";
> 

Hi Mike,

add this option to your aliases if you want to bypass certificate
validation: --no-verify-ssl

So your rt entry in /etc/aliases would look like this:

#rt: "|/opt/rt4/bin/rt-mailgate --queue 'General' --ca-file 
/etc/pki/tls/certs/ca-bundle.crt --action correspond --url 
https://testrt.rc.fas.harvard.edu/ --no-verify-ssl"

Martin

Re: [rt-users] rt-mailgate problem - certificate verify failure ?

[Martin Drasar]

On 21.8.2012 16:16, Ethier, Michael wrote:
> Hi Martin,
> 
> Thanks for the suggestion but if I enable --no-ssl I will be creating a 
> security
> vulnerability no ?
> 
> Thanks,
> Mike

Hi,

that's for sure. This was a suggestion for a development machine (the
name testrt.rc.fas.harvard.edu suggest that it is).

If you want to avoid this step then you have to have a valid certificate
for testrt.rc.fas.harvard.edu signed by a certificate authority that is
in the ca bundle you are passing to rt-mailgate.

Martin

Re: [rt-users] rt-mailgate problem - certificate verify failure ?

[Thomas Sibley]

On 08/21/2012 08:03 AM, Martin Drasar wrote:
> If you want to avoid this step then you have to have a valid certificate
> for testrt.rc.fas.harvard.edu signed by a certificate authority that is
> in the ca bundle you are passing to rt-mailgate.

Martin's referring to the --ca-file argument you can pass.

You can also simply make sure to put your CA root cert used for signing
into /etc/ssl/certs/ or your system's equivalent.

See `perldoc bin/rt-mailgate` for more info.

Re: [rt-users] rt-mailgate and web based authentication

[Martin Wheldon]

Hi Tom,

Sounds like you may missing a Location section from your apache config. 
Something like...



   Order Allow,Deny
   Allow from 127.0.0.1


Best Regards

Martin Wheldon

On 2013-01-16 16:38, Thomas  Misilo wrote:

Hi,

I am switched from using LDAP to CAS for authentication, and now
because it redirects to the login screen, mailgate isn't working. I
was wondering if anyone had a workaround or solution to this?

Thanks,

Tom

 !DSPAM:9,50f6cf2333231759512251!

[rt-users] rt-mailgate Unknown encoding 'charset="utf-8"'

[charlyc...@yahoo.com.ar]

Hi,

I've been running rt-mailgate to download my emails and today I started getting 
this error message on the fetchmail log.

RT server error.

The RT server which handled your email did not behave as expected. It
said:

Unknown encoding 'charset="utf-8"' at /data/rt4/sbin/../lib/RT/I18N.pm line 542.

Stack:
  [/usr/local/share/perl5/Carp.pm:100]
  [/usr/local/lib64/perl5/Encode.pm:188]
  [/data/rt4/sbin/../lib/RT/I18N.pm:542]
  [/data/rt4/sbin/../lib/RT/I18N.pm:214]
  [/data/rt4/sbin/../lib/RT/I18N.pm:210]
  [/data/rt4/sbin/../lib/RT/EmailParser.pm:282]
  [/data/rt4/sbin/../lib/RT/Interface/Email.pm:1433]
  [/data/rt4/share/html/REST/1.0/NoAuth/mail-gateway:61]



This is my configuration on the RT_Config.pm:

    Set(@EmailInputEncodings, qw(utf-8 iso-8859-1 us-ascii));


There is no configuration for this parameter on the RT_SiteConfig.pm.

RT Version: 4.0.8


Do you know why this might happen?

Thank you, Charly

[rt-users] rt-mailgate on different server than RT

[Matt Nichols]

Hello,

 

Is it possible to run rt-mailgate on a separate server than
RT? I’d like to run rt-mailgate on our mail server and have it talk to
the RT server. How is rt-mailgate on the mail server going to know how to
authenticate to the RT web interface in order to comment on tickets? Can I
create an rt-mailgate config somewhere with a username and password for it to
use when connecting to the RT web interface? 

 

 






___
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


We're hiring! Come hack Perl for Best Practical: 
http://bestpractical.com/about/jobs.html

Re: [rt-users] rt-mailgate ignoring --no-verify-ssl?

[Aaron C. de Bruyn]

Fixed it.  Apparently --no-verify-ssl only deals with the hostname on
the certificate.

I added the following to the 'use' section at the top of rt-mailgate:

use IO::Socket::SSL;

and then in the get_useragent function, I added the following ssl_opts line:

$ua->ssl_opts( SSL_verify_mode => IO::Socket::SSL::SSL_VERIFY_NONE );

Now my legitimately signed wildcard cert (*.mydomain.tld) doesn't
error out because of a bad hostname, or an untrusted cert in the
middle of the chain.

-A



On Wed, Apr 29, 2015 at 9:01 PM, Aaron C. de Bruyn  wrote:
> Mailgate has been driving me nuts.  I downloaded 4.2.10 and set it up
> on a bright, shiny new server.
>
> I'm running fetchmail on my RT box using the following to send tickets to RT:
>
> poll mail.mydomain.tld with protocol pop3
>username engineering password -redacted- mda
> "/opt/rt4/bin/rt-mailgate --no-verify-ssl --queue engineering --action
> correspond --url https://tickets.mydomain.tld --debug"
>
> Fetchmail complains about the MDA erroring out.  Increasing fetchmail
> debugging shows:
>
> fetchmail: about to deliver with: /opt/rt4/bin/rt-mailgate
> --no-verify-ssl --queue engineering --action correspond --url
> https://tickets.mydomain.tld/ --debug
> #***/opt/rt4/bin/rt-mailgate: temp file is '/tmp/Ax6Or2dgc1/23FBulXCfc'
> /opt/rt4/bin/rt-mailgate: connecting to
> https://tickets.mydomain.tld//REST/1.0/NoAuth/mail-gateway
> HTTP request failed: 500 Can't connect to tickets.mydomain.tld:443
> (certificate verify failed). Your webserver logs may have more
> information or there may be a network problem.
>
> /opt/rt4/bin/rt-mailgate: undefined server error
> fetchmail: MDA returned nonzero status 75
>  not flushed
> fetchmail: POP3> QUIT
>
>
> I even get an SSL error when running from the command line:
>
> root@tickets:/opt# /opt/rt4/bin/rt-mailgate --no-verify-ssl --queue
> engineering --action correspond --url https://tickets.mydomain.tld/
> --debug
> test 
> /opt/rt4/bin/rt-mailgate: temp file is '/tmp/9vlYhx9C9X/kI4IQo0RRw'
> /opt/rt4/bin/rt-mailgate: connecting to
> https://tickets.mydomain.tld//REST/1.0/NoAuth/mail-gateway
> HTTP request failed: 500 Can't connect to tickets.mydomain.tld:443
> (certificate verify failed). Your webserver logs may have more
> information or there may be a network problem.
>
> /opt/rt4/bin/rt-mailgate: undefined server error
> root@tickets:/opt#
>
> It's acting like it's ignoring --no-verify-ssl.
>
> Am I missing something?
>
> Thanks,
>
> -A

Re: [rt-users] rt-mailgate needs http for comment

[Alex Vandiver]

On Sat, Sep 05, 2015 at 11:22:48PM -0700, Joseph D. Wagner wrote:
> I had apache set to allow rt over https only.  Trying over http would fail.
> 
> rt-mailgate was working perfectly fine over https when using
> "--action correspond".  However, when using "--action comment", it
> fails saying it is unable to connect.
>
> When I changed my apache configuration to allow http on local
> connections, it started working.
> 
> I suspect there is some code in the comment path of rt-mailgate that
> is forcing it over the http connection, rather than properly
> deriving the connection from the url parameter.
> 
> Being new to rt, I am open to the possibility I misconfigured
> something.  Is anyone else able to reproduce this?

I strongly suspect misconfiguration in your /etc/aliases.  The only
difference between correspond and comment paths is the value of a
query parameter that they POST:

https://github.com/bestpractical/rt/blob/stable/bin/rt-mailgate.in#L168-L170

Check to make sure that you have https:// on all of your aliases, and
that you've run newaliases (or equivalent) after updating them.
 - Alex

Re: [rt-users] rt-mailgate needs http for comment

[Joseph D. Wagner]

Here it is.  I left everything intact except the url.

prc:"|/usr/bin/rt-mailgate --queue 'Performance Review' 
--action correspond --url https://./rt";
prc-staff:  "|/usr/bin/rt-mailgate --queue 'Performance Review' 
--action comment--url https://./rt";


Joe

On 09/05/2015 11:32 PM, Alex Vandiver wrote:

On Sat, Sep 05, 2015 at 11:22:48PM -0700, Joseph D. Wagner wrote:

I had apache set to allow rt over https only.  Trying over http would fail.

rt-mailgate was working perfectly fine over https when using
"--action correspond".  However, when using "--action comment", it
fails saying it is unable to connect.

When I changed my apache configuration to allow http on local
connections, it started working.

I suspect there is some code in the comment path of rt-mailgate that
is forcing it over the http connection, rather than properly
deriving the connection from the url parameter.

Being new to rt, I am open to the possibility I misconfigured
something.  Is anyone else able to reproduce this?

I strongly suspect misconfiguration in your /etc/aliases.  The only
difference between correspond and comment paths is the value of a
query parameter that they POST:

 
https://github.com/bestpractical/rt/blob/stable/bin/rt-mailgate.in#L168-L170

Check to make sure that you have https:// on all of your aliases, and
that you've run newaliases (or equivalent) after updating them.
  - Alex

Re: [rt-users] rt-mailgate needs http for comment

[Alex Vandiver]

On Sun, Sep 06, 2015 at 12:31:28AM -0700, Joseph D. Wagner wrote:
> Here it is.  I left everything intact except the url.
> [snip]

Those look fine.  Double-check that you have not multiply-defined
prc-staff elsewhere in aliases, and that you've run `newaliases`.
Short of that, my only suggestion is to turn on bug logging in your
MTA -- I can say with certainty that rt-mailgate doesn't deal
differently with correspond vs comment and http/https connections.
 - Alex

Re: [rt-users] rt-mailgate needs http for comment

[Joseph D. Wagner]

Ok, I'm inching closer.  I found out that it works if I run it from the 
command line, but not when sendmail fires it off.  (This probably gave 
me the false sense that it worked by switching to HTTP.)


I turned on debug level logging in RT.  It logged a bunch of stuff when 
run from the command line, but it didn't log anything when sendmail did it.


Joseph D. Wagner

Re: [rt-users] rt-mailgate needs http for comment

[Joseph D. Wagner]

Figured it out.  I created a catch-all address in virtusertable. Unknown 
to me, virtusertable gets processed before aliases, so it was hitting 
the catch-all and never made it to aliases.


Joseph D. Wagner

On 09/06/2015 12:13 PM, Alex Vandiver wrote:

On Sun, Sep 06, 2015 at 12:31:28AM -0700, Joseph D. Wagner wrote:

Here it is.  I left everything intact except the url.
[snip]

Those look fine.  Double-check that you have not multiply-defined
prc-staff elsewhere in aliases, and that you've run `newaliases`.
Short of that, my only suggestion is to turn on bug logging in your
MTA -- I can say with certainty that rt-mailgate doesn't deal
differently with correspond vs comment and http/https connections.
  - Alex

[rt-users] rt-mailgate in lab environment stopped working

[Cena, Stephen (ext. 300)]

I've been beating my head against this for days now and can't figure this out. 
I original had (as much as possible) a clone of our production environment in a 
lab. I reached a point where I was forced to re-IP the lab environment which 
went well. Now, rt-mailgate simply doesn't work. Outbound mail does work 
(postfix). If I use the /etc/aliases file for commands like I usually to, 
fetchmail attempts to contact an SMTP server for local delivery. If I actually 
embed the rt-mailgate command inside fetchmailrc I now get "http request 
failed: 500 can't connect to SERVER:80. Web server logs may have more info". I 
can't find anything.

I've put in a new mail server to see if that was the issue, but I simply cannot 
get the lab server to pick up mail anymore. As far as I can tell, DNS is 
functioning properly. What am I missing?

Stephen Cena
Senior Systems Administrator
Quality Vision International, Inc.
Phone: (585) 544-0450 x300
To notify helpdesk: http://helpdesk.ogp.qvii.com or email: 
hd-gene...@qvii.com
To report email issues: postmas...@qvii.com

[rt-users] rt-mailgate in lab environment stopped working

[Cena, Stephen (ext. 300)]

Thomas - You are correct. It wouldn't be so bad if the RT site wasn't working. 
If I use the exact same address I use for the web server in the rt-mailgate 
scripts it fails. If I put that address into a web browser, I can use the 
system as expected. I'm trying to figure out what the "disconnect" is now 
between rt-mailgate and the server.


Well, that error message is pretty clear ? when fetchmail tries to spawn 
rt-mailgate, that process can?t connect to RT.

You should replace SERVER:80 in your fetchmailrc with the URL you?re using to 
connect  to RT in your browser.


HTH,

Thoomas

-- next part --

Re: [rt-users] rt-mailgate, --queue extension and disabled queues

[Kevin Falcone]

On Mon, Mar 28, 2011 at 11:48:32AM +0200, Aaron Ross wrote:
>Hi all,
>Our users are reporting that before we upgraded to 3.8.8 queues that were 
> disabled did not
>continue to receive mails, but that post upgrade they are. It's entirely 
> possible we lost a
>local change in the upgrade.
>I'm wondering if that (accepting mail for disabled queues) is an expected 
> behavior. And if so
>where the code that does the lookup actually lives.

As far as I know, you've always been able to create tickets in
disabled Queues.  Someone 'fixed' that early in 3.8.x but it breaks
Approvals so it was changed back.  You can probably git blame it to
find the details.

-kevin


pgp2HruovKdUr.pgp
Description: PGP signature

[rt-users] rt-mailgate and [EMAIL PROTECTED] with selfsigned certificate

[Stefan Oeser - emendis GmbH]

Hello,

  I ran into problems with setting up RT3 on https. I configured some 
Ticket-Transaction via Mail in RT3.
With http-Protocol, all things work fine, but rt-mailgate has some troubles 
with the httpS-Protocol. I always get
an Error: "Connection refused". All needed modules (Crypt::SSLeay) are 
installed. Is it possible, that there are
some difficulties with the selfsigned certificate?

Using a browser to enter my RT3, I need to accept some Popup-Windows and accept 
the certificate manually,
perhaps, rt-mailgate doesn't accept the certificate automatically, which 
results in the mentioned error??

I would be very grateful for some help  :)
Best regards,
Stefan Oeser

___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:

If you sign up for a new RT support contract before December 31, we'll take
up to 20 percent off the price. This sale won't last long, so get in touch 
today. 
Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745.


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

Re: [rt-users] RT-Mailgate hack to remove quoted replies

[Adam Clarke]

On 04/04/2009, at 6:16 AM, Tom Lahti wrote:

> I am having an awful time with getting users to remove quoted text  
> from
> replies.  I've begun looking at rt-mailgate code to figure a way to  
> remove
> the " Original Message " and below it that Outlook creates  
> when you
> hit reply.
>
> the write_down_message() function seems to either create a temp file  
> or use
> memory to take the message from STDIN.  I thought about stripping it  
> down
> during reading from STDIN but its being read in binmode 8k at a  
> time, so the
> " Original Message " might be broken across chunks.  So that  
> won't work.
>
> After write_down_message(), I could simply regex it into oblivion --  
> if its
> in memory.  If its in the temp file... it doesn't seem like a scalable
> solution to read the temp file and re-write it.  We've already  
> written the
> message to the temp file once.
>
> What I'd like to do is go back to write_down_message() and look for  
> the key
> line, and do some sneaky read-ahead of a few bytes into the next  
> buffer if
> the end of the buffer _could_ be a broken "Original Message" line,  
> and then
> seek back to the beginning of that chunk if it isn't.
>
> Finally,  I suspect that Outlook puts attachments after the body, in  
> which
> case an email reply that contains attachments would get the  
> attachments
> dropped unless I keep reading for a MIME boundary, in which case I  
> have to
> know what the boundary is in the first place, which means parsing  
> the header.

I don't think it is crazy to want to solve the problem but I suspect  
you would regret the method by which you are considering solving it.

I haven't tried this, but if I were going to I would do it on  
retrieval and display rather than by altering the message on the way  
in. That way when it turns out your parsing is imperfect you haven't  
damaged the original and you might even offer the user a way to  
recover by peeking at the original.

Cheers
--
Adam Clarke
www.strategicdata.com.au


___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sa...@bestpractical.com


Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
Buy a copy at http://rtbook.bestpractical.com

Re: [rt-users] RT-Mailgate hack to remove quoted replies

[Jerrad Pierce]

> in. That way when it turns out your parsing is imperfect you haven't
> damaged the original and you might even offer the user a way to
> recover by peeking at the original.
More specifically, I'd recommend doing it the same way RT handles
letting users see the outgoing messages. Don't show it on Display.html,
but do on History.html.

Incidentally, if you manage to get a robust version of this working I'd
be interested in adopting it too.

-- 
Cambridge Energy Alliance: Save money. Save the planet.
___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sa...@bestpractical.com


Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
Buy a copy at http://rtbook.bestpractical.com

Re: [rt-users] RT-Mailgate hack to remove quoted replies

[Gary Greene]

There are a number of interesting mods that I've noted he's working on that I'm 
interested in. (For instance the scrip changes to enforce only requesters can 
change the ticket's status, etc.

--
Gary L. Greene, Jr.
IT Operations
Minerva Networks, Inc.
Tel:  (408) 240-1239
Cell: (650) 704-6633
 

> -Original Message-
> From: rt-users-boun...@lists.bestpractical.com 
> [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf 
> Of Jerrad Pierce
> Sent: Monday, April 06, 2009 12:00 PM
> To: Tom Lahti; rt-users Users
> Subject: Re: [rt-users] RT-Mailgate hack to remove quoted replies
> 
> > in. That way when it turns out your parsing is imperfect you haven't
> > damaged the original and you might even offer the user a way to
> > recover by peeking at the original.
> More specifically, I'd recommend doing it the same way RT handles
> letting users see the outgoing messages. Don't show it on 
> Display.html,
> but do on History.html.
> 
> Incidentally, if you manage to get a robust version of this 
> working I'd
> be interested in adopting it too.
> 
> -- 
> Cambridge Energy Alliance: Save money. Save the planet.
> ___
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> 
> Community help: http://wiki.bestpractical.com
> Commercial support: sa...@bestpractical.com
> 
> 
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
> Buy a copy at http://rtbook.bestpractical.com
> 
___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sa...@bestpractical.com


Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
Buy a copy at http://rtbook.bestpractical.com

Re: [rt-users] RT-Mailgate hack to remove quoted replies

[Tom Lahti]

Gary Greene wrote:
> There are a number of interesting mods that I've noted he's working on
> that I'm interested in. (For instance the scrip changes to enforce only
> requesters can change the ticket's status, etc.

Actually, I accomplished that with just scrips.  And then I convinced
ownership it was a bad idea, because it meant that people working on tickets
could no longer use their ticket list as a "to-do" list, and it wasn't
really needed because a requestor can always re-open a resolved ticket by
just replying to the email.

They were actually trying to solve another issue where a requestor was not
notified when a ticket was resolved.  That's what happens when owners try to
play systems analyst without telling the engineers what the actual problem
is and just try to ask for what they think the best solution would be instead.

However, if you're dying for it all you have to do it apply a scrip to
condition "On Resolve" with action prep:

return 1;

and action cleanup:

return 1 if $self->TransactionObj->IsInbound;
$self->TicketObj->_Set(Field => 'Status', Value => 'open', RecordTransaction
=> 0);
return 1;

And then, when someone other than a requestor resolves a ticket, the cleanup
code sets it back to open. The IsInbound method of the Transaction object
returns true if the transaction was generated by a requestor.

Then you just do the same thing in reverse for conditions that generate
'resolved' emails so you aren't sending out an email when a non-requestor
tries to resolve.  I tried playing around with template code to send
different emails whether it was a requestor or not (Dear requestor, XXX
would like you to resolve ticket YYY), but Text::Template parsing is rather
limited and it never worked the way I wanted it to.  Notably, you can't have
a conditional (like an 'if' statement) span blocks.


-- 
-- 
   Tom Lahti
   BIT Statement LLC

   (425)251-0833 x 117
   http://www.bitstatement.net/
-- 
___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sa...@bestpractical.com


Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
Buy a copy at http://rtbook.bestpractical.com

Re: [rt-users] rt-mailgate undefined server error for only

[Jon Baker]

Thanks, Kevin -

I did run the make testdeps and have the following missing dependencies:

SOME DEPENDENCIES WERE MISSING.
FASTCGI missing dependencies:
CGI::Fast...MISSING
FCGI...MISSING
SQLITE missing dependencies:
DBD::SQLite >= 1.00...MISSING

I'm not using Fast CGI or SQL Lite, so I didn't have those installed.   
I installed DBD::SQLite but am unable to get the CGI::Fast/FCGI to go  
away (I installed fcgi via yum and also attempted to install CGI::Fast  
via cpan but cpan told me it was installed and up to date)  After  
restarting the server after installing SQLite there was no change.

The message in question is very simple - it's a mixed html/text  
message coming from Outlook with the subject "Test" and a signature in  
the body.

On Jun 16, 2009, at 4:33 PM, rt-users-requ...@lists.bestpractical.com  
wrote:

> If you want to check your module versions, you can use make testdeps
> from an RT tarball
>
>> If I set the timeout to 600 then it does seem to go through sometimes
>> - but I know that letting it take 10 minutes implies there's a deeper
>> problem somewhere, I'm hoping someone can point me in the right
>> direction to get this solved.
>
> This sounds like you either have a very large attachment or very
> complex message, but without seeing the contents of the message
> its hard to guess.
>
>> We updated to FC11 from FC10 on Friday, if that matters, although I
>> have a separate system that is also running RT that I'm able to send
>> the same message into without issue (I have successfully caught the
>> raw message and am able to attempt to send it through rt-mailgate via
>> the command line)
>
> I would look at the dep checking mentioned above first, as FC probably
> messed with your perl and module versions
>
> -kevin

-- 
Jon Baker
Information Technology
Willie George Ministries
1003 N 129th E Ave
Tulsa OK 74116
(918) 234-5656


___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sa...@bestpractical.com


Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
Buy a copy at http://rtbook.bestpractical.com

Re: [rt-users] rt-mailgate undefined server error for only

[Ruslan Zakirov]

Run ./configure with proper set of options. SQLite and FastCGI are not
required if you don't use them.

On Wed, Jun 17, 2009 at 1:52 AM, Jon Baker wrote:
> Thanks, Kevin -
>
> I did run the make testdeps and have the following missing dependencies:
>
> SOME DEPENDENCIES WERE MISSING.
> FASTCGI missing dependencies:
>        CGI::Fast...MISSING
>        FCGI...MISSING
> SQLITE missing dependencies:
>        DBD::SQLite >= 1.00...MISSING
>
> I'm not using Fast CGI or SQL Lite, so I didn't have those installed.
> I installed DBD::SQLite but am unable to get the CGI::Fast/FCGI to go
> away (I installed fcgi via yum and also attempted to install CGI::Fast
> via cpan but cpan told me it was installed and up to date)  After
> restarting the server after installing SQLite there was no change.
>
> The message in question is very simple - it's a mixed html/text
> message coming from Outlook with the subject "Test" and a signature in
> the body.
>
> On Jun 16, 2009, at 4:33 PM, rt-users-requ...@lists.bestpractical.com
> wrote:
>
>> If you want to check your module versions, you can use make testdeps
>> from an RT tarball
>>
>>> If I set the timeout to 600 then it does seem to go through sometimes
>>> - but I know that letting it take 10 minutes implies there's a deeper
>>> problem somewhere, I'm hoping someone can point me in the right
>>> direction to get this solved.
>>
>> This sounds like you either have a very large attachment or very
>> complex message, but without seeing the contents of the message
>> its hard to guess.
>>
>>> We updated to FC11 from FC10 on Friday, if that matters, although I
>>> have a separate system that is also running RT that I'm able to send
>>> the same message into without issue (I have successfully caught the
>>> raw message and am able to attempt to send it through rt-mailgate via
>>> the command line)
>>
>> I would look at the dep checking mentioned above first, as FC probably
>> messed with your perl and module versions
>>
>> -kevin
>
> --
> Jon Baker
> Information Technology
> Willie George Ministries
> 1003 N 129th E Ave
> Tulsa OK 74116
> (918) 234-5656
>
>
> ___
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> Community help: http://wiki.bestpractical.com
> Commercial support: sa...@bestpractical.com
>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com
>



-- 
Best regards, Ruslan.
___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sa...@bestpractical.com


Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
Buy a copy at http://rtbook.bestpractical.com

[rt-users] RT-Mailgate + Postfix on SLES10 Not Receiving Mail

[Victor Gehring]

Greetings,

After many hours scouring around the globe for answers, I have feel I have 
gathered enough diagnostic info to post my issue.  The RT server is up and 
sending mail via a relay fine.  I have configured RT with the recommended 
groups/perms and am able to create tx fine and such.  I have fiddled around 
with the aliases file, postfix's main.conf and apache2's vhost.conf until my 
eyes are bleeding, always restarting postfix, apache and running newaliases 
after each change/test msg.  After application of many good tips found, the RT 
server still refuses to accept mail.  Below is a sanitized section of the 
/var/log/mail.info log seemingly indicating that the message is bounced due to 
'unknown user'.  Of the many things I am not certain of, the docs indicate that 
a user must be created that is associated to the rt-mailgate script - but I am 
not sure how this needs to be done.  When replying to a tx, the bounced message 
will be returned to the sender ok.  I am decidedly stumped.  Can anyone point 
me in the right direction?

Oct 29 18:17:34 dt-rt postfix/smtpd[7118]: connect from 
exchange07.xxx.com[10.0.1.190]
Oct 29 18:17:34 dt-rt postfix/smtpd[7118]: ED9E318235: 
client=exchange07.xxx.com[10.0.1.190]
Oct 29 18:17:34 dt-rt postfix/cleanup[7121]: ED9E318235: 
message-id=
Oct 29 18:17:34 dt-rt postfix/qmgr[7108]: ED9E318235: 
from=, size=2574, nrcpt=1 (queue active)
Oct 29 18:17:34 dt-rt postfix/smtpd[7118]: disconnect from 
exchange07.yyy.com[10.0.1.190]
Oct 29 18:17:35 dt-rt postfix/local[7122]: ED9E318235: 
to=http://10.0.1.6/@dt-rt.yyy.com>, orig_to=, 
relay=local, delay=1, status=bounced (unknown user: 
"???/opt/rt3/bin/rt???mailgate ??queue general ??action correspond 
??url http://10.0.1.6/";)
Oct 29 18:17:35 dt-rt postfix/cleanup[7121]: 04E1F18239: 
message-id=<20091029221735.04e1f18...@dt-rt.yyy.com>
Oct 29 18:17:35 dt-rt postfix/qmgr[7108]: 04E1F18239: from=<>, size=4787, 
nrcpt=1 (queue active)
Oct 29 18:17:35 dt-rt postfix/qmgr[7108]: ED9E318235: removed

BTW - NOT running any virtual mail hosts that would interfere with the alaias 
pipe directive.
Also, the server is able to resolve its own url on the local browser.

RT 3.8.3. Postfix 2.2.9. mod_perl 2.02, SLES10SP2, apache2

Best regards,

Victor

___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sa...@bestpractical.com


Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
Buy a copy at http://rtbook.bestpractical.com

[rt-users] rt-mailgate/fetchmailrc question: email not leaving inbox

[Mauricio Tavares]

I have been using rt-mailgate and fetchmailrc to retrieve support emails 
from our mail server and feed them to RT. My /etc/fetchmailrc looks like 
this:


set syslog;
set daemon 20;

poll "mail.domain.com"
with protocol imap
username rt password weak
mda "/usr/bin/perl /usr/bin/rt-mailgate --url https://localhost/ \
--queue support --action correspond"

Usually, after fetchmail grabs the new mail and feeds it to rt-mailgate, 
the email leaves the rt inbox in the mail server. Well, since last 
afternoon it has not been doing that. The email is still being send to 
rt and becomes a ticket (or a followup to one) but it just now stays in 
the inbox as new mail.


Any suggestions?

RT Training in Washington DC, USA on Oct 25 & 26 2010
Last one this year -- Learn how to get the most out of RT!

Re: [rt-users] rt-mailgate 302 Error. No, not Plack.

[Kevin Falcone]

On Fri, Feb 24, 2012 at 08:54:00PM +, Jourdan Perla wrote:
>Install of RT3.8 on Ubuntu 10.4 LTS.
>I'm getting that pesky "302 Found" error as I'm trying to push mail into 
> my queues using
>rt-mailqueue.
>I've done the usual Googling and wiki hunts, and I've run out of options.
>- Aliases are working fine, it's a rt-mailgate error.
>- Plack is up to date (0.9985).
>- There's no extra '/'. It's finding rt-mailgate fine.
>- Not configured for SSL. That's on my to-do list, and if I need to bump 
> that up, I will.
>Command : /usr/bin/rt-mailgate --queue myqueue --action correspond --url
>http://myserver.com/rt -debug < test.msg
>Output:
>/usr/bin/rt-mailgate: temp file is '/tmp/TykSIIvN17'
>/usr/bin/rt-mailgate: connecting to 
> http://myserver.com/rt/REST/1.0/NoAuth/mail-gateway
>An Error Occurred
>=
>302 Found
>/usr/bin/rt-mailgate: undefined server error
>Thoughts?

What's in the RT logs.

What's your test.msg.

Also, Plack is only used in RT4

-kevin


pgpSqpmOCG7a2.pgp
Description: PGP signature

RT Training Sessions (http://bestpractical.com/services/training.html)
* Boston — March 5 & 6, 2012

Re: [rt-users] rt-mailgate 302 Error. No, not Plack.

[Kevin Falcone]

Please - keep list replies on the list.

On Fri, Feb 24, 2012 at 10:24:52PM +, Jourdan Perla wrote:
> Fixed it. I was missing an Auth exclusion for the /REST/1.0/NoAuth
> directory 
> 
> As for the RT logs, can't find them. And can't find out where they're
> configured.

Search in RT_Config.pm for the various Log config options and check
their documentation.  Then see what you have in your RT_SiteConfig.pm

-kevin

> 
> On 2/24/12 2:15 PM, "Kevin Falcone"  wrote:
> 
> >On Fri, Feb 24, 2012 at 08:54:00PM +, Jourdan Perla wrote:
> >>Install of RT3.8 on Ubuntu 10.4 LTS.
> >>I'm getting that pesky "302 Found" error as I'm trying to push mail
> >>into my queues using
> >>rt-mailqueue.
> >>I've done the usual Googling and wiki hunts, and I've run out of
> >>options.
> >>- Aliases are working fine, it's a rt-mailgate error.
> >>- Plack is up to date (0.9985).
> >>- There's no extra '/'. It's finding rt-mailgate fine.
> >>- Not configured for SSL. That's on my to-do list, and if I need to
> >>bump that up, I will.
> >>Command : /usr/bin/rt-mailgate --queue myqueue --action correspond
> >>--url
> >>http://myserver.com/rt -debug < test.msg
> >>Output:
> >>/usr/bin/rt-mailgate: temp file is '/tmp/TykSIIvN17'
> >>/usr/bin/rt-mailgate: connecting to
> >>http://myserver.com/rt/REST/1.0/NoAuth/mail-gateway
> >>An Error Occurred
> >>=
> >>302 Found
> >>/usr/bin/rt-mailgate: undefined server error
> >>Thoughts?
> >
> >What's in the RT logs.
> >
> >What's your test.msg.
> >
> >Also, Plack is only used in RT4
> >
> >-kevin
> >
> >RT Training Sessions (http://bestpractical.com/services/training.html)
> >* Boston — March 5 & 6, 2012
> 


pgp6lmZa2VEc3.pgp
Description: PGP signature

RT Training Sessions (http://bestpractical.com/services/training.html)
* Boston — March 5 & 6, 2012

Re: [rt-users] rt-mailgate 302 Error. No, not Plack.

[Jourdan Perla]

> Please - keep list replies on the list.

Sorry, will do.

Thought I had this licked, but now as I build a *clean* production image, I'm 
running into the same error again..

$ cat mbox | /usr/bin/rt-mailgate --queue general --action correspond --url 
http://rt.myserver.com /rt -debug
/usr/bin/rt-mailgate: temp file is '/tmp/Dm_pceG62x'
/usr/bin/rt-mailgate: connecting to 
http://rt.myserver.com/rt/REST/1.0/NoAuth/mail-gateway
An Error Occurred
=

302 Found

/usr/bin/rt-mailgate: undefined server error

Grep all my logs for what happens at the same time and
apache2/access.log:
rt.myserver.com - - [14/Mar/2012:14:05:33 -0700] "POST 
/rt/REST/1.0/NoAuth/mail-gateway HTTP/1.1" 302 715 "-" "libwww-perl/6.04"
mail.info:
Mar 14 14:05:33 RT-PROD-SVR postfix/qmgr[4393]: 17286120B94: 
from=, size=7604, nrcpt=1 (queue active)
mail.info:
Mar 14 14:05:33 RT-PROD-SVR postfix/local[29538]: 88DCB1207CF: 
to=http://rt.myserver.com/REST/1.0/NoAuth/mail-gateway An Error 
Occurred =  302 Found  /usr/bin/rt-mailgate: undefined server 
error )

rt3.log shows nothing but:
[Wed Mar 14 15:56:08 2012] [error]: gpg: error reading key: secret key not 
available (/usr/share/request-tracker3.8/lib/RT/Crypt/GnuPG.pm:2078)
Which is from earlier.

/etc/aliases:
# See man 5 aliases for format
postmaster:myroot
help:  "|/usr/bin/rt-mailgate --queue general --action correspond --url 
http://rt.myserver.com/rt -debug"
comment: "|/usr/bin/rt-mailgate --queue general --action comment --url 
http://rt.myserver.com/rt -debug"


I've got the following in my httpd.conf


   AllowOverRide None
   Satisfy Any


   AllowOverRide None
   Allow from all
   Satisfy Any


   Order allow,deny
   Allow from all
   Satisfy Any


   Order allow,deny
   Allow from all
   Satisfy Any


Logging options in RT_SiteConfig.d
## Logging Options
# From lowest to highest priority, the levels are:
#  debug info notice warning error critical alert emergency
Set($LogToSyslog, 'info');
Set($LogToScreen, 'warning');
# log to /var/log/rt3.log
Set($LogToFile, 'debug');
Set($LogDir, '/var/log');
Set($LogToFileNamed , "rt3.log");


On Fri, Feb 24, 2012 at 10:24:52PM +, Jourdan Perla wrote:
> Fixed it. I was missing an Auth exclusion for the /REST/1.0/NoAuth 
> directory
> 
> As for the RT logs, can't find them. And can't find out where they're 
> configured.

Search in RT_Config.pm for the various Log config options and check their 
documentation.  Then see what you have in your RT_SiteConfig.pm

-kevin

> 
> On 2/24/12 2:15 PM, "Kevin Falcone"  wrote:
> 
> >On Fri, Feb 24, 2012 at 08:54:00PM +, Jourdan Perla wrote:
> >>Install of RT3.8 on Ubuntu 10.4 LTS.
> >>I'm getting that pesky "302 Found" error as I'm trying to push 
> >>mail into my queues using
> >>rt-mailqueue.
> >>I've done the usual Googling and wiki hunts, and I've run out of 
> >>options.
> >>- Aliases are working fine, it's a rt-mailgate error.
> >>- Plack is up to date (0.9985).
> >>- There's no extra '/'. It's finding rt-mailgate fine.
> >>- Not configured for SSL. That's on my to-do list, and if I need 
> >>to bump that up, I will.
> >>Command : /usr/bin/rt-mailgate --queue myqueue --action 
> >>correspond --url
> >>http://myserver.com/rt -debug < test.msg
> >>Output:
> >>/usr/bin/rt-mailgate: temp file is '/tmp/TykSIIvN17'
> >>/usr/bin/rt-mailgate: connecting to 
> >>http://myserver.com/rt/REST/1.0/NoAuth/mail-gateway
> >>An Error Occurred
> >>=
> >>302 Found
> >>/usr/bin/rt-mailgate: undefined server error
> >>Thoughts?
> >
> >What's in the RT logs.
> >
> >What's your test.msg.
> >
> >Also, Plack is only used in RT4
> >
> >-kevin
> >
> >RT Training Sessions 
> >(http://bestpractical.com/services/training.html)
> >* Boston — March 5 & 6, 2012
> 

Re: [rt-users] rt-mailgate 302 Error. No, not Plack.

[Kevin Falcone]

On Wed, Mar 14, 2012 at 09:43:47PM +, Jourdan Perla wrote:
> 
> An Error Occurred
> =
> 
> 302 Found
> 
> /usr/bin/rt-mailgate: undefined server error

This is Apache issuing a 302 before it gets to RT

> Grep all my logs for what happens at the same time and
> apache2/access.log:
> rt.myserver.com - - [14/Mar/2012:14:05:33 -0700] "POST 
> /rt/REST/1.0/NoAuth/mail-gateway HTTP/1.1" 302 715 "-" "libwww-perl/6.04"
> 
> I've got the following in my httpd.conf
> 
> 
>AllowOverRide None
>Satisfy Any
> 
> 
>AllowOverRide None
>Allow from all
>Satisfy Any
> 
> 
>Order allow,deny
>Allow from all
>Satisfy Any
> 
> 
>Order allow,deny
>Allow from all
>Satisfy Any
> 

What else do you have in apache.  Are you redirecting from http to
https?  Since you're using the debian packages, what else is going on
there.  Also, this is where I feel compelled to ask why you're using
3.8 rather than 4.0 for a new install.

-kevin


pgp3svR3MHFCf.pgp
Description: PGP signature

Re: [rt-users] rt-mailgate 302 Error. No, not Plack.

[Jourdan Perla]

Using 3.8 since there are no RT4 packages for Ubuntu 10.4 LTS. Attempts to 
manually install RT4 on Lucid would result in a whole 'nother ticket. Plan was 
to run 3.8 for now, then migrate to 4 on 12 this winter once things had settled 
down here.

No https redirects going on. I am using CAS Authentication (via mod_auth_cas) 
for the main site.


Apache httpd.conf
LoadFile /usr/lib/libcurl.so
LoadModule auth_cas_module /usr/lib/apache2/modules/mod_auth_cas.so

CASLoginURL https://cas.myserver.com/cas/login
CASValidateURL https://cas.myserver.com/cas/serviceValidate
CASCertificatePath /etc/ssl/certs/my_cas_bundle.pem
CASCookiePath /var/cache/apache2/mod_auth_cas/
CASSSOEnabled On
CASValidateServer On
CASDebug Off



 
   AuthType CAS
   AuthName " CAS"
 
   Require valid-user


   AllowOverRide None
   Satisfy Any


   AllowOverRide None
   Allow from all
   Satisfy Any


   Order allow,deny
   Allow from all
   Satisfy Any


   Order allow,deny
   Allow from all
   Satisfy Any


Satisfy Any
Allow from all


-Original Message-
From: rt-users-boun...@lists.bestpractical.com 
[mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Kevin Falcone
Sent: Wednesday, March 14, 2012 4:49 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] rt-mailgate 302 Error. No, not Plack.

On Wed, Mar 14, 2012 at 09:43:47PM +, Jourdan Perla wrote:
> 
> An Error Occurred
> =
> 
> 302 Found
> 
> /usr/bin/rt-mailgate: undefined server error

This is Apache issuing a 302 before it gets to RT

> Grep all my logs for what happens at the same time and
> apache2/access.log:
> rt.myserver.com - - [14/Mar/2012:14:05:33 -0700] "POST 
> /rt/REST/1.0/NoAuth/mail-gateway HTTP/1.1" 302 715 "-" "libwww-perl/6.04"
> 
> I've got the following in my httpd.conf
> 
> 
>AllowOverRide None
>Satisfy Any
> 
> 
>AllowOverRide None
>Allow from all
>Satisfy Any
> 
> 
>Order allow,deny
>Allow from all
>Satisfy Any
> 
> 
>Order allow,deny
>Allow from all
>Satisfy Any
> 

What else do you have in apache.  Are you redirecting from http to https?  
Since you're using the debian packages, what else is going on there.  Also, 
this is where I feel compelled to ask why you're using
3.8 rather than 4.0 for a new install.

-kevin

Re: [rt-users] rt-mailgate 302 Error. No, not Plack.

[Tim Cutts]

On 15 Mar 2012, at 17:44, Jourdan Perla wrote:

> Using 3.8 since there are no RT4 packages for Ubuntu 10.4 LTS. Attempts to 
> manually install RT4 on Lucid would result in a whole 'nother ticket.

I'm running 4.0.5 on Lucid.  Wasn't really a problem; I just don't use the 
packaged version and let 'make fixdeps' do its thing.  As you say though, 
waiting for 12.04 to come out is probably sensible, since Dominic *has* 
packaged rt4 more recently.

At one point I went to the effort of using dh-make-perl to update perl module 
packages to versions that RT needed, but for my 4.0.5 deployment I just thought 
"sod it" and took the fixdeps route.

The really hard bit actually was getting SphinxSE to work with the 
lucid-supplied MySQL server. *that* was painful, and I think if I were doing it 
again, I wouldn't use the packaged MySQL server either.  Actually, if I were 
really starting again I wouldn't use MySQL at all.

It's the Siren of databases, seducing you in with its lovely songs and apparent 
ease of use, and then smashing you to pieces on the rocks. :-/

Tim

--
 The Wellcome Trust Sanger Institute is operated by Genome Research
 Limited, a charity registered in England with number 1021457 and a
 company registered in England with number 2742969, whose registered
 office is 215 Euston Road, London, NW1 2BE.

Re: [rt-users] rt-mailgate Unknown encoding 'charset="utf-8"'

[Ruslan Zakirov]

This happens when email has encoding defined, but it's not correct value.
Newer versions convert such cases to "application/octet-stream". Change is
in 4.0.9rc1.


On Fri, Apr 5, 2013 at 6:00 AM, charlyc...@yahoo.com.ar <
charlyc...@yahoo.com.ar> wrote:

> Hi,
>
> I've been running rt-mailgate to download my emails and today I started
> getting this error message on the fetchmail log.
>
> RT server error.
>
> The RT server which handled your email did not behave as expected. It
> said:
>
> Unknown encoding 'charset="utf-8"' at /data/rt4/sbin/../lib/RT/I18N.pm
> line 542.
>
> Stack:
>   [/usr/local/share/perl5/Carp.pm:100]
>   [/usr/local/lib64/perl5/Encode.pm:188]
>   [/data/rt4/sbin/../lib/RT/I18N.pm:542]
>   [/data/rt4/sbin/../lib/RT/I18N.pm:214]
>   [/data/rt4/sbin/../lib/RT/I18N.pm:210]
>   [/data/rt4/sbin/../lib/RT/EmailParser.pm:282]
>   [/data/rt4/sbin/../lib/RT/Interface/Email.pm:1433]
>   [/data/rt4/share/html/REST/1.0/NoAuth/mail-gateway:61]
>
>
>
> This is my configuration on the RT_Config.pm:
>
> Set(@EmailInputEncodings, qw(utf-8 iso-8859-1 us-ascii));
>
>
> There is no configuration for this parameter on the RT_SiteConfig.pm.
>
> RT Version: 4.0.8
>
>
> Do you know why this might happen?
>
> Thank you, Charly
>
>


-- 
Best regards, Ruslan.

Re: [rt-users] rt-mailgate Unknown encoding 'charset="utf-8"'

[charlyc...@yahoo.com.ar]

Thank you for your answer.

1. Do you know if the tickets are still created? I wanted to validate it but we 
receive hundreds of emails per hour and it's difficult for me to do follow up.

2. If I update to 4.0.10 this will be solved?

Thank you for your help.





 De: Ruslan Zakirov 
Para: "charlyc...@yahoo.com.ar"  
CC: "rt-users@lists.bestpractical.com"  
Enviado: viernes, 5 de abril de 2013 5:04
Asunto: Re: [rt-users] rt-mailgate Unknown encoding 'charset="utf-8"'
 

This happens when email has encoding defined, but it's not correct value. Newer 
versions convert such cases to "application/octet-stream". Change is in 
4.0.9rc1.



On Fri, Apr 5, 2013 at 6:00 AM, charlyc...@yahoo.com.ar 
 wrote:

Hi,
>
>I've been running rt-mailgate to download my emails and today I started 
>getting this error message on the fetchmail log.
>
>RT server error.
>
>The RT server which handled your email did not behave as expected. It
>said:
>
>Unknown encoding 'charset="utf-8"' at /data/rt4/sbin/../lib/RT/I18N.pm line 
>542.
>
>Stack:
>  [/usr/local/share/perl5/Carp.pm:100]
>  [/usr/local/lib64/perl5/Encode.pm:188]
>  [/data/rt4/sbin/../lib/RT/I18N.pm:542]
>  [/data/rt4/sbin/../lib/RT/I18N.pm:214]
>  [/data/rt4/sbin/../lib/RT/I18N.pm:210]
>  [/data/rt4/sbin/../lib/RT/EmailParser.pm:282]
>  [/data/rt4/sbin/../lib/RT/Interface/Email.pm:1433]
>  [/data/rt4/share/html/REST/1.0/NoAuth/mail-gateway:61]
>
>
>
>This is my configuration on the RT_Config.pm:
>
>    Set(@EmailInputEncodings, qw(utf-8 iso-8859-1 us-ascii));
>
>
>There is no configuration for this parameter on the RT_SiteConfig.pm.
>
>RT Version: 4.0.8
>
>
>Do you know why this might happen?
>
>Thank you, Charly
>
>


-- 
Best regards, Ruslan. 

Re: [rt-users] rt-mailgate Unknown encoding 'charset="utf-8"'

[Ruslan Zakirov]

On Fri, Apr 5, 2013 at 4:25 PM, charlyc...@yahoo.com.ar <
charlyc...@yahoo.com.ar> wrote:

> Thank you for your answer.
>
> 1. Do you know if the tickets are still created? I wanted to validate it
> but we receive hundreds of emails per hour and it's difficult for me to do
> follow up.
>
> no, tickets are not created


> 2. If I update to 4.0.10 this will be solved?
>
>
yes.



> Thank you for your help.
>
>
>   --
> *De:* Ruslan Zakirov 
> *Para:* "charlyc...@yahoo.com.ar" 
> *CC:* "rt-users@lists.bestpractical.com" 
>
> *Enviado:* viernes, 5 de abril de 2013 5:04
> *Asunto:* Re: [rt-users] rt-mailgate Unknown encoding 'charset="utf-8"'
>
> This happens when email has encoding defined, but it's not correct value.
> Newer versions convert such cases to "application/octet-stream". Change is
> in 4.0.9rc1.
>
>
> On Fri, Apr 5, 2013 at 6:00 AM, charlyc...@yahoo.com.ar <
> charlyc...@yahoo.com.ar> wrote:
>
> Hi,
>
> I've been running rt-mailgate to download my emails and today I started
> getting this error message on the fetchmail log.
>
> RT server error.
>
> The RT server which handled your email did not behave as expected. It
> said:
>
> Unknown encoding 'charset="utf-8"' at /data/rt4/sbin/../lib/RT/I18N.pm
> line 542.
>
> Stack:
>   [/usr/local/share/perl5/Carp.pm:100]
>   [/usr/local/lib64/perl5/Encode.pm:188]
>   [/data/rt4/sbin/../lib/RT/I18N.pm:542]
>   [/data/rt4/sbin/../lib/RT/I18N.pm:214]
>   [/data/rt4/sbin/../lib/RT/I18N.pm:210]
>   [/data/rt4/sbin/../lib/RT/EmailParser.pm:282]
>   [/data/rt4/sbin/../lib/RT/Interface/Email.pm:1433]
>   [/data/rt4/share/html/REST/1.0/NoAuth/mail-gateway:61]
>
>
>
> This is my configuration on the RT_Config.pm:
>
> Set(@EmailInputEncodings, qw(utf-8 iso-8859-1 us-ascii));
>
>
> There is no configuration for this parameter on the RT_SiteConfig.pm.
>
> RT Version: 4.0.8
>
>
> Do you know why this might happen?
>
> Thank you, Charly
>
>
>
>
> --
> Best regards, Ruslan.
>
>
>


-- 
Best regards, Ruslan.

Re: [rt-users] rt-mailgate on different server than RT

[Nadeem Shahbaz]

Matt Nichols, on 2006-06-06 6:43 PM +0500, wrote :

> Is it possible to run rt-mailgate on a separate server than RT? 

at http://wiki.bestpractical.com/index.cgi?ManualInstallation, see
SETTING UP THE MAIL GATEWAY section

Nadeem
___
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


We're hiring! Come hack Perl for Best Practical: 
http://bestpractical.com/about/jobs.html

[rt-users] RT-Mailgate timeout error after upgrade to 4.2.6

[Richards, Matthew E ERDC-RDE-CERL-IL]

We are fighting an issue after updating RT from 4.2.3 to 4.2.6 and rt-mailgate. 
 We also updated our OS to Ubuntu 14.04.  Everything seems to be working in RT 
except rt-mailgate.  I've isolated it to an LWP::Protocol::https::Socket: 
Timeout error returned from the post to the RESTful service: my $r = $ua->post( 
$full_url, $post_params, Content_Type => 'form-data' );

I increased the timeout from 180 to 750 added extra debugging to the code to 
get more information.  I replaced our URL with localhost for security:

/opt/rt4/bin/rt-mailgate: connecting to 
https://localhost/REST/1.0/NoAuth/mail-gateway
ua->timeout: 750
ua->post full_url: https://localhost/REST/1.0/NoAuth/mail-gateway
ua->post post_params: HASH(0x149a6d0)
r->content : Can't connect to localhost:443

LWP::Protocol::https::Socket: Timeout at /usr/share/perl5/LWP/Protocol/http.pm 
line 41.

HTTP request failed: 500 Can't connect to localhost:443. Your webserver logs 
may have more information or there may be a network problem.

/opt/rt4/bin/rt-mailgate: undefined server error
fetchmail: MDA returned nonzero status 75
not flushed

There are no log entries in the apache error.log.  We have Set($LogToFile , 
'debug'); and did see one error that we corrected (a missing $RTAddressRegexp 
configuration).  There are no other errors in the rt.log file.   I don't even 
see an entry in the access.log.  Fiddler gives us the same error (504 - Gateway 
Timeout Error).  If I execute consecutive posts very quickly in Fiddler, after 
about seven 504 errors, I finally get a string of 200 (success) responses and 
some entries in the rt.log file to indicate it couldn't find a valid user 
(because I didn't supply one).  If I let it set for a minute, I get the 504 
errors again.

Thank you for any help,

Matthew E. Richards

-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] rt-mailgate in lab environment stopped working

[Thomas Bätzler]

Hi,

 

Stephen Cena asked:

*  I’ve been beating my head against this for days now and can’t figure this
out. I original had

*  (as much as possible) a clone of our production environment in a lab. I
reached a point

*  where I was forced to re-IP the lab environment which went well. Now,
rt-mailgate

*  simply doesn’t work. Outbound mail does work (postfix). If I use the
/etc/aliases file for

*  commands like I usually to, fetchmail attempts to contact an SMTP server
for local

*  delivery. If I actually embed the rt-mailgate command inside fetchmailrc
I now get

*  “http request failed: 500 can’t connect to SERVER:80. Web server logs may
have more

*  info”. I can’t find anything.

 

Well, that error message is pretty clear – when fetchmail tries to spawn
rt-mailgate, that process can’t connect to RT.

 

You should replace SERVER:80 in your fetchmailrc with the URL you’re using
to connect  to RT in your browser.

 

 

HTH,

Thoomas

 

 



smime.p7s
Description: S/MIME cryptographic signature

Re: [rt-users] rt-mailgate in lab environment stopped working

[Cena, Stephen (ext. 300)]

Ok; I figured out what it is but I don't know why. 

"Time Management for System Administrators" - page 30 "Some general advice" - 
#7 - "The strangest problems often turn out to be misconfigured DNS."

If I use the IP address for the server versus the FQDN, tickets flow in 
perfectly. If I use the FQDN of the server, it breaks.

It's bizarre: DNS appears to be functioning properly  in the test environment, 
but clearly based on this discovery it isn't.

I'll consider this "solved" as this is more than likely my own d#mn fault.

Stephen Cena
Senior Systems Administrator 
Quality Vision International, Inc.
Phone: (585) 544-0450 x300
To notify helpdesk: http://helpdesk.ogp.qvii.com or email: hd-gene...@qvii.com
To report email issues: postmas...@qvii.com

[rt-users] rt-mailgate config problems while on virtual dedicated server

[Phil Lawrence]

I'm having problems properly configuring rt-mailgate. I have a recipe
I made a few years ago for RHEL 4, but I had a real dedicated box that
time.  This time I have a dedicated virtual server hosted by godaddy.

I started with the fancy method described at
http://www.geert.triple-it.nl/node/rt_procmail.html, but soon realized
my root problem with that method was that I didn't know how to deliver
mail to an actual account on the box from postfix, which is using
virtual_alias to handle mail for my virtual domain.

So I went back to the basic way descried in manual_installation, where
you set up an alias for each queue.

postfix wouldn't let me put this in /etc/postfix/turbopanel/virtual_alias:
[EMAIL PROTECTED] "|/opt/rt3/bin/rt-mailgate --queue test
--action correspond --url https://virtualdomain.com";

It complained because it wasn't a valid hash format.

So I tried appending to /etc/aliases:
test: "|/opt/rt3/bin/rt-mailgate --queue 'test' --action correspond
--url https://virtualdomain.com";

and setting /etc/postfix/turbopanel/virtual_alias:
[EMAIL PROTECTED] [EMAIL PROTECTED]

that failed (relay error, I suppose another machine is actually
handling ip-999-999-999-999.ip.secureserver.net)

So I tried /etc/postfix/turbopanel/virtual_alias:
[EMAIL PROTECTED] [EMAIL PROTECTED]

which resolved to [EMAIL PROTECTED], and so failed:
Aug 25 12:37:41 ip-999-999-999-999 postfix/lmtp[27984]: 3F34315E35F6:
to=<[EMAIL PROTECTED]>,
relay=/var/lib/imap/socket/lmtp[/var/lib/imap/socket/lmtp], delay=0,
status=bounced (host
/var/lib/imap/socket/lmtp[/var/lib/imap/socket/lmtp] said: 550-Mailbox
unknown.  Either there is no mailbox associated with this 550-name or
you do not have authorization to see it. 550 5.1.1 User unknown (in
reply to RCPT TO command))



I also tried /etc/postfix/turbopanel/virtual_alias:
[EMAIL PROTECTED] [EMAIL PROTECTED]

and that failed:
Aug 25 12:40:36 ip-999-999-999-999 postfix/qmgr[28422]: 9AEA715E35F6:
to=<[EMAIL PROTECTED]>, relay=none, delay=0, status=bounced (bad address
syntax: "[EMAIL PROTECTED]")

I'm using RT 3.6.4 on CentOS 4.5 with postfix and cyrus.

Can anyone point me in the right direction?

Phil Lawrence
___
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

Re: [rt-users] rt-mailgate and [EMAIL PROTECTED] with selfsigned certificate

[Drew Barnes]

I leave http open only to the local machine so that rt-mailgate can
connect to it to create tickets.  Might not be the right solution, but
it works.

Stefan Oeser - emendis GmbH wrote:
> Hello,
>
>   I ran into problems with setting up RT3 on https. I configured some 
> Ticket-Transaction via Mail in RT3.
> With http-Protocol, all things work fine, but rt-mailgate has some troubles 
> with the httpS-Protocol. I always get
> an Error: "Connection refused". All needed modules (Crypt::SSLeay) are 
> installed. Is it possible, that there are
> some difficulties with the selfsigned certificate?
>
> Using a browser to enter my RT3, I need to accept some Popup-Windows and 
> accept the certificate manually,
> perhaps, rt-mailgate doesn't accept the certificate automatically, which 
> results in the mentioned error??
>
> I would be very grateful for some help  :)
> Best regards,
> Stefan Oeser
>
> ___
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:
>
> If you sign up for a new RT support contract before December 31, we'll take
> up to 20 percent off the price. This sale won't last long, so get in touch 
> today. 
> Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745.
>
>
> 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
>   
___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:

If you sign up for a new RT support contract before December 31, we'll take
up to 20 percent off the price. This sale won't last long, so get in touch 
today. 
Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745.


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

Re: [rt-users] rt-mailgate and [EMAIL PROTECTED] with selfsigned certificate

[Stephen Turner]

At Thursday 11/8/2007 06:48 AM, Stefan Oeser - emendis GmbH wrote:

Hello,

  I ran into problems with setting up RT3 on https. I configured 
some Ticket-Transaction via Mail in RT3.
With http-Protocol, all things work fine, but rt-mailgate has some 
troubles with the httpS-Protocol. I always get
an Error: "Connection refused". All needed modules (Crypt::SSLeay) 
are installed. Is it possible, that there are

some difficulties with the selfsigned certificate?

Using a browser to enter my RT3, I need to accept some Popup-Windows 
and accept the certificate manually,
perhaps, rt-mailgate doesn't accept the certificate automatically, 
which results in the mentioned error??


I would be very grateful for some help  :)
Best regards,
Stefan Oeser


Hello Stefan,

The way we've done this is to have apache listen on two ports for SSL 
connections. 443 requires certificates, 444 does not (i.e. 
username/password access). We use 444 for the mailgate connection.


Steve 


___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:

If you sign up for a new RT support contract before December 31, we'll take
up to 20 percent off the price. This sale won't last long, so get in touch today. 
   Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745.



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

Re: [rt-users] rt-mailgate and [EMAIL PROTECTED] with selfsigned certificate

[Joshua Lenmarc]

You might also want to check if the URL pointed to by rt-mailgate is
accessible. In my case, it was not resolved properly. Was able to know
after trying the URL with lynx. Made it work by hardcoding the host
address on /etc/hosts. HTH

> At Thursday 11/8/2007 06:48 AM, Stefan Oeser - emendis GmbH wrote:
> >Hello,
> >
> >   I ran into problems with setting up RT3 on https. I configured
> > some Ticket-Transaction via Mail in RT3.
> >With http-Protocol, all things work fine, but rt-mailgate has some
> >troubles with the httpS-Protocol. I always get
> >an Error: "Connection refused". All needed modules (Crypt::SSLeay)
> >are installed. Is it possible, that there are
> >some difficulties with the selfsigned certificate?
> >
> >Using a browser to enter my RT3, I need to accept some Popup-Windows
> >and accept the certificate manually,
> >perhaps, rt-mailgate doesn't accept the certificate automatically,
> >which results in the mentioned error??
> >
> >I would be very grateful for some help  :)
> >Best regards,
> >Stefan Oeser
>
> Hello Stefan,
>
> The way we've done this is to have apache listen on two ports for SSL
> connections. 443 requires certificates, 444 does not (i.e.
> username/password access). We use 444 for the mailgate connection.
>
> Steve
___
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

[rt-users] rt-mailgate comment and reply fail -- "Can't create output"

[chris]

>

I'm having problems with the comment and correspond functions.  When  
someone tries to email in a response to a ticket, they get a bounce  
with the errors below.   New tickets can be emailed in successfully,  
however.  Can anyone suggest what I might need to check?  Thanks!



> The original message was received at Thu, 18 Sep 2008 14:35:03  
> -0500 (CDT)
> from mailhub-3.xxx.xxx.xxx.xxx [129.186.140.13]
>
>- The following addresses had permanent fatal errors -
> "/opt/rt3/bin/rt-mailgate   --queue  
> 'general'   --action comment   -- 
> url http://myserver.xxx.xxx.xxx/";
> (reason: Can't create output)
> (expanded from: )
>
>- Transcript of session follows -
> 550 5.0.0 "/opt/rt3/bin/rt-mailgate   --queue  
> 'general'   --action comment   -- 
> url http://myserver.xxx.xxx.xxx/";... Can't create output
>
> Reporting-MTA: dns; xxx.xxx.xxx.xxx
> Received-From-MTA: DNS; mailhub-3.xxx.xxx.xxx.xxx
> Arrival-Date: Thu, 18 Sep 2008 14:35:03 -0500 (CDT)
>
> Final-Recipient: RFC822; rt-comment@ myserver.xxx.xxx.xxx
> X-Actual-Recipient: X-Unix; /opt/rt3/bin/rt- 
> mailgate   --queue 'general'   -- 
> action comment   --url http://myserver.xxx.xxx.xxx/
> Action: failed
> Status: 5.3.0
> Diagnostic-Code: X-Unix; 73
> Last-Attempt-Date: Thu, 18 Sep 2008 14:35:03 -0500 (CDT)
___
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

[rt-users] rt-mailgate undefined server error for only one user

[Jon Baker]

I'm having a sudden problem with rt-mailgate that is extremely  
puzzling to me, and I'm hoping I can get some guidance as to where to  
look to solve this problem.

I have mailgate set up on our local network so that 
rtq+programming-...@elmer.wgm 
, for example, is configured to send the incoming e-mail as a new  
ticket in the programming-web queue:

rtq:"|/usr/sbin/rt-mailgate --extension queue --action  
correspond --url http://alpha/rt/ --debug"

(I added the --debug this morning hoping to get more information on  
this problem)

I have a user whose messages to this address are returning the  
following error in the maillog:

alpha postfix/local[1521]: EF498880DA: to=, relay=local, delay=53746, delays=53563/0.08/0/183,  
dsn=4.3.0, status=deferred (temporary failure. Command output: /usr/ 
sbin/rt-mailgate: temp file is '/tmp/36HC1MaNJp' /usr/sbin/rt- 
mailgate: connecting to http://alpha/rt//REST/1.0/NoAuth/mail-gateway  
An Error Occurred =  500 read timeout  /usr/sbin/rt- 
mailgate: undefined server error )

What happens is that a ticket is created but the message goes back  
into the mail queue and tries again.  This morning there were about 15  
identical tickets and counting.  The same thing happened yesterday.   
It may also be limited to this single queue, as this user primarily  
enters tickets via mailgate.  The message appears to be submitted  
three minutes before the error, so it clearly is timing out for some  
reason, but I can't figure out why.

Where it gets odd is, if I send a message to the queue using the same  
to address (but my from address), it works fine:

alpha postfix/local[1641]: 9392A880DB: to=, relay=local, delay=6.8, delays=0.43/0.09/0/6.3,  
dsn=2.0.0, status=sent (delivered to command: /usr/sbin/rt-mailgate -- 
extension queue --action correspond --url http://alpha/rt/ --debug)

so it only appears to be this one user.  I don't see any errors in the  
rt log, just that the ticket was successfully created.  I have  
$LogToFile set to 'debug'.  We both have the same permissions (and  
"everyone" is able to create tickets.  Of course, it's not the ticket  
creation that's failing, obviously)

It's possible it could be a mail agent difference I suppose, I'm using  
Mac Mail and she is using Outlook.

Any ideas where I need to look to solve this?
-- 
Jon Baker
Information Technology
Willie George Ministries
1003 N 129th E Ave
Tulsa OK 74116
(918) 234-5656


___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sa...@bestpractical.com


Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
Buy a copy at http://rtbook.bestpractical.com

[rt-users] rt-mailgate undefined server error for only one user

[Jon Baker]

I've narrowed it down to the Create Ticket command in Email.pm:

 my ( $id, $Transaction, $ErrStr ) = $Ticket->Create(
 Queue => $SystemQueueObj->Id,
 Subject   => $Subject,
 Requestor => \...@requestors,
 Cc=> \...@cc,
 MIMEObj   => $Message
 );

If I comment out the MIMEObj line then the function returns without  
issue.  I'm thinking it is something wrong with my MIME parser, but I  
don't know the best way to go about fixing it - is there a perl module  
that I should re-install?

If I set the timeout to 600 then it does seem to go through sometimes  
- but I know that letting it take 10 minutes implies there's a deeper  
problem somewhere, I'm hoping someone can point me in the right  
direction to get this solved.

We updated to FC11 from FC10 on Friday, if that matters, although I  
have a separate system that is also running RT that I'm able to send  
the same message into without issue (I have successfully caught the  
raw message and am able to attempt to send it through rt-mailgate via  
the command line)
-- 
Jon Baker
Information Technology
Willie George Ministries
1003 N 129th E Ave
Tulsa OK 74116
(918) 234-5656


___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sa...@bestpractical.com


Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
Buy a copy at http://rtbook.bestpractical.com

Re: [rt-users] RT-Mailgate + Postfix on SLES10 Not Receiving Mail

[Alan Premselaar]

On 09/10/30 7:56, Victor Gehring wrote:
[snip...]
>
> Oct 29 18:17:35 dt-rt postfix/local[7122]: ED9E318235:
> to= correspond ??url http://10.0.1.6/@dt-rt.yyy.com>,
> orig_to=, relay=local, delay=1, status=bounced
> (unknown user: "???/opt/rt3/bin/rt???mailgate ??queue general
> ??action correspond ??url http://10.0.1.6/";)
Victor,

your problem lies in the lines above.  you apparently have some 
non-ascii / non-printable characters in your alias definition which 
postfix is choking on.  make sure that when you're editing your aliases 
file that you're using single-byte ASCII characters and not double-byte 
or extended ASCII characters.

hope this helps.

Alan
___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sa...@bestpractical.com


Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
Buy a copy at http://rtbook.bestpractical.com

Re: [rt-users] rt-mailgate/fetchmailrc question: email not leaving inbox

[Rob MacGregor]

On Thu, Sep 30, 2010 at 17:24, Mauricio Tavares  wrote:
> I have been using rt-mailgate and fetchmailrc to retrieve support emails
> from our mail server and feed them to RT. My /etc/fetchmailrc looks like
> this:
>
> set syslog;
> set daemon 20;
>
> poll "mail.domain.com"
> with protocol imap
> username rt password weak
> mda "/usr/bin/perl /usr/bin/rt-mailgate --url https://localhost/ \
> --queue support --action correspond"
>
> Usually, after fetchmail grabs the new mail and feeds it to rt-mailgate, the
> email leaves the rt inbox in the mail server. Well, since last afternoon it
> has not been doing that. The email is still being send to rt and becomes a
> ticket (or a followup to one) but it just now stays in the inbox as new
> mail.
>
> Any suggestions?

What's changed?  Something somewhere has changed, either with
fetchmail (did you just upgrade it) or with your mail server.  If you
can identify that you're most of the way to restoring the way it used
to work.

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche

RT Training in Washington DC, USA on Oct 25 & 26 2010
Last one this year -- Learn how to get the most out of RT!

[rt-users] rt-mailgate not relpying to new tickets via email

[Gian Sartor]

Hello all,

We are running RT 3.4, having recently upgraded from 3.3, on Debian 
testing. I noticed yesterday that the auto response emails to newly 
created tickets are not being sent out. Tickets are ending up in the 
correct queues, with the correct requester name, and in the ticket 
history, RT has a note saying that the email has been sent. Admin CC's 
of the relevant queues are receiving emails to say that a new ticket has 
come in.


These lines appear in the log file:

Jun 13 15:11:13 server RT: 
<[EMAIL PROTECTED]> #3948/25217 - 
Scrip 2 Autoreply on

Create (/usr/share/request-tracker3.4/lib/RT/Action/SendEmail.pm:237)
Jun 13 15:11:13 server postfix/sendmail[26477]: fatal: No recipient 
addresses found in message header
Jun 13 15:11:14 server RT: About to think about scrips for transaction 
#25218
Jun 13 15:11:14 server RT: 
<[EMAIL PROTECTED]> sent To: 
[EMAIL PROTECTED] Cc:  Bc

c:  (/usr/share/request-tracker3.4/lib/RT/Action/SendEmail.pm:297)

While searching for answers, the only thing I have found that relates to 
my problem is that I am missing the "-t" option from the script that 
reads the header. I assumed that this would be in rt-mailgate (but I am 
new to RT and am likely to be wrong) and it is not there.


Can anyone help / point me in the right direction?

Gian
___
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



We're hiring! Come hack Perl for Best Practical: 
http://bestpractical.com/about/jobs.html

[rt-users] rt-mailgate/libdb4.3 error on debian? RT3.4 and 3.6

[Jon Daley]

	I recently started having trouble with rt-mailgate where I get the 
error at the bottom of this email.
	I checked my aptitude logs to see what I had upgraded, and there 
are a number of packages, though libdb4.3 looks somewhat promising.  I 
have not tried downgrading it yet.
	I assumed that since I am running debian testing, and RT was 
orphaned a while back, that something was broken, and perhaps would be 
fixed in upgrading to 3.6.  So, I went ahead and did that (amazing how 
easy it was...) but I still get the same error.


	I can connect to the mail-gateway URL in my browser, and without 
any parameters, it will create a ticket with an empty body, etc. so it 
seems like that is all working.  I haven't gone all the way down the path 
yet, but it appears the failure is in LWP::Protocol, though that module 
hasn't been changed in a while, so it must be something upstream affecting 
it.
	Any ideas?  I know there are others of you running Debian - anyone 
up-to-date on the testing branch?


procmail: Executing "/usr/bin/rt-mailgate,--debug,--queue,Support,
--action,correspond,--url,https://limedaley.com/support/";

Connecting to https://limedaley.com/sup
  port//REST/1.0/NoAuth/mail-gateway 
at /usr/bin/rt-mailgate line 99, <> line 1.

An Error Occurred
=
500 Can't connect to limedaley.com:443 (Illegal seek)
This is /usr/bin/rt-mailgate exiting because of an undefined server error 
at /usr/bin/rt-mailgate line 147, <> line 1.

procmail: Program failure (75) of "/usr/bin/rt-mailgate"

___
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

Re: [rt-users] RT-Mailgate timeout error after upgrade to 4.2.6

[Kevin Falcone]

On Thu, Jul 31, 2014 at 09:03:16PM +, Richards, Matthew E ERDC-RDE-CERL-IL 
wrote:
> I increased the timeout from 180 to 750 added extra debugging to the code to
> get more information.  I replaced our URL with localhost for security:

Are you actually listening with SSL on localhost?  Is your webserver
configured to listen and allow that through to RT?


> see an entry in the access.log.  Fiddler gives us the same error (504 - 
> Gateway
> Timeout Error).  If I execute consecutive posts very quickly in Fiddler, after
> about seven 504 errors, I finally get a string of 200 (success) responses and
> some entries in the rt.log file to indicate it couldn’t find a valid user
> (because I didn’t supply one).  If I let it set for a minute, I get the 504
> errors again.

Is fiddler running on the machine connecting to localhost or somewhere
else?  It's a much more relevant test to use something like curl to
connect to localhost with the same arguments as rt-mailgate.

rt-mailgate isn't doing anything complicated, and if RT isn't logging
anything in debug mode, then normally this means your webserver is
bound only to the external hostname.

-kevin


pgpSxy8xFKVHk.pgp
Description: PGP signature
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] RT-Mailgate timeout error after upgrade to 4.2.6

[Richards, Matthew E ERDC-RDE-CERL-IL]

Hi Kevin,

Thank you for the reply.  

>  Are you actually listening with SSL on localhost?  Is your webserver
>  configured to listen and allow that through to RT?

443 is listening on localhost.  As you suggested, we tried curl from the 
localhost with both the FQDN and localhost URLs.  We had limited success 
(without any message content), but it still fails with rt-mailgate.  I suspect 
we need some content to test it further with curl.  Do you have a sample curl 
command line with post params for testing?

user@rt:~$ curl -I 
https://rt.fully.qualified.domain.name/REST/1.0/NoAuth/mail-gateway
HTTP/1.1 200 OK
Date: Mon, 04 Aug 2014 17:09:29 GMT
Server: Apache/2.4.7 (Ubuntu)
X-Frame-Options: DENY
Vary: Accept-Encoding
Content-Type: text/plain; charset=utf-8

user@rt:~$ curl -I https://localhost/REST/1.0/NoAuth/mail-gateway
HTTP/1.1 200 OK
Date: Mon, 04 Aug 2014 17:10:29 GMT
Server: Apache/2.4.7 (Ubuntu)
X-Frame-Options: DENY
Vary: Accept-Encoding
Content-Type: text/plain; charset=utf-8

Running rt-mailgate with fetchmail:

2 messages for RTUSER at hostmaster.fully.qualified.domain.name (36925 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 34826
fetchmail: POP3> TOP 1 
fetchmail: POP3< +OK
reading message rtu...@hostmaster.fully.qualified.domain.name:1 of 2 (34826 
octets) 
#**.***..*.*.*.*.*.*.*.**.*.*.*.*.*.*.*.**.*.*.*.*.*.*.*.**.*.*.*.*.*.*.**.*.*.*.*.*/opt/rt4/bin/rt-mailgate:
 temp file is '/tmp/63WuokOupY/OIpKtEaLCc'
/opt/rt4/bin/rt-mailgate: connecting to https://rt.fully.qualified.domain.name 
/REST/1.0/NoAuth/mail-gateway
HTTP request failed: 500 Can't connect to rt.fully.qualified.domain.name:443. 
Your webserver logs may have more information or there may be a network problem.

/opt/rt4/bin/rt-mailgate: undefined server error
fetchmail: MDA returned nonzero status 75
 not flushed
fetchmail: POP3> LIST 2
fetchmail: POP3< +OK 2 2099
fetchmail: POP3> TOP 2 
fetchmail: POP3< +OK


Again, when we added some additional debugging messages and the actual error is:
LWP::Protocol::https::Socket: Timeout at /usr/share/perl5/LWP/Protocol/http.pm 
line 41.

-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] RT-Mailgate timeout error after upgrade to 4.2.6

[Kevin Falcone]

On Mon, Aug 04, 2014 at 08:29:02PM +, Richards, Matthew E ERDC-RDE-CERL-IL 
wrote:
> 443 is listening on localhost. As you suggested, we tried curl from
> the localhost with both the FQDN and localhost URLs. We had limited
> success (without any message content), but it still fails with rt-
> mailgate. I suspect we need some content to test it further with curl.
> Do you have a sample curl command line with post params for testing?

Just run rt-mailgate by hand, handing it a correctly formatted
message and the --debug setting. If it works sporadically, you have some
serious problem with your webserver config.

If you're going to the localhost, I'm not actually sure why you're
involving SSL, but that's a separate issue.

-kevin



pgpY5fR35cHTa.pgp
Description: PGP signature
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] RT-Mailgate timeout error after upgrade to 4.2.6

[Richards, Matthew E ERDC-RDE-CERL-IL]

> If you're going to the localhost, I'm not actually sure why you're
> involving SSL, but that's a separate issue.

Actually, that was the issue.  You're right, there's no need to use SSL with 
localhost.  We have a rewrite from 80 to 443 for all interfaces and it always 
forces us to use https.  I guess we could have created a non-SSL site just for 
localhost.  The DoD has its own root CA that we added in a ca_file, but I think 
it's very slow and was causing the timeouts.  I changed the rt-mailgate 
get_useragent to "$ua->ssl_opts(SSL_verify_mode => 'SSL_VERIFY_NONE');" and 
that solved the issue.  It's a temporary fix until we create a locahost:80 
binding.  I don't like maintaining custom source.  Thanks for all the help.

Matt
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

Re: [rt-users] RT-Mailgate timeout error after upgrade to 4.2.6

[Kevin Falcone]

On Wed, Aug 06, 2014 at 09:44:40PM +, Richards, Matthew E ERDC-RDE-CERL-IL 
wrote:
> > If you're going to the localhost, I'm not actually sure why you're
> > involving SSL, but that's a separate issue.
> 
> Actually, that was the issue. You're right, there's no need to use SSL
> with localhost. We have a rewrite from 80 to 443 for all interfaces
> and it always forces us to use https. I guess we could have created a
> non-SSL site just for localhost. The DoD has its own root CA that we
> added in a ca_file, but I think it's very slow and was causing the
> timeouts. I changed the rt-mailgate get_useragent to "$ua-
> >ssl_opts(SSL_verify_mode => 'SSL_VERIFY_NONE');" and that solved the
> issue. It's a temporary fix until we create a locahost:80 binding. I
> don't like maintaining custom source. Thanks for all the help.

If you don't want to verify, why not just use the flag?

$ ./bin/rt-mailgate --help | grep verify
   "--ca-file" or "--no-verify-ssl", below.
   authority that should be used to verify the website's SSL certificate.
   preferentially use this option over "--no-verify-ssl", as it will
"--no-verify-ssl"

-kevin


pgpEGC686EGKR.pgp
Description: PGP signature
-- 
RT Training - Boston, September 9-10
http://bestpractical.com/training

[rt-users] rt-mailgate error wht ExternalAuth On User Creation by Email

[Luciano Ernesto da Silva]

Hello,

 

 

Some users send an email to email address of the queue to open tickets,
but we are getting this error on user creation, since we are using
ExternalAuth (RT4.0.2 + ExternalAuth 0.09):

 

 

Sat Oct 29 12:37:42 2011] [crit]: User creation failed in mailgateway:
Name in use (/opt/rt4/sbin/../lib/RT/Interface/Email.pm:244)

Trace begun at /opt/rt4/sbin/../lib/RT.pm line 249

Log::Dispatch::log('Log::Dispatch=HASH(0x7f4acf1969b0)', 'level',
'crit', 'message', 'User creation failed in mailgateway: Name in use')
called at /opt/rt4/sbin/../lib/RT/Inter

face/Email.pm line 244

RT::Interface::Email::MailError('To', 'john...@mydomain.com', 'Subject',
'User could not be created', 'Explanation', 'User creation failed in
mailgateway: Name in use', 'MIMEObj',
'MIME::Entity=HASH(0x7f4aced00a98)', 'LogLevel', 'crit') called at
/opt/rt4/sbin/../lib/RT/Interface/Email.pm line 999

 

 

I had set RT_SiteConfig.pm with 

Set($AutoCreateNonExternalUsers, 1);

Set($AutoCreate, {Privileged => 1});

 

On interface is granted rights to Everyone:

Comment on tickets

Create tickets 

Reply to tickets

 

 

My attributes on LDAP are these:

 

 

'attr_match_list'   => ['Name', 'EmailAddress'],

'attr_map'  => {'Name' => 'uid', 'EmailAddress' =>
'mail', 'RealName' => 'cn', 'ExternalAuthId' => 'uid'}

 

 

Actually I checked the list of users, I don't have any user with same
name of the requestor.

 

 

Should I use Set($AutoCreate, {UnPrivileged => 1}); or something like
that?

 

Tks

 

 

Luciano Silva


RT Training Sessions (http://bestpractical.com/services/training.html)
*  Barcelona, Spain — November 28 & 29, 2011

Re: [rt-users] rt-mailgate config problems while on virtual dedicated server

[Patrick Morris]

Phil Lawrence wrote:

I also tried /etc/postfix/turbopanel/virtual_alias:
[EMAIL PROTECTED] [EMAIL PROTECTED]

and that failed:
Aug 25 12:40:36 ip-999-999-999-999 postfix/qmgr[28422]: 9AEA715E35F6:
to=<[EMAIL PROTECTED]>, relay=none, delay=0, status=bounced (bad address
syntax: "[EMAIL PROTECTED]")
The error's right on that last one; it's bad address syntax. You should 
be able to get around it using "[EMAIL PROTECTED]".

___
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

Re: [rt-users] rt-mailgate config problems while on virtual dedicated server

[Phil Lawrence]

On 8/26/07, Patrick Morris <[EMAIL PROTECTED]> wrote:
> Phil Lawrence wrote:
> > I also tried /etc/postfix/turbopanel/virtual_alias:
> > [EMAIL PROTECTED] [EMAIL PROTECTED]
> >
> > and that failed:
> > Aug 25 12:40:36 ip-999-999-999-999 postfix/qmgr[28422]: 9AEA715E35F6:
> > to=<[EMAIL PROTECTED]>, relay=none, delay=0, status=bounced (bad address
> > syntax: "[EMAIL PROTECTED]")
> The error's right on that last one; it's bad address syntax. You should
> be able to get around it using "[EMAIL PROTECTED]".

I made the change (thank you) and now get:
  verify_user([127.0.0.1]!user.test) failed: Mailbox does not exist

Here's the details:

# cat /etc/postfix/turbopanel/virtual_alias
[EMAIL PROTECTED] [EMAIL PROTECTED]
[EMAIL PROTECTED] [EMAIL PROTECTED]

# tail -n 2 /etc/aliases
test: "|/opt/rt3/bin/rt-mailgate --queue 'test' --action correspond
--url https://virtualdomain.com/";
test-comment: "|/opt/rt3/bin/rt-mailgate --queue 'test' --action
comment --url https://virtualdomain.com/";

# grep '^Aug 27 07:10' /var/log/maillog
Aug 27 07:10:01 ip-72-167-16-99 postfix/smtpd[27811]: initializing the
server-side TLS engine
Aug 27 07:10:03 ip-72-167-16-99 postfix/smtpd[27811]: connect from
ug-out-1314.google.com[66.249.92.169]
Aug 27 07:10:04 ip-72-167-16-99 postfix/trivial-rewrite[28662]:
warning: do not list domain virtualdomain.com in BOTH mydestination
and virtual_mailbox_domains
Aug 27 07:10:04 ip-72-167-16-99 postfix/smtpd[27811]: warning: support
for restriction "check_relay_domains" will be removed from Postfix;
use "reject_unauth_destination" instead
Aug 27 07:10:05 ip-72-167-16-99 postfix/smtpd[27811]: 19C1D15E35C2:
client=ug-out-1314.google.com[66.249.92.169]
Aug 27 07:10:05 ip-72-167-16-99 postfix/cleanup[29779]: 19C1D15E35C2:
message-id=<[EMAIL PROTECTED]>
Aug 27 07:10:05 ip-72-167-16-99 postfix/qmgr[28117]: 19C1D15E35C2:
from=<[EMAIL PROTECTED]>, size=853, nrcpt=1 (queue active)
Aug 27 07:10:05 ip-72-167-16-99 spamc[30094]: connect(AF_INET) to
spamd at 127.0.0.1 failed, retrying (#1 of 3): Connection refused
Aug 27 07:10:06 ip-72-167-16-99 spamc[30094]: connect(AF_INET) to
spamd at 127.0.0.1 failed, retrying (#2 of 3): Connection refused
Aug 27 07:10:07 ip-72-167-16-99 spamc[30094]: connect(AF_INET) to
spamd at 127.0.0.1 failed, retrying (#3 of 3): Connection refused
Aug 27 07:10:08 ip-72-167-16-99 spamc[30094]: connection attempt to
spamd aborted after 3 retries
Aug 27 07:10:09 ip-72-167-16-99 postfix/pipe[30082]: 19C1D15E35C2:
to=<[EMAIL PROTECTED]>, orig_to=<[EMAIL PROTECTED]>,
relay=spamassassin, delay=5, status=sent (virtualdomain.com)
Aug 27 07:10:09 ip-72-167-16-99 postfix/qmgr[28117]: 19C1D15E35C2: removed
Aug 27 07:10:09 ip-72-167-16-99 postfix/pickup[28116]: A4EA815E35C6:
uid=99 from=<[EMAIL PROTECTED]>
Aug 27 07:10:09 ip-72-167-16-99 postfix/cleanup[29779]: A4EA815E35C6:
message-id=<[EMAIL PROTECTED]>
Aug 27 07:10:09 ip-72-167-16-99 postfix/qmgr[28117]: A4EA815E35C6:
from=<[EMAIL PROTECTED]>, size=960, nrcpt=1 (queue active)
Aug 27 07:10:10 ip-72-167-16-99 lmtpunix[27985]: accepted connection
Aug 27 07:10:10 ip-72-167-16-99 lmtpunix[27985]: lmtp connection
preauth'd as postman
Aug 27 07:10:10 ip-72-167-16-99 master[32171]: about to exec
/usr/lib/cyrus-imapd/lmtpd
Aug 27 07:10:10 ip-72-167-16-99 lmtpunix[27985]:
verify_user([127.0.0.1]!user.test) failed: Mailbox does not exist
Aug 27 07:10:10 ip-72-167-16-99 lmtpunix[32171]: executed
Aug 27 07:10:10 ip-72-167-16-99 postfix/lmtp[32146]: A4EA815E35C6:
to=<[EMAIL PROTECTED]>,
relay=/var/lib/imap/socket/lmtp[/var/lib/imap/socket/lmtp], delay=1,
status=bounced (host
/var/lib/imap/socket/lmtp[/var/lib/imap/socket/lmtp] said: 550-Mailbox
unknown.  Either there is no mailbox associated with this 550-name or
you do not have authorization to see it. 550 5.1.1 User unknown (in
reply to RCPT TO command))
Aug 27 07:10:10 ip-72-167-16-99 postfix/cleanup[29779]: AA6E315E35C4:
message-id=<[EMAIL PROTECTED]>
Aug 27 07:10:10 ip-72-167-16-99 postfix/qmgr[28117]: AA6E315E35C4:
from=<>, size=3010, nrcpt=1 (queue active)
Aug 27 07:10:10 ip-72-167-16-99 postfix/qmgr[28117]: A4EA815E35C6: removed
Aug 27 07:10:11 ip-72-167-16-99 postfix/smtp[32239]: AA6E315E35C4:
to=<[EMAIL PROTECTED]>,
relay=k2smtpout-v01.prod.mesa1.secureserver.net[64.202.189.86],
delay=1, status=sent (250 Accepted message qp 19387 bytes 3089)
Aug 27 07:10:11 ip-72-167-16-99 postfix/qmgr[28117]: AA6E315E35C4: removed
Aug 27 07:10:35 ip-72-167-16-99 postfix/smtpd[27811]: disconnect from
ug-out-1314.google.com[66.249.92.169]
___
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

Re: [rt-users] rt-mailgate config problems while on virtual dedicated server

[Phil Lawrence]

On 8/27/07, Phil Lawrence <[EMAIL PROTECTED]> wrote:
> On 8/26/07, Patrick Morris <[EMAIL PROTECTED]> wrote:
> > Phil Lawrence wrote:
> > > I also tried /etc/postfix/turbopanel/virtual_alias:
> > > [EMAIL PROTECTED] [EMAIL PROTECTED]
> > >
> > > and that failed:
> > > Aug 25 12:40:36 ip-999-999-999-999 postfix/qmgr[28422]: 9AEA715E35F6:
> > > to=<[EMAIL PROTECTED]>, relay=none, delay=0, status=bounced (bad address
> > > syntax: "[EMAIL PROTECTED]")
> > The error's right on that last one; it's bad address syntax. You should
> > be able to get around it using "[EMAIL PROTECTED]".
>
> I made the change (thank you) and now get:
>   verify_user([127.0.0.1]!user.test) failed: Mailbox does not exist

Fixed!  I had to:
# postconf -e "alias_maps = hash:/etc/aliases"
# postconf -e "alias_database = hash:/etc/aliases"
# newaliases

Thanks,
Phil Lawrence
___
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