Is there a max length for the address fields in the Email Block of an Advanced Printing, Break/Routing?
Sys Monitor reports the following error when this style is used.
Program Ice.Services.Lib.RunTask raised an unexpected exception with the following message: RunTask: The parameter 'address' cannot be an empty string.
If I delete the last address off of the CC field (It’s a static list, not an inserted field), it works.
Length of CC field when it fails: 193
Length when it works: 173.
I copied the CC text and viewed with with a Hex viewer to make sure there wasn’t some odd chars. Nothing outside of the normal ascii range.
That’s what we’ll probably do. Easier to maintain too, as many people in the IT groups know how to manage Exchange based groups. Very few (I.E. just me) know how to edit an E10 Report Style Break/Routing design.
But it would be nice to know if there is an actual limit. Not just address fields but for subject, attachment name, and body too.
I remember at least one time where I couldn’t use a distribution group and I ran into that limit too.
I was able to get around it by spreading addresses across “To” and “CC”.
In Breaking / Routing designer, I would enter E10_Order_Ack@test.com, or just E10_Order_Ack?
Even though the source email isn’t from a verified account (we don’t have E10 setup for authentication), the exchange server will process the group name and forward the message on to the members?
Or does using groups require more than the anonymous setup of specifying a mail server and port?
If you’re doing anonymous send to your Exchange server (which is what I do, limited to certain internal IP addresses), then when you setup a new Distribution group you need to remember to set it so that delivery is allowed to that group from OUTSIDE as well as internal senders – Exchange is seeing the email as external when received anon.
We discovered that distribution lists were not flowing at a site due to email server security setup.
There was a 3rd party Exchange admin. who only managed to allow individual email addresses to flow from Vantage. (addresses for the internal domain only and distro lists would still fail).
Temp workaround was to use the individual addresses.
And that is when I discovered there issues if too many addresses were used.