WiscList - Known Issues and Limits
This document details known issues and possible workarounds regarding WiscList. Note that issues listed below apply to WiscList, AdvisorList, Classlist (aka Classlist Utility) and WiscList Custom.
Mailing List Issues
WiscList will send a notification to list owners if there are no immediate recipients found for a sent mailing.
The warning message will look like this:
Your message was successfully distributed to list 'listname'.
However, no immediate recipients were found for your mailing.
You are receiving this message because the list is configured to
send a warning message to the sender when no active recipients are
found for a posting.
No immediate recipients will be found if one of the following is true:
There are no members in the list.
The mailing was sent to multiple lists, and all the members of one list are members of another list. For example: Consider the following two lists and their members:
List A: John, Joe, Drew, Bob, Bill
List B: John, Joe, Drew
If a mailing is sent to both List A and List B simultaneously (a.k.a. cross-posting), WiscList will see that John, Joe, and Drew already received a copy of the mailing on List A and will not send to them on List B. WiscList discovers that there are no more people left on List B to e-mail, so it sends out a courtesy notice to the list owner.
To allow mailing multiple lists, please follow the instructions in the following document: WiscList (Advanced) - Sending the Same Message to Multiple Lists (Cross-Posting).
If a list appends a footer to its messages and a message is posted with a large file attachment, it has been reported that the message's footer (containing unsubscribe information) becomes malformed. More specifically, the mail merge tags are not properly interpreted. To fix this issue, rewrite the footer to not include any mail merge tags. Mail merge tags have double percent signs (%%) surrounding them. This can be done from the list page in WiscList Admin.
When a message has been digitally signed, the list-configured footer is left off of the message even if the list has been configured to always include one.
When digitally signing a reply or forward where the following conditions are true:
- The mailing was not digitally signed.
- The list makes use of footers with mail merge tags.
The digital signature can sometimes be invalidated. Testing indicates the behavior is reproducible when the footer from the original message finds its way into the body of the reply or forward. This can happen when the original is broken into pieces for the purpose of addressing certain sections of the original individually.
If your list is going to be receiving heavy traffic with PKI attachments, we suggest that you create a custom footer to override ListManager's default. This can be done by composing a footer in Utilities > List Settings > E-mail Submitted Content > Footer.
In an effort to prevent the negative impacts of mailing loops, WiscList imposes a limit of 300 messages with the same To-From address combination within a 24 hour period. Once a list has exceeded this limit, further messages will not be delivered. Contact email@example.com for assistance.
WiscList imposes a limit of 5MB per message. Note that message size includes the size of any attachments. Encoding increases the size of the message up to 7mb which we allow. If you need to share a large file with members of your list, we recommend that you instead use a file hosting service like UW-Madison Box and direct your list members to download the file individually.
Other popular file hosting services include:
For security purposes, WiscList will not notify a non-member that their message was rejected. Administrators can check the incoming mail queue (Mailings > Mailing Status > Mail Queues > Mail Queue - Incoming) for rejection notices.
There is an issue with WiscList's underlying software causing calendar invites to be changed slightly in processing. O365 doesn't like this change and drops the calendar invite completely. The vendor is working on a fix for this issue. This problem occurs when 2 different things are happening:
- If a footer is present. The current workaround is to remove the footer completely which can be done from the list page in WiscList Admin.
- If O365 'encodes' the message. It isn't known when O365 decides to do this, but the only way to avoid it for sure is to leave the body of the invite blank. It may work with some text in it, or it may not.
IE/Edge are not supported at this time for HTML viewing. Other modern up to date browsers should work normally.
When Microsoft Excel on Mac exports a CSV file it does so with non-standard encoding. ListManager does not support this encoding for importing. In order get around this issue select 'MS-DOS Comma Separated' when saving the file.