Title: | Mailworks-unix |
Notice: | V2.0.4 now available -- see Note 4.37 5 |
Moderator: | TAMARA::NEUMAN::Neumann |
Created: | Wed Jun 02 1993 |
Last Modified: | Tue Jun 03 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 1384 |
Total number of notes: | 5851 |
Hello, I have a customer who has v2.7 of Teamlinks connecting to a MAILworks for UNIX server V2.0. When sending to an X.400 address that contains a SPACE for the ADMD, the server send a Non-delivery, indicating that there is a problem with the address. Can the server handle a space ADMD? I though that this problerm was fixed in V1.5 of MAILworks. We have checked the Mail profile to ensure that the semicolon was the delimeter for addressing. Some examples were: c=us;a= ;p=fed;o=fed;s=harris;s=randy Also, using the template failed as well. Any ideas? Thanks in adance for your support. Randy
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
1349.1 | MW/UNIX can handle space in ADMD; please post non-delivery report | KOALA::PAWELKO | Tue Feb 25 1997 13:48 | 17 | |
Hello Randy, MailWorks/UNIX V2.0 can definitely handle X.400 addresses that contain blank ADMD values. What exactly is the non-delivery report? Please post one here. Are you sure that the MTS routing is set up to handle such an address? I am guessing that it is the MTA that is returning the non-delivery report because it is unable to route the message. Seeing the non-delivery report will help us figure out what is happening. Also, please check the mcslog and the x488glog for pertinent errors. Regards, Mary |