Question re extension unpublished without prior email warning

[KianWilliam]

To whom it may concern:
I had a message from JED claiming the assigned extension: searchcustomhtml is unpublished due to the broken links,
I checked all links and no such event in my site.
I know the checking is done by software , maybe the server to my site was down while checking, but in any case
they usually send an email in regard with a broken link before unpublishing an extension, yet they didn't.
The extension is unpublished now and I just updated the extension after checking all the links.

[toivo]

The topic was moved to the subforum extensions.joomla.org - Feedback/Information.

It seems to be this extension: Searchcustomhtml. You need to raise a ticket with the JED team, AFAIK.

[webgobe]

The emails are sent out by a bot, which is works. The past month I received 4 such mails myself, the latest on 4th November. Probably some of mails are landing in various spam boxes, (server or personal/local ones). And the bot is... a piece of software. IF for some reason the URL listed in the JED entry does not respond with a valid status code, then is considered automatically a broken link. It is not enough to visually check the URL entered in the entry - you must check it to see if clicking on it leads you to the proper page. And yes, s**t happens. When the bot crawles the URLs there might be communication errors. Anyway, the delisting DOES NOT happen based on an isolated, one time check. The URL's found to be broken are re-checked, and the delisting happens only when the problem is (automatically) confirmed. So, if the URL's reported in these mails are falsely reported as being broken you can stay safe - if on the next crawl they are working, the threat is lifted.

[KianWilliam]

I always check spam folder and no such email, I open a ticket when I have time

[webgobe]

Check this first, and post there, if you think that the email wasn't sent to you:
https://github.com/joomla/jed-issues/issues
The technical issues such this one are examined and eventually fixed by the JED Dev team. I don't even have access to that bot which is responsible for this process.