On Fri May 30 2014 16:38, Clint Pachl wrote:
[...]
> I still think that the "550 Invalid recipient" error isn't intuitive when a
> client doesn't have the "locality" or the credentials required by the mail
> server.
Let's see it from the rule processors point of view. With a ruleset like
yours,
> accept from local for local alias <aliases> deliver to mbox
> accept from any for domain <domains> virtual <users> \
> deliver to maildir "/var/spool/vmail/%{dest.domain}/%{dest.user}"
> accept from local for any relay
there's only one rule that applies in the "non-local" (also
"non-authenticated") case, so the ruleset is going to be reduced to:
> accept from any for domain <domains> virtual <users> \
> deliver to maildir "/var/spool/vmail/%{dest.domain}/%{dest.user}"
When this rule is being evaluated, it expands the table <domains> and
compares its content with the recipient domain from the envelope. In
your case, it was 'devio.us'. This domain is obviously not part of
your <domains> table. So, smtpd concludes it's not the destination mail
server, but it's also not allowed to try to relay it, either.
Yes, there's no distinction being made between "non-local" and
"non-authenticated" senders, because it's just the same case. How could
the server know better? Should it return something along the lines of
"if you'd authenticated yourself, I might be able to deal with your mail
differently"? Therefore, the sender (correctly) receives "550 Invalid
recipient" in both cases.
Norman
--
You received this mail because you are subscribed to [email protected]
To unsubscribe, send a mail to: [email protected]
