| To: | Oliver Welter <mail@oliwel.de> |
|---|---|
| Subject: | Re: Debugging rejected mail |
| From: | Uncle George <netbeans@gatworks.com> |
| Date: | Wed, 11 Apr 2007 19:09:16 -0400 |
| Cc: | qmail@list.cr.yp.to |
| Delivered-to: | sp-com-lists@consult.net |
| Delivered-to: | gmail-qmail@securepoint.com |
| Delivered-to: | sp.com.list@gmail.com |
| Delivered-to: | mailing list qmail@list.cr.yp.to |
| In-reply-to: | <461D23F8.9070004@oliwel.de> |
| Mailing-list: | contact qmail-help@list.cr.yp.to; run by ezmlm |
| References: | <461D18A6.5090801@oliwel.de> <20070411175505.GA28444@discworld.dyndns.org> <461D23F8.9070004@oliwel.de> |
| User-agent: | Mozilla Thunderbird 1.0.2-6 (X11/20050513) |
but the point is to fetch the right connection - there are some hundreds a minute and I dont have a clue how to find the rightone. Doesnt 'tcpserver -v' print out the ip address as well as the port for the connection?
tcpdump can be used to dump all the raw packets into a file ie
tcpdump -i eth0 -w ImWatchingYou.log host mail.BadBoy.com
get the host & port from the tcpserver log file,
then use tcpdump to dump out the packets you want.
tcpdump -r ImWatchingYou.log -s 0 host xx.xx.xx.xx port nnnn
tcpdump will normally only print packet headers
Hope this is of help.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Debugging rejected mail, Kyle Wheeler |
|---|---|
| Next by Date: | New qmail SMTP AUTH patch, Traian ZVIRID |
| Previous by Thread: | Re: Debugging rejected mail, Oliver Welter |
| Next by Thread: | Re: Debugging rejected mail, Kyle Wheeler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |