On Mon, 15 Dec 2003, Gilad Ben-Yossef wrote:
On Monday 15 December 2003 15:27, Shachar Shemesh wrote:
Alon Altman wrote:Shachar,
Hi, Can you fix this?
Alon
This problem results from "stud.technion.ac.il" having a single name server, and that aserver being down. The only way to solve it is to bring to make sure that DNS resolving never fails for beak, for instance, by bringing up an official mirror DNS server for that domain.
I'm willing to set one up on fiasco, if you can get the technion admins to set up an additional NS record for the domain.
Are you sure? because the error message - "<[EMAIL PROTECTED]>: Sorry. Although I'm listed as a best-preference MX or A for that host, it isn't in my control/locals file, so I don't treat it as local. (#5.4.6)"
reads like it knows it an MX record for the domain (hence, DNS seems to be
working), but the domain isn't configured to be treated as local (or
virtual) so it doesn't know what to do with it.
The domain was configured like so: haifux.org. IN MX 10 vipe.technion.ac.il. haifux.org. IN MX 20 hamakor.org.il.
This means that beak was NOT the best-preference MX for that host. The only reason qmail thought it was is that vipe.technion.ac.il was not resolveable. My guess is that qmail assumed that this line is there by mistake, and totally ignored it. Taking Alon advice, and switching vipe for "haifux.org" (which must be resolveable, as it is hosted as a secondary DNS on beak) should solve that one.
That is already the case.My guess is that we need to allow relaying for all email going to the
haifux.org domain based on recipient domain name to get what the Haifux guys
want - a backup mail server that will accept the email and will deliver it
later when the real server is back on line.
No. qmail does not complain about the host not being in control/rcpthosts (the file dictating which hosts are ok for mai relay). It is complaining that it doesn't know how to perform a local delivery, which is mandated by it being the best MX record around.Does that make sense?
Actually, it would be even better if you forward all mail sent toI can do that, no problem. This will not solve the core issue, however. The problem was first reported to me this morning by Muli, when he tried to send mail to [EMAIL PROTECTED] You would still want this mail to be kept around by beak until vipe is back.
[EMAIL PROTECTED] (and only that address) to [EMAIL PROTECTED]
(our backup list server). Mail sent to other addresses should be retained
till vipe (=haifux.org) comes back again.
Also, to the best of my understanding, the backup list you mention will not forward the mails to the original list. It is just an alternative form of distribution, until the main list is back. As such, I'm not sure it's a good idea to perform this forward. If I'm wrong, just let me know and I'll do just that.
AlonWhile at it - anyone interested in a lecture about SMTP, DNS, and setting up these beasts with qmail? As an added bonus I can throw in ezmlm, virtual domains management (with and without vpopmail), mailbox vs. mail dirs, etc. I'm sending the same offer to Eddy of Telux - you have competition now :-)
Shachar
-- Shachar Shemesh Open Source integration & consulting Home page & resume - http://www.shemesh.biz/
-------------------------------------------------------------------------- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
