scheduled reporting not emailing

[abrist]

Does your nagios server have 2 ips? (one internal lan or vpn, and one external?)

[mobiledataforce]

Yes, I am monitoring on my internal LAN, and external hosts.

[scottwilkerson]

Looking back at the maillog on pg 1 of this thread, it looks like mail is being deferred

Apr 10 13:24:58 localhost postfix/smtp[17825]: 7F6ED27E32: host smtp-bb.vtext.com[69.78.128.213] refused to talk to me: 554 njbrspamp2.vtext.com
Apr 10 13:24:58 localhost postfix/bounce[17836]: warning: inet_protocols: IPv6 support is disabled: Address family not supported by protocol
Apr 10 13:24:58 localhost postfix/bounce[17836]: warning: inet_protocols: configuring for IPv4 support only
Apr 10 13:24:58 localhost postfix/smtp[17825]: 7F6ED27E32: to=<##########@vtext.com>, relay=smtp-sl.vtext.com[69.78.67.53]:25, delay=428973, delays=428973/0.09/0.82/0, dsn=4.0.0, status=deferred (host smtp-sl.vtext.com[69.78.67.53] refused to talk to me: 554 txslspamp1.vtext.com)

Out of curiosity, do you have your hostname set on the server? (you can see by typing hostname at the command like)

Code: Select all

hostname

[mobiledataforce]

No it is not set. It is the default localhost.localdomain.

[mobiledataforce]

Sendmail is not supported? I don't understand why that is the first option when configuring via the web then? I only see Sendmail and SMTP; what other options do I have?
Thanks.

Checking in..

[scottwilkerson]

No it is not set. It is the default localhost.localdomain.

This is likely the problem, many mail servers will reject mail from a MTA identifying itself as localhost

[mobiledataforce]

I set the hostname. Still have the same results.

[abrist]

Is the hostname fully qualified?

[mobiledataforce]

Yes.

[scottwilkerson]

If you still see items like this

Code: Select all

Apr 10 13:24:58 localhost postfix/smtp[17825]: 7F6ED27E32: to=<##########@vtext.com>, relay=smtp-sl.vtext.com[69.78.67.53]:25, delay=428973, delays=428973/0.09/0.82/0, dsn=4.0.0, status=deferred (host smtp-sl.vtext.com[69.78.67.53] refused to talk to me: 554 txslspamp1.vtext.com)

Then you are going to have to contact Verizon. I've done some research and all I can find are messages that say that this is caused by Verizon's spam filter

http://www.samsung-omnia.org/general-sa ... /#msg24552