Displaying 20 results from an estimated 10000 matches similar to: "Mailman, junk mail, DMARC and DKIM"
2015 Mar 19
0
DMARC and DKIM in mailman.
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
2014 Nov 07
2
[OT] mail address - centos mail list
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
2018 Mar 28
0
DKIM, DMARC, mailman. Oh Joy!
On Thu, 29 Mar 2018 06:51:50 +1300
Andrew Bartlett via samba <samba at lists.samba.org> wrote:
> On Wed, 2018-03-28 at 19:28 +0200, Reindl Harald via samba wrote:
> > *every* single message from this mailing list has a reply-to header
> > to the poster, independent who is the poster, no other mailing-list
> > on planet earth has a reply-to-header - it's that simple
2018 Mar 28
0
DKIM, DMARC, mailman. Oh Joy!
Am 28.03.2018 um 20:21 schrieb Andrew Bartlett via samba:
> On Wed, 2018-03-28 at 19:11 +0100, Rowland Penny wrote:
>> On Thu, 29 Mar 2018 06:51:50 +1300
>> Andrew Bartlett via samba <samba at lists.samba.org> wrote:
>>
>> are you sure about that Andrew ?
>
> All my samba list messages are 'munged' as I described.
>
>> If I log into
2018 Mar 28
2
DKIM, DMARC, mailman. Oh Joy!
On Wed, 2018-03-28 at 19:28 +0200, Reindl Harald via samba wrote:
> *every* single message from this mailing list has a reply-to header to
> the poster, independent who is the poster, no other mailing-list on
> planet earth has a reply-to-header - it's that simple - period
So, e-mail is hard these days, and mailing list e-mail is even harder.
Read up about the interactions between
2018 Mar 28
1
DKIM, DMARC, mailman. Oh Joy!
On Wed, 28 Mar 2018 20:49:26 +0200
Reindl Harald via samba <samba at lists.samba.org> wrote:
>
>
> Am 28.03.2018 um 20:21 schrieb Andrew Bartlett via samba:
> > On Wed, 2018-03-28 at 19:11 +0100, Rowland Penny wrote:
> >> On Thu, 29 Mar 2018 06:51:50 +1300
> >> Andrew Bartlett via samba <samba at lists.samba.org> wrote:
> >>
> >>
2018 Mar 28
2
DKIM, DMARC, mailman. Oh Joy!
On Wed, 2018-03-28 at 19:11 +0100, Rowland Penny wrote:
> On Thu, 29 Mar 2018 06:51:50 +1300
> Andrew Bartlett via samba <samba at lists.samba.org> wrote:
>
> are you sure about that Andrew ?
All my samba list messages are 'munged' as I described.
> If I log into Mailman and go to 'Reply-To: header munging' it tells me
> that we aren't removing any
2014 Nov 13
0
Not To James B. Byrne
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
2014 May 12
1
OpenDKIM and SELinux
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
2012 Mar 22
1
CentOS-6, Postfix and Mailman
We have a bunch of lists hosted on a CentOS-4.9 server
running sendmail and mailman that we are moving to a
CentOS-6 vm running postfix and mailman. I am testing the
setup and I am running into a problem no doubt caused by
my own ignorance wrt postfix.
Based on groking the web I discovered that the recommended
way to configure postfix to work with mailman is a script
called
2015 Aug 01
3
centos 6 and mailman and dmarc
so... I've got some mailman lists running on centos 6. apparently c6
has mailman 2.1.12, which is far too old to have the dmarc patches
(introduced in 2.1.16 and updated in 2.1.??, so of course, I'm having
ongoing issues with yahoo/sbc/att/aol/etc subscribers and bouncing
messages ending up causing 30%+ of my subscribers not to be able to get
mail. These are mostly non-technical
2019 Sep 17
0
OT: DMARC / DKIM Failure Reports
On 2019-09-17 09:06, Miroslav Geisselreiter wrote:
> Hi guys,
>
> when I send e-mails to CentOS mailing list <centos at centos.org>, I
> received DMARC / DKIM failure reports. Is it possible to solve this
> problem and if so how?
>
That is why DMARC took 10 years of heated discussions, before it was
actually implemented - in first place by big boys who will never
2015 Mar 31
3
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
2019 Sep 17
2
OT: DMARC / DKIM Failure Reports
Hi guys,
when I send e-mails to CentOS mailing list <centos at centos.org>, I received DMARC / DKIM failure reports. Is it possible to solve this problem and if so how?
This is the first report:
This is an email abuse report for an email message received from IP 208.100.23.70 on Tue, 17 Sep 2019 15:56:25 +0200.
The message below did not meet the sending domain's DMARC policy.
For
2015 Apr 01
0
opendkim-2.9.0
On Tue, March 31, 2015 16:18, Frank Cox wrote:
> 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
2020 Jul 03
0
samab-4.10 nsupdate
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
2020 Jul 02
0
samab-4.10 nsupdate
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
2020 Jun 30
0
samab-4.10 nsupdate
> 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
2020 Jul 02
1
samab-4.10 nsupdate
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
2020 Jun 25
0
samba-4.10.15 - Unable to demote secodary DC
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