similar to: opendkim-2.9.0

There was an update to opendkim 2.10.1 which I applied and now I am seeing this: warning: connect to Milter service inet:127.0.0.1:8891: Connection refused I tried to yum history rollback to 2.9.1 but that package has disappeared so I am evidently constrained to resolve this. Does anyone have any idea what has happened and why I might be getting that message? -- *** E-Mail is NOT a

Following the most recent kernel updates I restarted our outgoing SMTP MTA which was recently reconfigured to DKIM sign messages using OpenDKIM. This morning I discovered that Postfix had stopped on that server. Whether it is related to the Postfix issue or not is yet to be determined but, in the process of getting things restarted I ran across this error with Open DKIM: # service opendkim

CentOS-6.5 OpenDKIM-2.9.0 (epel) Postfix-2.6.6 (updates) I am trying to get opendkim working with our mailing lists. In the course of that endeavour I note that these messages are appearing in our syslog: May 4 20:50:02 inet08 setroubleshoot: SELinux is preventing /usr/sbin/opendkim from using the signull access on a process. For complete SELinux messages. run sealert -l

On Tue, 31 Mar 2015 16:11:38 -0400 James B. Byrne wrote: > Does anyone have any idea what has happened and why I might be getting > that message? I don't use that but have you checked to see if you now have a "rpmsave" file left after installing the update? If so, that's your old configuration and you might need to re-write the new configuration file to incorporate your

On Wed, November 12, 2014 15:50, g wrote: > > > On 11/12/2014 10:13 AM, Les Mikesell wrote: > >> >> Well, no. Per the headers: >> >> Authentication-Results: mx.google.com; spf=neutral (google.com: >> centos-bounces at centos.org does not designate permitted sender hosts) >> smtp.mail=centos-bounces at centos.org; dkim=neutral (body hash did not

CentOS-6.6 Postfix-2.11.1 (local) ClamAV-0.98.5 (epel) Amavisd-new-2.9.1 (epel) opendkim-2.9.0 (centos) pypolicyd-spf-1.3.1 (epel) Is there something going on in selinuxland with respect to clamav, amavisd-new and postfix? Since the most recent update of clamav I seem to be detecting more avc's. It may be that it is because I am looking for them more frequently but it seems to me that

CentOS-6.6 Postfix-2.11.1 (local) ClamAV-0.98.5 (epel) Amavisd-new-2.9.1 (epel) opendkim-2.9.0 (centos) pypolicyd-spf-1.3.1 (epel) /var/log/maillog Dec 11 16:52:09 inet18 setroubleshoot: SELinux is preventing /usr/bin/perl from read access on the file online. For complete SELinux messages. run sealert -l 62006e35-dcc8-4a4f-8e10-9f34757f3a4a Dec 11 16:52:10 inet18 setroubleshoot: SELinux is

On Fri, May 6, 2016 04:36, John Hodrien wrote: > On Fri, 6 May 2016, Gary Stainburn wrote: > >> What I didn't expect, and what really threw me was that this has >> been implemented via a simply 'yum update' of an existing system, >> not at a major release level. > > > Something like RHEL is stuck in a trap here. Either they never > change a default

On Fri, November 7, 2014 12:10, Bob Marcan wrote: > Hi. > Your mails to centos mailing list are constantly marked as spam by > gmail.com. > Marking it nospam is annoying and had no effect on gmail filtering. > I can filter it into the proper folder, but this will only fix my problem. > Can you do anything in that matter? > > Best regards, Bob > I do not think that I

On 2/10/19 3:46 PM, Michael A. Peters via dovecot wrote: > On 2/10/19 3:42 PM, Noel Butler via dovecot wrote: >> On 10/02/2019 12:49, Benny Pedersen via dovecot wrote: >> >>> >>> fixing mailman will be the fail, solve it by letting opendkim and >>> opendmarc not reject detected maillist will be solution, >> >> >> A general broad mailing

https://rhn.redhat.com/errata/RHBA-2015-0706.html Looks like they have fixed the problem. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB at Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

https://bugzilla.redhat.com/show_bug.cgi?id=1095359 Jan Kalu?a <jkaluza at redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed In Version|mailman-2.1.12-22.el6 |mailman-2.1.12-23.el6 Tadaaah! -- *** E-Mail is NOT a SECURE channel *** James B. Byrne

On 10/02/2019 12:49, Benny Pedersen via dovecot wrote: > fixing mailman will be the fail, solve it by letting opendkim and opendmarc not reject detected maillist will be solution, A general broad mailing list whitelist will be problematic, do work it needs to look for specific list type hidden headers, spammers and nasties will incorporate those headers into their trash that impersonates

On 2/10/19 3:42 PM, Noel Butler via dovecot wrote: > On 10/02/2019 12:49, Benny Pedersen via dovecot wrote: > >> >> fixing mailman will be the fail, solve it by letting opendkim and >> opendmarc not reject detected maillist will be solution, > > > A general broad mailing list whitelist will be problematic, do work it > needs to look for specific list type

I changed the entries in smb4.conf (smb.conf) to this: [global] . . . dns update command = /usr/local/sbin/samba_dnsupdate nsupdate command = /usr/local/bin/samba-nsupdate -d -g And this is what results when I run: samba_dnsupdate --verbose -d8 --all-names . . . update(nsupdate): SRV _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.brockley.harte-lyne.ca

I am testing DC administration using samba-4.10.15 on FreeBSD-12.1p6 and have run across this: [root at smb4-2 ~ (master)]# samba-tool domain join BROCKLEY.HARTE-LYNE.CA DC -U"BROCKLEY\administrator" INFO 2020-06-25 14:26:10,692 pid:47306 /usr/local/lib/python3.7/site-packages/samba/join.py #104: Finding a writeable DC for domain 'BROCKLEY.HARTE-LYNE.CA' INFO 2020-06-25

This is all the diagnostic information I can think of at the moment: [root at smb4-1 ~ (master)]# klist Credentials cache: FILE:/tmp/krb5cc_0 Principal: administrator at BROCKLEY.HARTE-LYNE.CA Issued Expires Principal Jul 2 10:35:11 2020 Jul 2 20:35:11 2020 krbtgt/BROCKLEY.HARTE-LYNE.CA at BROCKLEY.HARTE-LYNE.CA [root at smb4-1 ~ (master)]# grep nsup

> Could be because you added the wrong line to your smb4.conf (why does > freebsd call it smb4.conf ?), Why does freebsd put these things in /usr/local/etc/? Some questions have answers that are not worth the effort to know. > try: > nsupdate command = /usr/local/sbin/nsupdate -g I did catch that error earlier. But it makes no difference. samba_dnsupdate does not give any

Thank you for your patience. On Tue, June 30, 2020 16:48, Rowland penny wrote: > > From 'man smb.conf': > > nsupdate command (G) > > This option sets the path to the nsupdate command which is used for > GSS-TSIG dynamic DNS updates. > > Default: nsupdate command = /usr/bin/nsupdate -g > > dns update command (G) > > This

I have introduced some error in my dns resolution and I would like some help fixing it as I cannot seem to detect what I have done wrong. Briefly the setup is this: name servers: DNS01 - 216.185.71.33 DNS02 - 209.47.176.33 DNS03 - 216.185.71.34 DNS04 - 209.47.176.34 - offline DNS01 is a master DNS02-04 are slaves of 216.185.71.33 All are listed as authoritative for the zone test.com The