Topic: Why are my e-mails rejected after updates?

[botmansound@gmail.com]

Hello guys, I am not an expert but I have been using SME Server (9.2) for more than 15 years.
But I think I'll stop with SME Server. I hardly dare to apply an update anymore because after that my company can no longer receive e-mails !! We have a lot of problems with spam and over the years I have had it reasonably under control.
After much experimenting, I discovered that switching off the SPAM and VIRUS protection can receive my e-mails again. But then I get overloaded with SPAM and am no longer protected for VIRUS! If I switch on SPAM and VIRUS again after a few weeks, everything will continue to work as normal!
I have already had this problem 3 times since updating SME9.2!
This is really not possible anymore! I don't dare to carry out any updates anymore! With pain in my heart, I have to look for an alternative.
Do other users also have problems with this? Are the updates tested well before they are rolled out?
Who can tell me why this is?

Thanks in advance.

Regards,

Frank Botman

If I test my own e-mail then rejected info is:
Reporting-MTA: dns; googlemail.com
Received-From-MTA: dns; fjbotman@gmail.com
Arrival-Date: Mon, 22 Jul 2019 07:41:55 -0700 (PDT)
X-Original-Message-ID: <242CEEFE-49E0-4235-B9AA-79D84BDEFEB7@gmail.com>

Final-Recipient: rfc822; f.botman@botman.com
Action: failed
Status: 5.0.0
Remote-MTA: dns; mail.botman.com. (213.124.18.162, the server for the domain botman.com.)
Diagnostic-Code: smtp; 550 (dnsbl) v=spf1 -all
Last-Attempt-Date: Mon, 22 Jul 2019 07:41:58 -0700 (PDT)

Logbestanden bekijken
/var/log/yum/yum.log.1563801998: Bekeken om ma 22 jul 2019 17:42:06 CEST.
Loaded plugins: fastestmirror, post-transaction-actions, smeserver
Setting up Update Process
Loading mirror speeds from cached hostfile
 * base: ftp.nluug.nl
 * smeaddons: ftp.nluug.nl
 * smeextras: ftp.nluug.nl
 * smeos: ftp.nluug.nl
 * smeupdates: ftp.nluug.nl
 * updates: centos.mirror.transip.nl
Resolving Dependencies
--> Running transaction check
---> Package bind-libs.x86_64 32:9.8.2-0.68.rc1.el6_10.1 will be updated
---> Package bind-libs.x86_64 32:9.8.2-0.68.rc1.el6_10.3 will be an update
---> Package bind-utils.x86_64 32:9.8.2-0.68.rc1.el6_10.1 will be updated
---> Package bind-utils.x86_64 32:9.8.2-0.68.rc1.el6_10.3 will be an update
---> Package dbus.x86_64 1:1.2.24-9.el6 will be updated
---> Package dbus.x86_64 1:1.2.24-11.el6_10 will be an update
---> Package dbus-libs.x86_64 1:1.2.24-9.el6 will be updated
---> Package dbus-libs.x86_64 1:1.2.24-11.el6_10 will be an update
---> Package kernel.x86_64 0:2.6.32-754.17.1.el6 will be installed
---> Package kernel-firmware.noarch 0:2.6.32-754.12.1.el6 will be updated
---> Package kernel-firmware.noarch 0:2.6.32-754.17.1.el6 will be an update
---> Package kernel-headers.x86_64 0:2.6.32-754.12.1.el6 will be updated
---> Package kernel-headers.x86_64 0:2.6.32-754.17.1.el6 will be an update
---> Package libssh2.x86_64 0:1.4.2-2.el6_7.1 will be updated
---> Package libssh2.x86_64 0:1.4.2-3.el6_10.1 will be an update
---> Package python.x86_64 0:2.6.6-66.el6_8 will be updated
---> Package python.x86_64 0:2.6.6-68.el6_10 will be an update
---> Package python-libs.x86_64 0:2.6.6-66.el6_8 will be updated
---> Package python-libs.x86_64 0:2.6.6-68.el6_10 will be an update
---> Package tzdata.noarch 0:2019a-1.el6 will be updated
---> Package tzdata.noarch 0:2019b-2.el6 will be an update
---> Package vim-common.x86_64 2:7.4.629-5.el6_8.1 will be updated
---> Package vim-common.x86_64 2:7.4.629-5.el6_10.2 will be an update
---> Package vim-enhanced.x86_64 2:7.4.629-5.el6_8.1 will be updated
---> Package vim-enhanced.x86_64 2:7.4.629-5.el6_10.2 will be an update
---> Package vim-filesystem.x86_64 2:7.4.629-5.el6_8.1 will be updated
---> Package vim-filesystem.x86_64 2:7.4.629-5.el6_10.2 will be an update
---> Package vim-minimal.x86_64 2:7.4.629-5.el6_8.1 will be updated
---> Package vim-minimal.x86_64 2:7.4.629-5.el6_10.2 will be an update
--> Finished Dependency Resolution
--> Running transaction check
---> Package kernel.x86_64 0:2.6.32-754.10.1.el6 will be erased
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
 Package           Arch     Version                         Repository     Size
================================================================================
Installing:
 kernel            x86_64   2.6.32-754.17.1.el6             smeupdates     32 M
Updating:
 bind-libs         x86_64   32:9.8.2-0.68.rc1.el6_10.3      smeupdates    892 k
 bind-utils        x86_64   32:9.8.2-0.68.rc1.el6_10.3      smeupdates    189 k
 dbus              x86_64   1:1.2.24-11.el6_10              smeupdates    211 k
 dbus-libs         x86_64   1:1.2.24-11.el6_10              smeupdates    127 k
 kernel-firmware   noarch   2.6.32-754.17.1.el6             smeupdates     29 M
 kernel-headers    x86_64   2.6.32-754.17.1.el6             smeupdates    4.6 M
 libssh2           x86_64   1.4.2-3.el6_10.1                smeupdates    123 k
 python            x86_64   2.6.6-68.el6_10                 smeupdates     76 k
 python-libs       x86_64   2.6.6-68.el6_10                 smeupdates    5.3 M
 tzdata            noarch   2019b-2.el6                     smeupdates    506 k
 vim-common        x86_64   2:7.4.629-5.el6_10.2            smeupdates    6.7 M
 vim-enhanced      x86_64   2:7.4.629-5.el6_10.2            smeupdates    1.0 M
 vim-filesystem    x86_64   2:7.4.629-5.el6_10.2            smeupdates     15 k
 vim-minimal       x86_64   2:7.4.629-5.el6_10.2            smeupdates    422 k
Removing:
 kernel            x86_64   2.6.32-754.10.1.el6             @smeupdates   133 M
Transaction Summary
================================================================================
Install       1 Package(s)
Upgrade      14 Package(s)
Remove        1 Package(s)
Total download size: 81 M
Downloading Packages:
--------------------------------------------------------------------------------
Total                                            18 MB/s |  81 MB     00:04     
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction

  Updating   : python-2.6.6-68.el6_10.x86_64                               1/30

  Updating   : python-libs-2.6.6-68.el6_10.x86_64                          2/30

  Updating   : 32:bind-libs-9.8.2-0.68.rc1.el6_10.3.x86_64                 3/30

  Updating   : kernel-firmware-2.6.32-754.17.1.el6.noarch                  4/30

  Updating   : 2:vim-filesystem-7.4.629-5.el6_10.2.x86_64                  5/30

  Updating   : 2:vim-common-7.4.629-5.el6_10.2.x86_64                      6/30

  Updating   : 1:dbus-libs-1.2.24-11.el6_10.x86_64                         7/30

  Updating   : 1:dbus-1.2.24-11.el6_10.x86_64                              8/30

  Updating   : 2:vim-enhanced-7.4.629-5.el6_10.2.x86_64                    9/30

  Installing : kernel-2.6.32-754.17.1.el6.x86_64                          10/30

  Updating   : 32:bind-utils-9.8.2-0.68.rc1.el6_10.3.x86_64               11/30

  Updating   : kernel-headers-2.6.32-754.17.1.el6.x86_64                  12/30

  Updating   : 2:vim-minimal-7.4.629-5.el6_10.2.x86_64                    13/30

  Updating   : tzdata-2019b-2.el6.noarch                                  14/30

  Updating   : libssh2-1.4.2-3.el6_10.1.x86_64                            15/30

  Cleanup    : kernel-2.6.32-754.10.1.el6.x86_64                          16/30
warning:    erase unlink of /lib/modules/2.6.32-754.10.1.el6.x86_64/modules.order failed: No such file or directory
warning:    erase unlink of /lib/modules/2.6.32-754.10.1.el6.x86_64/modules.networking failed: No such file or directory
warning:    erase unlink of /lib/modules/2.6.32-754.10.1.el6.x86_64/modules.modesetting failed: No such file or directory
warning:    erase unlink of /lib/modules/2.6.32-754.10.1.el6.x86_64/modules.drm failed: No such file or directory
warning:    erase unlink of /lib/modules/2.6.32-754.10.1.el6.x86_64/modules.block failed: No such file or directory

  Cleanup    : python-2.6.6-66.el6_8.x86_64                               17/30

  Cleanup    : python-libs-2.6.6-66.el6_8.x86_64                          18/30

  Cleanup    : 32:bind-utils-9.8.2-0.68.rc1.el6_10.1.x86_64               19/30

  Cleanup    : 2:vim-enhanced-7.4.629-5.el6_8.1.x86_64                    20/30

  Cleanup    : 2:vim-common-7.4.629-5.el6_8.1.x86_64                      21/30

  Cleanup    : 1:dbus-1.2.24-9.el6.x86_64                                 22/30

  Cleanup    : 2:vim-filesystem-7.4.629-5.el6_8.1.x86_64                  23/30

  Cleanup    : kernel-firmware-2.6.32-754.12.1.el6.noarch                 24/30

  Cleanup    : kernel-headers-2.6.32-754.12.1.el6.x86_64                  25/30

  Cleanup    : tzdata-2019a-1.el6.noarch                                  26/30

  Cleanup    : 1:dbus-libs-1.2.24-9.el6.x86_64                            27/30

  Cleanup    : 32:bind-libs-9.8.2-0.68.rc1.el6_10.1.x86_64                28/30

  Cleanup    : 2:vim-minimal-7.4.629-5.el6_8.1.x86_64                     29/30

  Cleanup    : libssh2-1.4.2-2.el6_7.1.x86_64                             30/30
Migrating existing database wbl
Migrating existing database configuration
Migrating existing database domains
Migrating existing database spamassassin
Migrating existing database yum_updates
Migrating existing database networks
Migrating existing database accounts
Migrating existing database hosts
Migrating existing database confusbdisks
Migrating existing database yum_available
Migrating existing database yum_repositories
Migrating existing database backups
Migrating existing database mailpatterns
Migrating existing database yum_installed

  Verifying  : libssh2-1.4.2-3.el6_10.1.x86_64                             1/30

  Verifying  : 1:dbus-1.2.24-11.el6_10.x86_64                              2/30

  Verifying  : tzdata-2019b-2.el6.noarch                                   3/30

  Verifying  : 1:dbus-libs-1.2.24-11.el6_10.x86_64                         4/30

  Verifying  : python-libs-2.6.6-68.el6_10.x86_64                          5/30

  Verifying  : python-2.6.6-68.el6_10.x86_64                               6/30

  Verifying  : kernel-2.6.32-754.17.1.el6.x86_64                           7/30

  Verifying  : 2:vim-common-7.4.629-5.el6_10.2.x86_64                      8/30

  Verifying  : 2:vim-filesystem-7.4.629-5.el6_10.2.x86_64                  9/30

  Verifying  : 2:vim-enhanced-7.4.629-5.el6_10.2.x86_64                   10/30

  Verifying  : 2:vim-minimal-7.4.629-5.el6_10.2.x86_64                    11/30

  Verifying  : kernel-firmware-2.6.32-754.17.1.el6.noarch                 12/30

  Verifying  : 32:bind-utils-9.8.2-0.68.rc1.el6_10.3.x86_64               13/30

  Verifying  : 32:bind-libs-9.8.2-0.68.rc1.el6_10.3.x86_64                14/30

  Verifying  : kernel-headers-2.6.32-754.17.1.el6.x86_64                  15/30

  Verifying  : 2:vim-common-7.4.629-5.el6_8.1.x86_64                      16/30

  Verifying  : 2:vim-filesystem-7.4.629-5.el6_8.1.x86_64                  17/30

  Verifying  : python-libs-2.6.6-66.el6_8.x86_64                          18/30

  Verifying  : 1:dbus-1.2.24-9.el6.x86_64                                 19/30

  Verifying  : kernel-firmware-2.6.32-754.12.1.el6.noarch                 20/30

  Verifying  : libssh2-1.4.2-2.el6_7.1.x86_64                             21/30

  Verifying  : python-2.6.6-66.el6_8.x86_64                               22/30

  Verifying  : tzdata-2019a-1.el6.noarch                                  23/30

  Verifying  : 32:bind-utils-9.8.2-0.68.rc1.el6_10.1.x86_64               24/30

  Verifying  : 2:vim-enhanced-7.4.629-5.el6_8.1.x86_64                    25/30

  Verifying  : 32:bind-libs-9.8.2-0.68.rc1.el6_10.1.x86_64                26/30

  Verifying  : kernel-2.6.32-754.10.1.el6.x86_64                          27/30

  Verifying  : 2:vim-minimal-7.4.629-5.el6_8.1.x86_64                     28/30

  Verifying  : kernel-headers-2.6.32-754.12.1.el6.x86_64                  29/30

  Verifying  : 1:dbus-libs-1.2.24-9.el6.x86_64                            30/30
Removed:
  kernel.x86_64 0:2.6.32-754.10.1.el6                                           
Installed:
  kernel.x86_64 0:2.6.32-754.17.1.el6                                           
Updated:
  bind-libs.x86_64 32:9.8.2-0.68.rc1.el6_10.3                                   
  bind-utils.x86_64 32:9.8.2-0.68.rc1.el6_10.3                                 
  dbus.x86_64 1:1.2.24-11.el6_10                                               
  dbus-libs.x86_64 1:1.2.24-11.el6_10                                           
  kernel-firmware.noarch 0:2.6.32-754.17.1.el6                                 
  kernel-headers.x86_64 0:2.6.32-754.17.1.el6                                   
  libssh2.x86_64 0:1.4.2-3.el6_10.1                                             
  python.x86_64 0:2.6.6-68.el6_10                                               
  python-libs.x86_64 0:2.6.6-68.el6_10                                         
  tzdata.noarch 0:2019b-2.el6                                                   
  vim-common.x86_64 2:7.4.629-5.el6_10.2                                       
  vim-enhanced.x86_64 2:7.4.629-5.el6_10.2                                     
  vim-filesystem.x86_64 2:7.4.629-5.el6_10.2                                   
  vim-minimal.x86_64 2:7.4.629-5.el6_10.2                                       
Complete!
==============================================================
WARNING: You now need to run BOTH of the following commands
to ensure consistent system state:
signal-event post-upgrade; signal-event reboot
You should run these commands unless you are certain that
yum made no changes to your system.
==============================================================

[Jean-Philippe Pialasse]

hello botmansound,
first welcome for your first post after 15 years of using SME, seems it worked pretty well for all that time for not needing to register to the forum before!

First have you read the dedicated post and wiki page for SME 9.2 related update issues ?  here are the links for your convenience : https://forums.contribs.org/index.php/topic,53106.0.html https://wiki.contribs.org/SME_Server:9.2

Second, the yum log you show does not point to any package related to mail.

Then when you have issues with receiving email (which what i understand reading you), then the first step is to fry some eggs ! No, the first step is to refer to the mail deamon log. For incoming emails, the daemon is qpsmtpd. Please check this log simply from the server manager (or from the cli if you are comfortable) with virus scan and spamassassin enabled. You should quickly know what is wrong. If you have time you can also dig in older logs before you deactivates virus scan and spamassassin.

Hint, the mail header you sent points toward email refused because of a DNSBL bounce: 550 (dnsbl). Which tells that deactivating virus scan and spamassassin was not what helped, but you might also deactivate dnsbl and rhbl filtering.

Then you might have some reconfigured dnsbl services, or maybe a service that creates a lot of false positives. Again, reading your log will give you the answer.

Finally, what could also help in debugging this kind of issues is to check:
- for issues with qpsmtpd config

Code: [Select]

config show qpsmtpd- for templates-custom

Code: [Select]

/sbin/e-smith/audittools/templates- and for contribs which could potentially influence the mail delivery process.

Code: [Select]

/sbin/e-smith/audittools/newrpms
for the two last if you are not comfortable with cli, you can also find those information in the server manager in the debug menu.

[jameswilson]

Frank as the big man says even I cant see anything email there but I've seen that certain hosts have issues with email sent from self hosted systems. It's probably worth looking as to why as opposed to blaming sme for it. I'd put my mortgage on its not a sme issue as in something wrong with it
James


[EDIT]removed unecessary quote by moderator

[botmansound@gmail.com]

Hi Jean-Philippe,

Thank you for the detailed explanation. I have read all your tips and, where necessary, performed the tests. However, I cannot find any deviations. All software seems to be update and I also cannot find old templates. I also have no additional contribs installed.
Unfortunately I don't have time to delve deeply into this. I am also an amateur and do not understand everything that the logs says. But as I said, SME is a work horse for me and I was always be able to solve problems and updates by myself. Only the last 3 times updates give me this blocking e-mail trouble.

You wrote: Hint, the mail header you sent points toward email refused because of a DNSBL bounce: 550 (dnsbl). Which tells that deactivating virus scan and spamassassin was not what helped, but you might also deactivate dnsbl and rhbl filtering.
But this was before I deactivate the SPAM and VIRUS tools! First I deactivate the DNSBL and RHSBL, but my incoming e-mails are still blocked. Then I deactivate SPAM filtering, but my incoming e-mails are still blocked. Then I deactivate VIRUS Scanning and this was the key to get my e-mails again!
Now my e-mails are working correct but I have a lot of SPAM. Next weekend (when I have time) I will restore the SPAM and VIRUS settings and hope that the problem has solved itself! Because this was the same story 2 times earlier!
But it still does not make any sense to me!

Thanks in advance!

[EDIT]removed unecessary quote by moderator

[Jean-Philippe Pialasse]

Then check your clamav / clamd logs

And if you do not understand them post them here. At least snippet. Same thing for qpsmtpd logs.

From what you describe in last post this could point toward issue with clamav, either missing memory or failing to update its db

[ReetP]

Botman, your server has functioned well for years.

The first thing to do is keep calm and don't panic.

Computers don't have feelings, just logic.

Something is not functioning correctly so we need to slowly and calmly work out what the problem is. It's just logic.

We have to do this one step at a time.

You may not have time to delve deeply... but equally there may not be the quick answer that you seek, unless you pay for it. This is open source remember. We all have paying jobs. SME is what we do in our spare time. Help us to help you.

Follow what Jean Philippe has said. Post the output as requested. Don't try and guess - you are the one with the problem and asking for help!!!!

So post the output of the commands or no one can help you.

First the config command, and then the newrpms and templates.

Then have a look for errors in your qpsmtp and clamav logs.

It will only take a few minutes to do this.

[ReetP]

@all

Please don't quote long posts. It makes reading so juch harder.

Please quote selectively with a bit of careful editing

Thanks.

[janet]

Frank

Your issues do not sound like an inherent SME/Koozali server issue or fault as such.
It sounds like an issue to do with your configuration or general setup or external factors or large mail volume load.

As Reet & others say, the only way to answer you & resolve your problem is via a slower methodical analysis of your setup & server configuration etc.
This requires you to provide detailed answers & output from the commands advised to you.

I have been running sme server for longer than you & it has worked reliably without the update/mail issues you describe.

I have a question, is your server configured as server only mode with another gateway device in front of it ?
or
Is it configured as server/gateway mode with a bridged modem ?
or
Something else ?

Also what is output of
config show qpsmtpd

Also 2 thoughts come to mind, you may have  RBL & SBL lists that are too aggressive,
& if you have a very large volume of mail & have virus scanning enabled on mail & the server file system, & have spamassassin filtering enabled, you may have a very heavy CPU load which is slowing down mail processing.

[botmansound@gmail.com]

Hello Janet,

Thanks for taking time for me!

The server is server only mode

Output qpsmtpd:
[root@store ~]# config show qpsmtpd
qpsmtpd=service
    Bcc=disabled
    BccMode=cc
    BccUser=maillog
    DNSBL=disabled
    LogLevel=8
    MaxScannerSize=25000000
    RBLList=sbl-xbl.spamhaus.org,whois.rfc-ignorant.org,dnsbl.njabl.org,relays.ordb.org,abuse.rfc-ignorant.org,dsn.rfc-ignorant.org,postmaster.rfc-ignorant.org
    RHSBL=disabled
    RelayRequiresAuth=enabled
    SBLList=dbl.spamhaus.org
    TlsBeforeAuth=1
    UBLList=multi.surbl.org:8-16-64-128,black.uribl.com,rhsbl.sorbs.net
    URIBL=disabled
    access=public
    qplogsumm=disabled
    status=enabled

As you can see, everything is still  disabled.
Strange is when I disabled RBLList and SBLList, e-mails are still rejected!
After disabling Virus Scan en Spam Filtering, my e-mails are back.

If you need other log files, let me know!

Thanks in advance!

[ReetP]

As per JP above

Code: [Select]

/sbin/e-smith/audittools/templates


Code: [Select]

/sbin/e-smith/audittools/newrpms

For rejection you better start by looking in:

/var/log/qpsmtpd/current

Try:

Code: [Select]

tailf /var/log/qpsmtpd/current
Watch a mail come in and then you should see why it is getting blocked.

[janet]

Frank

I know it seems basic/obvious but we need to confirm.
After doing smaller changes to email related settings do you issue the command
signal-event email-update

After the upgrades do you issue the commands
signal-event post-upgrade
signal-event reboot

You say the server is in server only mode
What device is acting as firewall & gateway (in front of sme server).

You have some very aggressive lists configured (which can cause legitimate mail to be rejected/blocked), I would change these to more conservative settings, refer wiki or here are my conservative settings.
RBLList=zen.spamhaus.org
SBLList=dbl.spamhaus.org
UBLList=rhsbl.sorbs.net


Please post output of the commands that JPP & ReetP have shown.
Just saying it all looks OK to you is not sufficient, we need to see the results.
You have some very expert people willing to help you here, but we need your detailed feedback on all the questions previously asked.


You can also take a big processing load off your server regarding email virus filtering & spam filtering, by enabling executable content blocking in Server Manager Email panel.
If you block most or all executable content types, then many/most virus laden email messages will be rejected & returned to sender, & your virus scanning & spam filtering load (on CPU & memory) will reduce dramatically.
If you can block both zipv1 & zipv2 you will stop a huge virus load from even coming into your server.

[botmansound@gmail.com]

Hi Janet and others,

I made no changes for a week and turned off virus and spam to be able to receive e-mails. After this week I turned everything on again and I just keep receiving emails!
This is exactly the same behavior as I had 3 times before with software updates.
I have followed your advice and adjusted the RBLList, SBLList and UBLList. Furthermore, I have enclosed the requested data below.

But unfortunately I don't have the opportunity and time to immerse myself in this. With the next software update I will use this as a reference.

I thank everyone who wanted to help me with this problem!

Data:

[root@store ~]# /sbin/e-smith/audittools/templates
/etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/85DefaultAccess: MANUALLY_ADDED, OVERRIDE
/etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/80NoHTView: MANUALLY_ADDED, ADDITION
/etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/90e-smithAccess40ibays: MANUALLY_ADDED, OVERRIDE
/etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/90e-smithAccess10primary: MANUALLY_ADDED, ADDITION
/etc/e-smith/templates-custom/etc/proftpd.conf/05Chroot: MANUALLY_ADDED, OVERRIDE
/etc/e-smith/templates-custom/var/qmail/alias/.qmail-oblivion: MANUALLY_ADDED, ADDITION
/etc/e-smith/templates-custom/var/qmail/control/doublebounceto: MANUALLY_ADDED, OVERRIDE

[root@store ~]# /sbin/e-smith/audittools/newrpms
Loaded plugins: fastestmirror, post-transaction-actions, smeserver
Loading mirror speeds from cached hostfile
 * base: mirror.prolocation.net
 * smeaddons: ibsgaarden.dk
 * smeos: ibsgaarden.dk
 * smeupdates: ibsgaarden.dk
 * updates: centos.mirror.triple-it.nl
Extra Packages
DCC.x86_64                          1.3.145-25.el6.sme       @smeupdates-testing
e-smith-backup.noarch               2.4.0-45.el6.sme         @smeupdates-testing
e-smith-base.noarch                 5.6.0-36.el6.sme         @smeupdates-testing
e-smith-formmagick.noarch           2.4.0-2.el6.sme          @smeupdates-testing
e-smith-lib.noarch                  2.4.0-18.el6.sme         @smeupdates-testing
e-smith-manager.noarch              2.6.0-24.el6.sme         @smeupdates-testing
hddtemp.x86_64                      0.3-0.20.beta15.el6      @smecontribs
initscripts.x86_64                  9.03.61-2.el6.sme        @smeupdates-testing
perl-CGI-FormMagick.noarch          0.93-4.el6.sme           @smeupdates-testing
perl-Config-IniFiles.noarch         2.72-2.el6               @smecontribs
perl-Geography-Countries.noarch     2009041301-1.el6.sme     @smeupdates-testing
perl-IO-Socket-INET6.noarch         2.72-1.of.el6            @smecontribs
perl-IP-Country.noarch              2.28-1.el6.sme           @smeupdates-testing
perl-Net-Ident.noarch               1.24-1.el6.sme           @smeupdates-testing
perl-Proc-ProcessTable.x86_64       0.48-1.el6               @smecontribs
perl-Session-Token.x86_64           1.503-1.el6.sme          @smeupdates-testing
perl-rrdtool.x86_64                 1.4.7-1.el6.rfx          @smecontribs
qmail.x86_64                        1.03-20.el6.sme          @smeupdates-testing
rrdtool.x86_64                      1.4.7-1.el6.rfx          @smecontribs
smeserver-learn.noarch              1.0-13.el6.sme           @smecontribs
smeserver-locale-bg.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-da.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-de.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-el.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-es.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-et.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-fr.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-he.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-hu.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-id.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-it.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-ja.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-nb.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-nl.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-pl.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-pt.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-pt_BR.noarch       2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-ro.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-ru.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-sl.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-sv.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-th.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-tr.noarch          2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-zh_CN.noarch       2.4.0-30.el6.sme         @smeupdates-testing
smeserver-locale-zh_TW.noarch       2.4.0-30.el6.sme         @smeupdates-testing
smeserver-sme9admin.noarch          1.5-28.el6.sme           @smecontribs
smeserver-updates.noarch            1.4-2.el6.sme            @smecontribs
smeserver-usbdisksmanager.noarch    1.2-7.el6.sme            @smecontribs
smeserver-vacation.noarch           1.1-26.el6.sme           @smecontribs
smeserver-wbl.noarch                0.3.0-18.el6.sme         @smecontribs
spamassassin.x86_64                 3.4.2-2.el6.sme          @smeupdates-testing
sqlite.x86_64                       3.7.17-9.el6.sme         @smecontribs
sysstat.x86_64                      9.0.4-33el6_9.1          @updates

[root@store ~]# tailf /var/log/qpsmtpd/current
@400000005d44603f075ed164 19846 config(loglevel): hook returned (0,)
@400000005d44603f075edd1c 19846 dispatching QUIT
@400000005d44603f075ee4ec 19846 in config(me)
@400000005d44603f075ee8d4 19846 config(me): hook returned (0,)
@400000005d44603f075ef0a4 19846 221 botman.com closing connection. Have a wonderful day.
@400000005d44603f075ef48c 19846 click, disconnecting
@400000005d44603f075efc5c 19846 (post-connection) running plugin: tls
@400000005d44603f0de39c54 19846 Plugin tls, hook post-connection returned DECLINED,
@400000005d44603f1118c32c 19846 DESTROY called by main, /usr/bin/qpsmtpd-forkserver, 0
@400000005d44603f17760cd4 1984 cleaning up after 19846

[janet]

botmansound

As pointed out by JPP elsewhere, this is a better version of the tail command to run

tail -f /var/log/qpsmtpd/current

[ReetP]

Hmmm not exactly a standard SME then.

Also note you have been adding stuff from smeupdates-testing ??

You do know that those packages are in testing for a purpose don't you? They are not necessarily production ready. Hence the 'testing' part.

All software seems to be update and I also cannot find old templates.

Well, your output from /sbin/e-smith/audittools/templates says otherwise.

I also have no additional contribs installed.

And your output from /sbin/e-smith/audittools/newrpms says otherwise too...

hddtemp.x86_64                      0.3-0.20.beta15.el6      @smecontribs
perl-Config-IniFiles.noarch         2.72-2.el6               @smecontribs
perl-IO-Socket-INET6.noarch         2.72-1.of.el6            @smecontribs
perl-Proc-ProcessTable.x86_64       0.48-1.el6               @smecontribs
perl-rrdtool.x86_64                 1.4.7-1.el6.rfx          @smecontribs
rrdtool.x86_64                      1.4.7-1.el6.rfx          @smecontribs
smeserver-learn.noarch              1.0-13.el6.sme           @smecontribs
smeserver-sme9admin.noarch          1.5-28.el6.sme           @smecontribs
smeserver-updates.noarch            1.4-2.el6.sme            @smecontribs
smeserver-usbdisksmanager.noarch    1.2-7.el6.sme            @smecontribs
smeserver-vacation.noarch           1.1-26.el6.sme           @smecontribs
smeserver-wbl.noarch                0.3.0-18.el6.sme         @smecontribs
sqlite.x86_64                       3.7.17-9.el6.sme         @smecontribs

On top of that you have a newer version of spamassassin, and I am not sure why you have perl-IO-Socket-INET6.noarch there either - that usually comes with geoIP . Added to that you have added smeserver-learn.

So.

If you want to find out why the mails are being blocked you actually need to monitor the mail log continuously. The snippet you provided is meaningless and shows nothing. You have to actually find an error.

Ironically as JPP pointed out, your issue was almost certainly to do with DNSBL from this one line right early on:

Code: [Select]

Diagnostic-Code: smtp; 550 (dnsbl) v=spf1 -all
So your server was blocking mails via DNSBL. You most likely just didn't disable that correctly to start with.

Everything else thereafter just compounds that initial issue.

If you want to try and test this then put your server into the position where it 'blocks' mail again and then run the tail command on the log file continuously and look for errors.

An alternative may be to look for messages that have been denied.

eg:

Code: [Select]

grep deny /var/log/qpsmtpd/current
You might see something like this:

Code: [Select]

400000005d493991074eeefc 30994 (deny) logging::logterse: ` 81.19.222.9 9.222.19.81.baremetal.zare.com WIN-TQOTMK5RLND naughty 903 (helo) HELO name is not fully qualified. Read RFC 2821 msg denied before queued
@400000005d493991074f8754 30994 deny mail from <warrior@rima-tde.net> ((helo) HELO name is not fully qualified. Read RFC 2821)

The you can look at that transaction number 30994 by itself to see what happened

Code: [Select]

grep 30994 /var/log/qpsmtpd/current |tai64nlocal

Code: [Select]

2019-08-05 20:25:02.976263500 25856 250 <joe@blogs.com>, recipient ok
2019-08-06 10:25:40.650080500 30994 Accepted connection 1/40 from 81.19.222.9 / 9.222.19.81.baremetal.zare.com
2019-08-06 10:25:40.650321500 30994 Connection from 9.222.19.81.baremetal.zare.com [81.19.222.9]
2019-08-06 10:25:42.512730500 30994 (connect) earlytalker: pass, not spontaneous
2019-08-06 10:25:42.514201500 30994 (connect) relay: skip, no match
2019-08-06 10:25:42.605427500 30994 (connect) check_badcountries: GeoIP RemoteIP: 81.19.222.9
2019-08-06 10:25:42.605455500 30994 (connect) check_badcountries: GeoIP City: NA
2019-08-06 10:25:42.606289500 30994 (connect) check_badcountries: GeoIP Country: GB
2019-08-06 10:25:42.889607500 30994 (connect) dnsbl: pass
2019-08-06 10:25:42.890022500 30994 220 home.domain.com ESMTP
2019-08-06 10:25:42.968525500 30994 dispatching EHLO WIN-TQOTMK5RLND
2019-08-06 10:25:42.970046500 30994 (ehlo) helo: karma -1 (-1)
2019-08-06 10:25:42.970049500 30994 (ehlo) helo: fail, NAUGHTY, not FQDN
2019-08-06 10:25:42.971228500 30994 250-domain.com Hi 9.222.19.81.baremetal.zare.com [81.19.222.9]
2019-08-06 10:25:42.971230500 30994 250-PIPELINING
2019-08-06 10:25:42.971231500 30994 250-8BITMIME
2019-08-06 10:25:43.002527500 30994 250-SIZE 15000000
2019-08-06 10:25:43.002529500 30994 250 STARTTLS
2019-08-06 10:25:43.050903500 30994 dispatching MAIL FROM:<warrior@rima-tde.net>
2019-08-06 10:25:43.064038500 30994 (mail) resolvable_fromhost: pass, rima-tde.net has MX at mx.rima-tde.net
2019-08-06 10:25:43.122101500 30994 (mail) sender_permitted_from: karma -1 (-2)
2019-08-06 10:25:43.122103500 30994 (mail) sender_permitted_from: fail, tolerated, rima-tde.net: Sender is not authorized by default to use 'warrior@rima-tde.net' in 'mfrom' identity (mechanism '-all' matched)
2019-08-06 10:25:43.122291500 30994 (mail) naughty: disconnecting
2019-08-06 10:25:43.122613500 30994 (deny) logging::logterse: ` 81.19.222.9 9.222.19.81.baremetal.zare.com WIN-TQOTMK5RLND naughty 903 (helo) HELO name is not fully qualified. Read RFC 2821 msg denied before queued
2019-08-06 10:25:43.122652500 30994 deny mail from <warrior@rima-tde.net> ((helo) HELO name is not fully qualified. Read RFC 2821)
2019-08-06 10:25:43.122754500 30994 550 (helo) HELO name is not fully qualified. Read RFC 2821
2019-08-06 10:25:43.122778500 30994 click, disconnecting
2019-08-06 10:25:43.295360500 2216 cleaning up after 30994


Unfortunately I don't have time to delve deeply into this

But unfortunately I don't have the opportunity and time to immerse myself in this.

Neither do I quite frankly. We are all volunteers here. We all have lives and family and paying jobs.

You don't give us straight answers to straight questions which wastes our volunteer time, and you than can't be bothered to learn so you don't make the same mistakes again, and want a magic fix in 5 minutes.

This is an issue almost certainly completely of your own making, and we can only help you resolve it if you spend some of your own precious time on the situation (I have a sneaking feeling it is resolved but you haven't told us that hence your comment "With the next software update I will use this as a reference")

If you decide you have the time and patience to do more then let us know.