Re: [courier-users] RE: Debugging SMTP timeout problems

2003-06-06 Thread Juha Saarinen
On Wed, 4 Jun 2003, Robert Penz wrote:

  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1

  On Wednesday 04 June 2003 20:42, Julian Mehnle wrote:
   Currently, not even
 $ dig blackholes.mail-abuse.org NS
   works for me.
  NS does work

  whitestar# dig blackholes.mail-abuse.org NS

  ;  DiG 9.2.1  blackholes.mail-abuse.org NS
  ;; global options:  printcmd
  ;; Got answer:
  ;; -HEADER- opcode: QUERY, status: NOERROR, id: 29919
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;blackholes.mail-abuse.org. IN  NS

  ;; ANSWER SECTION:
  blackholes.mail-abuse.org. 82148 IN NS  west1.mail-abuse.org.
  blackholes.mail-abuse.org. 82148 IN NS  europe1.mail-abuse.org.
  blackholes.mail-abuse.org. 82148 IN NS  east1.mail-abuse.org.

  ;; Query time: 1 msec
  ;; SERVER: 127.0.0.1#53(127.0.0.1)
  ;; WHEN: Wed Jun  4 22:38:27 2003
  ;; MSG SIZE  rcvd: 105


  but I get no IP for blackholes.mail-abuse.org


  whitestar:# dig blackholes.mail-abuse.org

  ;  DiG 9.2.1  blackholes.mail-abuse.org
  ;; global options:  printcmd
  ;; Got answer:
  ;; -HEADER- opcode: QUERY, status: NXDOMAIN, id: 64561
  ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;blackholes.mail-abuse.org. IN  A

  ;; Query time: 173 msec
  ;; SERVER: 127.0.0.1#53(127.0.0.1)
  ;; WHEN: Wed Jun  4 22:38:30 2003
  ;; MSG SIZE  rcvd: 43

This is a bit off-topic for the list, but the above is correct because
blackholes.mail-abuse.org is a zone, and not a host. Hence no A record,
but you do get the NS records.

Try something like this for A records:

~$ dig 189.45.242.194.blackholes.mail-abuse.org. +short

If the IP address in question is listed, you'll have 127.0.0.2 returned.

More info at:

http://mail-abuse.org/rbl/usage.html


-- 
Juha Saarinen


---
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users


[courier-users] RE: Debugging SMTP timeout problems

2003-06-05 Thread Julian Mehnle
Robert Penz [EMAIL PROTECTED] wrote:
 I've the same problems since yesterday .. I can't send a mail via smtp
 auth for about 5 min or so, after that time it works again until the next
 5 problem minutes.

 I've tried to narrow the problem down.

 during this 5 mins I get only this, after this I time I get the server
 greeting. I've tried it from 5 computers (everyone in a other subnet and
 other dns servers) always the same. on localhost it works always.

This looks very much like a reverse DNS problem.

 I've used dig -x client_ip during this time to check if the dns stuff
 works and yes that does.

 I've following running, whichs is not the same as you've ?

 BLACKLISTS=-block=blackholes.mail-abuse.org,BLOCK/127.0.0.2
 -block=relays.mail-abuse.org,BLOCK/127.0.0.2
 -block=dialups.mail-abuse.org,BLOCK/127.0.0.2

Have you tried the following?

  $ dig 225.85.30.195.blackholes.mail-abuse.org ANY
  $ dig 225.85.30.195.blackholes.mail-abuse.org PTR

Currently, not even

  $ dig blackholes.mail-abuse.org NS

works for me.

It seems[1] like the registration period for the mail-abuse.net domain has
expired, and MAPS LLC forgot to renew it.

Julian.

[1] http://www.mehnle.net/tools/whois?object=mail-abuse.net



---
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users


[courier-users] Re: Debugging SMTP timeout problems

2003-06-05 Thread Sam Varshavchik
Robert Penz writes:


I've tried to narrow the problem down. 

during this 5 mins I get only this, after this I time I get the server 
greeting. I've tried it from 5 computers (everyone in a other subnet and 
other dns servers) always the same. on localhost it works always.

$ telnet outertech.com 25
Trying 194.242.45.189...
Connected to outertech.com.
Escape character is '^]'.
I've used dig -x client_ip during this time to check if the dns stuff works 
and yes that does.

I've following running, whichs is not the same as you've ?

BLACKLISTS=-block=blackholes.mail-abuse.org,BLOCK/127.0.0.2 
- -block=relays.mail-abuse.org,BLOCK/127.0.0.2 
- -block=dialups.mail-abuse.org,BLOCK/127.0.0.2
... and you are actually paying a licensing fee to MAPS, for using their 
RBL, or have a gratis contractual agreement with them, correct?

Otherwise, they've probably firewalled you off, as a nuisance, and all your 
DNS queries are timing out.



---
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users


[courier-users] RE: Debugging SMTP timeout problems

2003-06-05 Thread Julian Mehnle
Julian Mehnle [EMAIL PROTECTED] wrote:
 Robert Penz [EMAIL PROTECTED] wrote:
  I've following running, whichs is not the same as you've ?
 
  BLACKLISTS=-block=blackholes.mail-abuse.org,BLOCK/127.0.0.2
  -block=relays.mail-abuse.org,BLOCK/127.0.0.2
  -block=dialups.mail-abuse.org,BLOCK/127.0.0.2

 Have you tried the following?

   $ dig 225.85.30.195.blackholes.mail-abuse.org ANY
   $ dig 225.85.30.195.blackholes.mail-abuse.org PTR

 Currently, not even

   $ dig blackholes.mail-abuse.org NS

 works for me.

 It seems[1] like the registration period for the mail-abuse.net domain
 has expired, and MAPS LLC forgot to renew it.

 [1] http://www.mehnle.net/tools/whois?object=mail-abuse.net

Doh, I'm talking nonsense.  mail-abuse.org is different from mail-abuse.net!
The correct WHOIS query would be:
http://www.mehnle.net/tools/whois?object=mail-abuse.org which clearly shows
that mail-abuse.org has *not* expired.  Sorry for the confusion.

However, the `dig`s were correct though, and they're still timing out.

Julian.



---
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users


Re: [courier-users] RE: Debugging SMTP timeout problems

2003-06-05 Thread Robert Penz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday 04 June 2003 20:42, Julian Mehnle wrote:
 Currently, not even
   $ dig blackholes.mail-abuse.org NS
 works for me.
NS does work

whitestar# dig blackholes.mail-abuse.org NS

;  DiG 9.2.1  blackholes.mail-abuse.org NS
;; global options:  printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 29919
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;blackholes.mail-abuse.org. IN  NS

;; ANSWER SECTION:
blackholes.mail-abuse.org. 82148 IN NS  west1.mail-abuse.org.
blackholes.mail-abuse.org. 82148 IN NS  europe1.mail-abuse.org.
blackholes.mail-abuse.org. 82148 IN NS  east1.mail-abuse.org.

;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Jun  4 22:38:27 2003
;; MSG SIZE  rcvd: 105


but I get no IP for blackholes.mail-abuse.org


whitestar:# dig blackholes.mail-abuse.org

;  DiG 9.2.1  blackholes.mail-abuse.org
;; global options:  printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NXDOMAIN, id: 64561
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;blackholes.mail-abuse.org. IN  A

;; Query time: 173 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Jun  4 22:38:30 2003
;; MSG SIZE  rcvd: 43



- -- 
Regards,
Robert
- 
Robert Penz
robert.penz AT outertech.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+3lie8tTsQqJDUBMRAts0AJ49nF+hoC0nNizbgB/PP73E/2VQYwCfcfEx
54lZ3LNDXwghRyt7nymjIe8=
=yTuc
-END PGP SIGNATURE-



---
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users


[courier-users] RE: Debugging SMTP timeout problems

2003-06-02 Thread Julian Mehnle
Julian Mehnle wrote:
 [...] Today, the SMTP server started to act up: it accepts TCP
 connections virtually immediately, but then reacts only very, very slowly.
 Thus, most of the time, the connection times out on the client/peer side.
 [...]
 Can anyone give me some hints on how to debug the SMTP server's miserable
 performance?

I just read that the SpamCop DNS blacklist, which I'm using, has very
recently dropped out, so this is probably the cause.  Please ignore my
mail -- if the problem persists when the SpamCop blacklist starts working
again, I'll continue debugging.

Julian.



---
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users


[courier-users] Re: Debugging SMTP timeout problems

2003-06-02 Thread Sam Varshavchik
Julian Mehnle writes:

Hi all,

I have been running Courier 0.39.1 on Debian Linux as my mail server
(SMTP(S), POP3(S), IMAP(S)) for about a year now without any noteworthy
problems.  Today, the SMTP server started to act up: it accepts TCP
connections virtually immediately, but then reacts only very, very slowly.
Thus, most of the time, the connection times out on the client/peer side.
Other services (POP3, HTTP, ...) work as perfectly as ever.
Since there are no error messages in the logs, and the server's load is
negligible (below 0.5 at all times), I'm suspecting a hardware error (e.g.
harddisk), even though there are no hardware error messages in the logs as
well so far.
Can anyone give me some hints on how to debug the SMTP server's miserable
performance?
It a DNS or a firewall issue.  Incoming SMTP connections have the client's 
IP address resolved via DNS, followed by an ident query.

A nonfunctioning DNS server somewhere, or a broken firewall that's dropping 
identd packets, would slow things down.



---
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users