Nagios Notificatin by mail

An open discussion forum for obtaining help with Nagios Core. Nagios Core users of all experience levels are welcome here. Subforum have been created for the discussion of Nagios Core and Nagios Plugin development.

NOTE: The SourceForge.net mailing lists have been deprecated in favor of this forum in order to expedite support and provide additional features not available on the old mailing list.

Re: Nagios Notificatin by mail

Postby scottwilkerson » Tue Sep 04, 2018 7:33 am

that looks correct
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
User avatar
scottwilkerson
DevOps Engineer
 
Posts: 12331
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises

Re: Nagios Notificatin by mail

Postby michaelpn » Fri Sep 14, 2018 5:41 am

Hi Scottwilkerson,

Sorry for delayed answer but I had an very important case to solve.

now I have fixed it. After a long consideration and troubleshooting I restarted postfix services and it helped:)
I mean how difficult can it be :)

=>
dig fg.dk mx

; <<>> DiG 9.9.5-3ubuntu0.17-Ubuntu <<>> fg.dk mx
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34426
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 3

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;fg.dk. IN MX

;; ANSWER SECTION:
fg.dk. 3600 IN MX 10 as.fg.dk.

;; ADDITIONAL SECTION:
as.fg.dk. 3600 IN A 172.xx.x.xxx
as.fg.dk. 3600 IN A 172.xx.x.xxx

:)

I have added "base" file with my domain IP but I still get the same !P 127.0.1.1

=>
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.1.1

vi /etc/resolvconf/resolv.conf.d/base

nameserver 172.xx.x.xxx
nameserver 172.xx.x.xxx
~
~
~
~
~
~
"/etc/resolvconf/resolv.conf.d/base" 2L, 48C

Do you have any idea about?

Best Regards
Michael Pierre Nielsen
Michael Pierre
Forenede Gruppeliv
2500 Valby
Copenhagen
michaelpn
 
Posts: 54
Joined: Fri Jul 14, 2017 12:12 am

Re: Nagios Notificatin by mail

Postby ssax » Fri Sep 14, 2018 2:37 pm

If the MX lookup is failing, as a test you can edit your main.cf and change it from this:

Code: Select all
relayhost = fgmail3.fg.dk


To this:

Code: Select all
relayhost = [fgmail3.fg.dk]


And restart postfix and it will not do an MX lookup:

Code: Select all
service postfix restart


Let us know the results.
Be sure to check out our Knowledgebase for helpful articles and solutions!
User avatar
ssax
Dreams In Code
 
Posts: 3379
Joined: Wed Feb 11, 2015 12:54 pm

Previous

Return to Nagios Core

Who is online

Users browsing this forum: delboy1966, sampan1 and 38 guests