Re: Re: Re: [qmailtoaster] 451 dns issue with chkuser, but cmd line seems fine?

2009-07-07 Thread craig . p . mclaughlin
Well. I should learn to listen to my gut, and I should always remember what  
Rich Miller taught... EVERY comms issue on the internet comes down to some  
DNS error somewhere. :)


Thanks for the responses, gents. I ended up implementing a split-DNS, and  
that resolved my issues.


qmailtoaster is awesome. Thanks for all the fantastic bells & whistles!

Cheers,
--Craig

On Jul 6, 2009 5:27pm, craig.p.mclaugh...@gmail.com wrote:

1) yep
2) /etc/resolv.conf contains valid and working nameservers. I am able to  
use them to dig mx gmail.com (for example) AND use /bin/mail to deliver  
mail there. I was also able to use /bin/mail to deliver mail to one of  
the domains this toaster is responsible for.


I am currently operating under the theory that my hosting setup may be  
causing this. I have no solid-based-in-fact reason for this, simply that  
my gut says 'try this.'


External IPs are mapped 1:1 with RFC1918 IPs by my hosting provider (ie:  
I have 192.168.xy, which the world sees as 128.177.xy, assuming 128.177).  
I'm wondering if DNS is getting confused by the questions, or if qmail is  
getting confused by the responses.


So I'm setting up bind in a split-view mode, and will see if that makes a  
difference.



That said, I appreciate the response, and any others are welcome. :D



Cheers,
--Craig



On Jul 6, 2009 5:21pm, Eric Shubert e...@shubes.net> wrote:
> Craig McLaughlin wrote:
>
>
>
>
> All --
>
>
>
> Greetings, and thanks for the qmailtoaster setup. I love everything  
about it thus far... except that I seem to have muffed something up and  
cannot send any mail.

>
>
>
> The issue:
>
>
>
> Any mail sent through the toaster via squirrelmail (the only setup I  
have at the moment) fails with:

>
>
>
> Requested action aborted: error in processing
>
> 451 DNS temporary failure (#4.5.1 - chkuser)
>
>
>
> What's particularly frustrating is I don't seem to be able to find  
what, if any, log is catching / noting this error. I've looked at all the  
ones I can find under /var/log/qmail without any luck.

>
>
>
> I dug around for common issues & suggestions. Most seem to ask for  
confirmation that things work from the command line. Trying that, I can  
confirm that from the command line a "dig mx " works, and sending mail  
from /bin/mail also works. (as I ponder this fact, I wonder if this  
should be pointing me to something other than the toaster? yes? no?  
thoughts? :) )

>
>
>
> ANY pointers would be greatly appreciated, be they 'do this and it'll  
go away' or 'check this documentation, it might help.'

>
>
>
> Thanks,
>
> --Craig
>
>
>
>
>
>
> Did you set up a caching nameserver?
>
> What's in your /etc/resolv.conf ?
>
>
>
> --
>
> -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
>
>
>
>
>


Re: [qmailtoaster] 451 dns issue with chkuser, but cmd line seems fine?

2009-07-06 Thread Eric Shubert

Craig McLaughlin wrote:


All --

Greetings, and thanks for the qmailtoaster setup.  I love everything 
about it thus far... except that I seem to have muffed something up and 
cannot send any mail.


The issue:

Any mail sent through the toaster via squirrelmail (the only setup I 
have at the moment) fails with:


Requested action aborted: error in processing
451 DNS temporary failure (#4.5.1 - chkuser)

What's particularly frustrating is I don't seem to be able to find what, 
if any, log is catching / noting this error.  I've looked at all the 
ones I can find under /var/log/qmail without any luck.


I dug around for common issues & suggestions.  Most seem to ask for 
confirmation that things work from the command line.  Trying that, I can 
confirm that from the command line a "dig mx " works, and 
sending mail from /bin/mail also works.  (as I ponder this fact, I 
wonder if this should be pointing me to something other than the 
toaster?  yes?  no?  thoughts? :) )


ANY pointers would be greatly appreciated, be they 'do this and it'll go 
away' or 'check this documentation, it might help.'


Thanks,
--Craig



Did you set up a caching nameserver?
What's in your /etc/resolv.conf ?

--
-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] 451 dns issue with chkuser, but cmd line seems fine?

2009-07-06 Thread Craig McLaughlin
All --

Greetings, and thanks for the qmailtoaster setup.  I love everything about
it thus far... except that I seem to have muffed something up and cannot
send any mail.

The issue:

Any mail sent through the toaster via squirrelmail (the only setup I have at
the moment) fails with:

Requested action aborted: error in processing
451 DNS temporary failure (#4.5.1 - chkuser)

What's particularly frustrating is I don't seem to be able to find what, if
any, log is catching / noting this error.  I've looked at all the ones I can
find under /var/log/qmail without any luck.

I dug around for common issues & suggestions.  Most seem to ask for
confirmation that things work from the command line.  Trying that, I can
confirm that from the command line a "dig mx " works, and sending
mail from /bin/mail also works.  (as I ponder this fact, I wonder if this
should be pointing me to something other than the toaster?  yes?  no?
thoughts? :) )

ANY pointers would be greatly appreciated, be they 'do this and it'll go
away' or 'check this documentation, it might help.'

Thanks,
--Craig