Mail Server Connect Fail

[pweb]

OK.

telnet to mail server completed successfully ... showing application layer connectivity.

Seems to indicate problem may be in some setting in Log Server that I'm not aware of ... I assume there are no bugs in the software

[jolson]

I would like you to tail your maillog:

Code: Select all

tail -f /var/log/maillog

After you start the tail, please run the 'test' command from the Mail Settings menu. Is any of the maillog output helpful?

If not, we could tcpdump all of the information being transmitted:

Code: Select all

yum install tcpdump

Code: Select all

tcpdump -n host ip.of.smtp.server -X

Run the 'test' command once more, and show us what appears in the tcpdump. Feel free to obfuscate it if you're concerned about disclosing sensitive information.

[pweb]

The "tail" does not return anything after the daemon starts and the test button is depressed.

As for the tcpdump, I'm getting on thin ice. I can issue the commands but need some help on where/how to get the output.

TIA

[jolson]

The "tail" does not return anything after the daemon starts and the test button is depressed.

Is there more than one node in this cluster? If so, you'll need to tail the maillog on every node to identify which one is sending the mail.

As for the tcpdump, I'm getting on thin ice. I can issue the commands but need some help on where/how to get the output.

The tcpdump command can be run on the CLI just as you would run any other command. Once the tcpdump command is started, you can click the 'Test Settings' button, and tcpdump will return any relevant packets to standard out (text will be displayed in your terminal).

[jolson]

pweb,

We did some internal testing regarding the functionality of the SMTP relay, and one thing to take note of is that you'll want to press the 'Save Settings' button after every change that you make in your Mail Settings. The 'Test Settings' button will not take your newly entered settings unless you save them first.

[pweb]

Can't tell if we are making any progress.

1. The save login before "test" did not work.

2. Performed the tcpdump but am unable to capture the entire output from the VM window ... tcpdump results are returned, but the error is still spawned. The best I can do is the screen shot of the VM window showing the end of the tcpdump.

I appreciate the help you are providing.

[jolson]

The save login before "test" did not work.

Please ensure that your browser is not automatically filling the 'username' and 'password' fields of the SMTP configuration in. I have Nagios Log Server working with a fusemail server currently, so this is definitely possible.

It looks like your SMTP server requires authentication. Can you ensure that your user/pass are entered properly and the proper security setting is selected?

Is it possible for you to provide me with a working set of test credentials to your SMTP server? You could PM me the username/password, and delete the account once I'm through my testing.

Best,


Jesse

[pweb]

Have sent pm with mail account information.

Tried to use this account information as test from Log Server ... no joy.

c
y

[pweb]

Made some progress over the weekend.

Made connection to our mail server's private (inside) IP address via L2L VPN. When the test button is hit, it says test was successful, check to see that test email was received.

Checked all associated accounts, but no email was there.

Where does it go?

[jolson]

Have you made any progress here? I think that you should check your mail server's logs - they should point out what the problem might be.

Using the credentials that you sent me, I ran a tcpdump on the communication between my test NLS server and your SMTP server. The authentication portion was fine (used the user/pass you sent over, as well as STARTTLS authentication). Your mail server was very happy until the data portion was sent over:

The sent data portion from NLS (obfucated):

Code: Select all

P.9.....User-Age
nt:.Nagios.Log.S
erver.Date:.Mon,
.18.May.2015.15:
52:35.+0000.To:.
x.From:.<nagios@
x>.Re
turn-Path:.<nagi
os@x>
.Subject:.=?utf-
8?Q?Nagios_Log_S
erver_Test_Email
?=.Reply-To:."na
gios@x".<nagios@x>.X-Sende
r:[email protected]:
.Nagios.Log.Serv
er.X-Priority:.3
.(Normal).Messag
e-ID:.<x@x>.Mime-Version:
.1.0.Content-Typ
e:.text/plain;.c
harset=utf-8.Con
tent-Transfer-En
coding:.8bit..Th
is.email.is.a.te
st.from.Nagios.L
og.Server..

The reply from your server:

Code: Select all

[email protected].
.....K.......F~.
P.<..|..451.See.
http://pobox.com
/~djb/docs/smtpl
f.html...

It looks like your server is throwing a 451 code, and references the following document: http://pobox.com/~djb/docs/smtplf.html

According to this document, our test email has 'Bare LF' - line feed characters not preceded by an ASCII carriage-return (CR) character. This is apparently what's causing your mail server to reject the transmission from NLS.

If there is a setting in your mail server to allow Bare LF transmission, that will probably get you up and running. Until then, I'll have to talk with a developer about this and see whether or not this is a bug in our software.