After talking to Kohsuke, it was clear that it never worked that way. That is, the code was never written to append default suffix to recipients (without the suffix). The recipients are supposed to be "users" in the system and as such their email addresses are derived separately. So, what this bug turns out to be is an enhancement request in that if the default suffix is provided and recipients' list contains a stray email address, then the email address should be formed by concatenation.
Just curious – you said you were able to see this working like you say – i.e. email was sent to recipient.default-suffix. Do you remember which version it was, and more importantly that your mail server did not alias the email address you sent it to? (e.g. "joe" is not an invalid email address if your mail server aliases it to joe@somedomain).
After talking to Kohsuke, it was clear that it never worked that way. That is, the code was never written to append default suffix to recipients (without the suffix). The recipients are supposed to be "users" in the system and as such their email addresses are derived separately. So, what this bug turns out to be is an enhancement request in that if the default suffix is provided and recipients' list contains a stray email address, then the email address should be formed by concatenation.
Just curious – you said you were able to see this working like you say – i.e. email was sent to recipient.default-suffix. Do you remember which version it was, and more importantly that your mail server did not alias the email address you sent it to? (e.g. "joe" is not an invalid email address if your mail server aliases it to joe@somedomain).