Doxpop - Tools for Attorneys and Public Information Researchers: How to respond if you just received an "Electronic Service Undeliverable" message.

Monday, June 15, 2020

How to respond if you just received an "Electronic Service Undeliverable" message.


If you filed a document and soon thereafter, get an email that has "Electronic Service Undeliverable" in the subject line, that means there is a problem with the recipient's e-service contact or mail system. You didn't cause the problem, but you will have to resolve it for this filing. Here's how to do it:
  1. Start by contacting the intended recipient to see if they had a temporary problem with their email server. If that was the case, you can do a “Service Only” filing to retry e-service & avoid having to resort to paper.
  2. If you are a Doxpop customer, and the first suggestion didn't help, contact us right away for help determining what the problem was.
  3. The last resort is to print & mail or fax a copy… but that’s time consuming because, in addition to the time required to mail, you now have to file an amended certificate of service
SMTP Logs

When the recipient can't figure out what the problem is, you can help them by providing their IT support staff with a copy of your SMTP Log.
To access that log in Doxpop, do this:
  1. Click on the E-Filing tab and select “My Electronic Filings”
  2. Locate the affected filing, and click on the arrow to the left of the envelope number to expand details.
  3. Click on the green “Service Info” button next to the document that was undeliverable.
  4. A list of service contacts will appear. Next to the recipient that didn’t receive service, click on the green “View SMTP Log” Button.
  5. Click anywhere within the log listing and press [CTRL]-[A] then [CTRL]-[C] to select all text and copy it to your clipboard.
  6. Paste the copied text into your message to the intended recipient’s IT support staff.
Note: Should the question ever arise, this log is also proof that timely service was attempted, and was undeliverable due to a problem with the recipient’s email server.

No comments: