I have done some scripting and discovered an indescrepancy/failure to fully adhere to RFC rule in the MESSAGE object.
RFC822 says ofr the FROM: field:
However, using scripting, it is possible to actually create an email that does NOT have a proper formatted email address in the FROM field, and can simply contain a narrative name.This field contains the identity of the person(s) who wished
this message to be sent. The message-creation process should
default this field to be a single, authenticated machine
address, indicating the AGENT (person, system or process)
entering the message. If this is not done, the "Sender" field
MUST be present. If the "From" field IS defaulted this way,
the "Sender" field is optional and is redundant with the
"From" field. In all cases, addresses in the "From" field
must be machine-usable (addr-specs) and may not contain named
FROM: Joe Bloggs (not allowed)
FROM: Joe Blogss <firstname.lastname@example.org> (correct format)
In normal circumstances compiling the script should error if this was attempted. (By contrast the Microsoft CDO does exactly that if the format is incorrect as it will not allow this field to be without a full address).
If anyone wants to log it with the developers then maybe thats a good idea (I am not able to from my location).
Script to reproduce if required:
Code: Select all
HMSADMIN = "Administrator" HMSPWD = "password" Set oApp = CreateObject("hMailServer.Application") Call oApp.Authenticate(HMSADMIN, HMSPWD) BodyMsg = "Some body text etc" Set Message = CreateObject("hMailServer.Message") Message.FromAddress = "email@example.com" Message.From = "Housekeeping process" Message.AddRecipient "Joe Bloggs", "firstname.lastname@example.org" Message.Subject = "Housekeeping info" Message.HTMLBody = BodyMsg Message.Save