Menu

#34 JES 2.8 SMTP : 501 Syntax error

Version 2.x
closed-fixed
mfg8876
None
9
2014-04-08
2014-04-01
No

Hi,

I've got a problem with the SMTP part of JES 2.8.
The platform is windows 2008 R2 x64 / JRE 1.6.

JES is installed on a dedicated SMTP / POP3 server on a domain "mydomain.ad.corp".
Many servers on the domain use JES to send or receive email.

The env looks like this :
- "server0" is where JES is installed and running
- "server1" sends email using a java program : no problem
- "server2" reads and sends email through PDI (kettle) : no problem
- "server3" sends email with SendEmail.exe : no problem

The problem is : trying to send email through a VBScript with "CDO.Message" from any of the servers in the domain gives this error :
8004020E The server rejected the sender address. The server response was: 501 Syntax error (no parameters allowed)

All the sending parameters are the same. The sender address is OK.
I've also tried with Powershell, and it works great. Only the VBS doesn't work at all.
Tried with different recipients (from, to), server IP address, FQDN, ...
And the same VBS works with the standard SMTP service on IIS.

Also, issuing the EHLO or HELO command in Telnet gives the error : 501 Syntax error (no parameters allowed)

As an alternative, i've started JES on port 8025 and the standard IIS SMTP on port 25, but it's not a good solution for me.

Have you any idea of what can cause this malfunction ?
Thanks

Discussion

  • mfg8876

    mfg8876 - 2014-04-04

    Hello there,

    unfortunately that error response can come from any supported SMTP command, be it EHLO or DATA. A server log would help a lot. Be certain to set to logging level to debug and try again. Then simply post that part of the log that relates to the matter.

    Regards,
    Andreas

     
  • mfg8876

    mfg8876 - 2014-04-05

    Alright, all the related problems have been identified and taken care of. New maintenance release to follow soon.

     
  • mfg8876

    mfg8876 - 2014-04-05

    fixed (update committed)

     
  • mfg8876

    mfg8876 - 2014-04-05
    • status: open --> closed-fixed
    • assigned_to: mfg8876
    • Priority: 5 --> 9
     
  • Sebastien Ramos

    Sebastien Ramos - 2014-04-05

    Great !
    I'll test it as soon as it is available.

     
  • mfg8876

    mfg8876 - 2014-04-05

    It is already available. You just need to download JES-2.8.1-bin.jar and copy over jes.jar. Let me know how it works.

     
  • Sebastien Ramos

    Sebastien Ramos - 2014-04-07

    Hello Andreas,
    i've copied the new jes.jar in the JES dir, and restarted the server. I've set wrapper.logfile.loglevel=DEBUG in wrapper.conf.
    Tested from VBScript : no luck, same error message.
    The logfile doesn't show much information.
    You'll find attached : wrapper.log and a VBS test program.

     

    Last edit: Sebastien Ramos 2014-04-07
  • mfg8876

    mfg8876 - 2014-04-07

    Hi Sebastien,

    this is rather odd. I have made considerable updates to command line parsing. Besides other changes, I have made sure to allow trailing characters in order to be as lenient as possible. I will attempt to use the VBS script file.
    In the meantime, I would also kindly ask to retry it yourself once more. There should be at least two log files available under the log dir, one is called jes.log the other jes2.log. Only error logs entries are appended to jes2.log. Could you take a look at those two?
    Alas, you are using the wrapper which means the standard logging facility is not active by default. before executing JES, you will need to add the following lines to wrapper.conf:
    wrapper.java.classpath.3=..lib/log4j-1.2.17.jar
    wrapper.java.additional.7=-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger
    wrapper.java.additional.8=-Dlog4j.configuration=file:/<JES INSTALL="" DIR="">/conf/log4j.properties

    Make sure to replace <JES INSTALL="" DIR=""> with the actual directory path that points to your JES installation. After starting the server, jes.log and jes2.log should be created and have log entries appended to them.

    Regards,
    Andreas

     

    Last edit: mfg8876 2014-04-07
  • mfg8876

    mfg8876 - 2014-04-07

    2014-04-07 17:08:08,840 - [SMTP:5] RFC5321SMTPServerSessionControl - Read Input: MAIL FROM: localpart@mexample.com

    The above command is invalid. It contains a space character after "MAIL FROM:"
    It is illegal no matter which RFC is implemented (821, 2821, 5321).

    I am extremely wary about relaxing the parsing process. What I will do, is provide an unofficial build later today that will relax parsing even further.

    PS: Your previous message has not magically disappeared, I deleted it on purpose.

     

    Last edit: mfg8876 2014-04-07
  • mfg8876

    mfg8876 - 2014-04-07

    Here is an unofficial copy of a version 2.8.2 jes.jar that should be able to parse the erroneous "CDO.Message" commands. Just overwrite the file in the jes install folder.

     
  • Sebastien Ramos

    Sebastien Ramos - 2014-04-08

    Hi Andreas,

    JES 2.8.2 tested and approved, great job !
    It works exactly as expected, problem solved.

    Thank you so much for the time spent, have a nice day.

    Regards,
    Sebastien

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.