[rt-users] rt-mailgate

[Robert Nesius]

On Mon, Jan 23, 2012 at 2:38 PM, Allen <allen+rtlist at crystalfontz.com>wrote:

> Landon wrote:
>
>> We simply use mod_rewrite to redirect everyone *except* the server itself
>> to https.  This way when rt-mailgate calls http://rt.ourdomain/com it is
>> not forced to use https while everyone else is.
>>
>
Landon - thank you for sharing those config lines.  I had debated exactly
that approach but had not dug into the mod-rewrite docs far enough to get
that line on my own.  Though - as I look at it - pretty simple regular
expression. :)   Thanks again!

Thanks. That is an easy, maintainable solution until the next version of
>> rt-mailgate that will let us specify the cert path, or until OpenSSL 1.x
>> gets it's act together with LWP.
>>
>
> But doesn't work for me. I solved some kind of mod-perl/apache
> redeclaration or some such problem (either spamming the logs or making
> apache not start -- cant remember which) that I solved by removing all RT
> apache configuration under regular http and just having the redirect to
> SSL. The SSL virtualhost container has the RT configs in it.
>

One other thought crossed my mind reading your earlier comments about
getting the environment variable into LWP::UserAgent via fetchmail configs.
 I think "export VAR=VALUE" is bash-specific syntax.  If the fetchmailrc
file is being read by /bin/sh, or bash running in /bin/sh compatibility
mode, that syntax could cause a problem.    You might try this:  "VAR=VALUE
/opt/rt4/bin/rt-mailgate ... ".   That syntax works for me via my aliases
file and is what I use in crontabs too.  I did see you use that syntax with
the env command - I've never tried that before myself but I've never needed
it either.

-Rob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20120124/3e221315/attachment.htm>