Hi Michael
Actually, assuming your domain is get-noticed.com, your DNS is quite
severely broken:
Serial number: 13
Primary name server: server1.merchantcapitalinc.com.
Primary mail server: mail.get-noticed.com.
Total # of records: 8 (3 NS, 2 MX, 3 A, 0 CNAME, 0 PTR, 0 Other)
Errors
----------------------------------------------------------------------
o The name server "server1.merchantcapitalinc.com." is not listed in
delegation data
The server "server1.merchantcapitalinc.com." is listed as being
authoritative for the zone according to the zone data, but there
is no NS record for that server in the delegation data.
Delegation data and zone data should always match.
o There is no PTR record for the host "mail.get-noticed.com."
There is no PTR record available for the host
"mail.get-noticed.com." which has the IP address 208.165.176.99.
o There is no PTR record for the host "ftp.get-noticed.com."
There is no PTR record available for the host
"ftp.get-noticed.com." which has the IP address 208.165.176.123.
o The zone contains more than one authoritative name server with the
same IP address
The name servers "ns1.merchantcapitalinc.com." and
"server1.merchantcapitalinc.com.", which are authoritative for
"get-noticed.com.", have the same IP address (208.165.176.98).
I'd also suggest using a more descriptive method of serial number for
your SOA record. The accepted format is yyyymmdd## where yyyy would be
1999, mm would be 10, dd would be 13 and ## would be the current number
of changes made that day, so 1999101303 would indicate you had made 3
changes to the DNS on that day. This is also Y2K compliant, which is a
Good Thing (tm)
A lot of mail servers do reverse lookups on the domain sending mail, as
an anti-spam measure, despite this being at odds with current RFC
practise and recommendations. I strongly suggest fixing your DNS at your
earliest convenience.
/wiZZ
----- Original Message -----
From: Michael M. Wiseman <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: 13 October 1999 10:27
Subject: RE: [IMail Forum] delays
> Actually, very few of them fail like that
> And the reverse DNS is fine ... but I will check again
> Almost every one completes in the first pass... but it takes forever
to go
> through 1000 names
> Any reason why it just takes so darn long?
>
> "MICHAEL"
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Daniel
Donnelly
> Sent: Wednesday, October 13, 1999 4:06 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [IMail Forum] delays
>
> Mike,
>
> If 999 of the addreses are delivered in th efirst pass, having that 1
left
> could take as long as the product of your SMTP, Queue Timer * Number
of
> Tries,
> before IMail will stop trying to deliver the message. The default
values
> mean
> it will be 10 hours before IMail stops trying. Only delivery to ALL
> addresses
> will cause it to finish before that time.
>
> The log you included, show that the remote host will not accept the
message,
> because it did a reverse lookup (Sender domain must resolve) and did
not
> find
> the hostname IMail is using. That is a 'failed delivery', but IMail
will
> continue delivery attempts. This is a DNS issue you need to address
before
> mail will be accepted at the remote end.
>
> Daniel Donnelly
> Ipswitch Technical Support
> ________________________________________________________
> See our Knowledge Base at http://support.ipswitch.com/kb
>
>
> In reply to 13 Oct message from [EMAIL PROTECTED]:
>
> >Yes. Lots of lines in between.. but I didn't think you wanted me to
> post
> >them all :)
> >Log is about 500k.
> >There are quite a few retries.
>
> >Over 1000 names on the list. Should it take 2 1/2 hrs for that ? I
see
> a
> >few retries.. and some failed events
>
> >xxxx' added by me
>
> >10:12 10:33 SMTP-(00000140) Connect interaccess.com
[207.70.126.130:25]
> >(1) 10:12 10:33 SMTP-(00000140) 220 neuman.interaccess.com ESMTP
> >Sendmail 8.9.0/8.9.0; Tue, 12 Oct 1999 09:33:21 -0500 (CDT) 10:12
10:33
> >SMTP-(00000140) >EHLO xxxxxxxxxxxxxxxxxxxxx 10:12 10:33
SMTP-(00000140)
> >250-neuman.interaccess.com Hello [xxx.xxx.xxx.xxx], pleased to meet
you
> >10:12 10:33 SMTP-(00000140) 250-EXPN
> >10:12 10:33 SMTP-(00000140) 250-VERB
> >10:12 10:33 SMTP-(00000140) 250-8BITMIME
> >10:12 10:33 SMTP-(00000140) 250-SIZE
> >10:12 10:33 SMTP-(00000140) 250-DSN
> >10:12 10:33 SMTP-(00000140) 250-ONEX
> >10:12 10:33 SMTP-(00000140) 250-ETRN
> >10:12 10:33 SMTP-(00000140) 250-XUSR
> >10:12 10:33 SMTP-(00000140) 250 HELP
> >10:12 10:33 SMTP-(00000140) >MAIL From xxxxxxxxxxxx 10:12 10:34
> >SMTP-(00000140) 451 xxxxxxxxxxxxxxx Sender domain must resolve
> >10:12 10:34 SMTP-(00000140) SMTP_DELIV_FAILED
> >10:12 10:34 SMTP-(00000140) >QUIT
> >10:12 10:34 SMTP-(00000140) 221 neuman.interaccess.com closing
> >connection
>
> >stuff like that ..
>
>
> >-----Original Message-----
> >From: [EMAIL PROTECTED]
> >[mailto:[EMAIL PROTECTED]]On Behalf Of Len Conrad
> >Sent: Monday, October 13, 2031 2:15 PM
> >To: [EMAIL PROTECTED]
> >Subject: Re: [IMail Forum] delays
>
> >Whoa, nice one, Michael!! There there are other log lines between
> those
> >two lines, non?
>
> >Can you see any retry attempts by smtp?
>
> >If the remote smto server(s) were busy, then the some Imail smtp
> >rdeliver lines will not be written (indicates delivery success) until
> >the remote server is retried.
>
> >What your the Imail:smtp retry delay period?
>
> >Len
> >================
>
>
> >>Sorry about the html before. Hope this is fixed this time
> >>
> >>Here is the mail delay I found in the log. Any suggestions as to
why
> it
> >>takes so long?
> >>
> >>
> >>10:12 07:26 SMTP-(0000015C) processing C:\IMAIL\spool\Q1af22ec.SMD
> >>10:12 10:08 SMTP-(0000005A) finished C:\IMAIL\spool\Q1af22ec.SMP
> status=3
> >>
> >>2 hrs 42 mins!!!
> >>
> >>Weird ...
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
