🚀 go-pugleaf

If I have an address

		something!else%host.UUCP@domain

while it is ugly, and I'd rather die than generate such an address, the
assumption is that "domain" will handle what is on the right hand side and
if it generated it, it must be able to handle it. 

While all of this is ugly, it is allowed because it is on the
left of the @ sign.  There is only one way to handle the above address.
Send it to "domain" for "domain" to handle "something!else%host.UUCP" however
it wants to. It is not a question of defined or undefined.  I have no
business looking at what is clearly the localpart of the address.

The case in question was a sendmail.cf that erroneously looked at this address
and decided it should go to "something".  This is wrong.  The sendmail.cf
in question actually took the address (again, using the above example) and
changed it to

	something!else%host.UUCP<@domain>

correctly focusing on "domain" and then decided, no, there is a bang in
there so then it changed it to the erroneous:

	else%host.UUCP@domain<@something.UUCP>

Based on that, it sent it via the wrong transport to the wrong host.  The
corrected sendmail.cf that I sent fixed this problem.

The point is that anything to the left of the @ is up to the host to the
right of the @ to handle.  You -- and the ultrix sendmail.cf shipped with
the product -- are breaking the rules.  You are peaking.  No peaking allowed.