I put together some pretty ugly hack. Here's what I've done - Jenkins is configured to send emails to docker0 host address (172.17.42.1) - host sendmail is now bound to 172.17.42.1 and loopback. - sendmail relay is limited to only localhost and 172.17 network. The rest of incoming traffic will be rejected to prevent the spammer from using us as a relay
This seems to be working just fine, except the the emails are coming from a noone.nowhere place, but that's crappy JavaMail client not being properly configured. It can be dealt with by installing some additional plugins to Jenkins, or something like this. Please chime in if you know any better - that'd be great! Thanks, Cos On Sat, Feb 06, 2016 at 07:33PM, Konstantin Boudnik wrote: > Thanks! I believe it should be pretty trivial - all we need is to forward > port 25 of the Jenkins container to the host's SMTP port. > > Cos > > On Sat, Feb 06, 2016 at 10:07PM, Ashish Singh wrote: > > Hi Cos, > > > > Let me know if you need any help over here. > > > > On 2/6/16, 10:25 AM, "[email protected] on behalf of Roman Shaposhnik" > > <[email protected] on behalf of [email protected]> wrote: > > > > >On Fri, Feb 5, 2016 at 11:40 PM, Konstantin Boudnik <[email protected]> > > >wrote: > > >> I've looked at it a bit more and I think our best bet here is to allow > > >> Jenkins > > >> to use host's MTA, which is already configured and should work just > > >> fine. This > > >> way, we aren't going to rely on anything 3rd party. Thoughts? > > > > > >Sounds reasonable to me. > > > > > >Thanks, > > >Roman. > > >
signature.asc
Description: Digital signature
