Resolved Upgrade Postfix but use as normal afterwards within Plesk

[learning_curve]

i was to tired to translate whole Error Message. As you can see, i am writing in english ;-) ahhh. #

I installed the missing packages and it worked. I later on saw the Post and firstly misunderstood it. I thought you ignored also the missing packages. I was wrong there

Ahhh Understand now Yes Post#5 on this thread shows us ignoring the warnings and installing the missing packages.
So you've already done this and it's all okay now. Sounds good!

 

[mdde]

@learning_curve its working perfectly know.
I even test the Email delivery (I forgot last time and mailq got full, my gosh :-/)
btw. Its a pity that Cloudlinux has got such old Postfix :/

 

[EricRB]

What about just

# yum install rpm-build openldap-devel cyrus-sasl-devel
# wget http://repos.oostergo.net/7/SRPMS/postfix-3.2.3-1.el7.centos.src.rpm
# rpmbuild --rebuild postfix-3.2.3-1.el7.centos.src.rpm
# rpm -Uvh /root/rpmbuild/RPMS/x86_64/postfix-3.2.3-1.el7.centos.x86_64.rpm
# touch /etc/postfix/postfix-files
# postfix set-permissions
# systemctl restart postfix
# systemctl status postfix
● postfix.service - Postfix Mail Transport Agent
Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2017-10-09 12:52:07 NOVT; 6s ago
Process: 20748 ExecStop=/usr/sbin/postfix stop (code=exited, status=0/SUCCESS)
Process: 20766 ExecStart=/usr/sbin/postfix start (code=exited, status=0/SUCCESS)
Process: 20763 ExecStartPre=/usr/libexec/postfix/chroot-update (code=exited, status=0/SUCCESS)
Process: 20759 ExecStartPre=/usr/libexec/postfix/aliasesdb (code=exited, status=0/SUCCESS)
Main PID: 20840 (master)
CGroup: /system.slice/postfix.service
├─20840 /usr/libexec/postfix/master -w
├─20841 pickup -l -t fifo -u
└─20842 qmgr -l -t fifo -u

Oct 09 12:52:07 ppu17-5.demo.pp.plesk.ru postfix[20766]: Postfix is running with backwards-compatible default settings
Oct 09 12:52:07 ppu17-5.demo.pp.plesk.ru postfix[20766]: See Postfix Backwards-Compatibility Safety Net for details
Oct 09 12:52:07 ppu17-5.demo.pp.plesk.ru postfix[20766]: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload"
Oct 09 12:52:07 ppu17-5.demo.pp.plesk.ru postfix/postfix-script[20835]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop
Oct 09 12:52:07 ppu17-5.demo.pp.plesk.ru postfix/postfix-script[20838]: starting the Postfix mail system
Oct 09 12:52:07 ppu17-5.demo.pp.plesk.ru postfix/master[20840]: daemon started -- version 3.2.3, configuration /etc/postfix

Hi Igor,
I note that after 3.25-1.el7.centos.src.rpm at oostergo.net, they dropped the ".centos" part of the file names, i.e., next is postfix-3.2.6-2.el7.src.rpm and all the way down to the current package, postfix-3.5.7-1.el7.src.rpm, there is no ".centos" in the file name. I'm assuming these are centos packages? And second question: I'm assuming that the same instructions would hold for upgrading postfix 2.10.1 to 3.5.7 ???

Eric

 

[IgorG]

postfix-3.5.7-1.el7.src.rpm, there is no ".centos" in the file name. I'm assuming these are centos packages?

Yes, "el7" means CentOS 7.

I'm assuming that the same instructions would hold for upgrading postfix 2.10.1 to 3.5.7 ???

I have not tried this upgrade.