Andrew Falanga wrote:
> ...
> While diagnosing this, I connect to the server (using Putty) from a
> machine in PN1, using either a mail client or telnet I'm unable to make
> a connection to the mail server over port 25. Using tcpdump during this
> putty session I do not even see the SYN packets fo
Andrew Falanga wrote:
Clients in the churches private network cannot send mail using this
server, though they can receive mail from it (POP). The church has a
private network, PN1, and the mail server sits at a church members house
because he has a static IP address; let's call that PN2. The
Sahil Tandon wrote:
Andrew Falanga <[EMAIL PROTECTED]> wrote:
It doesn't take a rocket scientist, or a computer scientist, to
figure out we've got DNS issues.
What exactly is the problem though? What problems are you having on
the mail server that lead you to the above conclusion?
George Davidovich wrote:
On Sat, Sep 06, 2008 at 07:28:28PM -0600, Andrew Falanga wrote:
Well, my clients at church are still having issues and after working with
George, a respondant to my original questions, I think that most, if not all,
of my problems are related to DNS and how we've got
Patrick Mahan wrote:
Andrew Falanga presented these words - circa 9/6/08 6:28 PM->
Hi,
Well, my clients at church are still having issues and after working
with George, a respondant to my original questions, I think that
most, if not all, of my problems are related to DNS and how we've got
Andrew Falanga presented these words - circa 9/6/08 6:28 PM->
Hi,
Well, my clients at church are still having issues and after working with
George, a respondant to my original questions, I think that most, if not all,
of my problems are related to DNS and how we've got it improperly configur
Andrew Falanga wrote:
*Not having* a reverse entry for a mail server is often
the cause of issues.
This I do know very well. I had similar problems when running a sendmail
backup spooler for Syracuse Networks back in 2000. The eventual solution was
that our ISP delegated control of our sub
On Sat, 6 Sep 2008 19:28:28 -0600
Andrew Falanga <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Well, my clients at church are still having issues and after working
> with George, a respondant to my original questions, I think that
> most, if not all, of my problems are related to DNS and how we've got
> i
On Sat, Sep 06, 2008 at 07:28:28PM -0600, Andrew Falanga wrote:
>
> Well, my clients at church are still having issues and after working with
> George, a respondant to my original questions, I think that most, if not all,
> of my problems are related to DNS and how we've got it improperly config
--On September 6, 2008 7:28:28 PM -0600 Andrew Falanga
<[EMAIL PROTECTED]> wrote:
Hi,
Well, my clients at church are still having issues and after working
with George, a respondant to my original questions, I think that most,
if not all, of my problems are related to DNS and how we've got it
Andrew Falanga <[EMAIL PROTECTED]> wrote:
> It doesn't take a rocket scientist, or a computer scientist, to
> figure out we've got DNS issues.
What exactly is the problem though? What problems are you having on
the mail server that lead you to the above conclusion?
--
Sahil Tandon <[EMAIL PR
Andrew Falanga wrote:
Hi,
Well, my clients at church are still having issues and after working with
George, a respondant to my original questions, I think that most, if not all,
of my problems are related to DNS and how we've got it improperly configured.
First, a crude drawing of how our ma
Hi,
Well, my clients at church are still having issues and after working with
George, a respondant to my original questions, I think that most, if not all,
of my problems are related to DNS and how we've got it improperly configured.
First, a crude drawing of how our mail server exists in the w
13 matches
Mail list logo