Re: [qmailtoaster] bypassing virtualdomains

2008-09-16 Thread Quinn Comendant
On Fri, 12 Sep 2008 10:26:13 -0400, Dan McAllister wrote:
 I've had to deal with this... and if you have control of BOTH ends 
 (old server and new) it's much easier...

I almost never have access to the old server. Any other ideas?

Quinn

-
 QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [qmailtoaster] bypassing virtualdomains

2008-09-12 Thread Dan McAllister
I've had to deal with this... and if you have control of BOTH ends (old 
server and new) it's much easier...


If your old server is a QMT, you can add a file in the control folder 
(usually /var/qmail/control) called smtproutes. The REAL functionality 
of this feature is so that you can configure a backup SMTP server that 
can queue mail for the main server until it is available again. However, 
it is equally useful in your migration environment -- simply make the 
old SMTP server a backup for the new one.


The formats for the file (and full documentation) is on the WIKI at 
http://wiki.qmailtoaster.com/index.php/Smtproutes


I hope this helps someone!

Dan

Daniel McAllister, President

IT4SOHO, LLC
PO BOX 507
St. Petersburg, FL 33731-0507

877-IT4SOHO: Toll Free
727-647-7646 In Pinellas
813-464-2093 In Hillsborough
727-507-9435 Fax Only

When did you do your last backup?

Ask me about unattended offsite backup solutions...
to protect your business, not just your data!



Quinn Comendant wrote:

Hi all,

Is there a way to have qmail-send check actual MX records for a domain before 
deciding if it is local or not (instead of by (more)rcpthosts and 
virtualdomains)?

An issue comes up occasionally when a domain is added on our server which is 
currently hosted somewhere else (i.e. it's a migration) and the DNS isn't 
updated for awhile until the client is prepared to finalize the migration. The 
problem is, until MX records are switched, they expect mail to be delivered to 
their existing mail server (i.e. not us) however messages that are sent from 
our server are delivered locally because the domain exists in (more)rcpthosts 
and virtualdomains. Any users who send mail to their domain is not received (or 
more likely, is bounced because the user has not added any mail accounts for 
the domain).

Solutions I've thought of:

- Ask people to use a different SMTP server when sending messages to the domain 
until DNS is migrated (i.e. smtp.gmail.com). PROBLEM: we can't possible insist 
the hundreds of mail users on our system do this.

- Comment out the domain in the (more)rcpthosts and virtualdomains control 
files. PROBLEM: when the DNS is finally switched for the domain, we'll most 
likely forget to un-comment the configuration.

Any other ideas?

Quinn

  


-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]