Worth noting, it may or may not impact your situation, is the
--no-verify-ssl flag you can put on your poll command.
I had a similar situation, different errors, but similar with the https /
cert issue.
set daemon 60
set invisible
set no bouncemail
set no syslog
set logfile /var/log/fetchmail.log
On Tue, 24 Feb 2015 14:42:23 + Daniel Moore
wrote:
> Example, I have a user that belongs to an exchange group that is currently
> the email for a contractors group that I have set up. He receives multiple
> emails when he is requestor, admin cc and so on.
Use one scrip with a "Notify" acti
HI,
I am currently testing to upgrade to RT 4.2.9. I am running 4.2.6 successfully
under normal http: (port 80). I am not wanting to sacrifice the https: ability
with the upgrade to 4.2.9 and would like to still be able to use the full email
functionality of RT.
Here is my setup. I am running
On Thu, 19 Feb 2015 18:06:05 -0500 "Joseph Mays" wrote:
> I have an installation or RT4.2 under Apache 2.4 on FreeBSD 10.1.
Sorry -- we've not updated the documentation for Apache 2.4 yet.
Replace:
Order allow,deny
Allow from all
..with:
Require all granted
Or use the mod_access_com
On Fri, 13 Feb 2015 18:41:45 + Andrew Wippler
wrote:
> After a few hours of sleep, I managed to get it working with this code:
> [snip]
For posterity, this is not the solution you want. If your users did
not come across as Privileged, there are likely a huge slew of other
hidden problems.
Review some of your LDAP settings. I think you have CN and DN in places
where you may want OU, and your LDAP user should be in a different format,
see below.
Hopefully this helps.
Use mine(working.. also cleaned..) as example:
Set($ExternalSettings, {
'My_LDAP' => {
'type'
Hi,
I am looking for a scrip that I can put somewhere in RT that will check for a
particular email address and not send more than one email to address.
Example, I have a user that belongs to an exchange group that is currently the
email for a contractors group that I have set up. He receives mu
No one is using LDAPS with Request Tracker ?
Guillaume Hilt
Le 18/02/2015 15:43, Guillaume Hilt a écrit :
Hello,
I'm using a fresh install of RT 4.0.19 on Ubuntu 14.04 AMD64, using
.deb packages.
I'm trying to make ExternalAuth work with LDAP over SSL (Active
Directory on 2008 R2 x64), w
Switching to an alternate authentication source, like LDAP, is
probably the only way you're going to enforce any type of password
policy.
--
Later,
Darin
On Tue, Feb 24, 2015 at 3:27 AM, Fredrik Rambris
wrote:
> Is there a way to check new passwords against a policy?
> I don't want users being a
Chris,
Thanks a lot for your help, it's exactly what I need !
And yes, it works in 4.2.6 .
Elisabeth
Is there a way to check new passwords against a policy?
I don't want users being able to change their password to weak ones like
123456 och Password123 etc.
Also... what is the recommended way to change all users passwords in one go?
--
Fredrik Rambris
CDON IT
Google Talk: fredrik.ramb...@cdon.co
11 matches
Mail list logo