From [email protected] Thu May  2 13:43:14 1996 -0800
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA05858;
       Thu, 2 May 96 13:43:14 -0700
Received: by mx1.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA20196;
       Thu, 2 May 96 13:34:42 -0700
Errors-To: [email protected]
Sender: [email protected]
Received: from mailhost1.cac.washington.edu by mx1.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA20190;
       Thu, 2 May 96 13:34:41 -0700
Received: from bart.cac.washington.edu by mailhost1.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA12172;
       Thu, 2 May 96 13:34:40 -0700
Received: from shiva2.cac.washington.edu by bart.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA20128;
       Thu, 2 May 96 13:34:39 -0700
Date: Thu, 2 May 1996 13:34:38 -0700 (PDT)
From: Terry Gray <[email protected]>
To: Steffen Sledz <[email protected]>
Cc: [email protected]
Subject: Re: PCPine (W32) and POP3
In-Reply-To: <[email protected]>
Message-Id: <Pine.ULT.3.94.960502133319.23262M-100000@shiva2.cac.washington.edu>
Organization: University of Washington;  Computing & Communications
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Alas, PC-Pine does not yet support POP.
Planned for later.

-teg

On Tue, 30 Apr 1996, Steffen Sledz wrote:

> I've problems to setup my pcpine (W32) to use a POP3 server. On a UNIX-pine I
> use the line
>
> incoming-folders="name" {popserver.domain/pop3}
>
> without problems. The same line with pcpine results in an
>
> "invalid remote specification"
>
> Any ideas?
>
> Steffen
>
>
> Steffen Sledz           email:    [email protected]
> DEngineering              fon:    +49 30 93644161
> D-12681 Berlin            fax:    +49 30 93644199
> Germany
>



From [email protected] Thu May  2 13:51:17 1996 -0800
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA06318;
       Thu, 2 May 96 13:51:17 -0700
Received: by mx2.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA08277;
       Thu, 2 May 96 13:48:00 -0700
Errors-To: [email protected]
Sender: [email protected]
Received: from mailhost1.cac.washington.edu by mx2.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA08271;
       Thu, 2 May 96 13:47:58 -0700
Received: from bart.cac.washington.edu by mailhost1.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA12460;
       Thu, 2 May 96 13:47:57 -0700
Received: from shiva2.cac.washington.edu by bart.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA20227;
       Thu, 2 May 96 13:47:56 -0700
Date: Thu, 2 May 1996 13:47:55 -0700 (PDT)
From: Terry Gray <[email protected]>
To: Michael Pelletier <[email protected]>
Cc: [email protected]
Subject: Re: does pc-pine support the "offline" model?
In-Reply-To: <Pine.3.89.9605021341.A9759-0100000@sparc10>
Message-Id: <Pine.ULT.3.94.960502134737.23262N-100000@shiva2.cac.washington.edu>
Organization: University of Washington;  Computing & Communications
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Sorry... not yet.

-teg

On Thu, 2 May 1996, Michael Pelletier wrote:

> Does your newest release support "offline" model (like POP-3)?
>
>                       Michael J. Pelletier
>               System Administrator, Intrinsix Corp.
>                       [email protected]
>                          [email protected]
>                        508-836-4100 #304
>
>



From [email protected] Thu May  2 15:29:24 1996 -0800
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA10220;
       Thu, 2 May 96 15:29:24 -0700
Received: by mx1.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA23449;
       Thu, 2 May 96 15:22:34 -0700
Errors-To: [email protected]
Sender: [email protected]
Received: from lists.u.washington.edu by mx1.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA23443;
       Thu, 2 May 96 15:22:33 -0700
Received: from shiva1.cac.washington.edu by lists.u.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA14584;
       Thu, 2 May 96 15:22:25 -0700
Date: Thu, 2 May 1996 15:22:25 -0700 (PDT)
From: Steve Hubert <[email protected]>
To: 'Mentor Cana' <[email protected]>
Cc: [email protected]
Subject: Re: BUG?! Resent-Subject:
In-Reply-To: <Pine.SUN.3.92.960424141108.19879G-100000@menger.eecs.stevens-tech.edu>
Message-Id: <Pine.ULT.3.94.960502152211.28519N-100000@shiva1.cac.washington.edu>
Organization: University of Washington; Computing and Communications
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Thanks, will be fixed in 3.94.

Steve Hubert <[email protected]>
Networks and Distributed Computing, Univ. of Washington, Seattle


On Wed, 24 Apr 1996, 'Mentor Cana' wrote:

> Hi,
>
>  When you bounce a message in 3.92 there are additional header fields
>  appended to the mail message:
>  Resent-From:
>  Resent-To:
>  Resent-Date:
>  Resent-Subject:
>
>  The first three field are OK.. BUT, the Resent-Subject: field is empty!
>  Shouldn't this field take the value of Subject: or enable you to put
>  abother subject?
>
>  I'm a LISTSERV mialing list owner and often use the bounce command. Today,
>  I bounced few messages and they were distributed without the Subject:
>  line.
>
> sincerely,
> Mentor
>
>
>
>



From [email protected] Thu May  2 17:21:42 1996 -0800
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA15056;
       Thu, 2 May 96 17:21:42 -0700
Received: by mx1.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA26421;
       Thu, 2 May 96 17:18:05 -0700
Errors-To: [email protected]
Sender: [email protected]
Received: from rain.psg.com by mx1.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA26415;
       Thu, 2 May 96 17:18:03 -0700
Received: by rain.psg.com (Smail3.1.29.1 #1)
       id m0uF8Wo-00038FC; Thu, 2 May 96 17:15 PDT
To: [email protected]
From: "Jake P. Policky" <[email protected]>
Subject: Prom
Date: Wed, 1 May 1996 13:21:38 -0500
Message-Id: <Pine.SOL.3.91.960501131539.1229E-100000@hobbes>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I would like to just personally thank everyone who came to prom April
30th.  The Prom Kings were delighted to provide the music for everyone
for the second year running.  We hope to see an even bigger turn out next
year!
                               Thanks,
                                   Jake



From [email protected] Thu May  2 17:21:55 1996 -0800
Return-Path: <[email protected]>
Received: from mx2.cac.washington.edu by shivams.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA15081;
       Thu, 2 May 96 17:21:55 -0700
Received: by mx2.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA14413;
       Thu, 2 May 96 17:18:08 -0700
Errors-To: [email protected]
Sender: [email protected]
Received: from rain.psg.com by mx2.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA14406;
       Thu, 2 May 96 17:18:06 -0700
Received: by rain.psg.com (Smail3.1.29.1 #1)
       id m0uF8ZD-00038UC; Thu, 2 May 96 17:17 PDT
To: [email protected]
From: [email protected] (Chris Koenigsberg)
Subject: Re: Mail to all users...
Message-Id: <[email protected]>
References: <[email protected]>
Date: Thu, 2 May 1996 19:29:41 GMT


In article <[email protected]>,
Magnus Sundin - Postmaster Studentdatorutskottet  <[email protected]> wrote:
>I'm postmaster at Malardalen University's student server.
>Sometime we wish to send mail to all Users on our server...
>Is it possible to configure Pine to "send mail" to all users, not one copy
>in each users mailbox, just a link-message to a file that only appears
>once when the user access Pine...

Interesting question.

Note that for users who are logging in to interactive Unix accounts,
you have the "msgs" program to put out system messages, plus the
/etc/motd "message of the day" file. (unless they figure out
".hushlogin" :-)

Also if you can get everyone to read Usenet news, you can post to a
newsgroup and request that everyone subscribe to it. (voluntary
solutions like this are not always feasible or desirable though)

But if users are accessing their mail remotely via IMAP and not
logging in to your server, neither seeing "msgs" nor "/etc/motd", what
then?

Sending mail to all users, one copy to every mailbox, really is not
the ideal way to accomplish your goal.

Perhaps IMAP could use something like the "POP bulletin" facility,
available with the Qualcomm Pop3 server. This does exactly what you
suggest, it uses a single master copy of the message, which is then
automatically downloaded by every POP3 client. (well, so there ARE
multiple copies generated, one on each POP client's hard disk, but at
least not in every mailbox on the server system disk, and not going
through the mail queues and local mail delivery system!)

With POP bulletins, all POP3 users will see the latest bulletins added
since their last Inbox download session, as if they had actually been
delivered to the user's inbox (mail spool drop file). Bulletins are
accessed by the POP server as individual message files in a system
directory, e.g. /var/spool/pop. Every user has a ".popbull" file
recording the number of the last bulletin they have downloaded (we've
modified our copy of the server, to keep a user's record as
".username.popbull" in a common /var/spool/pop directory, so we can
have POP-only users with no home directory on the server)

We are hopefully going to offer IMAP-only service sometime in the
future, so we would be interested in such an "IMAP bulletin" facility.

I guess you COULD do it by requesting all users to subscribe to a
certain shared "sytem bulletin" IMAP mailbox... which could indeed be
a Usenet newsgroup ....

You COULD put such a subscription into the fixed global Pine config,
for interactive Unix login Pine users at least, but then again they
would all see the "msgs" and /etc/motd anyway.

The real question is, what about remote IMAP-only users, using
PC-Pine?

Chris Koenigsberg
U. of Chicago Academic Computing Services
[email protected], [email protected]
http://www2.uchicago.edu/ns-acs/ckk/index.html
(also http://www.pobox.com/~ckk)


From [email protected] Thu May  2 19:43:10 1996 -0800
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA18078;
       Thu, 2 May 96 19:43:10 -0700
Received: by mx1.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA28625;
       Thu, 2 May 96 19:41:13 -0700
Errors-To: [email protected]
Sender: [email protected]
Received: from mailhost2.cac.washington.edu by mx1.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA28619;
       Thu, 2 May 96 19:41:12 -0700
Received: from bart.cac.washington.edu by mailhost2.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA19717;
       Thu, 2 May 96 19:41:11 -0700
Received: from shiva1.cac.washington.edu by bart.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA24098;
       Thu, 2 May 96 19:41:10 -0700
Date: Thu, 2 May 1996 19:41:10 -0700 (PDT)
From: Terry Gray <[email protected]>
To: Chris Koenigsberg <[email protected]>
Cc: [email protected]
Subject: Re: Mail to all users...
In-Reply-To: <[email protected]>
Message-Id: <Pine.ULT.3.94.960502190203.2966C-100000@shiva1.cac.washington.edu>
Organization: University of Washington;  Computing & Communications
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Chris,
IMAP has the concept of an "ALERT", but this is oriented to single
line messages, e.g. "System going down in 20 min."

With Pine or PC-Pine, a user will be asked to acknowledge the alert.

There is nothing in IMAP to prevent stuffing a canned message in each
mailbox, but this would indeed take up space in every mailbox.

Some form of shared folder arrangement makes sense, but Pine doesn't
provide any particular help in making sure people see it.

-teg


On Thu, 2 May 1996, Chris Koenigsberg wrote:

> We are hopefully going to offer IMAP-only service sometime in the
> future, so we would be interested in such an "IMAP bulletin" facility.
>
> I guess you COULD do it by requesting all users to subscribe to a
> certain shared "sytem bulletin" IMAP mailbox... which could indeed be
> a Usenet newsgroup ....
>
> You COULD put such a subscription into the fixed global Pine config,
> for interactive Unix login Pine users at least, but then again they
> would all see the "msgs" and /etc/motd anyway.
>
> The real question is, what about remote IMAP-only users, using
> PC-Pine?
>
> Chris Koenigsberg
> U. of Chicago Academic Computing Services
> [email protected], [email protected]
> http://www2.uchicago.edu/ns-acs/ckk/index.html
> (also http://www.pobox.com/~ckk)
>



From [email protected] Thu May  2 20:17:01 1996 -0800
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA18526;
       Thu, 2 May 96 20:17:01 -0700
Received: by mx1.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA28987;
       Thu, 2 May 96 20:13:39 -0700
Errors-To: [email protected]
Sender: [email protected]
Received: from newton.ncsa.uiuc.edu by mx1.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA28981;
       Thu, 2 May 96 20:13:38 -0700
Received: from me.uwo.ca (ts9-11.slip.uwo.ca [129.100.99.86]) by newton.ncsa.uiuc.edu (8.6.11/8.6.12) with SMTP id WAA23402; Thu, 2 May 1996 22:08:54 -0500
Date: Thu, 2 May 1996 22:08:54 -0500
Message-Id: <[email protected]>
X-Sender: [email protected] (Unverified)
X-Mailer: Windows Eudora Light Version 1.5.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected], [email protected],
       [email protected], [email protected], [email protected],
       [email protected], [email protected], [email protected],
       [email protected], [email protected], [email protected],
       [email protected], [email protected], [email protected],
       [email protected], [email protected],
       umforth%[email protected],
       info-m2%[email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected], [email protected],
       [email protected], [email protected],
       [email protected],
       [email protected],
       [email protected],
       [email protected], [email protected],
       [email protected], [email protected], [email protected],
       [email protected], [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], csys-ami%[email protected],
       ami-hard%[email protected], ami-tech%[email protected],
       [email protected], [email protected],
       [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected], [email protected],
       [email protected]
From: - <[email protected]>
Subject: http://pobox.com/~jjjsmith


http://pobox.com/~jjjsmith

CHECK OUT THIS DYNAMIC NEW SITE! WOW!




From [email protected] Thu May  2 20:20:41 1996 -0800
Return-Path: <[email protected]>
Received: from mx1.cac.washington.edu by shivams.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA18611;
       Thu, 2 May 96 20:20:41 -0700
Received: by mx1.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA29056;
       Thu, 2 May 96 20:18:27 -0700
Errors-To: [email protected]
Sender: [email protected]
Received: from rain.psg.com by mx1.cac.washington.edu
       (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA29050;
       Thu, 2 May 96 20:18:25 -0700
Received: by rain.psg.com (Smail3.1.29.1 #1)
       id m0uFBMS-00038TC; Thu, 2 May 96 20:16 PDT
To: [email protected]
From: [email protected] (Clint Danbury)
Subject: Re: Money for ISP who can answer this question
Date: 3 May 1996 00:21:12 GMT
Message-Id: <[email protected]>
References: <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]>

Jon Trulson ([email protected]) wrote:
:
:       If that's the case... then why don't you simply set your
: TIN_DOMAIN environment value to ssnShirt.com?  Like
:
: TIN_DOMAIN=ssnShirt.com
: export TIN_DOMAIN
:
:       Then run tin...
:


Ok Jon, I have just taken your advice I typed...


       set TIN_DOMAIN=ssnShirt.com
       export TIN_DOMAIN
       tin


So, next day I'll find out if your advice works
in real life.  Also, if you're an ISP and can
give me a local connection, and this idea of
yours works, drop me some email and we'll
talk money.

You are viewing proxied material from ftp.icm.edu.pl. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.