Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Qmail: users

QMTP

 

 

First page Previous page 1 2 3 Next page Last page  View All Qmail users RSS feed   Index | Next | Previous | View Threaded


michael at surfnetcity

Oct 6, 1997, 5:30 AM

Post #1 of 56 (2769 views)
Permalink
QMTP

As I understand from another thread, qmtp is not a "registered" port.
This raises a couple of questions, and I was wondering if anybody new the
answers.

First, did Dan release an RFC for qmtp?
Second, is there any plan to register (or whatever you do) a port for
qmtp?
Third, what happens if somebody else registers the port that we use for
qmtp?
I know it is a case of taking things as we go, but the third question
might be a problem, especially if everybody using qmail gets told to
change their QMTP port.
Have I got it all wrong here, and qmtp is only meant for local networks or
something?



Michael Samuel,

Surf-Net City - Internet Cafe and Internet Service Provider
http://www.surfnetcity.com.au/
Phone: +61 3 9593-9977
mailto:michael [at] surfnetcity


markd at mira

Jul 6, 1998, 5:06 PM

Post #2 of 56 (2716 views)
Permalink
Re: qmtp [In reply to]

As far as I recall, the only thing that official supports it is
maildir2qmtp from the serialmail package. Note in THOUGHTS that DjB has
QMTP support as something he'd like to do at some stage.


Regards.




At 01:49 7/07/98 +0200, you wrote:
>What is the point in running qmtpd? I don't see any of the qmail programs
>trying to connect to anything but port 25, while qmtp is at port 209.
>
>Greetz, Peter.
>--
>'I guess anybody who walks away from a root shell at : Peter van Dijk
> a nerd party gets what they deserve!' -- BillSF :peter [at] attic
>-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>finger hardbeat [at] selweird for my public PGP-key
> - --- - --- - --- - --- - --- - --- - --- - --- - --- -
>
>
>


peter at attic

Jul 6, 1998, 5:13 PM

Post #3 of 56 (2713 views)
Permalink
Re: qmtp [In reply to]

On Tue, 7 Jul 1998, Mark Delany wrote:

> As far as I recall, the only thing that official supports it is
> maildir2qmtp from the serialmail package. Note in THOUGHTS that DjB has
> QMTP support as something he'd like to do at some stage.

Yeah, I've been browsing the archive and now I know... Although I can't find
the RFCMXPS document or whatever it was called.

> >What is the point in running qmtpd? I don't see any of the qmail programs
> >trying to connect to anything but port 25, while qmtp is at port 209.

So.. Dan! When will we have QMTP support, so our mail gets in and out even
faster?

Greetz, Peter.
--
'I guess anybody who walks away from a root shell at : Peter van Dijk
a nerd party gets what they deserve!' -- BillSF :peter [at] attic
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
finger hardbeat [at] sabsoft for my public PGP-key
- --- - --- - --- - --- - --- - --- - --- - --- - --- -


mirko at picard

Jan 13, 1999, 7:23 AM

Post #4 of 56 (2727 views)
Permalink
Re: qmtp [In reply to]

On Wed, Jan 13, 1999 at 07:03:46AM -0700, Vern Hart wrote:
> So, uh, does anyone know if djb has figured out how to add qmtp delivery
> to qmail?
>
> And speaking of qmtp, the FAQ says to run it you do:
>
> tcpserver -u 7770 -g 2108 0 qmtp /var/qmail/bin/qmail-qmtpd &
>
> But doesn't that open you up as a relay? Or does qmtp have something
> built in that keeps unwanted relaying from happening?
Hello Vern, why don't you just specify rules for your tcpserver, I am doing
similar with xinetd for qmail-smtpd, so only company-users (or at least
those with a company-IP ;-)) may use it. As I configured some IP-filters
too, which will not allow any private company-IPs coming from the
outer-device (ISDN in fact), I am pretty sure that abuse is +- unavailable.

Regards
Mirko
--


vern at hart

Jan 13, 1999, 8:20 AM

Post #5 of 56 (2729 views)
Permalink
Re: qmtp [In reply to]

On Wed, 13 Jan 1999, Mirko Zeibig wrote:
>
> > And speaking of qmtp, the FAQ says to run it you do:
> >
> > tcpserver -u 7770 -g 2108 0 qmtp /var/qmail/bin/qmail-qmtpd &
> >
> > But doesn't that open you up as a relay? Or does qmtp have something
> > built in that keeps unwanted relaying from happening?
>
> Hello Vern, why don't you just specify rules for your tcpserver, I am doing

I was only pointing out that the instructions in the FAQ don't suggest
specifying rules. While I doubt spammers know how to send mail via qmtp
I wouldn't put it past them to figure out how.

Rules are a good thing.

Vern
--
,+'^'+,
Vern Hart O Creative Design Engineer - The Hungry Programmers
`+,.,+' vern [at] hungry http://www.hungry.org

8:20am up 31 day(s), 22:29, 20 users, load average: 0.34, 0.20, 0.18


mw at wierdlmpc

Jan 13, 1999, 8:48 AM

Post #6 of 56 (2716 views)
Permalink
Re: qmtp [In reply to]

On Wed, 13 Jan 1999, Mirko Zeibig wrote:
>
> > And speaking of qmtp, the FAQ says to run it you do:
> >
> > tcpserver -u 7770 -g 2108 0 qmtp /var/qmail/bin/qmail-qmtpd &
> >
> > But doesn't that open you up as a relay? Or does qmtp have something
> > built in that keeps unwanted relaying from happening?
>
> Hello Vern, why don't you just specify rules for your tcpserver, I am doing

I was only pointing out that the instructions in the FAQ don't suggest
specifying rules. While I doubt spammers know how to send mail via qmtp
I wouldn't put it past them to figure out how.

But you can read man qmail-qmtpd which tells you that relaycontrol is
exactly the same as for qmail-smtpd. It is just not a FAQ---b/c most
people are not using qmtpd.

Mate


adam at flounder

Jan 13, 1999, 8:54 AM

Post #7 of 56 (2694 views)
Permalink
Re: qmtp [In reply to]

Are there currently any everyday uses for qmtp? i.e. would it benefit me to
run it along with qmail-smtpd? Or is it pretty much only for specific
applications right now (such as mailing list hubs etc)..

-Adam


vern at hart

Jan 13, 1999, 8:56 AM

Post #8 of 56 (2699 views)
Permalink
Re: qmtp [In reply to]

On Wed, 13 Jan 1999, Mate Wierdl wrote:
>
> But you can read man qmail-qmtpd which tells you that relaycontrol is
> exactly the same as for qmail-smtpd. It is just not a FAQ---b/c most
> people are not using qmtpd.

Which brings us back to my original question:

> So, uh, does anyone know if djb has figured out how to add qmtp
> delivery to qmail?

Vern
--
,+'^'+,
Vern Hart O Creative Design Engineer - The Hungry Programmers
`+,.,+' vern [at] hungry http://www.hungry.org

8:56am up 31 day(s), 23:05, 21 users, load average: 0.16, 0.18, 0.20


adam at flounder

Jan 13, 1999, 10:18 AM

Post #9 of 56 (2731 views)
Permalink
Re: qmtp [In reply to]

From: Vern Hart <vern [at] hart>


> So, uh, does anyone know if djb has figured out how to add qmtp
> delivery to qmail?

How about something like this:

@ IN SOA flounder.net. hostmaster.flounder.net. (
1998100501 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Default TTL
;
@ IN NS ns1.flounder.net.
@ IN NS ns2.flounder.net.
@ IN MX ariel.flounder.net.
@ IN TXT "qmtp"

I know this has been suggested before. I was wondering what was wrong with
it..

--Adam


lyonsm at netbistro

Jan 13, 1999, 5:00 PM

Post #10 of 56 (2709 views)
Permalink
Re: qmtp [In reply to]

On Wed, 13 Jan 1999, Adam D. McKenna wrote:

> @ IN TXT "qmtp"

> I know this has been suggested before. I was wondering what was wrong with
> it..

IIRC, something about latency due to additional DNS lookups eating
whatever benefit QMTP would have provided in the first place.

DJB has documented a way to abuse MX preference values to indicate that
QMTP should be tried first when connecting to a given MX. Since MX'es
need to be looked up anyway, it's only apparent cost (ignoring than the
inherent ugliness of abusing MX preferences in this way) seems to be the
potential occasional QMTP connection attempt to sites that happen to use
certain high MX preferences, but don't run QMTP server, and employ
easily-spooked firewall administrators.

ftp://koobera.math.uic.edu/www/proto/mxps.txt

According to qmail/future.html, a "future version of qmail-remote" will
support this (or some similar) mechanism.


markd at mira

Jan 13, 1999, 5:22 PM

Post #11 of 56 (2738 views)
Permalink
Re: qmtp [In reply to]

Somewhere on DjB's web page is a "future" document wrt qmail where I recall
that he seems to have settled on using high valued MX preferences to
indicate a QMTP server.

IN MX 300001 some.host

means a QMTP server with a preference of 1.

Or some such.


Regards.

At 04:00 PM 1/13/99 -0800, M Lyons wrote:
>On Wed, 13 Jan 1999, Adam D. McKenna wrote:
>
>> @ IN TXT "qmtp"
>
>> I know this has been suggested before. I was wondering what was wrong with
>> it..
>
>IIRC, something about latency due to additional DNS lookups eating
>whatever benefit QMTP would have provided in the first place.
>
>DJB has documented a way to abuse MX preference values to indicate that
>QMTP should be tried first when connecting to a given MX. Since MX'es
>need to be looked up anyway, it's only apparent cost (ignoring than the
>inherent ugliness of abusing MX preferences in this way) seems to be the
>potential occasional QMTP connection attempt to sites that happen to use
>certain high MX preferences, but don't run QMTP server, and employ
>easily-spooked firewall administrators.
>
> ftp://koobera.math.uic.edu/www/proto/mxps.txt
>
>According to qmail/future.html, a "future version of qmail-remote" will
>support this (or some similar) mechanism.
>
>


nelson at crynwr

Jan 13, 1999, 8:01 PM

Post #12 of 56 (2709 views)
Permalink
Re: qmtp [In reply to]

M Lyons writes:
> Since MX'es need to be looked up anyway, it's only apparent cost
> (ignoring than the inherent ugliness of abusing MX preferences in
> this way)

Oh pish! It's not "abuse", it's an "hinting extension". Anything can
be tolerated if it has a fancy name.

> seems to be the potential occasional QMTP connection
> attempt to sites that happen to use certain high MX preferences,
> but don't run QMTP server, and employ easily-spooked firewall
> administrators.

If anyone happens to take offense, they can lower their MX preference
to something similar to what most people use. As I recall from the
last time this came up, only one host conflicted, of the hundreds of
hosts that happened to be the cache of my nameserver.

Of 4,381 MX records, only three come close to being in range:

31000 mailgateway1.uni-freiburg.de. ;Cr=auth [132.230.200.200]
32000 clark.net. ;Cr=answer [198.17.243.6]
32000 mailgateway2.uni-freiburg.de. ;Cr=auth [132.230.200.200]

--
-russ nelson <rn-sig [at] crynwr> http://crynwr.com/~nelson
Crynwr supports Open Source(tm) Software| PGPok | There is good evidence
521 Pleasant Valley Rd. | +1 315 268 1925 voice | that freedom is the
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | cause of world peace.


lyonsm at netbistro

Jan 14, 1999, 2:38 PM

Post #13 of 56 (2719 views)
Permalink
Re: qmtp [In reply to]

On 14 Jan 1999, Russell Nelson wrote:

> If anyone happens to take offense, they can lower their MX preference
> to something similar to what most people use. As I recall from the
> last time this came up, only one host conflicted, of the hundreds of
> hosts that happened to be the cache of my nameserver.

That's interesting. Out of curiosity, did you check out the conflicting
host? It would be incredibly ironic if the "conflicting" host turned out
to be running a QMTP server. :)


djb at cr

Jan 14, 1999, 6:32 PM

Post #14 of 56 (2695 views)
Permalink
Re: qmtp [In reply to]

I'm going to use a special MX host name format instead of special MX
preferences. The basic options will be

_magic.s.* I can receive mail by SMTP
_magic.q.* I can receive mail by QMTP
_magic.qs.* I can receive mail by QMTP or SMTP

with the possibility of future extensions such as

_magic.abcdqrsz.*

The client can select its favorite protocol. Of course, the server will
have to support SMTP for compatibility, whether or not SMTP is listed.

---Dan


rra at stanford

Jan 14, 1999, 6:38 PM

Post #15 of 56 (2705 views)
Permalink
Re: qmtp [In reply to]

D J Bernstein <djb [at] cr> writes:

> I'm going to use a special MX host name format instead of special MX
> preferences. The basic options will be

> _magic.s.* I can receive mail by SMTP
> _magic.q.* I can receive mail by QMTP
> _magic.qs.* I can receive mail by QMTP or SMTP

> with the possibility of future extensions such as

> _magic.abcdqrsz.*

> The client can select its favorite protocol. Of course, the server will
> have to support SMTP for compatibility, whether or not SMTP is listed.

That looks very similar to an RFC format... If you use _qmtp rather than
_magic.q and the existence of both _qmtp and _smtp records as indicating
that a host wants both types, doesn't it become basically identical to the
RFC format? If so, I don't see much gained by favoring one over the
other, and hence would tend towards staying with the compatible format.

--
Russ Allbery (rra [at] stanford) <URL:http://www.eyrie.org/~eagle/>


schwartz at bio

Jan 14, 1999, 6:54 PM

Post #16 of 56 (2718 views)
Permalink
Re: qmtp [In reply to]

Russ Allbery <rra [at] stanford> writes:
| That looks very similar to an RFC format... If you use _qmtp rather than
| _magic.q and the existence of both _qmtp and _smtp records as indicating
| that a host wants both types, doesn't it become basically identical to the
| RFC format? If so, I don't see much gained by favoring one over the
| other, and hence would tend towards staying with the compatible format.

If I understand correctly, Dan's proposal enables you to have just one
MX record per-host, rather than one MX record per-protocol per-host. I
imagine that's a reasonable efficiency concern, even if your MTA
doesn't artificially limit DNS replies to some small size.


shag at alter

Jan 14, 1999, 7:13 PM

Post #17 of 56 (2740 views)
Permalink
Re: qmtp [In reply to]

Minor quibble - see RFC 1912:

Allowable characters in a label for a host name are only ASCII
letters, digits, and the `-' character.... The presence
of underscores in a label is allowed in [RFC 1033], except [RFC 1033]
is informational only and was not defining a standard. There is at
least one popular TCP/IP implementation which currently refuses to
talk to hosts named with underscores in them.

But then right after that:

If a domain name is to be used for mail (not involving SMTP), it must
follow the rules for mail in [RFC 822], which is actually more
liberal than the above rules.

So does this mean that underscores are okay for MX records? I would say
no, since MX hosts are "host" names and not "domain" names.

If you're wondering how I know this, it's because I can remember at least
three instances where customers had underscores in the hostname of their
machines and they got all sorts of strange errors until we figured this
out. It's mostly NT people who do this; for some reason they don't like
dashes. However, the nameserver code was stock BIND (I forget which
version, 4.9.x I believe, but I haven't investigated the issue with BIND
8).

Personally I think it would be better simply to start using another port
besides 25. That's a simple and straightforward solution. Let people
who want to use QMTP use it by checking to see if the port is open. If
it's not fall back to SMTP and be done with it. Don't bother with the
DNS check. Or am I missing something here?

my $0.02-
shag

-----Original Message-----
From: D. J. Bernstein <djb [at] cr>
To: qmail [at] list <qmail [at] list>
Date: Thursday, January 14, 1999 5:32 PM
Subject: Re: qmtp


>I'm going to use a special MX host name format instead of special MX
>preferences. The basic options will be
>
> _magic.s.* I can receive mail by SMTP
> _magic.q.* I can receive mail by QMTP
> _magic.qs.* I can receive mail by QMTP or SMTP
>
>with the possibility of future extensions such as
>
> _magic.abcdqrsz.*
>
>The client can select its favorite protocol. Of course, the server will
>have to support SMTP for compatibility, whether or not SMTP is listed.
>
>---Dan
>


schwartz at bio

Jan 14, 1999, 7:50 PM

Post #18 of 56 (2695 views)
Permalink
Re: qmtp [In reply to]

"Racer X" <shag [at] alter> writes:
| Personally I think it would be better simply to start using another port
| besides 25. That's a simple and straightforward solution. Let people
| who want to use QMTP use it by checking to see if the port is open. If
| it's not fall back to SMTP and be done with it. Don't bother with the
| DNS check. Or am I missing something here?

The stock reply is that the latency induced by checking for nonexistant
qmtp servers would defeat its advantages. However, since bandwidth is
infinite, you could get around that by trying the qmtp and smtp
connections in parallel, and abort whichever one is still going when
the fast one finishes.


Jason.Haar at trimble

Jan 14, 1999, 7:51 PM

Post #19 of 56 (2706 views)
Permalink
Re: qmtp [In reply to]

On Thu, Jan 14, 1999 at 06:13:52PM -0800, Racer X wrote:
> Minor quibble - see RFC 1912:
>
> Allowable characters in a label for a host name are only ASCII
> letters, digits, and the `-' character.... The presence
> of underscores in a label is allowed in [RFC 1033], except [RFC 1033]
> is informational only and was not defining a standard. There is at
> least one popular TCP/IP implementation which currently refuses to
> talk to hosts named with underscores in them.
>

Yup - some implementors specifically filter against underscores.

e.g. The Web proxy server Squid doesn't allow underscores in URLs as they
"aren't allowed according to RFCxxx"...

[.Althought DJB could have meant "_magic" as a string yet to defined of
course...]

--
Cheers

Jason Haar

Unix/Network Specialist, Trimble NZ
Phone: +64 3 3391 377 Fax: +64 3 3391 417


adam at flounder

Jan 14, 1999, 8:01 PM

Post #20 of 56 (2725 views)
Permalink
Re: qmtp [In reply to]

er, why not just make a new command? screw the rfc's!!! :)

220 flounder.net ESMTP
qmtp
250 qmtp mode enabled
[etc..]

--Adam

----- Original Message -----
From: Scott Schwartz <schwartz [at] bio>
To: <qmail [at] list>
Sent: Thursday, January 14, 1999 9:50 PM
Subject: Re: qmtp


:"Racer X" <shag [at] alter> writes:
:| Personally I think it would be better simply to start using another port
:| besides 25. That's a simple and straightforward solution. Let people
:| who want to use QMTP use it by checking to see if the port is open. If
:| it's not fall back to SMTP and be done with it. Don't bother with the
:| DNS check. Or am I missing something here?
:
:The stock reply is that the latency induced by checking for nonexistant
:qmtp servers would defeat its advantages. However, since bandwidth is
:infinite, you could get around that by trying the qmtp and smtp
:connections in parallel, and abort whichever one is still going when
:the fast one finishes.
:
:


mw at moni

Jan 14, 1999, 8:21 PM

Post #21 of 56 (2695 views)
Permalink
Re: qmtp [In reply to]

On Fri, Jan 15, 1999 at 01:32:45AM -0000, D. J. Bernstein wrote:
> I'm going to use a special MX host name format instead of special MX
> preferences. The basic options will be
>
> _magic.s.* I can receive mail by SMTP
> _magic.q.* I can receive mail by QMTP
> _magic.qs.* I can receive mail by QMTP or SMTP
>

What is the meaning of all these? What is _magic.q.*, say? A host name
that is capable of receiving via qmtp would start with _magic.q.? So an MX
record would be like

movie.edu IN MX 10 _magic.q.movie.edu

Mate


dkelson at inconnect

Jan 14, 1999, 8:50 PM

Post #22 of 56 (2707 views)
Permalink
Re: qmtp [In reply to]

On Thu, 14 Jan 1999, Racer X wrote:

> Personally I think it would be better simply to start using another port
> besides 25. That's a simple and straightforward solution. Let people
> who want to use QMTP use it by checking to see if the port is open. If
> it's not fall back to SMTP and be done with it. Don't bother with the
> DNS check. Or am I missing something here?

A lot of people firewall off unused ports, so you would wait along time
for the connection attempt to time out.

Encoding the capabilities in the MX record host name is a good idea,
although there shouldn't be any underscores.

Dax Kelson
Internet Connect, Inc.


markd at mira

Jan 14, 1999, 9:26 PM

Post #23 of 56 (2705 views)
Permalink
Re: qmtp [In reply to]

At 09:21 PM 1/14/99 -0600, Mate Wierdl wrote:
>On Fri, Jan 15, 1999 at 01:32:45AM -0000, D. J. Bernstein wrote:
>> I'm going to use a special MX host name format instead of special MX
>> preferences. The basic options will be
>>
>> _magic.s.* I can receive mail by SMTP
>> _magic.q.* I can receive mail by QMTP
>> _magic.qs.* I can receive mail by QMTP or SMTP
>>
>
>What is the meaning of all these? What is _magic.q.*, say? A host name
>that is capable of receiving via qmtp would start with _magic.q.? So an MX
>record would be like
>
>movie.edu IN MX 10 _magic.q.movie.edu

Exactly.

And one that can do smtp and qmtp would be:

movie.edu IN MX 10 _magic.qs.movie.edu

Whether the "_magic" is literal or not is an interesting question. As a
literal has merit from the perspective of reducing collisions in the namespace.


Regards.


vern at hart

Jan 15, 1999, 1:13 AM

Post #24 of 56 (2720 views)
Permalink
Re: qmtp [In reply to]

On 15 Jan 1999, D. J. Bernstein wrote:
>
> I'm going to use a special MX host name format instead of special MX
> preferences. The basic options will be
>
> _magic.s.* I can receive mail by SMTP
> _magic.q.* I can receive mail by QMTP
> _magic.qs.* I can receive mail by QMTP or SMTP

Dan,

I assume you mean this to be implemented in dns thusly:

@ IN MX _magic.qs.domain.com.
_magic.qs IN A 1.2.3.4

Right?

Is _magic a literal string or do you plan on changing it?

The underscore doesn't work with bind8 (as tested on 8.1.1). Here's the
errors I get (clipped from syslog):

named[2713]: host name "_magic.qs.hart.com" (owner "hart.com") IN
(primary) is invalid - rejecting
named[2713]: hart.com:19: database naming error
named[2713]: hart.com:19: Database error (bad name
"_magic.qs.hart.com")
named[2713]: master zone "hart.com" (IN) rejected due to errors
(serial 1999011400)

So, what is the "_magic" string going to be?

Vern
--
,+'^'+,
Vern Hart O Creative Design Engineer - The Hungry Programmers
`+,.,+' vern [at] hungry http://www.hungry.org

1:12am up 33 day(s), 15:21, 16 users, load average: 0.10, 0.59, 0.83


ghudson at MIT

Jan 15, 1999, 5:32 AM

Post #25 of 56 (2741 views)
Permalink
Re: qmtp [In reply to]

Some notes on Dan's latest MXPS proposal, in the interest of maximal
awareness:

Russ Allbery suggested that it looked "very similar to an RFC format."
It bears no resemblance to any RFC I've seen. What Russ is thinking
of is son-of-RFC2052bis, which specifies a new RR type (SRV) which
looks like a generalized MX record. The standard name for a SRV
record (which is not not not an A record, no way, no how) according to
that draft is _foo._bar.domain. While I think the SRV record is the
best thing since sliced bread for new protocols, it doesn't have any
application for Dan in this area because he isn't interested in doing
an extra DNS lookup for all but epsilon of every current mail
delivery. (Incidentally, the way to use SRV as a protocol switch here
would be to do a single SRV query for _mail._tcp.domain and use the
port number in the returned records to decide which protocol to use.
But that's still an extra DNS lookup for every current mail receiver.)

Racer X asked about the underscores in Dan's proposal. Is the
domain-name part of an MX record a hostname? This is an interesting
question; it depends on who you ask. Paul Vixie (author of BIND) says
yes, while kre (co-chair of the dnsind working group) says no. The
host requirements RFC supports Paul, by my reading, but I'm just this
guy. At any rate, my past experience suggests that Dan couldn't give
a rat's ass whether the RFCs say it's okay, he only cares about what
works. Putting an underscore in the string "_magic" makes it unlikely
that anyone has existing MX records which will cause a false positive
for QMTP.

So what about BIND and putting underscores in A records? For modern
versions of BIND, you'll have to configure named to turn off checking
for underscores, or it will enforce that every A record in the master
file conforms to the hostname rules. I'm no BIND expert, but I
believe this requires BIND 8, and you can say in named.conf:

options { check-names master ignore; };
or zone "foo" { check-names ignore; ... };

If you have slave servers outside your administrative control, they
will give warnings and you might get flack about it. If this is a
problem or if you're using BIND 4.9.x, then the sky doesn't fall; you
just don't get to tell people to transfer mail to you using QMTP.

First page Previous page 1 2 3 Next page Last page  View All Qmail users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.