Posts tagged "smtp"

LiveCycle7: javax.mail.MessagingException: 554 Mail from [email@mail.com] rejected for policy reasons

Posted on February 21, 2011 by dmcmahon | Comments (0)

Issue

 If you are using the mail/notification functionality in LiveCycle 7, you may find that the mails are never received by the intended recipient.  If you look in the adminui you may find the action has stalled with the following error:

"javax.mail.MessagingException: 554 Mail from <email@mail.com> rejected for policy reasons"

Reason

 This is caused by a lack of privileges to use the SMTP mail server in your organisation.

Solution

Consult your IT department and request permission for the Lc Server to use the SMTP mail server to send email notifications.

reference: (1-28762420)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES: javax.mail.MessagingException: Could not connect to SMTP host: <hostname>, port: 25

Posted on October 6, 2009 by dmcmahon | Comments (0)

Issue

 If you are trying to send a mail from a process in LiveCycle ES, you may encounter the following exception in the log:

java.lang.RuntimeException: javax.mail.MessagingException: Could not connect to SMTP host: <hostname>, port: 25;
nested exception is:
java.net.SocketException: Software caused connection abort: connect

Reason

 If you are using Virus Scanner software they often block port 25 to prevent worm-type mass mailings.  In McAfee for example, you can verify this if you bring up the VirusScan Console and look at the Access Protection Task. Check the properties for the port settings.

Solution

 You should disable any anti-virus checks on port 25.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES: troubleshoot POP/SMTP email servers

Posted on October 1, 2009 by dmcmahon | Comments (0)

Troubleshoot SMTP server

If you are having problems connecting/using an SMTP server with LiveCycle, you should manually check that you can indeed connect and send e-mails by issuing the following set of commands on the server you want to connect from.

In this example, assuming you want to troubleshoot the connection to the SMTP server mail.company.com from a Windows server, you would issue the following from a command prompt:

cmd> telnet mail.company.com 25   
220 mail.company.com ESMTP Sendmail 8.13.3/8.13.3; Fri, 3 Mar 2006 17:22:29 GMT  
helo mydomain.com  
250 mail.company.com Hello bla-dhcp-206.company.com [<ip address>], pleased to meet you  
mail from: someone@mydomain.com  
250 2.1.0 someone@mydomain.com&hellip; Sender ok  
rcpt to: support@mail.company.com  
250 2.1.5 support@mail.company.com&hellip; Recipient ok  
data  
354 Enter mail, end with '.' on a line by itself  
Text of the message .  
250 2.0.0 k23HMTO3006628 Message accepted for delivery  
quit  
221 2.0.0 mail.company.com closing connection 
Connection to host lost.  
cmd>

Preferably you should attempt to use the same e-mail addresses for the sender and recipients as the one that are meant to be used by your application.  If any of the operations above fail, it means that the problem is NOT with your application, but with the SMTP server itself.  If it works, then you should try the same from a remote host, to see if your issue might have to do with a firewall or some network issue.

If you don’t get any errors when doing these 2 operations, then it means that your server is properly set to send email, so now you can switch to troubleshooting POP.

Troubleshoot POP server

 The POP3 manual commands are almost as easy as the SMTP commands. To check your mail with POP:

cmd> telnet popserver.somedomain.com 110
user <some_valid_user>
pass <user_password>
stat

Each of these commands should return “+OK”.  The “stat” command should also return 2 numbers indicating the number of new messages received, and messages left on the server.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)