headers
Fu Bar | 1 Nov 1995 03:57
Favicon

Re: [Linux-ISP] Re: checking logins for pop3

On Tue, 31 Oct 1995, Tim 'pass the Prozac' Sailer wrote:

> > Is the Qualcom popper comercial or freeware? Where can I find it?
>
> Free. ftp://ftp.qualcomm.com/

I just had to switch back to the pop3d that comes with Pine.  We've been
using the Qualcomm popper for a few weeks, but tongiht I got a call from
someone who could not read his mail via POP3.

When I telnetted directly to the port and logged in as him, I got the
following:

Unable to process From lines (envelops), change recognition modes.

This message comes from pop_dropcopy.c, but I'm not quite sure what  
causes it.  The headers in his mail spool on several messages were pretty
strange:

>>From oyster::mrgate::"a1::lezotte, philip a." <at> oyster.monsanto.com  Wed
>>Oct 18 14:21:51 1995 
>>Return-Path: oyster::mrgate::"a1::lezotte, philip a." <at> oyster.monsanto.com
>>Received: from tin (tin.monsanto.com [137.35.4.90]) by yoda.fdt.net
>>(8.6.12/8.6.9) with SMTP id OAA26043 for <lalezo <at> yoda.fdt.net>; Wed, 18
>>Oct 1995 14:21:49 -0400
>>From: oyster::mrgate::"a1::lezotte, philip a." <at> oyster.monsanto.com
>>Oct 18 14:21:51 1995
>>Return-Path: oyster::mrgate::"a1::lezotte, philip a." <at> oyster.monsanto.com
>>Received: from tin (tin.monsanto.com [137.35.4.90]) by yoda.fdt.net
>>(8.6.12/8.6.9) with SMTP id OAA26043 for <lalezo <at> yoda.fdt.net>; Wed, 18
(Continue reading)

Permalink | Reply | 3 comments |
headers
Jon Lewis | 1 Nov 1995 04:01
Picon

Re: Filtering Spam (was Re: A Call To Responsibility...)

On Tue, 31 Oct 1995, David Brownlee wrote:

> 	One idea (if you have CPU to burn)...
> 
> 	Pipe all messages to a small C program that parses the from
> 	address and rejects any that come from ' <at> site' where site does
> 	not hava valid A or MX record in the dns... (Maybe check
> 	Reply-To: as well...)
> 
> 	(As you would not be able to reply to them anyway :)

Interesting idea...but if you really have CPU/RAM to burn, do it in 
perl.  Actually, it seems like something that should be integrated into 
sendmail...if it's not already :-)

------------------------------------------------------------------
 Jon Lewis                      |  Mime attachments are OK
 jlewis <at> inorganic5.chem.ufl.edu |  But please ask before sending 
 http://inorganic5.chem.ufl.edu |  unsolicited huge files.
                                |  
_____Finger jlewis <at> inorganic5.chem.ufl.edu for PGP public key_____
Permalink | Reply | 1 comment |
headers
Fu Bar | 1 Nov 1995 05:25
Favicon

Re: [Linux-ISP] Re: checking logins for pop3

On Tue, 31 Oct 1995, Tim 'pass the Prozac' Sailer wrote:

> > Pine had no trouble reading messages like this, so I decided to try Pine's
> > in.pop3d, and it worked as well.  We had some problem many weeks ago with
> > in.pop3d, and that was the reason we switched to the Qualcomm popper...but
> > now I can't remember what the problem was. 
> 
> The real strange thing about this is you could have *no* pop3d running
> and Pine will still read the mail, since it uses imapd... :)

Um...pine could read it with no imapd too since it's setup here to read 
directly from the /var/spool/mail/$user file.

I suppose the people at University of Washington do things differently 
than the people at University of California.  Both Pine (reading the mail 
spool directly) and Pine's pop3d read the file just fine.  Popper chokes 
on it.  I haven't tried imap...I never learned the commands necessary to 
talk directly to impad as I can with pop3d.
Permalink | Reply | 0 comments |
headers
Bugs Bunny | 1 Nov 1995 14:58

Re: Filtering Spam (was Re: A Call To Responsibility...)

Jon Lewis writes on 31 October 1995 at 22:01:33
>On Tue, 31 Oct 1995, David Brownlee wrote:
>
>> 	One idea (if you have CPU to burn)...
>> 
>> 	Pipe all messages to a small C program that parses the from
>> 	address and rejects any that come from ' <at> site' where site does
>> 	not hava valid A or MX record in the dns... (Maybe check
>> 	[...]
>
>perl.  Actually, it seems like something that should be integrated into 
>sendmail...if it's not already :-)

That wouldn't be any fun now, would it? :-)

And doing so would probably add a lot of overhead to sendmail.

   Dan
--------------------- message is author's opinion only --------------------
J. Daniel Smith <DanS <at> bristol.com>              http://www.bristol.com/~dan
Bristol Technology Inc.	                    +1 203 438 6969, 438-5013 (FAX)
Ridgefield, Connecticut (USA)                       {info,jobs} <at> bristol.com
                                 --------
Von guten Maechten wunderbar geboren, erwarten wir getrost, was kommen
mag.  Gott ist mit uns am Abend und am Morgen, und ganz gewiss an
jedem neuen Tag.   - Dietrich Bonhoeffer
Permalink | Reply | 0 comments |
headers
Stephen R. van den Berg | 1 Nov 1995 15:33
Picon
Gravatar

Re: [Linux-ISP] Re: checking logins for pop3

Fu Bar <fubar <at> yoda.fdt.net> wrote:
>This message comes from pop_dropcopy.c, but I'm not quite sure what  
>causes it.  The headers in his mail spool on several messages were pretty
>strange:

>>>From oyster::mrgate::"a1::lezotte, philip a." <at> oyster.monsanto.com  Wed
>>>Oct 18 14:21:51 1995 
>>>Return-Path: oyster::mrgate::"a1::lezotte, philip a." <at> oyster.monsanto.com

>I made a backup copy of the mail file, and then edited all the "From " 
>and "From: " lines, and then popper was able to handle the file.  
>Manually fixing people's mail isn't much of a solution though.

>Pine had no trouble reading messages like this, so I decided to try Pine's
>in.pop3d, and it worked as well.  We had some problem many weeks ago with

>Is this header "bad" or does it simply expose a bug in popper?  Could an 

It exposes a bug in popper, the header is valid.

>/etc/procmailrc using formail perhaps be used to "clean up" headers on 
>incoming messages?

Of course.  Something like that can be kludged in.

:0
* ^^From [^ ]+ [^ ].*  \/[A-Z][a-z][a-z] [A-Z][a-z][a-z] [0-9]+ [0-9]+:.*$
| formail -I "From STRANGE_ADDRESS  $MATCH"

But the real solution is fixing the popper.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Louis J. LaBash Jr. | 1 Nov 1995 18:46

Return receipt?

Hi,

My boss uses Pegasus, and sent mail with "Return receipt" on. 
I was surprised to read the following on his machine: (edited)

Subject: Returned mail: Return receipt

  The original message was received at Wed, 1 Nov 1995 11:25:00 -0600
  from eniac.ac.siue.edu [146.163.15.8]

     ----- Transcript of session follows -----
  procmail: [6456] Wed Nov  1 11:25:00 1995
  procmail: Assigning "PATH=/home/labash/bin:/usr/bin:/bin:/usr/local/bin:"
  procmail: Assigning "MAILDIR=/home/labash/Mail"
  procmail: Assigning "DEFAULT=/home/labash/Mail/mbox"
  procmail: Assigning "LOGFILE=/home/labash/Mail/from"
  procmail: Opening "/home/labash/Mail/from"
  <labash <at> lcjones.aclib.siue.edu>... Successfully delivered

     ----- Message header follows -----

Have I misconfigured something?  Is there some way to stop this information
from being visible to the outside world?

Thanks.
--

-- 
Louis-ljl-{LLaBash <at> eniac.ac.siue.edu | lou <at> minuet.siue.edu}
Permalink | Reply | 0 comments |
headers
Olly Stephens | 1 Nov 1995 20:32
X-Face
Picon
Favicon

Re: mail to exmh gets misplaced with procmail


In the exmh-users mailing list,
iskender <at> csla.csl.sri.com (Iskender Agi) said:
|>
|> I just made some posts to a couple of mail groups, and got a barrage of
|> "user unknown" or "host unknown" replies.  So, I thought I would use
|> the following lines in my .procmailrc recommended in the procmail man
|> page to handle bounced mail.
|> 
|> :0 w:
|> * ^FROM_MAILER
|> | rcvstore +PostMaster
|> 
|> This morning, I find that all the mail for the exmh group also ended up
|> in my PostMaster folder.  I have another line in my .procmailrc to handle
|> the mail from this group.  This line is located below the line to sort
|> the bounced mail above.
|> 
|> :1
|> ^TO.*(exmh-users|exmh-announce).*
|> | rcvstore +Exmh
|> 

My guess is that it's the following line (which accompanies all mail sent
on the exmh-users mailing list):

  Sender: exmh-mail-errors <at> parc.xerox.com

If you look at the expansion of procmail's FROM_MAILER, you'll notice
that it looks for the text "Mail" (case insensitive) in the sender
(Continue reading)

Permalink | Reply | 4 comments |
headers
Paul Kenna | 2 Nov 1995 01:41
Picon
Picon

Phantom Email Addresses

I am developing a web site to be used as part of a training program for new
internet users with an emphasis on keeping everything as simple as possible.
To this end all access for students is to be through www pages with mail
converted into HTML pages and limited privacy provided through passwords etc.  

As my students will be using the system for between one week and one
semester I dont want to (nor do not have the ability to) have separate
alias' for each student but rather have all mail go through
<students <at> auservices.com>.

Two possible filtering strategies I've thought about are:

1.  To modify the "name" on the "name" <students <at> auservices.com> on the TO
line and then on receipt  filter the FROM firstly for
<students <at> auservices.com> and then the (name) variable against a list I keep
in the .procmail directory.  The output would then be redirected to the
appropriate directory for each student and the mail to html program
(MHonarc) run.

2.  To add an extra header line to the mail under the TO line such as
STUDENT: Bundoora Secondary College "name" and filter all replys for that
line.  If present redirect and convert.  If not to an unsorted area for
processing.

The  likely mail useage would be to autorepliers, other students in the
group and general email useage.  

Has anyone done anything like this or has any suggestions

Paul Kenna
(Continue reading)

Permalink | Reply | 1 comment |
headers
Paul Kenna | 2 Nov 1995 01:41
Picon
Picon

Re: Automativ retrieval of files by reply

when I ran this recipe on my machine I got an error message:
Invalid regexp "Subject: *(Re: *)?archive *get *\/([^ ]+\)" 
I'm uncertain what in this condition is not correct 

Paul Kenna

At 10:56 AM 10/23/95 -0700, Alan Stebbens wrote:
>> I am setting up a system in which recipients of a mailing list will be
>> asked to retrieve a file using SmartList. Ideally I would like to be
>> able to send a mail saying 'just reply to this message without editing
>> the reply' in order to allow the users to easily retrieve the file
>> concerned. This would require some playing with the keywords used to
>> trigger sendmail - e.g. being able to cope with a subject line of 
>> 
>> 	Subject: Re: archive get foo.bar
>> 
>> as well as allowing correct reply addresses.
>> 
>> Has anyone else actually done this?
>> 
>> Thanks,
>
>You do not need to bother sendmail about this, except possibly to use an
>alias.
>
>You could even set this up using your own, personal address.  Since
>seeing is believing, send me an email with the subject: "send help"
>(without the quotes).
>
>Or, instead of using your own address, you could create an alias, with a
(Continue reading)

Permalink | Reply | 0 comments |
headers
Stephen R. van den Berg | 2 Nov 1995 02:43
Picon
Gravatar

Re: mail to exmh gets misplaced with procmail

Olly Stephens <olly <at> dylan.zycad.com> wrote:
>In the exmh-users mailing list,
>iskender <at> csla.csl.sri.com (Iskender Agi) said:
>|> page to handle bounced mail.

>|> :0 w:
>|> * ^FROM_MAILER
>|> | rcvstore +PostMaster

>My guess is that it's the following line (which accompanies all mail sent
>on the exmh-users mailing list):

>  Sender: exmh-mail-errors <at> parc.xerox.com

>If you look at the expansion of procmail's FROM_MAILER, you'll notice
>that it looks for the text "Mail" (case insensitive) in the sender
>address.  For procmail 3.11pre4, the expansion is:

[...]

>Of course, this is *really hideous* so my answer is only an educated guess.

You are correct.  The fact that it is indeed hideous is exactly why it
is hidden behind a macro (it can't really be fast and comprehensive without
getting hideous).

>If I'm correct, you could avoid it by modifying your test to:

[...]
(Continue reading)

Permalink | Reply | 3 comments |

Gmane