notification-mails from system are send to incorrect recipient

    • OMV 4.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • notification-mails from system are send to incorrect recipient

      Hi together, sorry, my english is bad.

      In Notification / Settings I write the recipients Primary email: mail@[mydomain] and Secondary email: info@[mydomain].
      Test emails arrives the recipients correctly.


      But notification-mails sends the system to admin@[myhostname].localdomain. It's consequential, the mails can not be delivered.

      How can I fix it?

      Regards, Penni d:-)
    • Which service is sending this emails to admin? This user should never receive any email because this user is only used to login to the UI, nothing more. Because of that there is no rule that redirects emails to a real address. If you mail to user root for example they are redirected to your primary address.

      I assume a plug-in does not handle this correct.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • votdev wrote:

      Which service is sending this emails to admin?
      I think he means OMV as he is referring to notification-mails (updates, CPU usage, load average, memory usage etc).
      Odroid HC2 - armbian - Seagate ST4000DM004 - OMV4.x
      Asrock Q1900DC-ITX - 16GB - 2x Seagate ST3000VN000 - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!:
    • In the email header I found:
      < Received: by backup.localdomain (Postfix, from userid 999)("backup" is [myhostname])In the test-mail header it is< Received: by openmediavault.localdomain (Postfix, from userid 0)I have 2 systems. The seconds hostname is NASIn the syslog I find

      Source Code

      1. Mar 1 10:11:09 openmediavault postfix/pickup[1012]: DF259200386: uid=0 from=<root>
      2. Mar 1 10:11:09 openmediavault postfix/cleanup[10075]: DF259200386: message-id=<20190301091109.DF259200386@openmediavault.localdomain>
      3. Mar 1 10:11:09 openmediavault postfix/qmgr[1016]: DF259200386: from=<omv_nas@[mydomain]>, size=487, nrcpt=4 (queue active)
      4. Mar 1 10:11:09 openmediavault postfix/pipe[10077]: DF259200386: to=<openmediavault-notification@localhost.localdomain>, relay=omvnotificationfilter, delay=0.05, delays=0.03/0.01/0/0.01, dsn=2.0.0, status=sent (delivered via omvnotificationfilter service)
      5. Mar 1 10:11:10 openmediavault postfix/smtp[10078]: DF259200386: replace: header Subject: Test message from openmediavault: Subject: [openmediavault.local] Test message from openmediavault
      6. Mar 1 10:11:10 openmediavault postfix/smtp[10078]: DF259200386: to=<info@[mydomain]>, relay=smtp.udag.de[62.146.106.15]:587, delay=0.72, delays=0.03/0.02/0.42/0.25, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 69B2D48D0)
      7. Mar 1 10:11:10 openmediavault postfix/smtp[10078]: DF259200386: to=<info@[mydomain]>, relay=smtp.udag.de[62.146.106.15]:587, delay=0.72, delays=0.03/0.02/0.42/0.25, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 69B2D48D0)
      8. Mar 1 10:11:10 openmediavault postfix/smtp[10078]: DF259200386: to=<mail@[mydomain]>, relay=smtp.udag.de[62.146.106.15]:587, delay=0.72, delays=0.03/0.02/0.42/0.25, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 69B2D48D0)
      9. Mar 1 10:11:10 openmediavault postfix/qmgr[1016]: DF259200386: removed
      10. Mar 1 10:12:27 openmediavault postfix/qmgr[1016]: 7C67A20074C: from=<omv_nas@[mydomain]>, size=964, nrcpt=2 (queue active)
      11. Mar 1 10:12:28 openmediavault postfix/smtp[10078]: 7C67A20074C: to=<admin@openmediavault.localdomain>, orig_to=<admin>, relay=smtp.udag.de[62.146.106.15]:587, delay=2204, delays=2203/0/0.37/0.1, dsn=4.1.2, status=deferred (host smtp.udag.de[62.146.106.15] said: 450 4.1.2 <admin@openmediavault.localdomain>: Recipient address rejected: Domain not found (in reply to RCPT TO command))
      Display All

      ([mydomain] I changed)

      Thet's what I know in the moment.
    • votdev wrote:

      Which service is sending this emails to admin? This user should never receive any email because this user is only used to login to the UI, nothing more. Because of that there is no rule that redirects emails to a real address. If you mail to user root for example they are redirected to your primary address

      Source Code

      1. Mar 7 10:57:36 backup postfix/smtp[3619]: 2DF178C047C: to=<admin@backup.localdomain>, orig_to=<admin>, relay=smtp.udag.de[62.146.106.15]:587, delay=508, delays=507/0.01/0.4/0.13, dsn=4.1.2, status=deferred (host smtp.udag.de[62.146.106.15] said: 450 4.1.2 <admin@backup.localdomain>: Recipient address rejected: Domain not found (in reply to RCPT TO command))


      votdev wrote:

      I assume a plug-in does not handle this correct.

      all I have installed are:
      - openmediavault-shellinabox 3.4
      - openmediavault-usbbackup 4.0.8-1
      - openmediavault-snapraid 3.7.3
      - openmediavault-unionfilesystem 4.0.2
      - openmediavault-locate 3.4
      - openmediavault-omvextrasorg 4.1.15
      - openmediavault-resetperms 3.3
      - openmediavault-clamav 4.1.9

      The mails, what are send to admin, are:
      "Dear admin, your user account was used to log in to backup.local (192.168.0.31) via a web browser.[blablabla]"
      I think, this comes not from one of the plugins.


      Penni d:-)
    • What's the content of /etc/postfix/recipient_canonical?
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • Hmm, looks ok. I can not reproduce the issue because i get the login email and every other notification. So i have to say i really don't know how to fix your problem, Postfix seams to be a beast.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • Ah one thing i realised, the email goes to admin@backup.localdomain, but there catch all rule is @backup.local.

      What is the output of

      Shell-Script

      1. $ omv-confdbadm read 'conf.system.network.dns' --prettify
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • What is the output of

      $ hostname --fqdn
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • By the way, you do not need to set the domain to local. If you empty that configuration, then all notifications should be routed correct. But please execute the test mentioned above before doing any config changes.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • I empty the box with the domainname
      now output is

      Source Code

      1. "domainname": "",
      2. "hostname": "openmediavault"

      ...wait...
      ...wait...
      ...wait...

      OK. I logged in from a different IP. The login notification mail arrives me correctly to mail@[mydomain].
      I think, the right tip was, to empty the box with the domainname.


      Thank you verry much!

      Penni d: -)