Unknown is converted to error in cache

[adamlui]

in https://github.com/KudoAI/chatgpt.js/blob/1862d820cb94a18cfdf0d434ec851628d83a9285/docs/de/README.md

job https://github.com/KudoAI/chatgpt.js/actions/runs/23699285166/job/69039999485

Email deliveres fine, is handled by Cloudflare (fwds showcase@chatgptjs.org => adamlui@protonmail.com)

[thomas-zahner]

Thank you for reporting. There are two things going on.

1. The mail address cannot be reliably checked. Resulting in UNKNOWN.
2. The previously stored UNKNOWN result is retrieved and now reported as error.

The first issue might be a bug, but it might also be due to the mail server simply rejecting our request, related to the state of SMTP. I'm not yet entirely certain which is why I've opened up thomas-zahner/mailify#3.

Checking the mail address on my machine with lychee looks like this:

echo 'showcase@chatgptjs.org' | lychee - --include-mail -v

 [UNKNOWN] mailto:showcase@chatgptjs.org | Unknown mail status: Unclassified negative SMTP response: 5.5.2 Syntax error: failed to generate postmaster address. rJY4y7UEMJNM

The second point is a more obvious issue. lychee should definitely not report an "unknown" status as error when it is stored to the cache and then loaded from the cache again. This is a bug we should investigate more closely. This is why your first run didn't report the mail address as error but showed 16 unknown results. But the second run then erroneously reported every address as error, even though it should have reported it as unknown.

I've renamed the issue in order to track lychee's bug. (the second case) The first case is tracked via thomas-zahner/mailify#3.

[thomas-zahner]

Ah I've now just tested this on master and realised that this was just fixed with the latest commit, which is quite a funny coincidence. It was fixed via #2105 this hasn't been released yet.

But there might still be something wrong, because this means that Unknown is converted to CacheStatus::Error. Is this correct behaviour @mre?

[mre]

But there might still be something wrong, because this means that Unknown is converted to CacheStatus::Error. Is this correct behaviour @mre?

This is probably not correct, you're right.

[adamlui]

It happened to adam@elonsucks.org too (also handled by Cloudflare redir to adamlui@protonmail.com) https://github.com/elonsucks/why.elonsucks.org/actions/runs/23771818083/job/69264816349