On Tue, Apr 06, 1999 at 07:40:59PM -0400, Peter C. Norton wrote:
On Tue, Apr 06, 1999 at 06:31:03PM -0500, Chris Garrigues wrote:
netstat -a |fgrep '*:qmtp'
or the low-level C equivalent.
I'm not concerned with this. I'm concerned with Fred's proposal
relying on the status of
On Wed, Apr 07, 1999 at 08:53:29AM -0500, Fred Lindberg wrote:
Since SMTP and QMTP are linked anyway, the advertizing of QMTP by the
SMTP server could easily be linked to QMTP being up. Thus, a working
smtpd with a failed qmtpd (admin forgot to start?) would not advertize
QMTP. This would
On Tue, 6 Apr 1999, Peter C. Norton wrote:
On Tue, Apr 06, 1999 at 06:31:03PM -0500, Chris Garrigues wrote:
netstat -a |fgrep '*:qmtp'
or the low-level C equivalent.
I'm not concerned with this. I'm concerned with Fred's proposal
relying on the status of the remote smtp and
From: Richard Letts [EMAIL PROTECTED]
Date: Wed, 7 Apr 1999 19:06:04 +0100 (BST)
On Tue, 6 Apr 1999, Peter C. Norton wrote:
On Tue, Apr 06, 1999 at 06:31:03PM -0500, Chris Garrigues wrote:
netstat -a |fgrep '*:qmtp'
or the low-level C equivalent.
I'm not concerned
On Wed, 7 Apr 1999 10:37:48 -0400, Chris Johnson wrote:
Why not just implement QMTP in qmail-smtpd? qmail-smtpd would advertise QMTP in
its banner, and then the host connecting would be free to start firing away in
QMTP lingo. There would never be any question of QMTP being up, since
qmail-smtpd
On Wed, Apr 07, 1999 at 10:37:48AM -0400, Chris Johnson wrote:
On Wed, Apr 07, 1999 at 08:53:29AM -0500, Fred Lindberg wrote:
Since SMTP and QMTP are linked anyway, the advertizing of QMTP by the
SMTP server could easily be linked to QMTP being up. Thus, a working
smtpd with a failed qmtpd
On Wed, Apr 07, 1999 at 09:42:18AM +0200, Peter van Dijk wrote:
Well extend it a bit to ignore qmtp in smtp banners for like one hour if qmtp turns
out to be _not_ available. No big deal.
Right. I just wanted to throw that into the proposal. An hour is
probably a good long time.
-Peter
Instead of MX magic, would it be possible to use a local cache to keep
track of QMTP-capable hosts?
QMTP is most useful for hosts that we talk to often and [with
multi-recipient protocols] with smarthosts, etc. Thus, it should be
possible to use SMTP by default, recognize from the banner that
On Tue, Apr 06, 1999 at 05:57:37PM -0500, Fred Lindberg wrote:
When sending, one would look up host names in the cdb, and if
QMTP-capable start a QMTP dialog. If it fails, the db can be updated
with that info (it doesn't matter if it takes a while to make it to the
cdb since this should be
From: "Peter C. Norton" [EMAIL PROTECTED]
Date: Tue, 6 Apr 1999 19:26:46 -0400
The outbound smtp agent would have to be aware somehow of the
activities of its fellow outbound qmtp server. If the smtp listener
on a remote site is advertising qmtp, and its qmtp server is not
responding
10 matches
Mail list logo
