SMTP Test from CLI - Revision history

Ledhed: /* Testing SASL Auth */

2013-09-27T00:30:59Z

‎Testing SASL Auth

Ledhed: /* Testing SASL Auth */

2013-09-27T00:29:24Z

‎Testing SASL Auth

Ledhed: /* Testing SASL Auth */

2013-09-27T00:27:24Z

‎Testing SASL Auth

Ledhed: /* Testing SASL Auth */

2013-09-27T00:26:35Z

‎Testing SASL Auth

Ledhed: /* Testing SASL Auth */

2013-09-27T00:24:18Z

‎Testing SASL Auth

Ledhed: /* Testing SASL Auth */

2013-09-27T00:23:22Z

‎Testing SASL Auth

Ledhed at 00:22, 27 September 2013

2013-09-27T00:22:35Z

Ledhed: Created page with "When setting up a mail server sometimes its handy to be able to test from the command line. This can be accomplished with telnet or openssl == Telnet == telnet mx.server.tl..."

2013-09-26T00:32:14Z

Created page with "When setting up a mail server sometimes its handy to be able to test from the command line. This can be accomplished with telnet or openssl == Telnet == telnet mx.server.tl..."

New page

When setting up a mail server sometimes its handy to be able to test from the command line.

This can be accomplished with telnet or openssl

== Telnet ==
telnet mx.server.tld 25

ehlo my.hostname
Mail From: your@email.address
RCPT To: recipient@email.address
DATA
From: your@email.address
Subject: Put your subject here
Place the body of your message here then place a period on a line all by itself to finish the body of the message

.

== Testing SMTP/TLS with OpenSSL Client ==
openssl s_client -connect mx.server.com:25 -starttls smtp

ehlo my.hostname
Mail From: your@email.address
RCPT To: recipient@email.address
DATA
From: your@email.address
Subject: Put your subject here
Place the body of your message here then place a period on a line all by itself to finish the body of the message

.

[[Category:Postfix]]

← Older revision		Revision as of 00:30, 27 September 2013
Line 63:		Line 63:

	Recap		Recap
		+	echo -ne 'username' \| openssl enc -base64
		+	dXNlcm5hbWU=
		+	echo -ne 'password' \| openssl enc -base64
		+	cGFzc3dvcmQ=
		+
	telnet mx.server.tld 25		telnet mx.server.tld 25

@@ Line 60: / Line 60: @@
 If the username and password are correct you should get a 235 response like this:
 2.7.0 Authentication successful
 [[Category:Postfix]]

@@ Line 49: / Line 49: @@
   ehlo my.hostname
-Now issue the AUTH LOGIN command, in this format:   AUTH LOGIN <Encrypted username>
+Now issue the AUTH LOGIN command, in this format:   AUTH LOGIN followed by the encrypted username
   AUTH LOGIN dXNlcm5hbWU=

@@ Line 34: / Line 34: @@
 Step 1, get the encrypted version of your username and password
   echo -ne 'username' | openssl enc -base64
 Output will look like this:
   dXNlcm5hbWU=
   echo -ne 'password' | openssl enc -base64
 Output will look like this:

← Older revision		Revision as of 00:22, 27 September 2013
Line 28:		Line 28:

	.		.
		+
		+
		+	== Testing SASL Auth ==
		+	If the server you're trying to test supports SASL authentication you can test AUTH LOGIN as follows.
		+
		+	Step 1, get the encrypted version of your username and password
		+	echo -ne 'username' \| openssl enc -base64
		+	Output will look like this:
		+	dXNlcm5hbWU=
		+
		+	echo -ne 'password' \| openssl enc -base64
		+	Output will look like this:
		+	cGFzc3dvcmQ=
		+
		+	Now connect with one of the methods listed above (Telnet or OpenSSL)
		+	Issue the ehlo command:
		+	ehlo my.hostname
		+
		+	Now issue the AUTH LOGIN command, in this format: AUTH LOGIN <Encrypted username>
		+	AUTH LOGIN dXNlcm5hbWU=
		+
		+	If the server returns a 334 like this:
		+	334 UGFzc3dvcmQ6
		+
		+	Then enter your encrypted password
		+	cGFzc3dvcmQ=
		+
		+	If the username and password are correct you should get a 235 response like this:
		+	235 2.7.0 Authentication successful
		+

	[[Category:Postfix]]		[[Category:Postfix]]

@@ Line 65: / Line 65: @@
   telnet mx.server.tld 25
-DSN
+mx.server.tld ESMTP Postfix (Debian/GNU)
   ehlo my.hostname
 -mx.server.tld