Re: MX, ETRN and QMAIL

2000-01-18 Thread Chris Johnson

On Tue, Jan 18, 2000 at 04:51:49AM +0100, J.M. Roth iip" wrote:
 Hi there.
 
 I have 3 MXs for a domain. The lowest preference MX is the local server. The
 other 2 are the customer's internal server as well as an SMTP queueing
 machine (ETRN etc.). The local machine is there in case the customer's server
 and the mail queue fails.  If I send mail using the local server (outgoing
 mail server) it doesn't even go to the higher preference MX servers but
 simply delivers locally, instead to the highest preference MX, that is the
 customer's server or its queue. The domain is listed in rcpthosts and
 virtualdomains.

Take it out of virtualdomains. By putting it there you're telling qmail to
handle that domain locally, which isn't what you want. List it in rcpthosts
only.

Chris



Re: MX, ETRN and QMAIL

2000-01-18 Thread J.M. Roth

Ok, a few things.
I know, lower priority = higher number.
When I said lower priority I meant exactly that.
f.e.:
in MX 5 mail.customer.com
in MX 10 queue.server.com
in MX 20 ourbackup.ourdomain.com

in case MX5 and MX10 fail it should go to the appropriate account on MX20.

to Chris: taking it out of virtualhosts simply prevents it from ending up in
the right mailbox (has this to do something with DNS lookups?)

to Marc-Adrian: if I delete the domain out of rcpthosts the MX20 won't
receive anything for that domain

to David: thanks, I'm going to check out the smtproutes thing


SO: Any idea? Is smtproutes the right thing to do?

Best regards!

-- jmr

- Original Message -
From: Chris Johnson [EMAIL PROTECTED]
To: J.M. Roth iip" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, January 18, 2000 11:12 AM
Subject: Re: MX, ETRN and QMAIL





Re: MX, ETRN and QMAIL

2000-01-18 Thread J.M. Roth \(iip\)

Ok, sorry I meant virtualdomains.

As I said I would like a backup in case example.com AND the queue for it
fail.
This I've done with the MX records.

One disadvantage is, since the domain must be in rcpthosts on the 3rd
machine to receive anything, *if* mail is sent using this machine as
outgoing mail server, it doesn't even get sent to example.com, even though
it's higher preference...
Got it?

-- jmr
- Original Message -
From: "Chris Johnson" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, January 18, 2000 8:22 PM
Subject: Re: MX, ETRN and QMAIL


 On Tue, Jan 18, 2000 at 06:56:25PM +, [EMAIL PROTECTED] wrote:
  Yeah, but why not in virtualhosts.
  How can I distinguish between several mailboxes then on the backup
  machine??

 For one thing, there's no such thing as virtualhosts.

 Let's say the domain is example.com. You want queue.server.com to accept
mail
 for example.com, but you just want it to queue it and deliver it to
 mail.customer.com when that machine is available. Is that correct? Then,
on
 queue.server.com, put example.com in rcpsthosts and nowhere else. That's
*all*
 you have to do.

 Chris




Re: MX, ETRN and QMAIL

2000-01-18 Thread Chris Johnson

On Tue, Jan 18, 2000 at 08:43:57PM +0100, J.M. Roth iip" wrote:
 Ok, sorry I meant virtualdomains.
 
 As I said I would like a backup in case example.com AND the queue for it
 fail.  This I've done with the MX records.
 
 One disadvantage is, since the domain must be in rcpthosts on the 3rd machine
 to receive anything, *if* mail is sent using this machine as outgoing mail
 server, it doesn't even get sent to example.com, even though it's higher
 preference...
 Got it?

No. This is just not the case. rcpthosts only affects *incoming SMTP* mail, and
it has no affect whatsoever on where mail is ultimately delivered. It only
determines whether your SMTP server will accept the message at the SMTP "RCPT
TO" command. It will *not* cause a lower-preference mail exchanger to ignore
better-preference ones.

Set up the best-preference mail exchanger normally (with the domain in
rcpthosts and either locals or virtualdomains). On the non-best-preference mail
exchangers, put the domain on rcpthosts only. This is how it's done.

Chris



Re: MX, ETRN and QMAIL

2000-01-18 Thread J.M. Roth \(iip\)

Ok, I understand. Didn't have anything like this before. Never mind.
But how can I determine then where exactly the mail is delivered in case it
arrives on the lower-preference one, if I can't use virtualdomains or
whatever...
Thanks again  Best regards

-- jmr

- Original Message -
From: "Chris Johnson" [EMAIL PROTECTED]
To: "J.M. Roth iip"" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, January 18, 2000 9:52 PM
Subject: Re: MX, ETRN and QMAIL


 On Tue, Jan 18, 2000 at 08:43:57PM +0100, J.M. Roth iip" wrote:
  Ok, sorry I meant virtualdomains.
 
  As I said I would like a backup in case example.com AND the queue for it
  fail.  This I've done with the MX records.
 
  One disadvantage is, since the domain must be in rcpthosts on the 3rd
machine
  to receive anything, *if* mail is sent using this machine as outgoing
mail
  server, it doesn't even get sent to example.com, even though it's higher
  preference...
  Got it?

 No. This is just not the case. rcpthosts only affects *incoming SMTP*
mail, and
 it has no affect whatsoever on where mail is ultimately delivered. It only
 determines whether your SMTP server will accept the message at the SMTP
"RCPT
 TO" command. It will *not* cause a lower-preference mail exchanger to
ignore
 better-preference ones.

 Set up the best-preference mail exchanger normally (with the domain in
 rcpthosts and either locals or virtualdomains). On the non-best-preference
mail
 exchangers, put the domain on rcpthosts only. This is how it's done.

 Chris




MX, ETRN and QMAIL

2000-01-17 Thread J.M. Roth \(iip\)



Hi there.

I have 3 MXs for a domain. The lowest preference MX is the 
local server. The other 2 are the customer's internal server as well as an SMTP 
queueing machine (ETRN etc.). The local machine is there in case the customer's 
server and the mail queue fails.
If I send mailusingthe local server (outgoing mail 
server) it doesn't even go to the higher preference MX servers but simply 
delivers locally, instead to the highest preference MX, that is the customer's 
server or its queue. The domain is listed in rcpthosts and 
virtualdomains.

Any idea?
If I omitted some details, please don't hesitate to 
ask.
J.M. Roth


Re: MX, ETRN and QMAIL

2000-01-17 Thread David Anso

The host receiveing your message isn't looking up in DNS for that MX record
because it's config say's it's allowed to handle the message itself.
Configuring the domain in /var/qmail/control/smtproutes might help, but then
if the other two servers go down the messages will just sit in the local
hosts queue until they expire or one of the hosts come up.

Also are you aware that a lower number for an MX record means a higher
preference.


Regards

David Anso
Network Administrator (daveland.co.nz)

Email:  [EMAIL PROTECTED]

- Original Message -
From: J.M. Roth (iip)
To: [EMAIL PROTECTED]
Sent: Tuesday, January 18, 2000 4:51 PM
Subject: MX, ETRN and QMAIL


Hi there.

I have 3 MXs for a domain. The lowest preference MX is the local server. The
other 2 are the customer's internal server as well as an SMTP queueing
machine (ETRN etc.). The local machine is there in case the customer's
server and the mail queue fails.
If I send mail using the local server (outgoing mail server) it doesn't even
go to the higher preference MX servers but simply delivers locally, instead
to the highest preference MX, that is the customer's server or its queue.
The domain is listed in rcpthosts and virtualdomains.

Any idea?
If I omitted some details, please don't hesitate to ask.

J.M. Roth



Re: MX, ETRN and QMAIL

2000-01-17 Thread Marc-Adrian Napoli

Hi All,

 The host receiveing your message isn't looking up in DNS for that MX
record
 because it's config say's it's allowed to handle the message itself.
 Configuring the domain in /var/qmail/control/smtproutes might help, but
then
 if the other two servers go down the messages will just sit in the local
 hosts queue until they expire or one of the hosts come up.

 Also are you aware that a lower number for an MX record means a higher
 preference.

Even if qmail is configured to handle mail for a domain (through rcpthosts)
it should do the lookup on the MX for that domain right?

I've had situations where we are the second priority mail server for a
domain , and sending mail from our mail server to their domain doesn't go to
their server but to the local machine because we have that domain in
rcpthosts. Once i've taken the domain out of rcpthosts file it goes to the
first priority mail server not a problem.

This seems to be intimittent, so i must be missing something here.

Anyone?

Regards,

Marc-Adrian Napoli
Connect Infobahn Australia
+61 2 92811750