There are some interesting tricks:<\/p>\n
The commands to use in telnet with the “AUTH LOGIN” command:<\/p>\n
perl -MMIME::Base64 -e <\/code>'print encode_base64(\"username\");'<\/code><\/div>\nperl -MMIME::Base64 -e <\/code>'print encode_base64(\"password\");'<\/code><\/div>\n<\/div>\n<\/div>\n\nEHLO mailserver.com<\/code><\/strong><\/div>\n250-server1.mailserver.com Hello\u00a0 [1.1.1.2]<\/code><\/div>\n250-SIZE 52428800<\/code><\/div>\n250-PIPELINING<\/code><\/div>\n250-AUTH PLAIN LOGIN<\/code><\/div>\n250-STARTTLS<\/code><\/div>\n250 HELP<\/code><\/div>\nAUTH LOGIN<\/code><\/strong><\/div>\n334 VXNlcm5hbWU6<\/code><\/div>\ndXNlcm5hbWUuY29t<\/code><\/strong><\/div>\n334 UGFzc3dvcmQ6<\/code><\/div>\nbXlwYXNzd29yZA==<\/code><\/strong><\/div>\n<\/div>\nBUT, Exchange has NTLM auth only: 250-AUTH NTLM<\/div>\nSome sites suggest:<\/div>\n\n\n<\/h6>\naspNetEmail had been running fine when they were emailing through Exchange 2007, however, when they upgraded, everything quit working, and started throwing 2 main errors.<\/h6>\nThe 2 errors were:<\/h6>\na) “504 5.7.4 Unrecognized authentication type”
\nAnd, once (a) was resolved, (b) happened:
\nb) “550 5.7.1 Client does not have permission to send as this sender”<\/h6>\nLets talk about these 2 errors.<\/h6>\n504 5.7.4 Unrecognized authentication type
\n<\/strong>In this particular instance, the customer was using the AuthLogin authentication scheme in aspNetEmail. However, starting in Exchange 2010, the only authentication mechanism enabled is NTLM. On their Exchange 2007 server, they had other authentication schemes enabled. So, as soon as they upgraded to Exchange 2010, aspNetEmail was throwing an exception, basically saying that AuthLogin was no longer supported.<\/h6>\nThere are 2 ways to resolve this.
\na)\u00a0In the code, tell aspNetEmail to use the NTLM authentication scheme. In this instance, the customer didn’t want to touch the code base. So they decided for option (b), which was:
\nb)\u00a0Enable AuthLogin authenticaton on Exchange. To do this:
\nIn the Exchange console under server configuration:
\nSelect hub transport.
\nRight click\u00a0 the client server and select properties.
\nSelect the authentication tab.
\nCheck the Basic Authentication checkbox.
\nUncheck the Offer Basic only after TLS<\/h6>\nYou may have to restart the Exchange services.<\/h6>\nOnce this was resolved, the next error was thrown.<\/h6>\n550 5.7.1 Client does not have permission to send as this sender
\n<\/strong>This error was being thrown because the FROM address the customer was using, was different than the Exchange mailbox they were relaying through. Like the error message implies, this is a permissions issue. To resolve this, the following steps were taken.
\na)From an Exchange Command prompt, run the following command:
\nAdd-AdPermission -Identity “Default Receive Connector” -User “NT AUTHORITY\\Authenticated Users” -ExtendedRights ms-Exch-SMTP-Accept-Any-Sender<\/h6>\nc)\u00a0On the user account, in Active Directory, under Security, under the SELF account, select the Manage Send As Permission option.<\/h6>\n<\/blockquote>\n
I’re better off using the first way – sending credentials in a plane mode is not a good way.<\/p>\n
If you have a ticked checkbox “Offer Basic authentication only after starting TLS” in your receive connector you won’t be able enter “AUTH LOGIN” command until you type: “STARTTLS”. But after that you won’t be able to type plain text commands – the must be encoded :).<\/p>\n
You can try this command – unsuccess for me\u00a0 now:<\/p>\n
openssl s_client -debug -starttls smtp -crlf -connect localhost:25<\/code><\/pre>\nOpenSSL will do the STARTTLS handshake for you and you will be able to pick up the conversation from there (decrypted automatically on the fly).<\/p>\n