Hi,
I administer a postfix mail server on CentOS 6. Now I want to setup another with similar configuration.
But the postgrey package is no longer available in Epel for this CentOS release as I have seen now: https://admin.fedoraproject.org/pkgdb/package/rpms/postgrey/
1. Will I have to make an upgrade of the existing mail server to get security patches again or is it not critical to use the old package?
2. Can you give advice for an alternative setup of greylisting for postfix on CentOS 6?
Cheers,
Gabriele
On 23/04/16 02:13, Gabriele Pohl wrote:
I administer a postfix mail server on CentOS 6. Now I want to setup another with similar configuration.
But the postgrey package is no longer available in Epel for this CentOS release as I have seen now: https://admin.fedoraproject.org/pkgdb/package/rpms/postgrey/
- Will I have to make an upgrade of the existing mail server to get security patches again or is it not critical to use the old package?
You will have to get advice from the epel peopel for support for postgrey.
- Can you give advice for an alternative setup of greylisting for postfix on CentOS 6?
Postgrey is largely obsoleted by postscreen which comes with postfix versions 2.8 and up. You can get the latest postfix (including postscreen) for CentOS 6 from GhettoForge (www.ghettoforge.org).
Peter
On Sat, 23 Apr 2016 02:23:28 +1200 Peter peter@pajamian.dhs.org wrote:
On 23/04/16 02:13, Gabriele Pohl wrote:
I administer a postfix mail server on CentOS 6. Now I want to setup another with similar configuration.
But the postgrey package is no longer available in Epel for this CentOS release as I have seen now: https://admin.fedoraproject.org/pkgdb/package/rpms/postgrey/
- Can you give advice for an alternative setup of greylisting for postfix on CentOS 6?
Postgrey is largely obsoleted by postscreen which comes with postfix versions 2.8 and up. You can get the latest postfix (including postscreen) for CentOS 6 from GhettoForge (www.ghettoforge.org).
Thanks for your help and so quickly :)
I decided to try with current version of postgrey from projects github repository. https://github.com/schweikert/postgrey/releases/tag/version-1.36 as I want to avoid using more 3rd party repos.
Doing the first steps in manual installation (create directory and user) I found out, that I lack from knowledge on "ls" output..
There is a difference that I don't understand.
What does the "." at the right side of the attributes list mean?
directory manually created on the shell: drwxr-x--x 2 postgrey postfix 4096 Apr 22 17:19 /var/spool/postfix/postgrey/
created by package installation: drwxr-x--x. 2 postgrey postfix 4096 Apr 13 16:23 /var/spool/postfix/postgrey
I used this commands to create the first one
# mkdir /var/spool/postfix/postgrey # chmod 751 /var/spool/postfix/postgrey # groupadd --gid 493 postgrey # useradd --system --gid 493 --uid 493 --home /var/spool/postfix/postgrey -M --shell /sbin/nologin postgrey # chown postgrey /var/spool/postfix/postgrey # chgrp postfix /var/spool/postfix/postgrey
Can you give explanation what is causing the difference compared to the package created directory?
Gabriele
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Gabriele Pohl Sent: Friday, April 22, 2016 11:53 AM To: centos@centos.org Subject: [CentOS] output of "ls" (was: Re: Postgrey on CentOS 6)
On Sat, 23 Apr 2016 02:23:28 +1200 Peter peter@pajamian.dhs.org wrote:
On 23/04/16 02:13, Gabriele Pohl wrote:
I administer a postfix mail server on CentOS 6. Now I want to setup another with similar configuration.
But the postgrey package is no longer available in Epel for this CentOS release as I have seen now: https://admin.fedoraproject.org/pkgdb/package/rpms/postgrey/
- Can you give advice for an alternative setup of greylisting for postfix on CentOS 6?
Postgrey is largely obsoleted by postscreen which comes with postfix versions 2.8 and up. You can get the latest postfix (including postscreen) for CentOS 6 from GhettoForge (www.ghettoforge.org).
Thanks for your help and so quickly :)
I decided to try with current version of postgrey from projects github repository. https://github.com/schweikert/postgrey/releases/tag/version-1.36 as I want to avoid using more 3rd party repos.
Doing the first steps in manual installation (create directory and user) I found out, that I lack from knowledge on "ls" output..
There is a difference that I don't understand.
What does the "." at the right side of the attributes list mean?
Following the file mode bits is a single character that specifies whether an alternate access method such as an access control list applies to the file. When the character following the file mode bits is a space, there is no alternate access method. When it is a printing character, then there is such a method.
GNU `ls' uses a `.' character to indicate a file with an SELinux security context, but no other alternate access method.
A file with any other combination of alternate access methods is marked with a `+' character.
directory manually created on the shell: drwxr-x--x 2 postgrey postfix 4096 Apr 22 17:19 /var/spool/postfix/postgrey/
created by package installation: drwxr-x--x. 2 postgrey postfix 4096 Apr 13 16:23 /var/spool/postfix/postgrey
I used this commands to create the first one
# mkdir /var/spool/postfix/postgrey # chmod 751 /var/spool/postfix/postgrey # groupadd --gid 493 postgrey # useradd --system --gid 493 --uid 493 --home /var/spool/postfix/postgrey - M --shell /sbin/nologin postgrey # chown postgrey /var/spool/postfix/postgrey # chgrp postfix /var/spool/postfix/postgrey
Can you give explanation what is causing the difference compared to the package created directory?
Gabriele
On Fri, 22 Apr 2016 16:05:52 +0000 Richard Mann rmann@ilsworld.com wrote:
What does the "." at the right side of the attributes list mean?
Following the file mode bits is a single character that specifies whether an alternate access method such as an access control list applies to the file. When the character following the file mode bits is a space, there is no alternate access method. When it is a printing character, then there is such a method.
GNU `ls' uses a `.' character to indicate a file with an SELinux security context, but no other alternate access method. A file with any other combination of alternate access methods is marked with a `+' character.
ah, I only had a look at the man page of "ls", but this explanation can be found by
info coreutils 'ls invocation'
I will expand my search to info pages from now on ;(
Sorry for the noise and thanks for your hint!
Gabriele