NetNews Usenet Archive 1992 #20/NN_1992_20.iso/spool/vmsnet/mail/pmdf/2302

Internet Message Format | 1992-09-15 | 1.8 KB

Path: sparky!uunet!decwrl!infopiz!mccall!ipmdf-newsgate!list
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Notifying POP3 users of new mail.
Message-ID: <[e-mail]>
From: Ned Freed <[e-mail]>
Date: 15 Sep 1992 02:18:31 -0700 (PDT)
Organization: The Internet
Return-Path: <[e-mail]>
Resent-Date: 15 Sep 1992 02:18:31 -0700 (PDT)
Resent-From: [e-mail]
Errors-To: [e-mail]
Resent-Message-ID: <[e-mail]>
X-Vms-To: IN%"[e-mail]"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Lines: 25

This cannot be done efficiently in MASTER.COM -- it would require breaking
out of VMS MAIL for each message, and the overhead cost of doing this
is really huge. It is unfortunate that firing up VMS MAIL is expensive,
but it is and there's nothing we can do about it. It is also fairly
nontrivial to do the translation of local channel addresses into
meaningful usernames -- the rules for this are complex and far from
obvious.

The best way to do this would be for us to provide a hook in the local
delivery process to call some of your code. The best we could do
would be to give you the address we're passing to VMS MAIL (this is quite
different from the original recipient address). You could then go off
and do whatever you want with it.

Another possibility is for us to send out the notice ourselves. But
this requires some knowledge of the protocol used to ring up the
PC. POP is only a remote mail access protocol; it doesn't have remote
notification capability as far as I know. So what protocol do you use for
this?

We would probably just add the hook in any case; but we could also
write the specific module to deliver these notifications if, say,
Multinet is what you use as a transport.

                Ned