Off the top of my head.  Maybe something will shake loose...

- Just for grins, run through the process of sending with telnet using
ip addy on the local machine.  Here's an example to follow how to do
this: http://www.netadmintools.com/art276.html  I'm sure it will work
but what the heck...
- Have you looked at tcp.smtp?  Do you have
anything that might cause this in there?
- Is it at all possible you
have another machine on the network with the same IP?  Pull the nic
cable and ping the ip.

- This one's a reach but worth a shot,
maybe a switch problem?  Try putting the server and one other machine
on the same switch with NOTHING else connected, not even the rest of the
network, and test.

In these cases I try to break things down
into smaller bits and walk my way in or out.

Phil



> In my last reply, I lied.  I can now telnet to the
local address through
> console just fine.  Got a helo back and it
responded.  Outside in, is
> where
> the failure is.
> 
> I am getting spamdyke messages in my smtp log.  I see a
denied for an
> email
> that just tried to relay through
my server.
> 
> @400000004a7c0ab8320d2604 spamdyke[6976]:
DENIED_OTHER from:
> rshewf...@intelius.com to: gvick...@domain
origin_ip: 74.125.149.207
> origin_rdns:
na3sys009aog112.obsmtp.com auth: (unknown)
> 
> 
>
Spamdyke.conf is
> 
>
dns-blacklist-entry=zombie.dnsbl.sorbs.net
>
#dns-blacklist-entry=dul.dnsbl.sorbs.net
>
#dns-blacklist-entry=bogons.cymru.com
>
dns-blacklist-entry=zen.spamhaus.org
>
dns-blacklist-entry=bl.spamcop.net
>
graylist-dir=/var/spamdyke/graylist
> graylist-level=always
> graylist-max-secs=2678400
> graylist-min-secs=180
>
greeting-delay-secs=5
> idle-timeout-secs=60
>
ip-blacklist-file=/etc/spamdyke/blacklist_ip
>
ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords
>
ip-in-rdns-keyword-whitelist-file=/etc/spamdyke/whitelist_keywords
> ip-whitelist-file=/etc/spamdyke/whitelist_ip
>
local-domains-file=/var/qmail/control/rcpthosts
>
log-level=info
> log-target=stderr
> max-recipients=50
> #policy-url=http://my.policy.explanation.url/
>
rdns-blacklist-file=/etc/spamdyke/blacklist_rdns
>
rdns-whitelist-file=/etc/spamdyke/whitelist_rdns
>
recipient-blacklist-file=/etc/spamdyke/blacklist_recipients
>
recipient-whitelist-file=/etc/spamdyke/whitelist_recipients
>
reject-empty-rdns
> #reject-ip-in-cc-rdns
>
reject-missing-sender-mx
> reject-unresolvable-rdns
>
sender-blacklist-file=/etc/spamdyke/blacklist_senders
>
sender-whitelist-file=/etc/spamdyke/whitelist_senders
>
tls-certificate-file=/var/qmail/control/servercert.pem
> 
> 
> -----Original Message-----
>
From: news
[mailto:n...@ger.gmane.org] On Behalf Of Eric Shubert
> Sent:
Friday, August 07, 2009 11:39 AM
> To:
qmailtoaster-list@qmailtoaster.com
> Subject: Re: [qmailtoaster]
connection refused from clients sending email
> 
> Since
you're receiving mail, I don't see how it can be a routing problem.
> 
> spamdyke looks ok. To be sure it's running, are you
seeing spamdyke
> messages in the smtp log?
> (spamdyke
messages have ALLOWED or DENIED_ in them)
> 
> What does
your /etc/spamdyke/spamdyke.conf file contain?
> 
> Glen
Vickers wrote:
>> Yes, I can receive mail all day and my client
is able to download them.
>> Just can't send from external.  I
can send using squirrelmail.
>>
>> smtp]# ll
>> total 16
>> drwx------ 3 qmaill qmail 4096 Jul 29
12:38 log
>> lrwxrwxrwx 1 root   root    12 Aug  7 01:38 run
-> run.spamdyke
>> -rwxr-x--x 1 qmaill qmail  555 Apr 17
06:37 run.dist
>> -rwxr-x--x 1 qmaill qmail  584 Aug  7 03:58
run.spamdyke
>> drwx------ 2 qmaill qmail 4096 Aug  7 04:01
supervise
>>
>>
>> the run file reads
>>
>> #!/bin/sh
>> QMAILDUID=`id -u
vpopmail`
>> NOFILESGID=`id -g vpopmail`
>>
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
>>
SPAMDYKE="/usr/local/bin/spamdyke"
>>
SPAMDYKE_CONF="/etc/spamdyke/spamdyke.conf"
>>
SMTPD="/var/qmail/bin/qmail-smtpd"
>>
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
>>
HOSTNAME=`hostname`
>>
VCHKPW="/home/vpopmail/bin/vchkpw"
>>
REQUIRE_AUTH=0
>>
>> exec /usr/bin/softlimit -m
90000000 \
>>      /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x
$TCP_CDB -c "$MAXSMTPD"
>> \
>>      -u
"$QMAILDUID" -g "$NOFILESGID" 0 smtp \
>>  
   $SPAMDYKE --config-file $SPAMDYKE_CONF \
>>      $SMTPD
$VCHKPW /bin/true 2>&1
>>
>>
>> My
log file doesn't show anything hitting the server.  I have a record
>> of
>> when I telnet'd to localhost port 25 but
that's it.
>>
>>
>> -----Original
Message-----
>>
From: news [mailto:n...@ger.gmane.org] On
Behalf Of Eric Shubert
>> Sent: Friday, August 07, 2009 10:20
AM
>> To: qmailtoaster-list@qmailtoaster.com
>>
Subject: Re: [qmailtoaster] connection refused from clients sending
>> email
>>
>> Just to be sure, what does
>> # ls -l /var/qmail/supervise/smtp
>> show?
>>
>> You're seeing spamdyke messages in your smtp
log?
>>
>> Do I understand correctly that you're
receiving email from outside
>> servers ok, you're just not
able to submit from an external client?
>>
>> Glen
Vickers wrote:
>>> I did that.  No change.  Still unable to
comm. Through port 25 inside
>>> or
>>>
outside network, only through SSH. (ssh to the box then run telnet
>> localhost
>>> or telnet (IP addy).
>>>
>>> -----Original Message-----
>>>
From: news [mailto:n...@ger.gmane.org] On Behalf Of
Eric Shubert
>>> Sent: Friday, August 07, 2009 8:43 AM
>>> To: qmailtoaster-list@qmailtoaster.com
>>>
Subject: Re: [qmailtoaster] connection refused from clients sending
>>> email
>>>
>>> Glen Vickers
wrote:
>>>> Telnet gives connection refused.  However, I
can ssh and such into the
>>>> box just fine.  I can get
to other ports except 25.  I've already
>>>> checked with
my ISP and they haven't blocked anything.  My ISP would
>>>> block me if I made an open relay or my SMTP went
retarded and started
>>>> spamming people.  I am pretty
confident its not an ISP issue.
>>>>
>>>> This happened about 2 weeks ago and I did run new model
and patched
>>>> up.
> 
>>>> The
problem went away for about 2 weeks but now its back.
>>>>
>>>> Glen
>>>>
>>> Jake and Phil have good suggestions (as usual).
>>>
>>> Are you using spamdyke? If so,
>>> # cd /var/qmail/supervise/smtp
>>> # ln -sf
run.spamdyke run
>>> will fix it. qtp-newmodel effectively
disables spamdyke.
>>>
>>
>>
>

> 
> --
> -Eric 'shubes'
> 
> 
>
----------------------------------------------------------------------------
> -----
> Qmailtoaster is sponsored by Vickers Consulting
Group
> (www.vickersconsulting.com)
>     Vickers
Consulting Group offers Qmailtoaster support and
>
installations.
>       If you need professional help with your
setup, contact them today!
>
----------------------------------------------------------------------------
> -----
>      Please visit qmailtoaster.com for the latest
news, updates, and
> packages.
> 
>       To
unsubscribe, e-mail:
>
qmailtoaster-list-unsubscr...@qmailtoaster.com
>      For
additional commands, e-mail:
>
qmailtoaster-list-h...@qmailtoaster.com
> 
> 
>

>
---------------------------------------------------------------------------------
> Qmailtoaster is sponsored by Vickers Consulting Group
>
(www.vickersconsulting.com)
>     Vickers Consulting Group offers
Qmailtoaster support and
> installations.
>       If you
need professional help with your setup, contact them today!
>
---------------------------------------------------------------------------------
>      Please visit qmailtoaster.com for the latest news, updates,
and
> packages.
> 
>       To unsubscribe,
e-mail:
> qmailtoaster-list-unsubscr...@qmailtoaster.com
>
     For additional commands, e-mail:
>
qmailtoaster-list-h...@qmailtoaster.com
> 
> 
>

Reply via email to