Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I want to upgrade my postfix installation on my Debian Etch server from 2.3.8 to 2.9.5 in an attempt to fight the tremendous amount of spam reaching my mailserver. Currently the server receives about 20 spam mails every second. Most of them are filtered out by spamassassin but I want to free up the postfix processes by using postscreen(8).
I did a test first in a virtual environment (which is pretty much a copy of my production server). I downloaded the source from postfix.org and ran
Code:
make upgrade
That succeeded without errors. But apparently, my /etc/init.d/postfix script no longer worked.
Anyway, I was wondering if this is the proper way to upgrade postfix. And if so, how can I get the script working again? And will my postfix configuration files still work? Anything else I need to watch out for?
Thanks in advance, any help and any suggestions are greatly appreciated!
Etch is WELL out of security support.
You should look at upgrading to Lenny (currently oldstable), then Squeeze (current stable) at least (Wheezy is due out shortly).
I know, but there's a reason this server is still running Etch. It will be replaced by a new server (with either Squeeze or Wheezy) this summer. Until then, I want to upgrade postfix (amongst other things).
The reason I want to upgrade is because since yesterday, my mailserver is being flooded with requests like these
Code:
Feb 4 22:10:42 server1 postfix/smtpd[27460]: NOQUEUE: reject: RCPT from unknown[187.242.135.149]: 554 5.7.1 Service unavailable; Client host [187.242.135.149] blocked using zen.spamhaus.org; http://www.spamhaus.org/query/bl?ip=187.242.135.149; from=<maintainp95@bernina.co.il> to=<c0a5e4b@mydomain.com> proto=ESMTP helo=<customer-TOR-135-149.megared.net.mx>
Feb 4 22:10:42 server1 postfix/smtpd[29771]: NOQUEUE: reject: RCPT from r186-54-139-10.dialup.adsl.anteldata.net.uy[186.54.139.10]: 554 5.7.1 Service unavailable; Client host [186.54.139.10] blocked using zen.spamhaus.org; http://www.spamhaus.org/query/bl?ip=186.54.139.10; from=<alliterationsd7@pip.com.au> to=<vansommeren@mydomain.com> proto=ESMTP helo=<anteldata.net.uy>
Feb 4 22:10:42 server1 postfix/smtpd[27460]: lost connection after DATA from unknown[187.242.135.149]
Feb 4 22:10:42 server1 postfix/smtpd[27460]: disconnect from unknown[187.242.135.149]
Feb 4 22:10:42 server1 postfix/smtpd[28661]: connect from unknown[93.155.169.232]
Feb 4 22:10:42 server1 postfix/smtpd[29771]: lost connection after DATA from r186-54-139-10.dialup.adsl.anteldata.net.uy[186.54.139.10]
Feb 4 22:10:42 server1 postfix/smtpd[29771]: disconnect from r186-54-139-10.dialup.adsl.anteldata.net.uy[186.54.139.10]
Feb 4 22:10:42 server1 postfix/smtpd[28661]: NOQUEUE: reject: RCPT from unknown[93.155.169.232]: 554 5.7.1 Service unavailable;Client host [93.155.169.232] blocked using zen.spamhaus.org; http://www.spamhaus.org/query/bl?ip=93.155.169.232; from=<readilyu098@polysto.com> to=<cpn@mydomain.com> proto=ESMTP helo=<[93.155.169.232]>
Feb 4 22:10:42 server1 postfix/smtpd[28661]: lost connection after DATA from unknown[93.155.169.232]
Feb 4 22:10:42 server1 postfix/smtpd[28661]: disconnect from unknown[93.155.169.232]
Feb 4 22:10:43 server1 postfix/smtpd[28944]: connect from 36-40-245-190.fibertel.com.ar[190.245.40.36]
Feb 4 22:10:43 server1 postfix/smtpd[28944]: NOQUEUE: reject: RCPT from 36-40-245-190.fibertel.com.ar[190.245.40.36]: 554 5.7.1 Service unavailable; Client host [190.245.40.36] blocked using zen.spamhaus.org; http://www.spamhaus.org/query/bl?ip=190.245.40.36; from=<unreleased8@fiemg.com.br> to=<cp@mydomain.com> proto=ESMTP helo=<36-40-245-190.fibertel.com.ar>
Feb 4 22:10:43 server1 postfix/smtpd[28944]: lost connection after DATA from 36-40-245-190.fibertel.com.ar[190.245.40.36]
Feb 4 22:10:43 server1 postfix/smtpd[28944]: disconnect from 36-40-245-190.fibertel.com.ar[190.245.40.36]
Feb 4 22:10:44 server1 postfix/smtpd[29730]: connect from unknown[190.87.234.85]
Feb 4 22:10:44 server1 postfix/smtpd[27460]: warning: 201.250.187.56: hostname 201-250-187-56.speedy.com.ar verification failed: Name or service not known
Feb 4 22:10:44 server1 postfix/smtpd[27460]: connect from unknown[201.250.187.56]
Feb 4 22:10:44 server1 postfix/smtpd[27460]: NOQUEUE: reject: RCPT from unknown[201.250.187.56]: 554 5.7.1 Service unavailable; Client host [201.250.187.56] blocked using zen.spamhaus.org; http://www.spamhaus.org/query/bl?ip=201.250.187.56; from=<timmymd6@nobleenergyinc.com> to=<ionml@mydomain.com> proto=ESMTP helo=<201-250-187-56.speedy.com.ar>
Feb 4 22:10:44 server1 postfix/smtpd[27460]: NOQUEUE: reject: RCPT from unknown[201.250.187.56]: 554 5.7.1 Service unavailable; Client host [201.250.187.56] blocked using zen.spamhaus.org; http://www.spamhaus.org/query/bl?ip=201.250.187.56; from=<timmymd6@nobleenergyinc.com> to=<md@mydomain.com> proto=ESMTP helo=<201-250-187-56.speedy.com.ar>
Feb 4 22:10:44 server1 postfix/smtpd[27460]: NOQUEUE: reject: RCPT from unknown[201.250.187.56]: 554 5.7.1 Service unavailable; Client host [201.250.187.56] blocked using zen.spamhaus.org; http://www.spamhaus.org/query/bl?ip=201.250.187.56; from=<timmymd6@nobleenergyinc.com> to=<suy1@mydomain.com> proto=ESMTP helo=<201-250-187-56.speedy.com.ar>
Feb 4 22:10:45 server1 postfix/smtpd[27460]: lost connection after DATA from unknown[201.250.187.56]
Feb 4 22:10:45 server1 postfix/smtpd[27460]: disconnect from unknown[201.250.187.56]
Well, they are all being successfully rejected.
Upgrading postfix isn't going to stop them, or do anything different.
To reduce load on your mail system you could block the offending ip (ranges) with iptables rules - or set up fail2ban to do it for you.
I don't want to block entire IP ranges because most (all) of this spam is coming from malware on people's computers. I'd be blocking legitimate ISPs. That's why I wanted to give postscreen a try.
So you will be needing to upgrade to squeeze then.
Alternatively, you could try backporting postfix from wheezy, although my guess is you would also need to backport a metric shitload of the core system as well.
Last edited by descendant_command; 02-05-2013 at 09:36 PM.
So you will be needing to upgrade to squeeze then.
Yes, but like I said, there's a reason this system is still running Etch. It will be replaced by a Squeeze/Wheezy system this summer.
Quote:
Alternatively, you could try backporting postfix from wheezy, although my guess is you would also need to backport a metric shitload of the core system as well.
LIke I said, Postfix 2.9.5 compiled without a problem. But /etc/init.d/postfix no longer works.
Seems pretty clear - it doesn't support the 'quiet-stop' parameter.
Use a supported parameter, e.g. postfix start (or stop, reload, abort, flush, check, status, set-permissions, upgrade-configuration)
Seems pretty clear - it doesn't support the 'quiet-stop' parameter.
Use a supported parameter, e.g. postfix start (or stop, reload, abort, flush, check, status, set-permissions, upgrade-configuration)
Yes, thank you. But I was wondering if this is the proper way to upgrade postfix. And will my postfix configuration files still work? And if there's anything else I need to watch out for?
Yes, thank you. But I was wondering if this is the proper way to upgrade postfix. And will my postfix configuration files still work? And if there's anything else I need to watch out for?
The proper way would be to install the debian package.
No idea if your existing config will still work, my guess would be probably not (the init script being a prime example).
Watch out for everything.
Last edited by descendant_command; 02-06-2013 at 05:42 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
