SASL authentication with SMTP

I want to authenticate using GSS-API for SMTP.
Can anyone please guide me?
Is there any doc or sample code available?

Wow, this is an obscure solution, but it works. According to this thread, the problem is that:
Although Comcast advertises "AUTH LOGIN PLAIN", the Postfix SASL library won't do plain text auth by default. It needs to be told it's okay with:
smtp_sasl_security_options = noanonymous
Solution:
$ su -
$ cd /etc/postfix
$ cp main.cf main.cf.no_smtp_sasl_security_options
$ echo 'smtp_sasl_security_options = noanonymous' >> ./main.cf
$ serveradmin stop mail
$ serveradmin start mail
I'm not sure how often /etc/postfix/main.cf is overwritten, but presumably this happens every time you change and save Mail settings in Server Admin, so you must redo these steps every time you change the Mail server if you want to use smtp.comcast.net as your mail relay.
AAPL, would you please add a toggle to handle this in Server Admin?

Similar Messages

  • Are there any known issues concerning using DIGEST-MD5 SASL authentication with iPlanet Directory Server 5.0 on Windows NT 4.0?

    I am developing support for the DIGEST-MD5 sasl mechnism on a c-ldap client. I am using the evaluation version of the iPlanet Directory Server 5.0 which lists DIGEST-MD5 as a supported SASL mechanism. The server is running on NT 4.0 After installing the Directory Server with the test database, a changed the passwordStorageScheme from the default of SSHA to clear text. I then added my test user. When I run my test I always get back a resultCode of 49 (invalidCredentials). The digest-challenge I receive from the server and my digest-response are shown below. I have satisfied myself that the calculation of the response directive in the digest response is correct. Does anyone see any problems in the digest response or have any other suggestions? Is there a known problem with the iPlanet Directory Server 5.0?
    digest-challenge:
    realm="BGB2.ndp.provo.novell.com",nonce="Ed8UPLXsWaC6CN",qop="auth",algorithm=md5-sess,charset=utf-8
    digest-response:
    username="uid=bgbrown,ou=people,dc=siroe,dc=com",realm="BGB2.ndp.provo.novell.com",cnonce="A9IuPJKr30RiwL",nc=00000001,qop=auth,digest-uri="ldap/BGB2.ndp.provo.novell.com",response=97061205298e5ebaf206c8ac3598fdce,charset=utf-8,nonce="Ed8UPLXsWaC6CN"

    Found the answer. When the username is an LDAP DN it needs to be proceeded by "dn:".
    example: username="dn:uid=bgbrown,ou=people,dc=siroe,dc=com"
    The server also accepts a simple uid value.
    example: username="bgbrown"

  • Authentication with SASL

    Hello,
    I recently installed POSTFIX which uses SASL authentication, I have found javadocs for javax.security.sasl but am unsure how to implement these, does anyone have any experience of doing this?
    Can I leave the rest of my smtp code and just alter the authentication bit, or will more need to change?
    Any pointers appreciated

    I think I have get little bit closer to get SASL authentication work, but now my program throws this kind of exception:
    javax.naming.AuthenticationException: SASL authentication failed. Root exception is java.lang.NoSuchMethodError
    at com.sun.jndi.ldap.sasl.LdapSasl.saslBind(LdapSasl.java:116)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.sun.jndi.ldap.LdapClient.saslBind(LdapClient.java:369)
    at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:185)
    at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2386)
    at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:239)
    at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:74)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
    at javax.naming.InitialContext.init(InitialContext.java:217)
    at javax.naming.InitialContext.<init>(InitialContext.java:193)
    at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:78)
    My code (I'm using jdk1.3.1):
    import javax.naming.*;
    import javax.naming.directory.*;
    import java.util.Hashtable;
    class DigestTesti {
    public static void main(String[] args) {
         Hashtable env = new Hashtable();
         env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.ldap.LdapCtxFactory");
         env.put(Context.PROVIDER_URL, "ldap://000.000.000.000:000");
         env.put(Context.SECURITY_AUTHENTICATION, "DIGEST-MD5");
         env.put(Context.SECURITY_PRINCIPAL, "dn:uid=JDoe,ou=...,o=...,dc=..., dc=...");
         env.put(Context.SECURITY_CREDENTIALS, "...");
         env.put("java.naming.security.sasl.realm", "...");
         try {
         DirContext ctx = new InitialDirContext(env);
         System.out.println(ctx);
         } catch (NamingException e) {
         e.printStackTrace();
    What could been wrong with my code?
    Regards,
    Janne

  • Broken SSL/TLS SMTP authentication with Outlook Express

    Hi All,
    I've created two ports for SMTP-Authentication with required SSL/TLS : port 25 and port 587. Everythings work fine on port 25 (both smtp-auth and ssl/tls works).
    But when using Outlook Express with port 587, the problems happens:
    Your server has unexpectedly terminated the connection. Possible causes for this include server problems, network problems, or a long period of inactivity. Account: 'pop.cbn.net.id', Server: 'smtps.cbn.net.id', Protocol: SMTP, Port: 587, Secure(SSL): Yes, Error Number: 0x800CCC0F
    I've already disable windows firewall, Desktop Antivirus etc. but still not works.
    Does anyone has the same problem? Thank you.

    Sorry I'm a little late to the party.
    This is a bug in OE. It is attempting to do an SSL negotiation immediately when the connection opens, like what a web browser does for HTTPS connections, rather than using the STARTTLS mechanism to start TLS in the middle of the connection. In other words, it's attempting to use the old, never actually standardized SMTPS protocol if you attempt to do secure SMTP on any port other than 25. When we deployed mandatory SSL/TLS here, we had to deploy an SMTPS server on port 465, just for OE users (our mail relay server is not an IronPort).
    SMTPS was never standardized, never even made it past one Internet-Draft. It's allocation of port 465 was later revoked by IANA and reassigned to another protocol. Yet it was treated as gospel by many mail client authors. I refused to support it on our mail server until it became obvious that OE simply wouldn't work otherwise (getting correct STARTTLS operation by using port 25 is not always available because of ISPs doing port 25 blocking). I don't blame IronPort in the least for not supporting it, although it does make this situation harder to resolve.
    I have learned to hate OE.

  • AuthenticationFailedException when using JNDI and JavaMail with SMTP auth

    Hi all - I've been banging my head on this one for awhile now - hopefully someone else has done this.
    We are working in a servlet container (tomcat), and need obtain a mail session from JNDI. We do this as follows:
                   Context initCtx = new InitialContext();
                   Context envCtx = (Context) initCtx.lookup("java:comp/env");
                   Session mailSession=(Session) envCtx.lookup("mailSession/trumpetinc");so far so good. The jndi entry for the mail session is configured in server.xml as follows:
              <Resource name="mailSession/trumpetinc" scope="Shareable" type="javax.mail.Session"/>
              <ResourceParams name="mailSession/trumpetinc">
                <parameter>
                  <name>mail.smtp.host</name>
                  <value>mail.server.com</value>
                </parameter>
                <parameter>
                  <name>mail.smtp.password</name>
                  <value>ABCDEFG</value>
                </parameter>
                <parameter>
                  <name>mail.smtp.user</name>
                  <value>trumpet_kevin</value>
                </parameter>
             <parameter>
               <name>mail.smtp.auth</name>
               <value>true</value>
             </parameter>
              </ResourceParams>With the above, whenever we hit Transport.send(msg), we got an AuthenticationFailedException thrown. I have run into this before with SMTP authentication, so I decided to try using the transport.sendMessage() method instead.
    So, I get the transport:
    Transport trans = mailSession.getTransport("smtp");
    trans.connect();Then I send my message using:
    msg.saveChanges();
    trans.sendMessage(msg, msg.getAllRecipients());and finally, I close the transport:
    trans.close();Unfortunately, I'm still getting the exception. Is it possible that my connect() method is not picking up the JNDI properties set in the server.xml file (this seems likely)? If so, what's the best way for me to get those properties so I can set them explicitly in the connect() method?
    Thanks in advance,
    - Kevin

    Hi,
    I have faced the same problem and after some googling and trying I have discovered what causes the AuthenticationFailedException exception. I just wanted to share the knowedge maybe it will be helpfull to others.
    Here it is what the API says:
    To use SMTP authentication you'll need to set the mail.smtp.auth property (see below) and provide the SMTP Transport with a username and password when connecting to the SMTP server. You can do this using one of the following approaches:
    1.Provide an Authenticator object when creating your mail Session and provide the username and password information during the Authenticator callback.
    Note that the mail.smtp.user property can be set to provide a default username for the callback, but the password will still need to be supplied explicitly.
    This approach allows you to use the static Transport send method to send messages.
    2.Call the Transport connect method explicitly with username and password arguments.
    This approach requires you to explicitly manage a Transport object and use the Transport sendMessage method to send the message. The transport.java demo program demonstrates how to manage a Transport object. The following is roughly equivalent to the static Transport send method, but supplies the needed username and password:
    Using the Transport.connect makes the JNDI not very helpfull for configuration.
    It seems that using just the mail.smtp.user and mail.smtp.pass is not sufficient for the authentication.
    so, the solution is :
    just place these to lines in the JNDI configuration:
              username="test"
              password="test1"
    so it should looks as follows:
              <Resource name="mail/Session" auth="Container"
              type="javax.mail.Session"
              username="test"
              password="test1"
              mail.transport.protocol="smtp"
              mail.smtp.auth="true"     
              mail.smtp.host="localhost"
              mail.smtp.port="25"
              mail.smtp.user="test"
              mail.smtp.password="test1"
    />
    where test and test1 are the user's credentials
    Regards,
    Kiril
    Message was edited by:
    Kireto
    Message was edited by:
    Kireto

  • Cannot establish TLS with SMTP...wrong address, connection error 5

    An error occurred sending mail: The mail server sent an incorrect greeting: Cannot establish TLS with SMTP server 65.55.176.126:587, SSL_connect error 5:connection closed.

    Is this for an Outlook/Hotmail type account? What do you have for the server settings under Tools/Account Settings/Outgoing Server (SMTP)? (For outlook/hotmail it should be STARTTLS security on port 587, normal password authentication, email address for the User name.)
    If you have an anti-virus/security program scanning outgoing mail, disable that option and see if it helps.

  • Error 550 5.7.1 unable to relay with SMTP PORT 25 Exchange 2013

    Hi All,
    I know this issue has been posted for a while, but still can't resolved issue. We've new Exchange 2013 SP1 (CU4) installation, everything is working properly, the OWA, Exchange Client Connection, SMTP/POP with SSL, except with SMTP Using Port 25 Non-Encrypted
    Connection.  
    If I'm using the SMTP Port 25 without TICK "My Outgoing Server (SMTP) Requires authentication", I've got the error: "550 5.7.1 Unable to relay", but if I TICK the option above, my message will be deliver without any error, how do i get
    rid this problem, I need to UN-TICK the option above for the time being, since we've hundreds email account, I want to avoid to educate and tell the user and even remote their PC, just to configure this issue, it will drive me crazy, we're going to use the
    Exchange Client Connection in the future, If everything is smooth and ok.
    I research this problem on the Internet and of course with TECHNET, but still can't, anyone can help me on this?
    fyi, I tried so many things, delete the default the Default Front End Transport for Port 25, it also not fix my issue.
    Thx
    Irwan

    Hi
    You can paste the output of below result
    Get-receiveconnector | fl name,bindings,PermissionGroups
    I think your default receive connector should be missing out some permissions.
    Also try to see if you get any message on protocol logs and paste them too
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
    (MVP)

  • Need Authentication for SMTP Access

    I have this Java program (SendMail.java) for sending email; however, my ISP requires authentication for SMTP server access, i.e. I receive a 550 Authentication Required error. Does anyone know how to go about coding authentication into a program like SendMail so that the userID and password can be sent back to the server?
    * SendMail.java
    * Created on July 13, 2005, 8:09 PM
    * To change this template, choose Tools | Options and locate the template under
    * the Source Creation and Management node. Right-click the template and choose
    * Open. You can then make changes to the template in the Source Editor.
    * @author Owner
    // SendMail by Tony Swain.
    // Send mail via SMTP
    // To do Appletisize it.
    import java.io.BufferedReader;
    import java.io.FileInputStream;
    import java.io.InputStreamReader;
    import java.io.PrintStream;
    import java.net.Socket;
    import java.util.StringTokenizer;
    import java.net.Authenticator;
    import java.net.*;
    // To do. Finish multiThreading &| write que Thread.
    // this programs sends mail Via SMTP as defined in RFC 821.
    // ftp://ftp.isi.edu/in-notes/rfc821.txt
    public class SendMail   
    Object mailLock              = null;  //In case we want a multi-threaded mailer
    public String mailServerHost = "";
    public String from           = "";
    public String to             = "";
    public String replyTo        = "";
    public String subject        = "Java is Fun";
    public String mailData       =
       "HyperSendMail";
    public String errorMsg = "";
    public Socket mailSendSock = null;
    public  BufferedReader inputStream = null;
    public PrintStream outputStream    =  null;
    public String serverReply          = "";
    SendMail()
       // Doesn't do anything but we need this for extension purposes.
    // Server, from,to,subject, data
    SendMail(String server,String tFrom,String tTo,String sub,String sendData)
       mailServerHost = server;
       mailLock=this; // Thread Monitor passed constructor later. Default this Monitor.
       from = tFrom;
       to   = tTo;
       if(sendData != null)
          mailData = sendData; 
    /*  Just a note to remind myself to add this for cross app./Applet & Runnable.
       & Threadsafe readLine()  I'm too lazy ATM
    SendMail()
       if(mailLock != null)
          if(mailLock instanceof Applet)
             Applet app = (Applet)
    public void send()
       if(!open())          //Yikes! get out of here.
          return;    
       try
          outputStream.println("HELO sendMail");
          serverReply = inputStream.readLine(); 
       catch(Exception e0)
          e0.printStackTrace();
       try
          outputStream.println("MAIL FROM: "+from);
          serverReply = inputStream.readLine();
            // I cheat and don't look for the whole 550
            // we know 5 is an error anyway. Add it in if you want.
          if(serverReply.startsWith("5"))
             close("FROM: Server error :"+serverReply);
             return;
       // Note the switch here. we could get mail from somewhere and by
       // pre setting replyTo reply somewhere else :)
          if(replyTo == null)
             replyTo = from;
          outputStream.println("RCPT TO: <"+to+">");
           // Ya got me! I didn't look for any  250 OK messages. Add it in if you really want.
           // A real programmer will spend 30 hours writing self modifying code in order
           // to save 90 nano seconds ;)  we assume if it did't give an error it must be OK.
          serverReply = inputStream.readLine();
          if(serverReply.startsWith("5"))
             close("Reply error:"+serverReply);
             return;
          outputStream.println("DATA");
          serverReply = inputStream.readLine();
          if(serverReply.startsWith("5"))
             close("DATA Server error : "+serverReply);
             return;
          outputStream.println("From: "+from);
          outputStream.println("To: "+to);
          if(subject != null)
             outputStream.println("Subject: "+subject);
          if(replyTo != null)
             outputStream.println("Reply-to: "+replyTo);
          outputStream.println("");
          outputStream.println(mailData);
          outputStream.print("\r\n.\r\n");
          outputStream.flush();
          serverReply = inputStream.readLine();
          if(serverReply.startsWith("5"))
             close("DATA finish server error: "+serverReply);
             return;
          outputStream.println("quit");
          serverReply = inputStream.readLine();
          if(serverReply.startsWith("5"))
             close("Server error on QUIT: "+serverReply);
             return;
          inputStream.close();
          outputStream.close();
          mailSendSock.close();
       catch(Exception any)
          any.printStackTrace();
          close("send() Exception");
       close("Mail sent");
    public boolean open()
       synchronized(mailLock)
          try
             mailSendSock = new Socket(mailServerHost, 25);
             outputStream = new PrintStream(mailSendSock.getOutputStream());
             inputStream = new BufferedReader(new InputStreamReader(
              mailSendSock.getInputStream()));
             serverReply = inputStream.readLine();
             if(serverReply.startsWith("4"))
                errorMsg = "Server refused the connect message : "+serverReply;
                return false;
          catch(Exception openError) 
             openError.printStackTrace();
             close("Mail Socket Error");
             return false;
          System.out.println("Connected to "+mailServerHost);
          return true;
    public void close(String msg)
              //try to close the sockets
       System.out.println("Close("+msg+")");
       try
          outputStream.println("quit");
          inputStream.close();
          outputStream.close();
          mailSendSock.close();
       catch(Exception e)
          System.out.println("Close() Exception");
         // We are closing so see ya later anyway
    public static void main(String Args[])
    SendMail sm = new
    // * NOTE:
    // Erase these values right away! Just to show you how it is done.
    // Whatever you do don' release it with my mail server hardcoded.
    // last thing I need is 10 million Java mail test spams :)
    SendMail(
              "outgoing.myISP.net",         //Mail Server
              "[email protected]",       // sender
              "[email protected]",       // Recipient
              "Java mail test",               // Subject
              "test test test!");             // Message Data
              sm.send();                      // Send it!
    }

    There is no one in the forum who can shed some light on my problem?

  • Configuring SquirrelMail to use SSL with SMTP

    I ran the conf.pl script to have SquirrelMail access my IMAP server via SSL, and everything works.
    I then tried to use SSL with SMTP as well but when I used SquirrelMail to send mail, I got an error saying "Can't open SMTP stream". What is the correct setting to tell conf.pl to use?
    I had secure SMTP enabled and chose CRAM-MD5 for the authentication method.
    I actually have my web server and smtp server on the same machine, so this is more of a hypothetical question. In the end I turned off secure SMTP and set authentication back to none.
    Ben

    I don't have access to logs right now, but to answer your other question, SSL works fine when sending from Mail.
    But with Mail, I supply the username and password; which user does SquirrelMail use to send?

  • SASL Authentication...again...

    Last time i posted this question:
    While using iDS 5.1 and a test user "uid=jdoe,ou=xxx,o=xxx" we've been getting same results over and over again: Authentication failed. Passwords are being set to CLEARTEXT, user being created using default user template so it contains the userpassword-attribute, and in the Java-code we've been using MD5 Digest authentication 'cause that's the method it supports. This is what is being done in the code:
    1. Client connects server using ldapHost and ldapPort.
    2. Hashtable "env" is being constructed.
    3. Environment properties INITIAL_CONTEXT_FACTORY, PROVIDER_URL, SECURITY_PRINCIPAL and SECURITY_CREDENTIALS of context are being specified.
    4. if ldapconnection.isauthenticated() is TRUE, print "success", else print "failed".
    All environment properties are of course used via env.put(context.property_name, "value");
    Is this it? What else should it do? All values match the ones being set in DS. Still authentication fails. "
    We still have this problem but the thing that has come up is the supportedSASLMechanisms gives "no attributes" if asked with database name, but gives correct values when asked just with IP-address of server. To make long story short, this works:
    Attributes attrs = ctx.getAttributes("ldap://<ip-address>"new String[]{"supportedSASLMechanisms"});
    System.out.println(attrs);
    This doesn't work:
    Attributes attrs = ctx.getAttributes("ldap://<ip-address>/o=<organization>"new String[]{"supportedSASLMechanisms"});
    System.out.println(attrs);
    Is there a access control in NetscapeRoot that differs from our database controls that makes this happen?

    I think I have get little bit closer to get SASL authentication work, but now my program throws this kind of exception:
    javax.naming.AuthenticationException: SASL authentication failed. Root exception is java.lang.NoSuchMethodError
    at com.sun.jndi.ldap.sasl.LdapSasl.saslBind(LdapSasl.java:116)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.sun.jndi.ldap.LdapClient.saslBind(LdapClient.java:369)
    at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:185)
    at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2386)
    at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:239)
    at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:74)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
    at javax.naming.InitialContext.init(InitialContext.java:217)
    at javax.naming.InitialContext.<init>(InitialContext.java:193)
    at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:78)
    My code (I'm using jdk1.3.1):
    import javax.naming.*;
    import javax.naming.directory.*;
    import java.util.Hashtable;
    class DigestTesti {
    public static void main(String[] args) {
         Hashtable env = new Hashtable();
         env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.ldap.LdapCtxFactory");
         env.put(Context.PROVIDER_URL, "ldap://000.000.000.000:000");
         env.put(Context.SECURITY_AUTHENTICATION, "DIGEST-MD5");
         env.put(Context.SECURITY_PRINCIPAL, "dn:uid=JDoe,ou=...,o=...,dc=..., dc=...");
         env.put(Context.SECURITY_CREDENTIALS, "...");
         env.put("java.naming.security.sasl.realm", "...");
         try {
         DirContext ctx = new InitialDirContext(env);
         System.out.println(ctx);
         } catch (NamingException e) {
         e.printStackTrace();
    What could been wrong with my code?
    Regards,
    Janne

  • Jdk1.3 vs jdk1.4 and SASL authentication

    I'm trying to get SASL authentication work with jdk1.3 and iPlanet Directory Server. Everytime I get same exception:
    SASL authentication failed. Root exception is java.lang.NoSuchMethodError
    When I try with jdk1.4 everything works fine. Now I'm just wondering that is there other things that I should take care when I try get authentication work with jdk1.3. I know that all the extension packages are integrated to the jdk1.4 and I have set same packages to the CLASSPATH when I'm trying to do same with jdk1.3, but same exception occurs than above.
    Does anyone know what's the problem?
    Thanks,
    Janne

    Hi ,
    Jsse 1.0.3 (strictly this version only) is needed along with jdk1.3 for the SASL or SSL authentication to be done fine.
    Hope this helps,
    Regards,
    Sathya

  • Jdk1.3 vs jdk1.4 SASL authentication

    I'm trying to get SASL authentication work with jdk1.3 and iPlanet Directory Server. Everytime I get same exception:
    SASL authentication failed. Root exception is java.lang.NoSuchMethodError
    When I try with jdk1.4 everything works fine. Now I'm just wondering that is there other things that I should take care when I try get authentication work with jdk1.3. I know that all the extension packages are integrated to the jdk1.4 and I have set same packages to the CLASSPATH when I'm trying to do same with jdk1.3, but same exception occurs than above.
    Does anyone know what's the problem?
    Thanks,
    Janne

    Hi ,
    Jsse 1.0.3 (strictly this version only) is needed along with jdk1.3 for the SASL or SSL authentication to be done fine.
    Hope this helps,
    Regards,
    Sathya

  • Mail SASL authentication problem - solved

    My outgoing mail stopped working. I had been relaying mail through my ISP's smtp server and at some point i started getting SASL authentication errors ("no worthy mechs found").
    I searched and found a thread that contained a fix: http://discussions.apple.com/thread.jspa?threadID=2207959
    The fix was rather mysterious (to me at least) in that it involved adding one line to my /etc/postcript/main.cf file. The line was: "smtpsasl_securityoptions =".
    I was going to post a reply to the thread, but the thread is "archived".
    Why do threads get archived? Too old?
    Well, anyway, I don't like having to open a separate thread for this, but I hope this helps someone solve the same problem I was having.
    Also, if anyone has any kind of real explanation for why this fix works and/or whether it is likely to survive future software changes made by apple (or has a better way to fix that will), I would love to hear about it.
    Thanks.

    Try installing ldap1.2.4 and putting ldap.jar and providerutil.jar in your bootclasspath.

  • NTLM Integration with SMTP

    Hi Dear Members,
    I am getting following exception on NTLM authentication for SMTP ,Can you please send me the integration of NTLM with javamail SMTP.
    Thank you very much
    Anil .
    535 5.7.3 Authentication unsuccessful
    javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

    Thank you Shanon,
    I would like to post whole exception,Can you please check once and let me know its surely problem with permissions.
    *50-EXCH07.corp.scwa.com Hello [10.1.1.31]*
    *250-SIZE 52428800*
    *250-PIPELINING*
    *250-DSN*
    *250-ENHANCEDSTATUSCODES*
    *250-STARTTLS*
    *250-AUTH GSSAPI NTLM*
    *250-8BITMIME*
    *250-BINARYMIME*
    *250 CHUNKING*
    DEBUG SMTP: Found extension "SIZE", arg "52428800"
    DEBUG SMTP: Found extension "PIPELINING", arg ""
    DEBUG SMTP: Found extension "DSN", arg ""
    DEBUG SMTP: Found extension "ENHANCEDSTATUSCODES", arg ""
    DEBUG SMTP: Found extension "STARTTLS", arg ""
    DEBUG SMTP: Found extension "AUTH", arg "GSSAPI NTLM"
    DEBUG SMTP: Found extension "8BITMIME", arg ""
    DEBUG SMTP: Found extension "BINARYMIME", arg ""
    DEBUG SMTP: Found extension "CHUNKING", arg ""
    DEBUG SMTP: Attempt to authenticate
    DEBUG SMTP: check mechanisms: LOGIN PLAIN DIGEST-MD5 NTLM
    DEBUG SMTP: mechanism LOGIN not supported by server
    DEBUG SMTP: mechanism PLAIN not supported by server
    DEBUG SMTP: mechanism DIGEST-MD5 not supported by server
    DEBUG NTLM: type 1 message: suppliedDomain: scwa.com; suppliedWorkstation: anilp; flags: 0x00001201
    DEBUG NTLM: type 1 message length: 45
    AUTH NTLM TlRMTVNTUAABAAAAATIAAAgACAAgAAAABQAFACgAAABTQ1dBLkNPTUFOSUxQ
    *334 TlRMTVNTUAACAAAAAAAAADgAAAABAgACqACFj4Jj6BkAAAAAAAAAAAAAAAA4AAAABQLODgAAAA8=*
    TlRMTVNTUAADAAAAGAAYAEAAAAAwADAAWAAAABAAEACIAAAAEAAQAJgAAAAKAAoAqAAAAAAAAAAAAAAAARIAAAb3tgt0MQY2IrDhGFlWlhKgREXn6rmaxI5fXysDocEtqWQeLTtIEl8BAQAAAAAAABB/XLilL8sBp04jz40bvfgAAAAAAAAAAHMAYwB3AGEALgBjAG8AbQBsAGUAdgBlAGwAbwBuAGUAYQBuAGkAbABwAA==
    *535 5.7.3 Authentication unsuccessful*
    javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

  • I get error message: "An error occurred with the  publication of album...Authentication with server failed...whenever I open a facebook file in my iPhoto. In each file, most of my photos have disappeared. What do I need to do?

    I get error message: "An error occurred with the  publication of album...Authentication with server failed. Please check your login and password information" whenever I open a facebook file in my iPhoto. In each file, most of my photos have disappeared. I am hoping I can retrieve these "lost" files. What do I need to do?

    Message was edited by: leroydouglas
    better yet, try this solution:
    https://discussions.apple.com/message/12351186#12351186

Maybe you are looking for