[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference abbott::mailworks-vms

Title:	MailWorks for OpenVMS
Notice:	kit info notes 3-6; policies note 2; reporting bugs note 7
Moderator:	KOALA::LAVASH

Created:	Wed Jul 28 1993
Last Modified:	Mon Jun 02 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1583
Total number of notes:	6814

1558.0. "Mailworks rejecting mail from Internet via x.400" by COMICS::HALFACREE (Nothing is as it seems....) Tue Mar 18 1997 11:15

    Hi,
    
    I have a customer who is trying to receive mail from the Internet via
    Mercury's x.400 service. The mails get pass through MRX without any
    problems but then gets rejected by Mailworks.
    
    The same message if sent via the same route but to VMSmail works okay.
    
    The only thing so far that we have found is that the message is sent as
    a content_type of %x16 where as mails sent from x400 via Mercury and
    then through MRX have a content_type of %x02.
    
    Customer is using MRX S2.3-004 and Mailworks v1.3A, they don't have any
    eco's applied for Mailworks but at the moment I don't thing just
    upgrading is going to fix the problem.
    
    Has anyone else had any instances of sending mail from the internet
    through x.400 into Mailworks ???
    
    Thanks,
    
    Mike

T.R	Title	User	Personal Name	Date	Lines
1558.1		ZUR01::ASHG	Grahame Ash @RLE	`Wed Mar 19 1997 03:12`	10
	Hi Mike, What do you mean by "rejected by Mailworks"? Non-delivery report? Any logfile information? Can you post a dump of the message? This should certainly work. I didn't understand the comment about the content type. All messages passed to MRX should have a Content Type of 2 - the Mercury MTA has to downgrade the message if it's originally P22. grahame
1558.2		COMICS::HALFACREE	Nothing is as it seems....	`Wed Mar 19 1997 05:49`	174
	Hi Grahame, Thanks for the reply, apologies for the vagueness of the original note. To answer some of your questions, the mail message gets non-delivered and the originator gets a reason of :- Your message was not delivered to: [email protected] for the following reason: Required communication could not be effected ** The following information is directed towards the local administrator ** and is not intended for the end user * * DR generated by: /PRMD=x400gw1/ADMD=cwmail/C=gb * at 12 Mar 1997 13:15:28 +0000 Below is a copy of the message dumped :- CON_0 SET UMPDUENVELOPE MID MPDUIDENTIFIER GDOM GLOBALDOMAINIDENTIFIER COUNTRY COUNTRYNAME2 PRINTABLE PRINTABLESTRING Len = 00000002 gb %X6762 ADMIN ADMINISTRATIONDOMAINNAME2 PRINTABLE PRINTABLESTRING Len = 00000006 cwmail PRINTABLE PDOMSTRING Len = 00000003 net %X6E6574 IA5 MPDUIDSTR Len = 00000020 <MAPI.Id.0016.006d33322020202043 ORNAME ORNAME SEQ STANDARDATTRIBUTELIST COUNTRY COUNTRYNAME PRINTABLE COUNTRY_P Len = 00000002 gb %X6762 ADMIN ADMINISTRATIONDOMAINNAME PRINTABLE AMDNAME_P Len = 00000006 cwmail CON_2 PRIVATEDOMAINIDENTIFIER PRINTABLE PRDNAME_P Len = 00000003 net %X6E6574 SEQ DOMAINDEFINEDATTRIBUTELIST SEQ DOMAINDEFINEDATTRIBUTE PRINTABLE TYPE Len = 00000007 RFC-822 PRINTABLE VALUE Len = 00000015 lm32(a)dial.pipex.com ENCTYPES ENCODEDINFORMATIONTYPES CON_0 Len = 00000003 . . %X042000 CONTENT_TYPE BUILTINCONTENTTYPE Len = 00000001 . %X16 UACONTID UACONTENTID Len = 00000007 TEST500 PERMSGFLG PERMESSAGEFLAG Len = 00000002 .. %X0480 CON_2 SET RECIPIENTINFO ORNAME SEQ STANDARDATTRIBUTELIST COUNTRY COUNTRYNAME PRINTABLE COUNTRY_P Len = 00000002 gb %X6762 ADMIN ADMINISTRATIONDOMAINNAME PRINTABLE AMDNAME_P Len = 00000006 cwmail CON_2 PRIVATEDOMAINIDENTIFIER PRINTABLE PRDNAME_P Len = 00000005 forbo %X666F72626F CON_5 CON_0 SURNAME Len = 00000008 mccreesh CON_1 GIVENNAME Len = 00000004 john %X6A6F686E CON_0 Len = 00000001 . %X01 CON_1 Len = 00000002 .. %X00A0 MTRACE TRACEINFORMATION SEQ TRACEELEMENT GDOM GLOBALDOMAINIDENTIFIER COUNTRY COUNTRYNAME2 PRINTABLE PRINTABLESTRING Len = 00000002 gb %X6762 ADMIN ADMINISTRATIONDOMAINNAME2 PRINTABLE PRINTABLESTRING Len = 00000006 cwmail PRINTABLE PDOMSTRING Len = 00000003 net %X6E6574 SET DOMAINSUPPLIEDINFO CON_0 ARRIVAL Len = 00000011 970312145837+0000 CON_2 ACTION Len = 00000001 . %X00 SEQ TRACEELEMENT GDOM GLOBALDOMAINIDENTIFIER COUNTRY COUNTRYNAME2 PRINTABLE PRINTABLESTRING Len = 00000002 gb %X6762 ADMIN ADMINISTRATIONDOMAINNAME2 PRINTABLE PRINTABLESTRING Len = 00000006 cwmail PRINTABLE PDOMSTRING Len = 00000007 x400gw1 SET DOMAINSUPPLIEDINFO CON_0 ARRIVAL Len = 00000011 970312145841+0000 CON_2 ACTION Len = 00000001 . %X00 SEQ TRACEELEMENT GDOM GLOBALDOMAINIDENTIFIER COUNTRY COUNTRYNAME2 PRINTABLE PRINTABLESTRING Len = 00000002 GB %X4742 ADMIN ADMINISTRATIONDOMAINNAME2 PRINTABLE PRINTABLESTRING Len = 00000006 CWMAIL SET DOMAINSUPPLIEDINFO CON_0 ARRIVAL Len = 0000000D 970312150558Z CON_2 ACTION Len = 00000001 . %X00 OCT UMPDUCONTENT Len = 0000019A ..1.k...0312145837-TEST500.?`=0.a...gbb...cwmail....net0"0 ..RFC-822..lm32 (a)dial.pipex.com.311./`-0+a...gbb...cwmail....forbo....MCCREESH..JOHN....TEST50 0..0...1....Hi John ,....This is a test from Mercury Communications Ltd , to tes t your ..Intern et Domain name.....If you receive this msg can you please ..relpy to it an Thanks, Mike
1558.3		COMICS::HALFACREE	Nothing is as it seems....	`Wed Mar 19 1997 06:38`	13
	Another update I've just received from the customer after speaking to Mercury is as follows :- According to Mercury, the 1988 X.400 standard specifies a P22 bodypart content; the 1984 X.400 standard specifies a P2. They are sending us a P22 and can't downgrade to P2. As MRX is only 1984 compliant does that mean it's just passing this message through as P22 hoping that the receiving UA is able to do something with it ?? Because it's failing at DMW and not MRX. Mike
1558.4	Yes, we need to know if the P22 is a prob for MW	ZUR01::ASHG	Grahame Ash @RLE	`Wed Mar 19 1997 08:28`	12
	Mike, As you've only posted the envelope, we can't see if the content actually has been downgraded. Perhaps it is OK, and the problem is that MW can't cope with a Content Type value of 22? According to the downgrading rules (X.419 Annex B), the Content Type value should be unchanged - so Mercury may well be doing the right thing, legally. These rules are a bit of a nonsense though, as they say that the Content itself should also be unchanged. grahame
1558.5	P2 content of x409 file	COMICS::HALFACREE	Nothing is as it seems....	`Thu Mar 27 1997 05:57`	69
	Hi, I've dumped the x409 file and the P2 content is below :- CON_0 SET HEADING APP_11 IPMESSAGEID PRINTABLE PRINTABLESTRING Len = 00000017 0321153526-Test Message CON_0 ORIGINATOR ORNAME ORNAME SEQ STANDARDATTRIBUTELIST COUNTRY COUNTRYNAME PRINTABLE COUNTRY_P Len = 00000002 gb %X6762 ADMIN ADMINISTRATIONDOMAINNAME PRINTABLE AMDNAME_P Len = 00000006 cwmail CON_2 PRIVATEDOMAINIDENTIFIER PRINTABLE PRDNAME_P Len = 00000003 net %X6E6574 SEQ DOMAINDEFINEDATTRIBUTELIST SEQ DOMAINDEFINEDATTRIBUTE PRINTABLE TYPE Len = 00000007 RFC-822 PRINTABLE VALUE Len = 00000016 jpmcc(a)compuserve.com CON_2 PRIMARYRECIPIENTS SET RECIPIENT CON_0 RECIPORDES ORNAME SEQ STANDARDATTRIBUTELIST COUNTRY COUNTRYNAME PRINTABLE COUNTRY_P Len = 00000002 gb %X6762 ADMIN ADMINISTRATIONDOMAINNAME PRINTABLE AMDNAME_P Len = 00000006 cwmail CON_2 PRIVATEDOMAINIDENTIFIER PRINTABLE PRDNAME_P Len = 00000005 forbo %X666F72626F CON_5 CON_0 SURNAME Len = 00000008 mccreesh CON_1 GIVENNAME Len = 00000004 john %X6A6F686E CON_8 SUBJECT S61 S61STRING Len = 0000000C Test Message SEQ BODY CON_0 TEXT SET REPORTOIRE IA5 IA5STRING Len = 0000002B Here's another test from the net..