Skip to Main Content

Application Development Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

postmaster delivery notification

807574Jul 31 2007 — edited Feb 10 2020
Hi all,

While i send the meeting requests to users, though the meeting requests get updated in the attendees' calendars i get a postmaster delivery notification mail in my inbox. Also, my calendar too gets updated when i raise a meeting request.

The reason i get in the postmaster delivery notification mail is:
"Illegal host/domain name found".

Please let me know if anybody had got this error earlier and how to get rid of it.

Regards,
lmeenakshy

Comments

807574
Hi,

Sounds like one of the recipients of the meeting, whether that be a resource or a user has an invalid mail: attribute or perhaps the user is forwarding to another address at that is invalid.

You will need to investigate further into the actual address the email was destined for and track down which of the recipients this may correspond to.

Without actually providing the full postmaster delivery notification message (including all headers) there isn't much more I can offer - please note that this may not be appropriate to include in the forum so perhaps you should raise a sun support request.

Regards,

Shane.
807574
Hi Shane,

Here are the contents of the postmaster delivery mail.
This report relates to a message you sent with the following header fields:

Message-id: <0JM400303VD94N00@lavanya.spanservices.com>
Date: Thu, 02 Aug 2007 11:59:18 +0530
From: John Doe <jdoe@spanservices.com>
To: demo2@spanservices.com, Demo5@spanservices.com
Subject: outing

Your message cannot be delivered to the following recipients:

Recipient address: @lavnaya.spanservices.com:demo2@spanservices.com
Original address: demo2@spanservices.com
Reason: Illegal host/domain name found

Here are the contents in the attatched notepad alongwith the mail
Return-path: <jdoe@spanservices.com>
Received: from tcp_intranet-daemon.lavanya.spanservices.com by
lavanya.spanservices.com
(Sun Java(tm) System Messaging Server 6.3-0.15 (built Feb 9 2007))
id <0JM400301VDDZ800@lavanya.spanservices.com>; Thu,
02 Aug 2007 11:59:38 +0530 (IST)
Received: from Leena.spanservices.com ([10.10.20.127])
by lavanya.spanservices.com
(Sun Java(tm) System Messaging Server 6.3-0.15 (built Feb 9 2007))
with ESMTP id <0JM400302VD94N00@lavanya.spanservices.com> for
demo2@spanservices.com (ORCPT demo2@spanservices.com); Thu,
02 Aug 2007 11:59:35 +0530 (IST)
Content-return: prohibited
Date: Thu, 02 Aug 2007 11:59:18 +0530
From: John Doe <jdoe@spanservices.com>
Subject: outing
To: demo2@spanservices.com, Demo5@spanservices.com
Message-id: <0JM400303VD94N00@lavanya.spanservices.com>
MIME-version: 1.0
X-Mailer: Sun Outlook Connector 7.2.310.1
X-MSReally-From: jdoe@spanservices.com
x-cdsi-MAPIMsgClass: IPM.Schedule.Meeting.Request
X-Sun-calendar-msg: REQUEST


Please see if you can give any more suggestions on this issue.

If anybody else has had the same problem ,please let me know.

Regards,
lmeenakshy
807574
Hi,

The problem is very subtle. The address you are attempting to send to is built up of the users mailhost: attribute (the user being the account which has the mail: attribute of demo2@spanservices.com) and their address:

@lavnaya.spanservices.com:demo2@spanservices.com

Note that the mailhost you are attempting to send to is "lavnaya" whereas from the header information the host is actually called "lavanya" (note how the "an" characters are reversed). Messaging server tried delivering to this invalid mailhost and it was unable to resolve the IP address - so the email bounced.

If you correct the mailhost: attribute for demo2 user this problem should be fixed. You may also want to work out how this user managed to get provisioned with the incorrect mailhost: attribute - if you used the DA GUI you may have incorrectly set a default mailhost: for the domain so this problem could also be occurring for other users.

Regards,

Shane.
1 - 3
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Aug 30 2007
Added on Jul 31 2007
3 comments
103 views