RE: [Mimedefang] Security note: Open port 25 on internal mail se rvers

2004-02-05 Thread Stephen Johnson
On Wed, 2004-02-04 at 23:47, Justin wrote: > relay (which the FBI later confiscated), and an AIX machine that was an > open relay. I knew where the first two groups were but didn't know where Just FYI, all AIX servers are open relays out of the box. IBM unbelievably uses FEATURE(`promiscious_rela

RE: [Mimedefang] Security note: Open port 25 on internal mail se rvers

2004-02-04 Thread Justin
On Wed, 4 Feb 2004 [EMAIL PROTECTED] wrote: > In fact, relay-test all your machines that listen on port 25 as a > matter of habit. I happened to relay check our entire campus once back when I first started my previous job. I found an entire lab of around a dozen SGI's that were of course open

RE: [Mimedefang] Security note: Open port 25 on internal mail se rvers

2004-02-04 Thread Kelson Vibber
At 04:16 PM 2/4/2004, [EMAIL PROTECTED] wrote: One SMTP server (A) that accepts only authenticated sessions and allows relay for those. Another SMTP server (B) that accepts any session but does not allow relay. The trick is to only have A listed as an MX record. B does *not* need to be listed as a

RE: [Mimedefang] Security note: Open port 25 on internal mail se rvers

2004-02-04 Thread Matthew . van . Eerde
> From: Lucas Albers [mailto:[EMAIL PROTECTED] > David F. Skoll said: > > 3) Even if you don't have MX or A records pointing to internal mail > > servers, you should firewall off port 25 on internal mail > servers from > > the outside world. We've seen instances of the MyDoom > virus bypassing >

RE: [Mimedefang] Security note: Open port 25 on internal mail se rvers

2004-02-04 Thread Matthew . van . Eerde
> From: Matthew.van.Eerde ... > We use this same setup. > > One SMTP server (A) that accepts only authenticated sessions > and allows relay for those. > Another SMTP server (B) that accepts any session but does not > allow relay. > > The trick is to only have A listed as an MX record. B does