Topic: Mail logs filled with SMTP error messages

[gmphoto]

I don't know if I am posting this message in the correct forum so here goes. Forum admin please shift to correct forum if necessary.

I have searched the forums.

I am a relative novice with SME and Linux.

I recently checked my mail log and found a huge list of messages as follows. Hundreds an hour.

Apr  6 00:05:06 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve acttax.com
Apr  6 00:05:06 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve accio.com
Apr  6 00:05:57 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve jrtr.org
Apr  6 00:05:57 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve linan.net
Apr  6 00:05:58 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve mgmql.mailserver.idv.tw
Apr  6 00:06:38 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve jrtr.org
Apr  6 00:06:38 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve auktionstermin.info
Apr  6 00:06:39 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve bas-reliefs.com
Apr  6 00:07:08 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve mnw.net
Apr  6 00:07:08 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve 10minutemail.com
Apr  6 00:07:08 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve jchqrb
Apr  6 00:07:08 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve kkee.co.kr
Apr  6 00:07:08 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve t-maker.co.kr
Apr  6 00:07:08 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve cawi.be
Apr  6 00:07:45 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve borderlinedisorder.com
Apr  6 00:07:45 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve pansamson.com.my
Apr  6 00:07:45 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve mco.edu
Apr  6 00:07:45 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve netmediaonline.dk
Apr  6 00:07:46 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve boekenet.com
Apr  6 00:08:15 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve pittsburghtodo.com
Apr  6 00:08:15 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve varmolda.pt
Apr  6 00:08:15 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve hascolek.com
Apr  6 00:08:41 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve actacmb-voyages.com
Apr  6 00:08:42 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve hausbrandt.fr
Apr  6 00:08:43 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve 88you.com.tw
Apr  6 00:08:43 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve upd-westpac.com
Apr  6 00:08:43 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve es.dupont.com
Apr  6 00:09:09 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve actacmb-voyages.com
Apr  6 00:09:10 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve colettaconsultants.ca
Apr  6 00:09:11 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve AFSK.AU.DK
Apr  6 00:09:11 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve MACRESOURCE.ORG
Apr  6 00:09:12 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve dongbulogix.com
Apr  6 00:09:12 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve brad-com.freeserve.co.uk
Apr  6 00:10:06 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve bradscustomcaps.com
Apr  6 00:10:58 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve bolsaimoveis.com.br
Apr  6 00:10:58 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve borkum-top-fewos.de
Apr  6 00:10:59 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve bolaget.com
Apr  6 00:10:59 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve exalumnos.com
Apr  6 00:10:59 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve bmla.com
Apr  6 00:10:59 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve 4-egas.com
Apr  6 00:10:59 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve boyhart.plus.com
Apr  6 00:10:59 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve cleanrussia.ru
Apr  6 00:11:00 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve exalumnos.com
Apr  6 00:11:00 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve berzelius.se
Apr  6 00:11:00 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve trainingassociates.com
Apr  6 00:11:00 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve wilsonlog.com
Apr  6 00:11:01 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve epcri.com
Apr  6 00:11:01 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve jaydemail.com
Apr  6 00:11:52 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve polytechkorea.com
Apr  6 00:11:52 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve inlt.paypal.com
Apr  6 00:11:52 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve 222.122.60.114
Apr  6 00:11:52 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve verticalit.net
Apr  6 00:11:53 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve northernlightsband.com
Apr  6 00:11:53 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve inlt.paypal.com
Apr  6 00:11:53 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve daniele-voyance.com
Apr  6 00:11:53 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve e-hkma.com
Apr  6 00:12:45 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve actacmb-voyages.com
Apr  6 00:13:25 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve centrapoint.com
Apr  6 00:13:26 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve unmikonline.org
Apr  6 00:13:26 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve admin.firstbanks.com
Apr  6 00:13:26 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve admin.fbol.com
Apr  6 00:13:26 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve luk.be
Apr  6 00:13:27 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve interpolispensioenen.nl
Apr  6 00:13:27 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve borkum-top-fewos.de
Apr  6 00:13:28 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve benginflatables.de
Apr  6 00:13:28 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve update.firstbanks.com
Apr  6 00:13:28 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve exalumnos.com
Apr  6 00:13:28 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve bordeaux-metropole.com
Apr  6 00:13:28 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve admin.firstbanks.com
Apr  6 00:13:28 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve update.firstbanks.com
Apr  6 00:13:28 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve jaydemail.com
Apr  6 00:13:28 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve scfederal.digitalinsight.com
Apr  6 00:13:28 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve jaydemail.com
Apr  6 00:13:28 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve exalumnos.com
Apr  6 00:13:29 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve fopsjaken.nl
Apr  6 00:13:29 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve ralfv.de
Apr  6 00:13:29 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve update.digitalinsight.com
Apr  6 00:13:29 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve berzelius.se
Apr  6 00:13:29 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve daniele-voyance.com
Apr  6 00:13:29 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve cunet.org
Apr  6 00:13:29 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.ADORNLLC.COM
Apr  6 00:13:29 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve midnightspecial.org
Apr  6 00:13:29 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.baylorhealth.edu
Apr  6 00:13:30 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve chemicalbank.digitalinsight.com
Apr  6 00:13:30 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.MiniMinit.com
Apr  6 00:13:30 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.tirekingdom.com
Apr  6 00:13:30 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.covertfashions.com.au
Apr  6 00:13:31 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.schuncks.de
Apr  6 00:13:31 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve support.cunet.org
Apr  6 00:13:31 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve apex.cunet.org
Apr  6 00:13:31 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve cunet.org
Apr  6 00:13:32 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve chemicalbank.net
Apr  6 00:13:32 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve verify.digitalinsight.com
Apr  6 00:13:32 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.siapav.it
Apr  6 00:13:32 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve chemicalbank.net
Apr  6 00:13:32 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve chemicalbank.digitalinsight.com
Apr  6 00:13:32 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve chemicalbank.digitalinsight.com
Apr  6 00:13:33 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve verify.digitalinsight.com
Apr  6 00:13:33 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.tagaviation.com
Apr  6 00:13:33 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.mvh.org
Apr  6 00:13:33 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.johnlewis.com
Apr  6 00:13:33 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.hynesight.net
Apr  6 00:13:33 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.INFOCORP.CL
Apr  6 00:13:33 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.ams.dk
Apr  6 00:13:34 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.linkos.bg
Apr  6 00:13:34 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.B-G-S.COM
Apr  6 00:13:34 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.plexus.com
Apr  6 00:13:34 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.telecom.co.nz
Apr  6 00:13:37 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.LETS-TALK-COMPUTERS.COM
Apr  6 00:14:28 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.AMPSONLINE.COM
Apr  6 00:14:28 xxxxxxxmail fetchmail[10825]: SMTP error: 450 Could not resolve newsletter.Gjemnes.Kommune.no

I am running Fetchmail version 1.3.4-10 on an SME 7.1 server in server only mode to retrieve POP email from an external mail server.

I don't know if this has anything to do with the these messages.

Any clues?

Thanks in advance

[David Harper]

Welcome to the forums

Can you please tell us a little bit about your server and how it is configured? At first glance, it looks like something is trying to use your server as a spam relay -- but I could be wrong about this.

[gmphoto]

Thanks for the welcome and reply.

That's what I fear.

Information is as follows.

I set this SME 7.1 machine up for some friends who needed an IMAP mail server using the Fetchmail contrib checking their web and mail hosting company. The amount of outgoing traffic on their broadband connection doesn't seem to reflect the amount of traffic that would have to be if it was being used as a spam relay.

The SME is a standard server install apart from the Fetchmail contrib mentioned.

I am tempted to reinstall and restore their email and see if it continues.

They have had an issue in the past in that I think there domain name was being used as a return address by some spammer so I am wondering if this is a consequence of that predicament. At one stage they were receiving hundreds of spam emails an hour (which the SME was successfully filtering) until they requested spam filtering at their ISP.

What other info might be helpful?

Thanks
Gary

[David Harper]

You should definitely upgrade to the latest version, 7.4.

I also have a few more questions:

1. Is SMTP authentication enabled for users, or can anyone access the service?
2. Is the server operating in Server Only mode?

However, all that said I agree with your hypothesis that...

... [their] domain name was being used as a return address by some spammer so I am wondering if this is a consequence of that predicament.

I would upgrade to 7.4, and update fetchmail to the latest version (in the smecontribs repository), as a first step. 7.1 is very old now.

[Stefano]

You should definitely upgrade to the latest version, 7.4.

I agree..

before you do it, please read here

HTH
Ciao
Stefano

[gmphoto]

You should definitely upgrade to the latest version, 7.4.

I also have a few more questions:

1. Is SMTP authentication enabled for users, or can anyone access the service?

SMTP authentication is for internal users only so I don't think it can be used as a mail relay from an external source. They are running an all Mac shop and their machines are not on 24/7 so I assume that it is not one of their internal machines being a spam zombie.

2. Is the server operating in Server Only mode?

Yes it is and only being used as a mail server - nothing else.

However, all that said I agree with your hypothesis that...

I would upgrade to 7.4, and update fetchmail to the latest version (in the smecontribs repository), as a first step. 7.1 is very old now.

Yes I will do that this week and report my results back here.

Thanks for the help - nice to be part a community rather than thrashing around the whole interweb trying to find a starting point.

Cheers
Gary

[David Harper]

No problem. Don't forget to let us know how you get on.