OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Wietse Venema (wietse_at_porcupine.org)
Date: Mon Sep 02 2002 - 13:07:45 CDT

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    John Peach:
    > > And, did you see any light after doing some how work?
    >
    > He never called me back on Friday - I'm not going to attempt to troubleshoot
    > something without having *some* idea of whats going on at the far end.
    > I did some research on IDS - I asked our firewall guys :-) As far as I can see
    > IDS can have nothing to do with this; he must have some kind of firewall as
    > well (maybe a PIX, although he told me otherwise).
    >
    > I have looked fairly closely at some of my logs and it looks like there may
    > well be some kind of configuration which will not talk to a postfix server - I
    > can see a fair number of IPs which do nothing more than connect, then
    > disconnect.

    Not to sound hostile, but isn't it a bit premature to announce on
    a public list that Postfix cannot talk to some software?

            Wietse

    > If and when this guy gets back to me, I'll snoop the traffic and see if that
    > tells me anything more interesting......
    >
    > >
    > > Wietse
    > >
    > > John Peach:
    > > > I know there is a potential problem with postfix living behind a PIX at
    > > > certain software revisions.
    > > > I have a client who has a mickeysoft implementation behind an IDS (Post.Office
    > > > v3.5.3 release 223 ID# 0-54203U100L2S100V35). I don't yet know what release is
    > > > on the IDS.
    > > > The symptoms are that he can make a connection to a postfix server and the
    > > > connection drops immediately. I have confirmed this behaviour by having him
    > > > email my home address and exactly the same thing happens (that is running
    > > > 1.1.11-20020819 and at work I have 1.1.7). I had him send to an email address
    > > > I have which runs sendmail and it worked fine. It appears to be just postfix
    > > > where this happens.
    > > > Before I get down to running snoop and trying to decipher the packet
    > > > information, has anyone else seen this kind of behaviour? I'm hoping that it's
    > > > a Cisco problem which a software upgrade will fix......
    > > >
    > > >
    > > >
    > > > -
    > > > To unsubscribe, send mail to majordomopostfix.org with content
    > > > (not subject): unsubscribe postfix-users
    > > >
    > > >
    > >
    > > -
    > > To unsubscribe, send mail to majordomopostfix.org with content
    > > (not subject): unsubscribe postfix-users
    > >
    >
    >
    >
    > -
    > To unsubscribe, send mail to majordomopostfix.org with content
    > (not subject): unsubscribe postfix-users
    >
    >

    -
    To unsubscribe, send mail to majordomopostfix.org with content
    (not subject): unsubscribe postfix-users