From owner-freebsd-isp Sun Jan 14 1:10:49 2001 Delivered-To: freebsd-isp@freebsd.org Received: from net2.dinoex.sub.org (net2.dinoex.de [212.184.201.182]) by hub.freebsd.org (Postfix) with ESMTP id C631937B401 for ; Sun, 14 Jan 2001 01:10:28 -0800 (PST) Received: from gate.dinoex.sub.org (dinoex@localhost) by net2.dinoex.sub.org (8.11.2/8.11.2) with BSMTP id f0E9A7B15194 for ; Sun, 14 Jan 2001 10:10:07 +0100 (CET) (envelope-from dirk.meyer@dinoex.sub.org) X-MDaemon-Deliver-To: To: freebsd-isp@FreeBSD.ORG Message-ID: <21e7dW2RC5@dmeyer.dinoex.sub.org> From: dirk.meyer@dinoex.sub.org (Dirk Meyer) Organization: privat Subject: Re: sendmail queue Date: Sun, 14 Jan 2001 10:04:23 +0100 X-Mailer: Dinoex 1.77 References: <3A613A19.3D7A6895@quake.com.au> <002401c07df7$ac1c3de0$0400a8c0@Home> X-Gateway: ZCONNECT gate.dinoex.sub.org [UNIX/Connect 0.90] X-Accept-Language: de,en X-PGP-Fingerprint: 44 16 EC 0A D3 3A 4F 28 8A 8A 47 93 F1 CF 2F 12 X-Noad: Please don't send me ad's by mail. I'm bored by this type of mail. X-Copyright: (C) Copyright 1999 by Dirk Meyer -- All rights reserved. X-Note: sending SPAM is a violation of both german and US law and will at least trigger a complaint at your provider's postmaster. X-PGP-Key-Avail: mailto:pgp-public-keys@keys.de.pgp.net Subject:GET 0x331CDA5D X-ZC-VIA: 20010114000000W+1@dinoex.sub.org Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ryan Masse wrote, > How will the SMS know what the primary MX record is if this machine is on a > sepereate network? how do i configure this? > > primary server---> > mail, web, ftp, etc > > secondary--> > only secondary mail server IT must be published in your DNS zone, here an example: www.some-domain.net. IN A 192.168.1.1 ftp.some-domain.net. CNAME www.some-domain.net. mail.some-domain.net. CNAME www.some-domain.net. backup.some-other.net. IN A 192.168.2.1 some-domain.net. IN MX 10 www.some-domain.net. some-domain.net. IN MX 20 backup.some-other.net. The number behind MX is the "Costs", so the lowest available server will win. > how does the secondary mail server 1. know to queue the mail and not send it > to a local inbox 2. know when to send the queued mail to the primary MX 3. > know the primary MX in the first place? --------------------------- 1a) The secondary mailserver needs a configuration line, by default he block relaying for it. But if he find a direction for this mail in his configuration, he will accept mail and handle it. in /etc/mail/mailtertable: (Like Leif suggested): # store only, wait for external REQUEST to deliver some-domain.net. dsmtp:[www.some-domain.net] 2a) In the first case the primary server must connect and issue and "ETRN" command, to tell the secondary to start delivering the mail to him. --------------------------- 1b) in /etc/mail/mailtertable: # for automatic delivery, secondary server will try it each queue run. some-domain.net. smtp:[www.some-domain.net] 2b) Sendmail will try each queue run, (can be 1 to 30 minutes) to deliver Mail. To reduce the times it trys to deliver you can configure it: define(`confMIN_QUEUE_AGE', `30m') in your *.mc files. or in the sendmail.cf file directly: # minimum time in queue before retry O MinQueueAge=30m --------------------------- 3) The secondary servers knows it cause it is written into the mailertable, as the next destination. In this example, "www.some-domain.net". kind regards Dirk - Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message