That doesn't work very well. The spam bots use different emails. And gmail
marks the entire message thread as spam, not just the spam reply.
On Sun, Apr 23, 2017 at 7:20 AM, Dewangga Bachrul Alam <
dewangg...@xtremenitro.org> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Mark as
I tried that, but the replica's "getcert list" doesn't seem to show any
results. "Number of certificates and requests being tracked: 0." Is that
expected ?
On Sun, Apr 23, 2017 at 8:50 PM, Fraser Tweedale
wrote:
> On Sun, Apr 23, 2017 at 03:32:19AM -0400, Prasun Gera wrote:
On Sun, Apr 23, 2017 at 03:32:19AM -0400, Prasun Gera wrote:
> Thank you. That worked for the master. How do I fix the replica's cert ?
> This is on ipa-server-4.4.0-14.el7_3.7.x86_64 on RHEL7. I am not using
> ipa's DNS at all. Did this happen because of that ?
>
This is not related to DNS.
To
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark as spam, and they gone from my inbox. :)
On 04/23/2017 05:10 PM, Prasun Gera wrote:
> This still continues to be a problem. Was any solution identified
> for this ? Why are the emails not obfuscated on the public archives
> ?
>
> On Tue, Dec
This still continues to be a problem. Was any solution identified for this
? Why are the emails not obfuscated on the public archives ?
On Tue, Dec 27, 2016 at 7:32 AM, Martin Basti wrote:
>
>
> On 27.12.2016 13:22, Outback Dingo wrote:
>
>> Im still getting nude porn spam
Thank you. That worked for the master. How do I fix the replica's cert ?
This is on ipa-server-4.4.0-14.el7_3.7.x86_64 on RHEL7. I am not using
ipa's DNS at all. Did this happen because of that ?
On Thu, Apr 20, 2017 at 9:06 PM, Fraser Tweedale
wrote:
> On Thu, Apr 20, 2017
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello!
I've successfully create replica, everything works fine but why my
signed CA certificate didn't automatically transfer to another
replica(s)? Is it normal?
Trying to add manually, but the certificate in replica(s) still using
self-signed.
Hi Jochen,
Thanks for your quick reply! As I just left the office I don't have the log
ATM. The installation however failed after setting up de Tomcat PKI service,
where the ipa-replica-install script was waiting for the service to come up.
While manually trying to reach the service using
I don't know that what we did is the most correct or even best way to
manage an upgrade, but here's what I did.
We started with two nodes, ipa1 and ipa2. Both running Fedora.
I built a new system, ipa3, and installed IPA on it, then made it a replica.
I then removed the replication agreements
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello!
Just update, manually add external CA(s) and signed certificated was
successful, but why it's didn't automatically transferred to
replica(s) from master.
On 04/22/2017 03:00 PM, Dewangga Bachrul Alam wrote:
> Hello!
>
> I've successfully
"B.harries" writes:
> Second attempt
> We then tried to install a fresh CentOS server, having FreeIPA version
> 4.4 and attaching it as a second master to our IPA instance. This
> however didn't work out as well,
I did that to move my installation from Fedora to CentOS
11 matches
Mail list logo