feat(seo): IIS SMTP relay dostaje wlasna strone, za jedynym sygnalem jaki mamy - #251

…h signal we have

Search Console produced its first data today: eight clicks in three weeks, and
one page moving on its own - WINDOWS-SERVER.html, impressions up 107%. Two of
fifty-three pages on this site touch Windows at all, and one of them is the one
Google is pushing.

That page buries four distinct searches in one document: an app pointed
straight at the relay, PowerShell and Task Scheduler, an Exchange Send
Connector, and the IIS SMTP relay. This project's own position, written into
tools/build-error-pages.py and proved by seventeen error pages, is that a page
covering many things loses each of them to a page covering one.

IIS goes first because it is the largest legacy install base and had the
thinnest treatment - thirteen lines for a component Microsoft has not supported
since 2008 and which a great deal of Windows software still delivers to. The
usual advice, reconfigure the application, is useless when the application is a
vendor binary whose only mail setting is "deliver to local SMTP server". That
case deserves a straight answer rather than a suggestion to rewrite software
somebody does not own.

The page leads with how this fails rather than how to configure it, because the
failure is the part nobody sees: IIS keeps accepting mail on localhost exactly
as before, the smart host refuses it, and messages pile up in Queue and Badmail
with no alert of any kind. The first symptom is somebody noticing a report
stopped arriving weeks ago. Both directories are named, because checking them
is the honest test and is worth scheduling whichever option is taken.

The three options are stated with what each costs, including that mail through
this relay leaves from a generated address rather than the customer's own
domain - which rules it out for customer-facing mail and is said before the
configuration table rather than after it.

Linked from the section it was split out of and from the triage table on the
homepage, so it does not repeat this week's mistake of shipping a page nothing
points at.