Table: Enhanced list troubleshooting
| Problem |
Cause |
Solutions |
| Subscribers complain that they cannot
reply to messages received from an enhanced list. |
Message was sent to an enhanced-list that did not permit Reply
to Sender. |
- Administer the enhanced-list to
allow Reply to Sender, if appropriate.
- Educate your subscribers about ELA
functionality.
|
| Community IDs for the sender or
recipient incorrectly administered. |
Administer Community IDs for sender
or recipient, if appropriate. |
| Subscribers complain of getting multiple copies of the same
message. |
Recipient is on more than one list. |
- ELA does not check nested lists
to verify if the same name appears in more than one place.
Print out a copy of your enhanced-lists and remove duplicates,
if possible.
- Educate your subscribers about ELA
functionality.
|
| You inadvertently deleted the shadow mailbox. |
— |
ELA raises a warning alarm. Any messages waiting in the delivery
"queue" are lost.
Recreate the shadow mailbox and
then verify the shadow extension on the Configure ELA page
and click Save.
|
| Recipient reports that she or he did
not get an ELA message. |
Mailing list not current. |
Check the mailing list for the recipient's name. Administer,
if necessary. |
| Subscriber's mailbox not administered
correctly. |
- Check the Activity Log to verify
that the subscriber did not receive the message.
- Check the Subscriber screen for
the affected subscriber. Look at the Mailbox Size. Put the
subscriber in a COS with a larger mailbox, if necessary.
- Check the List Measurements Subscriber
Day screen for the affected subscriber. Look at the available
mailbox space. Advise the subscriber to delete unneeded
messages and greetings, if appropriate.
- Check that Community ID is correct.
|
|
System delivery failure.
|
System delivery failures can arise
from many sources.
|
| Sending Restrictions not consistent across machines. |
Administer the same Community IDs and sending restrictions
for all networked messaging systems. |
| The name of an enhanced-list member keeps disappearing from
enhanced lists. |
System feature to delete nonadministered remote subscribers
is active. |
- From Messaging command prompt, enter
ch�sys�fe. Access page 4 and change the Even if on
Mailing List? field to n.
- Readminister the remote subscriber.
|
| Subscribers complain that they cannot send a message to an
enhanced-list mailbox. |
Subscriber belongs to a community with sending restrictions
administered. |
Consider whether to change this subscriber's community ID
to allow the subscriber to use enhanced lists. |
| Recipient asks why he or she received
the message from the enhanced-list much later than other recipients.
|
Subscriber mailbox is full. |
Check the List Measurements Subscriber Day screen for the
affected subscriber. Look at the available mailbox space. Advise
the subscriber to delete unneeded messages and greetings, if
appropriate, or consider putting the subscriber in a COs with
a larger mailbox. |
| Enhanced list was very large. |
Remember that ELA slows traffic
during periods of heavy user traffic. Inform the subscriber
that message delivery to a large recipient population does take
time. |
| Networking problems between originator
system and recipient system. |
Perform networking troubleshooting.
See Troubleshooting for more information.
|
| You inadvertently delete an enhanced-list. |
— |
There are two ways to restore an enhanced list:
- Re-enter the names on the list.
- Restore the data from the previous
night's backup.
Warning!
There is no way to selectively restore only enhanced-lists
from backup data. Your system will lose all incremental
administration data from the point of backup. Use this method
only if you are sure the business can tolerate the loss
of recent administration.
|
