Discuss

discuss@lists.centos.org

12 participants
34747 discussions

How do I default to "Folder View" in my custom KDE user profile?
by Nicolas Kovacs 14 Nov '16

14 Nov '16

Hi, I'm currently busy tweaking KDE 4.14 on CentOS 7 to my needs. I want to use it as a base for an enterprise class desktop. In my humble opinion, CentOS' default KDE configuration is not very usable, so I created a default user profile that looks more like what openSUSE looked like a few years back. Here's the little script I'm using to install the various configuration files and stubs in the relevant places: https://github.com/kikinovak/centos/blob/master/el7/scripts/05-installer-pr… And here are the files that are harmed during the process: :) https://github.com/kikinovak/centos/tree/master/el7/kde What I did basically was to modify the panel's size, add a handful of default application launchers to the panel and to the kickoff menu, define Firefox and Thunderbird as default applications, default to double-click instead of single-click, define a set of defaults for the window manager, tweak a few things for Dolphin and Konsole, and add a nice custom wallpaper. The result is a sober-looking KDE desktop fit for use in a production environment. One thing I can't seem to define is a default "folder view" for the desktop. Instead of the plasmoids on the desktop introduced with KDE4, I'd like my environment to behave like a "classic" desktop with folders and files on the desktop, and where a right click can - for example - create a folder. My KDE is in french, but if I remember correctly, this setup is called "Folder View" in english. Question: how can I define this behavior as default? Which file or stub do I have to put in /etc/skel so a newly created user's KDE defaults to "Folder View"? Cheers from the sunny South of France, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

2 1

Centos OS Crash Recovery, Inquiry.
by Christopher G. Halnin 12 Nov '16

12 Nov '16

Dear Sir/s, As I have mentioned in my previous email, is there a way to recover or bring back to life a crashed Centos OS after doing a Hard Driver repartition or resizing? Thanks. Regards, CHRIS

7 9

CentOS-announce Digest, Vol 141, Issue 2
by centos-announce-request＠centos.org 12 Nov '16

12 Nov '16

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CEBA-2016:2660 CentOS 6 tzdata BugFix Update (Johnny Hughes) 2. CESA-2016:2658 Important CentOS 6 java-1.7.0-openjdk Security Update (Johnny Hughes) 3. CESA-2016:2674 Moderate CentOS 6 libgcrypt Security Update (Johnny Hughes) 4. CESA-2016:2675 Important CentOS 6 pacemaker Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Sat, 12 Nov 2016 06:28:43 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:2660 CentOS 6 tzdata BugFix Update Message-ID: <20161112062843.GA33086(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:2660 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-2660.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 79aadf39d1fbd4fc83ab9dc610110e23499aac90754707c89cf360a8fd328eea tzdata-2016i-1.el6.noarch.rpm 6e10e00482045d3aea477a5bcb2d5eada4296eeabe8d4aea1c6eab1b7c48dddf tzdata-java-2016i-1.el6.noarch.rpm x86_64: 79aadf39d1fbd4fc83ab9dc610110e23499aac90754707c89cf360a8fd328eea tzdata-2016i-1.el6.noarch.rpm 6e10e00482045d3aea477a5bcb2d5eada4296eeabe8d4aea1c6eab1b7c48dddf tzdata-java-2016i-1.el6.noarch.rpm Source: f76d0dd2edefea0abd1baacdf5ab023faa266a0470ff1aed2b381af1047c8ed0 tzdata-2016i-1.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Sat, 12 Nov 2016 06:29:49 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:2658 Important CentOS 6 java-1.7.0-openjdk Security Update Message-ID: <20161112062949.GA33373(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:2658 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-2658.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 84471d342bae31c540a46012d4744ece56043c3f6d144c05434049aa2a0b6fe9 java-1.7.0-openjdk-1.7.0.121-2.6.8.1.el6_8.i686.rpm b982f2a265d95d25fc7fcbafc566a03bf5631f3134a568ccc6d98eef0b863055 java-1.7.0-openjdk-demo-1.7.0.121-2.6.8.1.el6_8.i686.rpm c60467173506f6c67175823eddb932f9a45f2f25272603ecaf277b7c50e2e952 java-1.7.0-openjdk-devel-1.7.0.121-2.6.8.1.el6_8.i686.rpm 764968076a17b338e82d7f799751003b6b4f783d6182b8623b383a889de3ef08 java-1.7.0-openjdk-javadoc-1.7.0.121-2.6.8.1.el6_8.noarch.rpm 4d7073f9fc9861874b0f7553423a5e492d2d204171de886417f32e8fc6c1e548 java-1.7.0-openjdk-src-1.7.0.121-2.6.8.1.el6_8.i686.rpm x86_64: 1be5736e5227ad2084c78ca2e578bf4cadd319d1d68699987999ebabd7179a01 java-1.7.0-openjdk-1.7.0.121-2.6.8.1.el6_8.x86_64.rpm d9903a233c4d5249dd51fd2f57d1e611fde97cbc58acd88a760fd222a518787c java-1.7.0-openjdk-demo-1.7.0.121-2.6.8.1.el6_8.x86_64.rpm 7db634dc3a6aeed8009f260bc4fe88c3ea77cedd9f34a68ed839cc26f16f3f57 java-1.7.0-openjdk-devel-1.7.0.121-2.6.8.1.el6_8.x86_64.rpm 764968076a17b338e82d7f799751003b6b4f783d6182b8623b383a889de3ef08 java-1.7.0-openjdk-javadoc-1.7.0.121-2.6.8.1.el6_8.noarch.rpm 4bef0534d5ea08cd102cf80b227ce582ddb8923f891991cd3a03936195ad607b java-1.7.0-openjdk-src-1.7.0.121-2.6.8.1.el6_8.x86_64.rpm Source: 8062121312b899bfb1d0b784f2d5b23687f72b72982d7c517973f2a147af15ee java-1.7.0-openjdk-1.7.0.121-2.6.8.1.el6_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Sat, 12 Nov 2016 06:30:21 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:2674 Moderate CentOS 6 libgcrypt Security Update Message-ID: <20161112063021.GA33618(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:2674 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-2674.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 12f569a66c65aedcf6899fdc85fd4a7ece9179735863e8863c3819b03b901faf libgcrypt-1.4.5-12.el6_8.i686.rpm 6d5a5300eff1d6313c70288692d69341c1cafe0d6748ff4d9b2c5ff0a3e49874 libgcrypt-devel-1.4.5-12.el6_8.i686.rpm x86_64: 12f569a66c65aedcf6899fdc85fd4a7ece9179735863e8863c3819b03b901faf libgcrypt-1.4.5-12.el6_8.i686.rpm 81c29e7ec131ff3f1e867679b355228ebf9c10a57a680c40766a118a71d7ba71 libgcrypt-1.4.5-12.el6_8.x86_64.rpm 6d5a5300eff1d6313c70288692d69341c1cafe0d6748ff4d9b2c5ff0a3e49874 libgcrypt-devel-1.4.5-12.el6_8.i686.rpm e978512343d86c5435f0dc3585d5816d7495db711d137fdb8f5f6a21dd363baf libgcrypt-devel-1.4.5-12.el6_8.x86_64.rpm Source: e7510256aa30561185faf8b9e6881f714a19d18ee39f0a39a949d28a97d83114 libgcrypt-1.4.5-12.el6_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Sat, 12 Nov 2016 06:32:37 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:2675 Important CentOS 6 pacemaker Security Update Message-ID: <20161112063237.GA34048(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:2675 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-2675.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 31fcac629b2920ab0f812e81e39492739260a8af612071327b80bbdd4b45f01c pacemaker-1.1.14-8.el6_8.2.i686.rpm ae677515b8583c8c309e9d1560424a55c25af318493122562a3c972cf8b91cb9 pacemaker-cli-1.1.14-8.el6_8.2.i686.rpm b064c53ab4f71121ecbd81d95f1de311a0e17d4e42a3d62963e7202129ec3d43 pacemaker-cluster-libs-1.1.14-8.el6_8.2.i686.rpm 081b0eb88c806d26fadfb17d0da03e08fefd28883eab6cdf55c5ac83dffbe3c3 pacemaker-cts-1.1.14-8.el6_8.2.i686.rpm 931c3a4015b8496481d81b4c4ee71688de4e5f31d76a25f76aff1cb2baa6916b pacemaker-doc-1.1.14-8.el6_8.2.i686.rpm ab42e45a1bb11e878f75f3a1ef965b4856701308394aa2cae3ff2bb480791c6e pacemaker-libs-1.1.14-8.el6_8.2.i686.rpm 5733ce005f7c73a20eba6b6d357c4c92bef405b670a7f2625a17ed16e5125e7f pacemaker-libs-devel-1.1.14-8.el6_8.2.i686.rpm 8a0aa1ea6a089661264601fc8764a36fda3b50883884c167f50bd9eb80ef1c0a pacemaker-remote-1.1.14-8.el6_8.2.i686.rpm x86_64: 945d27b8bcab2a8c05590a80488f0261031dfc97cf48d4ef97f97df42a8eba93 pacemaker-1.1.14-8.el6_8.2.x86_64.rpm c36a46fb2696beec1d546bb5d840d174e240c200a2c64397024726451bfef2d2 pacemaker-cli-1.1.14-8.el6_8.2.x86_64.rpm b064c53ab4f71121ecbd81d95f1de311a0e17d4e42a3d62963e7202129ec3d43 pacemaker-cluster-libs-1.1.14-8.el6_8.2.i686.rpm d7be10dbe33f1a6f440869f1e0036e608e2c450b222df503f6ff43de8052e511 pacemaker-cluster-libs-1.1.14-8.el6_8.2.x86_64.rpm 2bb04399c0c8e66f8901b2c1bfd950a262ef9ef4939557bf4b31fe1c5654dff8 pacemaker-cts-1.1.14-8.el6_8.2.x86_64.rpm 4a2e619571742e7209381f10c70fc1ea164b23e203be418e598aeb01e9f74c26 pacemaker-doc-1.1.14-8.el6_8.2.x86_64.rpm ab42e45a1bb11e878f75f3a1ef965b4856701308394aa2cae3ff2bb480791c6e pacemaker-libs-1.1.14-8.el6_8.2.i686.rpm 95c0ec0e5f9e8299e63d4608f7f5cc59c242f236dae863db528e9b9b12536f8d pacemaker-libs-1.1.14-8.el6_8.2.x86_64.rpm 5733ce005f7c73a20eba6b6d357c4c92bef405b670a7f2625a17ed16e5125e7f pacemaker-libs-devel-1.1.14-8.el6_8.2.i686.rpm 3d0cad04cca12d659af5c339d0e81af4ea284d3e368bf1626f5c817a46e7e55e pacemaker-libs-devel-1.1.14-8.el6_8.2.x86_64.rpm 43b32a61d459a602b0ed26674f4b7bd2f5a3a8f5243453d0d938127a94b1c1ca pacemaker-remote-1.1.14-8.el6_8.2.x86_64.rpm Source: 0f71956e745c651f330c1f45e0a88648ccd86e6b82cf4d99f12396d3310375b8 pacemaker-1.1.14-8.el6_8.2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 141, Issue 2 ***********************************************

1 0

clamd@amavisd fails under systemd
by Rob Kampen 12 Nov '16

12 Nov '16

Trying to set up a mail server under CentOS7 - having done this with CentOS5 and CentOS6 over the last decade with no issues and reliable service, it was time to upgrade (?) to CentOS7. Shouldn't be a problem, right? Getting to grips with systemd has been challenging - to say the least. So a brief overview of what I am trying to set up: postfix / amavisd-new / spamassassin / clamav so we can receive mail and deal with the major rubbish that gets thrown at any open port 25 smtp service. no problems installing each of the above and their configuration files. Just as an aside, there are many recipes for this combo of packages - none of which work as advertised. There was a time when one could safely follow a how-to guide and have things working - I have regularly used the CentOS wiki guides - however they have become stale and what worked fine for 5 & 6 DO NOT WORK for CentOS7 - mainly due to systemd and firewalld So we have: systemctl status postfix.service ● postfix.service - Postfix Mail Transport Agent Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2016-10-26 18:13:25 EDT; 1 weeks 5 days ago Main PID: 2762 (master) CGroup: /system.slice/postfix.service ├─ 2762 /usr/libexec/postfix/master -w ├─ 2782 qmgr -l -t unix -u └─25274 pickup -l -t unix -u systemctl status spamassassin.service ● spamassassin.service - Spamassassin daemon Loaded: loaded (/usr/lib/systemd/system/spamassassin.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2016-11-08 05:18:04 EST; 50min ago Process: 27412 ExecStart=/usr/bin/spamd --pidfile /var/run/spamd.pid $SPAMDOPTIONS (code=exited, status=0/SUCCESS) Process: 27410 ExecStartPre=/sbin/portrelease spamd (code=exited, status=0/SUCCESS) Main PID: 27417 (/usr/bin/spamd ) CGroup: /system.slice/spamassassin.service ├─27417 /usr/bin/spamd --pidfile /var/run/spamd.pid -d -c -m5 -H ├─27418 spamd child └─27419 spamd child systemctl status amavisd.service ● amavisd.service - Amavisd-new is an interface between MTA and content checkers. Loaded: loaded (/usr/lib/systemd/system/amavisd.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2016-11-08 05:18:05 EST; 50min ago Docs: http://www.ijs.si/software/amavisd/#doc Process: 27426 ExecStart=/usr/sbin/amavisd -c /etc/amavisd/amavisd.conf (code=exited, status=0/SUCCESS) Main PID: 27427 (/usr/sbin/amavi) CGroup: /system.slice/amavisd.service ├─27427 /usr/sbin/amavisd (master) ├─27479 /usr/sbin/amavisd (ch1-avail) └─27480 /usr/sbin/amavisd (ch1-avail) but for the life of me, I cannot get clamd@amavisd to stay up. It always comes up and then dies after about 1 second : systemctl status clamd(a)amavisd.service ● clamd(a)amavisd.service - clamd scanner (amavisd) daemon Loaded: loaded (/usr/lib/systemd/system/clamd@.service; enabled; vendor preset: disabled) Active: inactive (dead) since Tue 2016-11-08 05:18:13 EST; 34min ago Process: 27421 ExecStart=/usr/sbin/clamd -c /etc/clamd.d/%i.conf (code=exited, status=0/SUCCESS) Main PID: 27421 (code=exited, status=0/SUCCESS) Nov 08 05:18:11 media.xxxx.xxx clamd[27481]: OLE2 support enabled. Nov 08 05:18:11 media.xxxx.xxx clamd[27481]: PDF support enabled. Nov 08 05:18:11 media.xxxx.xxx clamd[27481]: SWF support enabled. Nov 08 05:18:11 media.xxxx.xxx clamd[27481]: HTML support enabled. Nov 08 05:18:11 media.xxxx.xxx clamd[27481]: XMLDOCS support enabled. Nov 08 05:18:11 media.xxxx.xxx clamd[27481]: HWP3 support enabled. Nov 08 05:18:11 media.xxxx.xxx clamd[27481]: Self checking every 600 seconds. Nov 08 05:18:13 media.xxxx.xxx clamd[27481]: Pid file removed. Nov 08 05:18:13 media.xxxx.xxx clamd[27481]: --- Stopped at Tue Nov 8 05:18:13 2016 Nov 08 05:18:13 media.xxxx.xxx clamd[27481]: Socket file removed. I can run the clamd service manually just fine and everything works - i.e. /usr/sbin/clamd -c /etc/clamd.d/amavisd.conf –nofork=yes returns a functioning service - thus my config files must be okay but try it with systemd and you hit a brick wall - nothing in any logs to give me a clue why it comes up and then closes down After many days of google chasing, I have found a number of folk hitting the same issue, yet none of these have posted anything resembling a solution, most have had other issues that were in error. If there is anyone that has this combo of services working under CentOS7 and can shed any insight on why I cannot get this service to actually run, it would be very much appreciated. TIA Rob

3 8

ldns-dane
by James B. Byrne 11 Nov '16

11 Nov '16

This is an epel package but I thought that I would ask here first. I am encountering unexpected behaviour from this program and I would like to know if it is a bug, or I am configuring something wrong, of if this is intended behaviour. ldns-dane version 1.6.16 (ldns version 1.6.16) When I attempt to specify the entire certificate as the desired data source for this program I get the following error: ldns-dane \ -n -o 0 \ -c CA_HLL_ROOT_2016.pem \ create harte-lyne.ca 443 \ 2 0 2 <selector> should be in range [0-1] Likewise I cannot specify the output format as no-hash. ldns-dane \ -n -o 0 \ -c CA_HLL_ROOT_2016.pem \ create harte-lyne.ca 443 \ 2 1 0 <matching type> should be in range [0-2] In fact, 0 is not an accepted value in any of these positions: ldns-dane \ -n -o 0 \ -c CA_HLL_ROOT_2016.pem \ create harte-lyne.ca 443 \ 0 1 1 <certificate usage> should be in range [0-3] Why is zero invalid? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@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

1 0

Trouble setting up HP Officejet Pro 8600 printer on CentOS 7 + KDE
by Nicolas Kovacs 11 Nov '16

11 Nov '16

Hi, I just installed a CentOS 7 + KDE desktop in my office's network. So far, I'm quite happy with the results, though I have some trouble getting the printer to work. All the other machines in my office (server, desktops, workstation) are running Slackware64 14.1 or 14.2, and they can all use the printer perfectly. I installed hplip-gui and ran it. The printer is a network printer, it has a static IP in the network and can also be addressed by its hostname. [kikinovak@alphamule:~] $ host hp-officejet hp-officejet.microlinux.lan has address 192.168.2.252 When I run hp-setup with the default options, the setup program "sees" the printer, but informs me that there is a "communication problem". I figure this is because the default seach method is mDNS/Bonjour. I tried again with the SLP option, and this time the setup procedure went OK. Or it seemed so, as the test page was blank. Now what? A few details about my system: SELinux, IPv6 and firewall are disabled. CUPS is running OK. I checked on the HP website that this printer requires HPLIP 3.11.10 or greater, which seems OK, since the HPLIP version shipping with CentOS is 3.13.something. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

2 3

Relocation of logfiles in logwatch
by adrian＠pa0rda.nl 11 Nov '16

11 Nov '16

Hi, I try to teach logwatch that some of my logfiles are relocated. E.g., mail mailog now lives in mail/info and secure has moved too auth/info. I adjusted /etc/logwatch/conf/logfiles/SERVICE.conf accordingly but logwatch does not understand. What is the right way to adapt logwatch to the new reality? Adrian -- Adri P. van Bloois Antonlaan 104 email: adrian(a)pa0rda.nl 3701 VG Zeist voice: +31-(0)-30-6912741 The Netherlands fax: NONE 52 05'15.77"N 5 4'44.56"E QTH-locater JO 22 OC "Elegance is not a dispensable luxury but a factor that decides between success and failure." Edsger W. Dijkstra

1 0

cent7 package librados2 appears to be 2 versions behind red hat. any reason for this?
by Christian, Mark 10 Nov '16

10 Nov '16

Any chance we can get the following package built and added to the centos mirrors? $ rpm -qpi librados2-0.94.5-1.el7.x86_64.rpm warning: librados2-0.94.5-1.el7.x86_64.rpm: Header V3 RSA/SHA256 signature: NOKEY, key ID fd431d51 Name : librados2 Relocations: (not relocatable) Version : 0.94.5 Vendor: Red Hat, Inc. Release : 1.el7 Build Date: Wed 22 Jun 2016 12:33:13 PM PDT Install Date: (not installed) Build Host: x86- 017.build.eng.bos.redhat.com Group : System Environment/Libraries Source RPM: ceph-common-0.94.5- 1.el7.src.rpm Size : 5342816 License: LGPL-2.0 Signature : RSA/8, Tue 27 Sep 2016 02:49:30 AM PDT, Key ID 199e2f91fd431d51 Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> URL : http://ceph.com/ Summary : RADOS distributed object store client library Description : RADOS is a reliable, autonomic distributed object storage cluster developed as part of the Ceph distributed storage system. This is a shared library allowing applications to access the distributed object store using a simple file-like interface. Thank you, Mark

2 1

glusterfs bits..
by lejeczek 10 Nov '16

10 Nov '16

hi everyone before I subscribe to yet another @list I was hoping a centosian here has some experience and know the answer - I've started googling but have to failed - glusterfs does not translate local FS (xfs) quotas and presents them to its clients, does it? It is only glusterfs own quota functions that we have to manage quoatas? many thanks. L.

1 0

mailing list mail from @yahoo addresses
by Richard 10 Nov '16

10 Nov '16

[extracted from "Re: [CentOS] dnf and failing epel" message chain.] > From: lejeczek peljasz at yahoo.co.uk > Date: Fri Nov 4 13:39:40 UTC 2016 >> Date: Friday, November 04, 2016 08:51:07 -0400 >> From: Jonathan Billings <billings(a)negate.org> >> >>> On Fri, Nov 04, 2016 at 12:30:02PM +0000, lejeczek wrote: >>> >>> ps. I wonder if my email get though to the group, I receive >>> mailing list emails but I don't get my own emails? >> >> You can sign into this URL: >> >> https://lists.centos.org/mailman/listinfo/centos >> >> ... and change the settings. One of the settings is whether to >> "Receive your own posts to the list". Make sure it is marked as >> "yes". > > it's been there always. > Some mailing lists I do have this problem with, others work > fine, and it's not the settings reason, certainly not that > one setting and rest looks ok too. > I wonder if Centos mailman uses some blocking/blacklisting? > But then why the group gets my emails but me? I believe that the issue is that yahoo updated their dmarc record a bit ago, so now won't accept mail, from 3rd-parties, that has an @yahoo... "mailfrom", as yours do on this list. If the non-@yahoo mailing sender doesn't do what's necessary to deal with enforced dmarc, and your mail provider enforces dmarc, you won't see messages from @yahoo correspondents -- which is likely why you aren't seeing your own list messages. Additionally if a mailing list has enough @yahoo posters, this can generate sufficient bounces to get you kicked off the mailing list on a regular basis. There are various ways for mailers/mailing lists to deal with the enforced dmarc. My understanding is that with Mailman, which this list uses, one has to upgrade to -3. Email service providers can't send to/from Yahoo Mail addresses Questions about our DMARC policy Why are my emails bouncing? We've updated the DMARC record with "p=reject" for multiple Yahoo domains. This means all DMARC compliant mail receivers (including Yahoo, Hotmail, and Gmail) are now bouncing emails sent as "@yahoo.com" addresses that aren't sent through Yahoo servers. Any messages without a proper Domain Keys Identified Mail (DKIM) signature or Sender Policy Framework (SPF) alignment will be rejected. <https://help.yahoo.com/kb/SLN24016.html> <https://yahoomail.tumblr.com/post/82426900353/yahoo-dmarc-policy-change-wha…>

6 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss