[qmailtoaster] Hypervisor recommendations for virtualizing QMT

Hi all, I'm curious to hear which hypervisors some of you guys are using for virtualizing QMT or just VMs in general. I played around with Citrix XenServer for a good 6-8 months last year, very very briefly checked out Hyper-V, and currently am running Xen on CentOS 5.7 on a few of my PowerEd

Re: [qmailtoaster] Re: Sanesecurity, spamassassin & spamdyke

Casey Price Smile Global Technical Support Submit or check trouble tickets http://billing.smileglobal.com www.smileglobal.com Follow us on Twitter Find us on Facebook On 1/25/12 8:14 PM

Re: [qmailtoaster] Re: Sanesecurity, spamassassin & spamdyke

On 1/25/12 10:40 AM, Eric Shubert wrote: On 01/24/2012 11:15 PM, Casey Price wrote: No worries Eric...I appreciate the insight! We have a few hundred domains with several thousand users. You should be able to get by with a single host in that case. Might need to beef it up a little though de

[qmailtoaster] Re: resolv.conf

That's what I'd do. # yum remove bind # yum install pdns-recursor # service pdns-recursor start # dig @127.0.0.1 yahoo.com (to be sure it's working) # chkconfig pdns-recorsor on That should do it. Also be sure that nameserver 127.0.0.1 is the first (and perhaps only) line in your resolv.conf fil

Re: [qmailtoaster] Re: resolv.conf

hmm, Ok, well I guess its about time I did something with this server since it has been set this way since the beginning 7yrs ago :) I have always noticed some performance issues related to our dns and mail. So, I guess my first step would be to remove Bind and install powerdns or visa versa

[qmailtoaster] Re: resolv.conf

Rather than messing with resolv.conf file to see what happens from each resolver, use the @ option with dig. Then you'll know specifically what each server gives you. If it were me, I'd 86 the authoritative DNS on QMT (do you *really* need that there?), and install powerdns-recursor there and

Re: [qmailtoaster] Re: resolv.conf

If I go into the resolv and set nameserver to one of my current nameservers IP and do a dig on any of the ones that did not resolv I will get an answer and when I put 127.0.0.1 as the nameserver I will finally get an answer, but if I try another domain that has not been queried then it will def

Re: [qmailtoaster] Re: resolv.conf

It still comes back with no answer section just list root servers On 01/25/2012 03:32 PM, Eric Shubert wrote: Can you # dig @127.0.0.1 somedomain.com ? (on QMT host) On 01/25/2012 02:21 PM, David wrote: Strike that... Still having issues almost like its not looking any deeper than 127.0.0.1 fo

[qmailtoaster] Re: resolv.conf

Can you # dig @127.0.0.1 somedomain.com ? (on QMT host) On 01/25/2012 02:21 PM, David wrote: Strike that... Still having issues almost like its not looking any deeper than 127.0.0.1 for a resolv. On 01/25/2012 03:09 PM, David wrote: Eric, I think I may have it.. I had to review my hosts and re

Re: [qmailtoaster] Re: resolv.conf

Strike that... Still having issues almost like its not looking any deeper than 127.0.0.1 for a resolv. On 01/25/2012 03:09 PM, David wrote: Eric, I think I may have it.. I had to review my hosts and resolv.conf files they looked a little screwy so I set them with typical settings with my do

Re: [qmailtoaster] Re: resolv.conf

Eric, I think I may have it.. I had to review my hosts and resolv.conf files they looked a little screwy so I set them with typical settings with my domain info I also took a closer look at my dns. I believe the real problem was in the host and resolv.conf files because it is moving so muc

Re: [qmailtoaster] Re: FW: Error in POP3 over SSL

Hi Eric. I have been using Dovecot for pop3 for some time now (since version 1.2 X in 2009 - currently I'm running version 2.0.10) - no problems. I recall somebody wrote a 'how to', that took You through the changes from qmail-pop3 and IMAP to dovecot . If I'm not wrong it was Amit and Ale

Re: [qmailtoaster] Re: resolv.conf

All 3 are authoritative with one being the master. I may have it working but seems it still doesnt resolv mxtoolbox.com On 01/25/2012 02:37 PM, Eric Shubert wrote: Are the 3 servers authoritative? It's generally a good practice to keep authoritative DNS servers separate from recursors. Of co

Re: [qmailtoaster] Re: resolv.conf

Sry for all the inline post but Im bouncing between 2 issues at the moment here is a partial copy of my config on the nameserver in question : options { directory "/var/named"; dump-file "/var/named/data/cache_dump.db"; statistics-file "/var/named/data/named_stats.txt"; /*

[qmailtoaster] Re: resolv.conf

Are the 3 servers authoritative? It's generally a good practice to keep authoritative DNS servers separate from recursors. Of course it can be done, but it typically leads to problems. On 01/25/2012 01:31 PM, David wrote: Currently I have 3 DNS servers running here at the NOC and the mail se

Re: [qmailtoaster] Re: resolv.conf

Where do your DNS servers go for lookups?  Are you going to root servers or are you using your providers servers?  It seems something upstream of your server is goofy. > Currently I have 3 DNS servers running here at the NOC and the mail > server is on one of the slaves. > I did a few dig comm

Re: [qmailtoaster] Re: resolv.conf

Do I need to allow recursive on 127.0.0.1? On 01/25/2012 02:12 PM, Eric Shubert wrote: On 01/25/2012 12:44 PM, David wrote: calling on the collective :) My resolv.conf looks like this: nameserver 63.147.8.8 <--- MX server nameserver 63.147.8.7 nameserver 63.147.8.9 domain wletc.com search wle

Re: [qmailtoaster] Re: resolv.conf

Currently I have 3 DNS servers running here at the NOC and the mail server is on one of the slaves. I did a few dig commands and it seems to resolv the popular domain request like yahoo,google,msn,hotmail and others but I could not resolv mxtoolbox.com or freeside.biz Is there something wrong

[qmailtoaster] Re: resolv.conf

On 01/25/2012 12:44 PM, David wrote: calling on the collective :) My resolv.conf looks like this: nameserver 63.147.8.8 <--- MX server nameserver 63.147.8.7 nameserver 63.147.8.9 domain wletc.com search wletc.com Do I need to add the line:? nameserver 127.0.0.1 The reason I ask is when I do I

[qmailtoaster] resolv.conf

calling on the collective :) My resolv.conf looks like this: nameserver 63.147.8.8 <--- MX server nameserver 63.147.8.7 nameserver 63.147.8.9 domain wletc.com search wletc.com Do I need to add the line:? nameserver 127.0.0.1 The reason I ask is when I do I get error messages when I send. Than

[qmailtoaster] Re: FW: Error in POP3 over SSL

As another option, you might try using dovecot for pop3/pop3s services instead of qmail-pop3. I haven't yet done so myself (mostly imap users here), but I seem to recall someone here saying that they're using it w/out any problem. If anyone is using dovecot for pop3, would you chime in here pl

[qmailtoaster] Re: Sanesecurity, spamassassin & spamdyke

On 01/24/2012 11:15 PM, Casey Price wrote: No worries Eric...I appreciate the insight! We have a few hundred domains with several thousand users. You should be able to get by with a single host in that case. Might need to beef it up a little though depending on what it's got. I meant to comm

Re: [qmailtoaster] FW: Error in POP3 over SSL

I'm with Dan, Pull out the Howitzer and dial that out of the way so you know for sure it is or isn't the culprit.  I do that same thing, I add a 0 to the end number.  Every time i ran the updates, I would have to fix that again. > The most common reason for this error is that the pop3 server isn

Re: [qmailtoaster] FW: Error in POP3 over SSL

The most common reason for this error is that the pop3 server isn't being given enough RAM when it starts up to be able to run the SSL/TLS encryption/decryption. CD into your /var/qmail/supervise/pop3-ssl/ folder and edit the file named run. You'll see a lin

[qmailtoaster] Error in POP3 over SSL

Hi Everyone, I had implemented SSL certificate on my server around a month back and everything was working fine till today. But from today I'm getting error while downloading mails. POP3, SMTP,IMAP, IMAP over SSL and SMTP over SSL working fine. But POP3 over SSL is giving error. I have attach t