Mail resolver failures

[slide]

Several users of email-ext have reported issues with email resolution
([1], [2], [3], [4]). I am looking for ways to mitigate these
problems, but I am not sure what to do. I was considering adding an
option to blacklist mail resolvers, but I don't think that is very
user friendly. Anyone have any ideas? The email-ext is using the
Mailer API's email resolution to resolve email addresses, so this is
something that would be seen in the default Mailer as well.

slide

[1] - https://issues.jenkins-ci.org/browse/JENKINS-12577
[2] - https://issues.jenkins-ci.org/browse/JENKINS-13715
[3] - https://issues.jenkins-ci.org/browse/JENKINS-13700
[4] - https://issues.jenkins-ci.org/browse/JENKINS-13102

--
Website: http://earl-of-code.com

[kohsuke Kawaguchi (CB)]

I think we should (1) fix those issues in the respective plugins
(perforce and active-directory), and (2) improve core so that even if a
MailAddressResolver throws an exception, it shouldn't swallow it and
move on.

I'll make the #2 change in the core.

On 05/29/2012 01:40 PM, Slide wrote:

> Several users of email-ext have reported issues with email resolution
> ([1], [2], [3], [4]). I am looking for ways to mitigate these
> problems, but I am not sure what to do. I was considering adding an
> option to blacklist mail resolvers, but I don't think that is very
> user friendly. Anyone have any ideas? The email-ext is using the
> Mailer API's email resolution to resolve email addresses, so this is
> something that would be seen in the default Mailer as well.
>
> slide
>
> [1] - https://issues.jenkins-ci.org/browse/JENKINS-12577
> [2] - https://issues.jenkins-ci.org/browse/JENKINS-13715
> [3] - https://issues.jenkins-ci.org/browse/JENKINS-13700
> [4] - https://issues.jenkins-ci.org/browse/JENKINS-13102
>

--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins

[slide]

I assume you mean it _should_ swallow the error and continue? I'll look
at the perforce and AD plugins and see if I can find anything. Is there
anything I can do in the email-ext plugin?

Sent from my Windows Phone
From: Kohsuke Kawaguchi
Sent: 5/29/2012 5:58 PM
To: [hidden email]
Cc: Slide
Subject: Re: Mail resolver failures

I think we should (1) fix those issues in the respective plugins
(perforce and active-directory), and (2) improve core so that even if a
MailAddressResolver throws an exception, it shouldn't swallow it and
move on.

I'll make the #2 change in the core.

On 05/29/2012 01:40 PM, Slide wrote:

> Several users of email-ext have reported issues with email resolution
> ([1], [2], [3], [4]). I am looking for ways to mitigate these
> problems, but I am not sure what to do. I was considering adding an
> option to blacklist mail resolvers, but I don't think that is very
> user friendly. Anyone have any ideas? The email-ext is using the
> Mailer API's email resolution to resolve email addresses, so this is
> something that would be seen in the default Mailer as well.
>
> slide
>
> [1] - https://issues.jenkins-ci.org/browse/JENKINS-12577
> [2] - https://issues.jenkins-ci.org/browse/JENKINS-13715
> [3] - https://issues.jenkins-ci.org/browse/JENKINS-13700
> [4] - https://issues.jenkins-ci.org/browse/JENKINS-13102
>

--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins