I have not had any success in using a format like that. It's not a valid email. However, one workaround that I like to use, because most 'systems' don't allow this kind info-stuffing, is to use Google Groups. Create a group, have as a member the email you actually want it to go to. Include with the group a Subject Tag (Something like <FMSA12 My Office Rack 2>. When that email comes through, it will be labeled with the subject like: <FMSA12 My Office Rack 2> Email Subject Line.
Perhaps I am already hung over but I think this Google Groups goes the opposite way I need. I want to have each FileMaker Server have an Identifiable Name as part of the e-mail when it arrives in a "catchall" email address. The catchall e-mail address is the transport mechanism for this type of notification which is used mostly for troubleshooting and went an Error message is thrown the e-mail goes to PageDuty and then to the sysadmin on duty.
I note that I am able to do this tagging with FileMaker Server 12. It was/is a little harder in 11 and at various points in the history of server it has worked without a probably.
I well reread your post later..... thanx for the suggestion....
What happens if you add the fully resolved name into your address book? That should cause it to display properly in the mail client.
After I re-read the original I realized that probably wouldn't work. Ignore me. I'm sick.
Separate group for each server. That will give you a different email address for each server...which is delivered to the same address with the Subject tagged for the server.
Perhaps I am not see the method .... Not having used google for mail ( yet )
What does the Google group allow one to trigger on? Can it use the long headers and use the actual source IP ( not the gateway IP which is likely a NAT gateway which is not the true location. ) If I could use the FQDN of the helo=FQDN==FMSA12-My-Office-Rack-2.mydomain.private then I could use this method.
You could right say to me: "LMGTFY" but with a please and for the benefit of other here, could provide an example of what is possible .....
Here is a sample of the Long Headers of test message generated by a FileMakerServer 12.... (Note the e-mail labels do work in this case )
Reply-To: VMW-MacPro-MLS-FMSA12-86 <firstname.lastname@example.org>
Delivery-Date: Tue, 31 Dec 2013 23:34:54 -0500
Received: from mx2.myEmailprovider.net ([18.104.22.168]) by mail.myEmailprovider.net with esmtp (Exim 4.77) (envelope-from <email@example.com>) id 1VyDWA-0003dl-PM for firstname.lastname@example.org; Tue, 31 Dec 2013 23:34:54 -0500
Received: from mail.myEmailprovider.net ([22.214.171.124]) by mx2.myEmailprovider.net with esmtp (Exim 4.77) (envelope-from <email@example.com>) id 1VyDWC-0006N5-Jm for firstname.lastname@example.org; Tue, 31 Dec 2013 23:34:56 -0500
Received: from a-nat-gateway.com ([126.96.36.199]:49989 helo=vmw-macpro-mls-fmsa12-86.thaijavaworks.net) by mail.myEmailprovider.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from <email@example.com>) id 1VyDWA-0003df-Ee for firstname.lastname@example.org; Tue, 31 Dec 2013 23:34:54 -0500
Content-Type: text/plain; charset=UTF-8
Thank you again.