You've whitelisted locahost in spamdyke, so spamdyke's allowing it. CHKUSER is rejecting this one. What's in your tcp.smtp file? (and did you regenerate the cdb after changing it?)

Kjetil Paulsen wrote:
Guess so, here are the log entry from trying to send from squirrelmail:

@400000004af52e171ed800f4 tcpserver: status: 1/100
@400000004af52e171edc332c tcpserver: pid 5743 from 127.0.0.1
@400000004af52e171edc3714 tcpserver: ok 5743 blue:127.0.0.1:25 <http://127.0.0.1:25> :127.0.0.1::32941 @400000004af52e171f093e6c spamdyke[5743]: DEBUG(filter_rdns_missing()@filter.c:848): checking for missing rDNS; rdns: localhost @400000004af52e171f09c724 spamdyke[5743]: DEBUG(filter_rdns_whitelist_file()@filter.c:956): searching rDNS whitelist file(s); rdns: localhost @400000004af52e171f0a5b94 spamdyke[5743]: DEBUG(filter_rdns_blacklist_file()@filter.c:1059): searching rDNS blacklist file(s); rdns: localhost @400000004af52e171f0accdc spamdyke[5743]: DEBUG(filter_ip_whitelist()@filter.c:1127): searching IP whitelist file(s); ip: 127.0.0.1 @400000004af52e171f0b8474 spamdyke[5743]: FILTER_WHITELIST_IP ip: 127.0.0.1 file: /etc/spamdyke/whitelist_ip(1) @400000004af52e1722e56efc CHKUSER accepted sender: from <[email protected]::> remote <www.jforce.no:unknown:127.0.0.1> rcpt <> : sender accepted @400000004af52e1722e9763c spamdyke[5743]: DEBUG(filter_recipient_relay()@filter.c:2183): checking relaying; relay-level: 0 recipient: [email protected] <mailto:[email protected]> ip: 127.0.0.1 rdns: localhost local_recipient: false relaying_allowed: false @400000004af52e172642653c CHKUSER rejected relaying: from <[email protected]::> remote <www.jforce.no:unknown:127.0.0.1> rcpt <[email protected] <mailto:[email protected]>> : client not allowed to relay @400000004af52e18265c4a24 spamdyke[5743]: FILTER_OTHER: response: "553 sorry, that domain isn't in my list of allowed rcpthosts (#5.5.3 - chkuser)" @400000004af52e18265c51f4 spamdyke[5743]: DENIED_OTHER from: [email protected] <mailto:[email protected]> to: [email protected] <mailto:[email protected]> origin_ip: 127.0.0.1 origin_rdns: localhost auth: (unknown)
@400000004af52e18268365dc tcpserver: end 5743 status 0
@400000004af52e1826836dac tcpserver: status: 0/100


On Sat, Nov 7, 2009 at 10:20 AM, Kjetil Paulsen <[email protected] <mailto:[email protected]>> wrote:

    I've only done qtp-install-spamdyke and not touched anything after
    that, I'm also getting error when trying to send emails from
    Squirrelmail :/
    "Message not sent. Server replied: Requested action not taken:
    mailbox name not allowed

    553 sorry, that domain isn't in my list of allowed rcpthosts (#5.5.3
    - chkuser)"

    I've turned on debuging in spamdyke, is it the smtp log I should be
    looking in for these problems?

    /K

    On Fri, Nov 6, 2009 at 3:51 PM, Eric Shubert <[email protected]
    <mailto:[email protected]>> wrote:

        Kjetil Paulsen wrote:

            Hi again... I installed spamdyke and also bought and
            installed new certificates from RapidSSL, it solved the
            problem with this particular domain... however I'm now
            having trouble sending emails from one of my domains (the
            main one) when connected from external networks

            First one is from a mobile broadband dialup:

            The message could not be sent because one of the recipients
            was rejected by the server. The rejected e-mail address was
            '[email protected] <mailto:[email protected]>
            <mailto:[email protected]
            <mailto:[email protected]>>'<mailto:'[email protected]
            <mailto:[email protected]>'
            <mailto:%[email protected]
            <mailto:[email protected]>%27>>. Subject 'testing',
            Account: 'jforce.no <http://jforce.no> <http://jforce.no>',
            Server: 'jforce.no <http://jforce.no> <http://jforce.no>',
            Protocol: SMTP, Server Response: '554 Refused. Your IP
            address is listed in the RBL at zen.spamhaus.org
            <http://zen.spamhaus.org> <http://zen.spamhaus.org>', Port:
            25, Secure(SSL): No, Server Error: 554, Error Number: 0x800CCC79


        I presume you're using port 25 for submission, as you shouldn't
        get this error on port 587. Using port 587 for submission is a
        good practice if it's feasible.

        On port 25, spamdyke bypasses all filters for authenticated
        sessions, so you shouldn't be getting this error if spamdyke's
        configured properly. Are you using the stock spamdyke
        configuration, or have you tweaked it? Please post.

            Second one is from my daytime employers network:


            The message could not be sent because one of the recipients
            was rejected by the server. The rejected e-mail address was
            '[email protected] <mailto:[email protected]>
            <mailto:[email protected]
            <mailto:[email protected]>>'<mailto:'[email protected]
            <mailto:[email protected]>'
            <mailto:%[email protected]
            <mailto:[email protected]>%27>>. Subject 'testing',
            Account: 'jforce.no <http://jforce.no> <http://jforce.no>',
            Server: 'jforce.no <http://jforce.no> <http://jforce.no>',
            Protocol: SMTP, Server Response: '553 sorry, that domain
            isn't in my list of allowed rcpthosts (#5.5.3 - chkuser)',
            Port: 25, Secure(SSL): No, Server Error: 553, Error Number:
            0x800CCC79


        Again, your session is not authenticated. Your spamdyke
        configuration will probably hold the answer. You might try
        turning on spamdyke's detailed logging (slick) to see what's
        happening. See spamdyke documentation for how-to.


            Have spamdyke overwritten some other configuration?! Before
            relaying with username/pwd worked perfectly... I guess the
            first error is because this is a dialup network and marked
            as unsafe(?)


        No, you're simply not authenticating, at least that spamdyke can
        see.

            /K



            On Wed, Nov 4, 2009 at 8:17 PM, Jake Vickers
            <[email protected] <mailto:[email protected]>
            <mailto:[email protected]
            <mailto:[email protected]>>> wrote:

               Kjetil Paulsen wrote:

                   seeing the exact problem here from one particular
                domain, started
                   some weeks ago...

                   my server says:
                   tcpserver: pid 15053 from 89.20.252.149
                   tcpserver: ok 15053 blue:10.0.0.7:25
                <http://10.0.0.7:25> <http://10.0.0.7:25>

                   :89.20.252.149::4609
                   tcpserver: status: 4/100

                   the email transcript:
                   Attempting SMTP connection to [jforce.no
                <http://jforce.no> <http://jforce.no/>]
                   Resolving MX records for [jforce.no
                <http://jforce.no> <http://jforce.no/>] (DNS

                   Server: 89.20.252.130)...
                   *  P=000 S=000 D=jforce.no <http://jforce.no>
                <http://jforce.no/> TTL=(60)
                   MX=[jforce.no <http://jforce.no> <http://jforce.no/>]
                {84.234.141.2}    Attempting SMTP connection to
                [84.234.141.2:25 <http://84.234.141.2:25>
                   <http://84.234.141.2:25/>]

                   Waiting for socket connection...
                   Connection established (89.20.252.149:3324
                <http://89.20.252.149:3324>
                   <http://89.20.252.149:3324/> -> 84.234.141.2:25
                <http://84.234.141.2:25>
                   <http://84.234.141.2:25/>)    Waiting for protocol to
                start...

                   *  Error: 60 second wait for protocol timeout
                exceeded    This message is 61 minutes old; it has 0
                minutes left in this queue    Remote queue lifetime
                exceeded; message placed in retry queue


                   anyone have any suggestions? can't find anything in
                the logs that
                   indicate problems :/



                   On Tue, Nov 3, 2009 at 3:02 AM, jim jackson
                <[email protected] <mailto:[email protected]>
                   <mailto:[email protected]
                <mailto:[email protected]>>> wrote:

                       Hey guys, My server can send mail without any
                problem and
                       receive mail from gmail, hotmail, yahoo etc
                however I'm having
                       trouble receiving mail from my other domain which
                is hosted by
                       another company.


                       Anyone have advice on how to troubleshoot error:
                Connected to
                       ip but connection died. 4.4.2.


               I think I remember this popping up a while back when
            connecting to
               MSExchange servers and TLS. It may be resolved by
            regenerating the
               TLS certificate - if it's expired, most MTAs will still
            use it with
               just a warning but some Exchange servers may be
            configured to deny
               expired certificates.
               More detailed logging would be helpful though.




-- /**
            kjetil
            */
            ---------------------------------------------------------
            Kjetil Paulsen      [email protected]
            <mailto:[email protected]>
            <mailto:[email protected]
            <mailto:[email protected]>>

            http://gofaster.no
            ---------------------------------------------------------
            -Many secrets of art and nature
                         are thought by the unlearned to be magical-



-- -Eric 'shubes'


        
---------------------------------------------------------------------------------
        Qmailtoaster is sponsored by Vickers Consulting Group
        (www.vickersconsulting.com <http://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 <http://qmailtoaster.com> for
        the latest news, updates, and packages.
                To unsubscribe, e-mail:
        [email protected]
        <mailto:[email protected]>
           For additional commands, e-mail:
        [email protected]
        <mailto:[email protected]>





-- /**
    kjetil
    */
    ---------------------------------------------------------
Kjetil Paulsen [email protected] <mailto:[email protected]>
    http://gofaster.no
    ---------------------------------------------------------
    -Many secrets of art and nature
                  are thought by the unlearned to be magical-




--
/**
kjetil
*/
---------------------------------------------------------
Kjetil Paulsen [email protected] <mailto:[email protected]>
http://gofaster.no
---------------------------------------------------------
-Many secrets of art and nature
              are thought by the unlearned to be magical-


--
-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: [email protected]
    For additional commands, e-mail: [email protected]


Reply via email to