On Mon, Jan 9, 2012 at 1:34 PM, Robert Nesius wrote:
> I made a recently change to how my apache2 server was configured to redirect
> all requests through https. Now emails are not flowing through to RT - I
> tracked the issue down to rt-mailgate complaining about not being able to
> verify the c
I made a recently change to how my apache2 server was configured to
redirect all requests through https. Now emails are not flowing through to
RT - I tracked the issue down to rt-mailgate complaining about not being
able to verify the certificate. I'm a little perplexed on how to proceed
or how t
On Mon, Oct 31, 2011 at 09:49:51AM -0200, Luciano Ernesto da Silva wrote:
>Actually I checked the list of users, I don't have any user with same name
> of the requestor.
Search for the user, don't just read the list of users. The list is only
Privileged users.
-kevin
pgpYPNTo9Mk67.pgp
Des
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/sb
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 TakeAc
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 8
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 up
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
beh
: 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
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 autocreat
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 runni
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 em
Simon Gao schrodinger.com> writes:
> What caused this error?Is using secure http required for rt-mailgate to work?
Simon,
Please install the version of Plack and it should be fixed:
http://search.cpan.org/~miyagawa/Plack-0.9970/
(0.9971 is broken and being fixed, don't use it!)
Cheers,
CLK
Changing to use secure http made it working:
rt: "|/opt/rt3/bin/rt-mailgate --debug --queue general --action
correspond --url https://rt.example.com/";
rt-comment: "|/opt/rt3/bin/rt-mailgate --debug --queue general --action
comment --url https://rt.example.com/";
However, rt.log logged fo
Hi,
I am testing a new RT 3.8.9 server. rt-mailgate does not work.
Running rt-mailgate manually generated following:
$ echo "test" | /opt/rt3/bin/rt-mailgate --queue general --action correspond
--url http://rt.example.com/ --debug
/opt/rt3/bin/rt-mailgate: temp file is '/tmp/GViVd10Ltg'
/opt/rt3/
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
> us
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 h
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
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? I
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:
I've got just about everything setup with the exception of
rt-mailgate. I'm not sure if this is an abnormal setup but I've got a
forward facing MTA that contains an alias for my RT address which is
forwards to the RT maching internally called 'services'. I use a basic
sendmail setup with a unix use
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
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
201
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
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'
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
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
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
# /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 pa
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 Admi
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 Irvin
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.
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
Hi, all.
If my rt.log is telling me the below, what this suggests me?
procmail: Executing
"rt-mailgate,--debug,--queue,general,--action,correspond,--url,https://rtracker.rt.pop-sp.rnp.br/rt";
Connecting to
https://rtracker.rt.pop-sp.rnp.br/rt/REST/1.0/NoAuth/mail-gateway at
/usr/bin/rt-mailga
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
> ??act
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
I believe this has been asked many times before but I am not finding
info on the actual setup. I need to run rt-mailgate in our mailserver
which is in a different machine than rt. Does rt-mailgate need some
files from the rt distribution to run or it is self-sufficient? If it
does need
Thanks all. Got it.
Kevin W. Gagel
Network Administrator
Local 5448
My blog:
http://mail.cnc.bc.ca/blogs/gagel
My shared files:
http://mail.cnc.bc.ca/users/gagel
--- Original message ---
Subject: Re: [rt-users] rt-mailgate error
From: Kevin Falcone
To: RT Users
Date: 06/07/2009 10:02 AM
On
On Jul 6, 2009, at 12:53 PM, Kevin Gagel wrote:
> I'm getting the following error.
> ---Paste---
> Command output: RT server error.
> The RT server which handled your email did not behave as expected.
> It said:
> temporary failure - RT couldn't find the queue: general
> ---End Paste---
>
> I h
> 1) Would this mean I'd need a dummy account of some type to get messages
> through?
Should not be necessary for receipt. I'm running on RHEL4 over SSL and
required no
special hoops to get mailgate to work that I can recall, beyond what's
on the wiki.
If you have SELinux enabled, you might need t
System:
RHEL 5
RT 3.8.1
Apache 2.2.3
So I'm currently trying to get rt-mailgateway set-up properly. I've got SMTP
set-up properly and the mail-log reflects messages I try to send. However,
when the message was passed to the aliased command it was breaking. I then
discovered it was a au
Looks like this may indeed be a bug with MySQL 5.1:
http://bugs.mysql.com/bug.php?id=45559
--
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
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 miss
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 S
On Jun 16, 2009, at 4:24 PM, Jon Baker wrote:
> 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 => \...@req
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,
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
http://wiki.bestpractical.com/view/Rights most probably
On Sat, May 9, 2009 at 4:09 AM, Aleksey Tsalolikhin
wrote:
> On Fri, May 8, 2009 at 4:54 PM, Aleksey Tsalolikhin
> wrote:
>>
>> The fine manual states,
>>
>> You also need to give the Everyone pseudogroup the privilege
>> "CreateTic
UI -> Configuration -> Global -> Group Rights
On Sat, May 9, 2009 at 3:54 AM, Aleksey Tsalolikhin
wrote:
> Hi. I am configuring an email gateway for RT 3.8.2.
>
> rt-mailgate fails with:
>
> /opt/rt3/bin/rt-mailgate: connecting to
> https://rt.example.com/rt//REST/1.0/NoAuth/mail-gateway
> not o
On Fri, May 8, 2009 at 4:54 PM, Aleksey Tsalolikhin
wrote:
>
> The fine manual states,
>
> You also need to give the Everyone pseudogroup the privilege
> "CreateTicket" on all queues that rt-mailgate will be using,
> because mail requests are by default unauthenticated.
>
> How do I gi
Hi. I am configuring an email gateway for RT 3.8.2.
rt-mailgate fails with:
/opt/rt3/bin/rt-mailgate: connecting to
https://rt.example.com/rt//REST/1.0/NoAuth/mail-gateway
not ok - Could not load a valid user
The fine manual states,
You also need to give the Everyone pseudogroup the priv
On Thu, Apr 30, 2009 at 5:06 PM, Ruslan Zakirov wrote:
> 3.8's mailgate dowsn't allow you to create a ticket with a requestor.
It is working when it receives a real email. Thanks for your help
>
>
> On Fri, May 1, 2009 at 1:01 AM, Asif Iqbal wrote:
> > The upgraded RT 3.8.2 is failing with rt
On Thu, Apr 30, 2009 at 5:06 PM, Ruslan Zakirov wrote:
> 3.8's mailgate dowsn't allow you to create a ticket with a requestor.
>
Currently my mailserver talks to RT to create the ticket. So RT does not
have to
listen to SMTP. Makes it that much secure.
So my mail server qmail receives the messa
3.8's mailgate dowsn't allow you to create a ticket with a requestor.
On Fri, May 1, 2009 at 1:01 AM, Asif Iqbal wrote:
> The upgraded RT 3.8.2 is failing with rt-mailgate. The original installation
> works just fine. What am I missing?
>
> (iqbala)@qmail:~$ echo this is a test | /tmp/rt-mailgate
The upgraded RT 3.8.2 is failing with rt-mailgate. The original installation
works just fine. What am I missing?
(iqbala)@qmail:~$ echo this is a test | /tmp/rt-mailgate --queue syshelp
--action correspond --url https://192.168.0.174 --debug
/tmp/rt-mailgate: temp file is '/tmp/mmF2JFMLdU'
/tmp/rt
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
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
> 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
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.
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
On Mar 27, 2009, at 2:46 PM, Jon Baker wrote:
>
> On Mar 27, 2009, at 6:04 AM, rt-users-requ...@lists.bestpractical.com
> wrote:
>
>>> I just started using custom subject tags with my RT and now my rt-
>>> mailgate is changing the subject to strange things, putting the
>>> ticket
>>> tag into the
On Mar 27, 2009, at 6:04 AM, rt-users-requ...@lists.bestpractical.com
wrote:
>> I just started using custom subject tags with my RT and now my rt-
>> mailgate is changing the subject to strange things, putting the
>> ticket
>> tag into the subject. Is there a setting to prevent the subject f
I think I found my answer. I was using the example I found in the
mailing list, which wasn't quite right. I read carefully the comments
in the RT_Config.pm file and saw that the regex command is supposed to
look like this:
Set($EmailSubjectTagRegex, qr/(?:example.com|example.org)/i );
Usi
On Mar 26, 2009, at 4:56 PM, Jon Baker wrote:
> I just started using custom subject tags with my RT and now my rt-
> mailgate is changing the subject to strange things, putting the ticket
> tag into the subject. Is there a setting to prevent the subject from
> being changed by rt-mailgate?
This
Ok, I'm obviously doing something wrong...
I am putting this in my RT_SiteConfig.pm:
Set( $EmailSubjectTagRegex, qr/\Q($rtname|Alert)\E/i );
but when I reply to a ticket it now creates a new ticket. If I change
it to
Set( $EmailSubjectTagRegex, qr/\Q$rtname\E/i );
it behaves as normal. Am
Thanks, that looks like that was it.
It might be a good idea to put a notice or link next to the field for
the custom subject tag in a future release, that doesn't seem (at
least to me) like something I would have expected to have to set
something in RT_SiteConfig for.
On Mar 26, 2009, at
On Thu, Mar 26, 2009 at 16:56, Jon Baker wrote:
> I just started using custom subject tags with my RT and now my rt-
> mailgate is changing the subject to strange things, putting the ticket
> tag into the subject. Is there a setting to prevent the subject from
> being changed by rt-mailgate?
You'
I just started using custom subject tags with my RT and now my rt-
mailgate is changing the subject to strange things, putting the ticket
tag into the subject. Is there a setting to prevent the subject from
being changed by rt-mailgate?
___
http://l
>
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
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
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.
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
My RT install has been running fine for a couple of years until a recent
routine upgrade of the packages. Since then, no mail has been able to
get to RT.
I tested with
cat /usr/bin/test |/etc/smrsh/rt-mailgate --queue sales --action
correspond --url http://mail.globaltradinglimited.com/rt
and
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 P
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 P
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 w
[EMAIL PROTECTED] wrote:
> On Sun, Feb 24, 2008 at 10:03:22AM -0500, Steve Cochran wrote:
>>
>> This might be more of a MTA question, but we're using rt-mailgate set
>> up in /etc/aliases with postfix. httpd stopped working on our RT
>> server, so obviously new mail couldn't be put into RT.
>>
>>
On Sun, Feb 24, 2008 at 10:03:22AM -0500, Steve Cochran wrote:
>
> This might be more of a MTA question, but we're using rt-mailgate set
> up in /etc/aliases with postfix. httpd stopped working on our RT
> server, so obviously new mail couldn't be put into RT.
>
> My question is would the
This might be more of a MTA question, but we're using rt-mailgate set
up in /etc/aliases with postfix. httpd stopped working on our RT
server, so obviously new mail couldn't be put into RT.
My question is would the mail queue up anywhere to be reprocessed? RT
is so robust that I can't image
It looks like the mail did end up coming in after a while. There were
two messages in limbo; one came in some 30 minutes or more after the
other. Curious...
Yitzchak Schaffer
Systems Librarian
Touro College Libraries
33 West 23rd Street
New York, NY 10010
Tel (212) 463-0400 x230
Fax (212) 627
Greetings:
We just went live with RT. I then started fooling around with
configuration, and changed the name of the incoming queue without
changing it in the mail alias. Oops. Now that we've had a "Could not
record email: RT couldn't find the queue," is that mail stored someplace?
Many th
That little hint was what I needed , thanks Ruslan
It was not intentional, trust me !!!
Although everything was working using the GUI,
I had numerous ownership and permission confusion throughout my install.
The most glaring, carrying over the apache user in my rt group as it was on my
original sy
s or from RT/mail logs?
>
> Secondly, rt-mailgate works just fine with HTTPS only installs - you've got
> to make sure that all your SSL related PERL modules have been installed,
> namely Crypt::SSLeay
>
> Lastly, what do your aliases look like?
>
>
> James Moseley
>
al.com>
Subject
more info...
I saw this on the list ...
same scenario ... I am moving to new hardware/versions and trying to do SSL
so I tried this as well... my error: Connecting to
http://x/REST/1.0/NoAuth/mail-gateway at /opt/rt3/bin/rt-mailgate line
102, <> line 1.
---
stly, what do your aliases look like?
James Moseley
"Roy Sowa"
<[EMAIL PROTECTED]
al.comSubject
[rt-users] rt-mailgate HTTPS
01/20/2008 08:11
I have seen list reference to email tickets not working with HTTPS
configurations.
Some indicate that a local http connection must exist for the rt-mailgate to
work
my current install is 3.6.5 using Lighttpd
Everything is working fine using the GUI.
but I cannot get emails to open tickets.
I ha
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
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
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) ar
Hi There
I'm relatively new to RT but so far it's proven to be a very useful tool! I
am having a slight problem after setting it up on a new server/upgrading to
RT 3.6, specifically where my Exim setup tries to deliver messages to RT
queues.
My current setup details:
Debian etch
Apache 2
Mysql 5
Hello,
I have a fresh installation of RT3.4 on Ubuntu 6.06 and am having problems
with rt-mailgate processing incoming emails. I see these types of error
messages in the /var/log/mail.log:
Oct 9 15:40:46 helpdesk postfix/local[6290]: D0EC1682B9:
to=<[EMAIL PROTECTED]>, relay=local, delay=1, stat
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
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]>,
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]"
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_proc
Hi folks
I'm trying to get rt-mailgate working (via fetchmail) and I get an error. I've
included the email I get back along with the sendmail logs, the fetchmailrc
and /etc/aliases entry.
I think the problem may be that RT doesn't know which user to use. In the
perldoc for rt-mailgate it says
Hi,
in the rt-mailgate man, in the SETUP says:
'Much of the set up of the mail gateway depends on your MTA and mail routing
configuration. However, you will need first of all to create an RT user for the
mail gateway and assign it a password; this helps to ensure that mail coming
into the web se
wiki: MailGatewayAccessControl
On 2/2/07, Roy El-Hames <[EMAIL PROTECTED]> wrote:
Hi there;
rt-3.6.1 and apach2 mysql5 and exim4
I have rebuilt my RT dev box copying stuff from the live system including the
RT bits in exim.conf
I forgot to change my
data = "|/opt/rt3/bin/rt-mailgate --queue .
101 - 200 of 219 matches
Mail list logo
