We also see this same issue. Validated via postfix logs that emails to invalid addresses are actually generated by Observium.

When new alert is triggered Observium sends the email to the actual real designated alert email address, but also generate these emails to invalid addresses, looks like it tries to send email to the device ID #, eg. 119@domain.com where 119 is the Observium device ID for one of our switches.

On 06/19/2017 12:59 PM, Attila Nagy wrote:
I would be interested how your server gets to try to send the e-mail to that strange e-mail address: 56@observium.xxxxx.com

Don't you have some strange mail forwarding rules with a typo in it?
What is the user ID of your user (simon@xxxxx.com)?
Watch through the postfix log to see if observium/php really tries to send the e-mail to this e-mail address (56@...). Here you can decide where is the failure (observium/postfix)

Tylla

On 2017-06-19 18:21, Simon Mousey Smith wrote:
Sample email if helps:


Date: Mon, 19 Jun 2017 15:21:11 +0100 (BST)
From: Mail Delivery System <MAILER-DAEMON@observium.xxxxx.com>
To: root@observium.xxxxx.com
Subject: Undelivered Mail Returned to Sender

[-- Attachment #1: Notification --]
[-- Type: text/plain, Encoding: 7bit, Size: 0.4K --]

This is the mail system at host observium.xxxxx.com.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                   The mail system

<56@observium.xxxxx.com> (expanded from <56>): unknown user: "56"

[-- Attachment #2: Delivery report --]
[-- Type: message/delivery-status, Encoding: 7bit, Size: 0.3K --]

Reporting-MTA: dns; observium.xxxxx.com
X-Postfix-Queue-ID: 4AA00200C2B
X-Postfix-Sender: rfc822; root@observium.xxxxx.com
Arrival-Date: Mon, 19 Jun 2017 15:21:10 +0100 (BST)

Final-Recipient: rfc822; 56@observium.xxxxx.com
Original-Recipient: rfc822;56@observium.xxxxx.com
Action: failed
Status: 5.1.1
Diagnostic-Code: X-Postfix; unknown user: "56"

[-- Attachment #3: Undelivered Message --]
[-- Type: message/rfc822, Encoding: 7bit, Size: 16K --]

Date: Mon, 19 Jun 2017 15:21:10 +0100
From: Observium <observium@observium.xxxxx.com>
To: simon@xxxxx.com
Subject: ALERT: [router.xxxxx] [device] Device Is Down
X-Mailer: Observium 17.6.8665

------------------------------------
ALERT
Device Is Down
------------------------------------
Entity:      router.xxxxx
Conditions:  device_status equals 0 (0)
Metrics:     device_status = 0
Duration:    5m (2017-06-19 15:16:10)
------------------------------------

------------------------------------
Device:      router.xxxxx
Hardware:
OS:          TP-LINK Router
Location:    xxxxx
Uptime:      Down 5m
------------------------------------

E-mail sent to: simon@vvvvv.com
E-mail sent at: Mon, 19 Jun 2017 15:21:10 +0100

--
Observium Professional 17.6.8665
http://www.observium.org




Regards

Simon

On 19 Jun 2017, at 17:11, Adam Armstrong <adama@memetic.org> wrote:

If you run test_alert.php -d for this particular alert, what is its output?

adam.

On 19/06/2017 17:10:16, Simon Mousey Smith <simonsmith5521@gmail.com> wrote:

Hi,

Im still getting these, generated today too

Had 4 today so far (faulty server, groan)

Simon

On 19 Jun 2017, at 16:57, Adam Armstrong <adama@memetic.org> wrote:

Are they still being generated, or were there just a couple generated on the 15th?

adam.

On 19/06/2017 16:48:10, Tim Cooper <lists@coop3r.com> wrote:



> On 19 Jun 2017, at 16:42, Tim Cooper wrote:
>
>
>>
>> As just noticed these errors in roots mail on the server
>>
>> <33@observium.xxxxx.com> (expanded from <33>): unknown user: “33”
>> <37@observium.xxxxx.com> (expanded from <37>): unknown user: “37"
>>
>
> I'm seeing these erroneous emails also running r8665. At a rough guess it looks like we first started noticing them after upgrading on 15th June (r8663)
>
> Also seems Telegram alerts stopped working since 13th June (r8661 ish?)

Ignore that last bit. Telegram is working fine after all. It's just the undeliverable emails we are seeing
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium



_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium




_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium