That's the reason and I actually emailed that to the list last night. Doesn't
seem to have gotten here. This is what I posted:
The RFC for a message-id is to have it alone the same line as an email address.
In cases where a message arrives without a message-id, I accept it and then
create a message-id for it using a UUID. In order to make it RFC compliant, I
just added the text @houseoffusion.com to the end of the UUID. Should solve the
problem.
If I was really strict, I'd force all mail to the HoF server to have a proper
message-id. It's still an idea.


Could the messageid be rejected because the servers are looking for a domain
name at the end of the id? I think I ran into that problem before. You may want
to try <[EMAIL PROTECTED]>


-----Original Message-----
From: Howie Hamlin [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 17, 2003 4:39 PM
To: inFusion Support List
Subject: Re: [iMS] message-id errors


Looks valid to me...I have no idea why it's being rejected.

Regards,

Howie

----- Original Message -----
From: "Michael Dinowitz" <[EMAIL PROTECTED]>
To: "inFusion Support List" <[EMAIL PROTECTED]>
Sent: Monday, February 17, 2003 1:25 PM
Subject: [iMS] message-id errors


> I'm getting a few bouncebacks from some mail servers with a message of an
> invalid message-id (or invalid header id for the same message). This is the
> message-id:
> Message-ID: <A15624E3-EAAB-4C5C-943F849E0C425CFE>
> According to what I know, this is valid. Is there something I'm missing?
>
> Michael Dinowitz
> Master of the House of Fusion
> http://www.houseoffusion.com
>
==^=======================================================
     This list server is Powered by iMS
   "The Swiss Army Knife of Mail Servers"
   --------------------------------------
To leave this list please complete the form at 
http://www.coolfusion.com/iMSSupport.cfm
Need an iMS Developer license?  Sign up for a free license here:
http://www.coolfusion.com/iMSDevelopers.cfm
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
Note: You are subscribed as [email protected]
==^=======================================================


Reply via email to