Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!TAURUS.BITNET!LEONID From: LEONID@TAURUS.BITNET Newsgroups: comp.protocols.ibm Subject: BSMTP problem with UREP 3.2 Message-ID: <8804211947.AA10142@jade.berkeley.edu> Date: 20 Apr 88 12:30:17 GMT Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: leonid%taurus.bitnet@jade.berkeley.edu Organization: The Internet Lines: 44 The problem I am going to describe below has occured since we installed PSU UREP version 3.2 with it's BSMTP code. This has occured mostly with old versions of Columbia (crosswell) MAILER running on VM, and lately it occures with CUNYVM too. It seems that the UREP code does not understand the full command set of BSMTP and upon receiving something it cannot interpret it drops the message and send a REPLY file back to the offending MAILER. I have not succeeded to capture the original BSMTP command sequence that caused the problem, but at the end of this message I supply the REPLY filw. The current situation is that mail send by CUNYVM (and others) to TAURUS.BITNET directly get dropped, and mail send to MATH.TAU.AC.IL works fine since it passes through TAUNIVM's MAILER. As it seems to me, the solution would be: a) to fix the UREP code (!) b) to remove extravagant commands and parameters from FAl and Columbia Mailers. Of course a) is preferrable, but I can do it, the UREP code is totally undocumented, not a single line of comment! I would appreciate any help. Please reply directly to me: leonid@taurus.bitnet leonid%math.tau.ac.il@cunyvm.cuny.edu ---------------------- HELO TAURUS.BITNET VERB ON MAIL FROM:<> RCPT TO: DATA 220 taurus.bitnet Batch Simple Mail Transfer Ready 250 OK 250 OK 504 Command parameter not implemented 503 Bad sequence of commands 354 Start Mail input; end with . 503 Bad sequence of commands 221 taurus.bitnet closing transmission . QUIT ---------------------------