qmail Digest 7 Feb 1999 11:00:14 -0000 Issue 544

Topics (messages 21581 through 21599):

...re your site
        21581 by: Brian Behlendorf <[EMAIL PROTECTED]>
        21593 by: "Sam" <[EMAIL PROTECTED]>

RFC incompliance in qmail-remote
        21582 by: Peter van Dijk <[EMAIL PROTECTED]>
        21588 by: Harald Hanche-Olsen <[EMAIL PROTECTED]>
        21597 by: "D. J. Bernstein" <[EMAIL PROTECTED]>

case dependent addrsesses
        21583 by: "Roger O. Svenning" <[EMAIL PROTECTED]>
        21592 by: Mate Wierdl <[EMAIL PROTECTED]>

case dependent addresses
        21584 by: "Roger O. Svenning" <[EMAIL PROTECTED]>
        21586 by: Chris J/#6 <[EMAIL PROTECTED]>
        21587 by: "Roger O. Svenning" <[EMAIL PROTECTED]>
        21590 by: Harald Hanche-Olsen <[EMAIL PROTECTED]>

Incomplete Message Headers
        21585 by: Harald Hanche-Olsen <[EMAIL PROTECTED]>

case dependent addresses -solved
        21589 by: "Roger O. Svenning" <[EMAIL PROTECTED]>

source-debs of qmail 1.03?
        21591 by: "Mike Gerber" <[EMAIL PROTECTED]>

masquerading a fake IP in the headers
        21594 by: Omer Ansari <[EMAIL PROTECTED]>
        21595 by: Chris Johnson <[EMAIL PROTECTED]>

pine and qmail-inject
        21596 by: "A.Y. Sjarifuddin" <[EMAIL PROTECTED]>

Qmail RPM available?
        21598 by: Bill Parker <[EMAIL PROTECTED]>
        21599 by: Keith Burdis <[EMAIL PROTECTED]>

Administrivia:

To subscribe to the digest, e-mail:
        [EMAIL PROTECTED]

To unsubscribe from the digest, e-mail:
        [EMAIL PROTECTED]

To bug my human owner, e-mail:
        [EMAIL PROTECTED]

To post to the list, e-mail:
        [EMAIL PROTECTED]


----------------------------------------------------------------------


On Fri, 15 Jan 1999, Sam wrote:
> On 16 Jan 1999, D. J. Bernstein wrote:
> 
> > I've cut off access to the 208.250-255.*.* dialups.
> 
> Should do the same for 134.34-39.*.*.

Um, I don't get it.  I see lots of valid mail to/from 134.34-39.*.*, and
they appear to be allocated to different companies:


taz% whois -h whois.arin.net 134.34.0.0
University of Konstanz (NET-KISS)
   Rechenzentrum
   Universitaetsstrasse 10
   Postfach 5560
   D-78434 Konstanz
   GERMANY

   Netname: KISS
   Netnumber: 134.34.0.0

taz% whois -h whois.arin.net 134.35.0.0
North American MORPHO Systems, Inc. (NET-NAMSI)
   1148 Broadway Plaza, Suite 101
   Tacoma, WA 98402

   Netname: NAMSI
   Netnumber: 134.35.0.0

taz% whois -h whois.arin.net 134.36.0.0
University of Dundee (NET-DUNDEE-UNIV)
   Dundee DD1 4HN
   Scotland
   UNITED KINGDOM

   Netname: DUNDEE-UNIV
   Netnumber: 134.36.0.0

   Coordinator:
      Whitehead, Mike  (MW176-ARIN)  [EMAIL PROTECTED]
      +44 382 23181 ext. 4759

taz% whois -h whois.arin.net 134.37.0.0
Hewlett-Packard Company (NETBLK-HP10) HP10         134.37.0.0 -
134.38.255.255
Partek Corporation (NET-PARTEK) PARTEK
134.37.0.0

taz% whois -h whois.arin.net NET-PARTEK
Partek Corporation (NET-PARTEK)
   P.O. Box 61
   00501 HELSINKI
   FINLAND

   Netname: PARTEK
   Netnumber: 134.37.0.0

taz% whois -h whois.arin.net 134.38.0.0
Hewlett-Packard Company (NETBLK-HP10) HP10         134.37.0.0 -
134.38.255.255
Rentenanstalt / Swiss Life (NET-SWISSLIFE-1) SWISSLIFE-1
134.38.0.0

taz% whois -h whois.arin.net NET-SWISSLIFE-1
Rentenanstalt / Swiss Life (NET-SWISSLIFE-1)
   General Guisan Quai 40
   Postfach
   CH-8022 Zuerich
   SWITZERLAND

taz% whois -h whois.arin.net 134.39.0.0
Communications Technology Center (NET-CTCNET1)
   3101 Northup Way
   Bellevue, WA 98004

   Netname: CTCNET1
   Netnumber: 134.39.0.0







On Sat, 6 Feb 1999, Brian Behlendorf wrote:

> On Fri, 15 Jan 1999, Sam wrote:
> > On 16 Jan 1999, D. J. Bernstein wrote:
> > 
> > > I've cut off access to the 208.250-255.*.* dialups.
> > 
> > Should do the same for 134.34-39.*.*.
> 
> Um, I don't get it.  I see lots of valid mail to/from 134.34-39.*.*, and
> they appear to be allocated to different companies:
> 
> 
> taz% whois -h whois.arin.net 134.34.0.0

Slight typing error.  Try 153.34-39.*.*






qmail-remote immediately disconnects after sending QUIT. This is in violation
with RFC821 section 4.1.1

Greetz, Peter.




- Peter van Dijk <[EMAIL PROTECTED]>:

| qmail-remote immediately disconnects after sending QUIT. This is in
| violation with RFC821 section 4.1.1

Maybe so, but that section of RFC821 also specifies that no loss of
mail should result from this practice:

            If the connection is closed prematurely the receiver should
            act as if a RSET command had been received (canceling any
            pending transaction, but not undoing any previously
            completed transaction) [...]

At this point, there *is* no pending transaction, so it's hard to see
any harmful effect from this.

- Harald




Peter van Dijk writes:
> qmail-remote immediately disconnects after sending QUIT. This is in
> violation with RFC821 section 4.1.1

No, it is not in violation of RFC 821.

RFC 821 _recommends_ that the client send QUIT and wait for the reply
before closing the connection; but there are cases where sending QUIT is
impossible, and there are good reasons to avoid waiting for the reply.

---Dan





>> Is there any way to get qmail to accept email addresses
>> regardless of whether it's upper/lowercase or a mixture of these ?
>
>Well, according to the dot-qmail manpage:
>
>   For convenience, qmail-local converts any uppercase letters in ext
>   to lowercase.
>
>So, USER@host is controlled by .qmail-user.
>
>If you mean you want user@host to be a different address than USER@host
>then you'll have to edit qmail-local.c and find where it converts
>uppercase letters to lowercase and remove that code.

What I mean is that i have address [EMAIL PROTECTED] but sending mail to
[EMAIL PROTECTED] ends up with a "unkown user" -error

-Roger





On Sat, Feb 06, 1999 at 02:52:15PM +0100, Roger O. Svenning wrote:
> 
> >> Is there any way to get qmail to accept email addresses
> >> regardless of whether it's upper/lowercase or a mixture of these ?
> >
> >Well, according to the dot-qmail manpage:
> >
> >   For convenience, qmail-local converts any uppercase letters in ext
> >   to lowercase.
> >
> >So, USER@host is controlled by .qmail-user.
> >
> >If you mean you want user@host to be a different address than USER@host
> >then you'll have to edit qmail-local.c and find where it converts
> >uppercase letters to lowercase and remove that code.
> 
> What I mean is that i have address [EMAIL PROTECTED] but sending mail to
> [EMAIL PROTECTED] ends up with a "unkown user" -error

But you get the error not from qmail but your password checking program---If
I remember correctly.

Mate

-- 
---
Mate Wierdl | Dept. of Math. Sciences | University of Memphis  




Here's what maillog says about the failed delivery. to [EMAIL PROTECTED]
Sending mail to [EMAIL PROTECTED] works (as said earlier) fine.

Feb  6 13:58:07 pop qmail: 918309487.442134 info msg 101: bytes 636 from 
<[EMAIL PROTECTED]> qp 5081 uid 82
Feb  6 13:58:07 pop qmail: 918309487.484501 starting delivery 1822: msg 101 to local 
[EMAIL PROTECTED]
Feb  6 13:58:07 pop qmail: 918309487.488136 status: local 1/10 remote 0/20
Feb  6 13:58:07 pop qmail: 918309487.541671 delivery 1822: failure: 
ROS:popmail:intrafish.no/Reason_for_failure:_/Unknown_local_POP_user_ROS_(#5.1.1)/
Feb  6 13:58:07 pop qmail: 918309487.558683 status: local 0/10 remote 0/20
Feb  6 13:58:07 pop qmail: 918309487.675399 bounce msg 101 qp 5085
Feb  6 13:58:07 pop qmail: 918309487.696871 end msg 101

Anyone got any ideas why this is happening.

-Roger






This is a problem with vchkpw...solution mailed...posting here to inform the 
rest of the list. If anyone else wants the solution, please get in touch.

Chris...

-- 
 @}--- Chris Johnson ~~~~~~~~~~~~~~~~~~~~~~\~~~~~~~~ [EMAIL PROTECTED] \--{@
   \ If not for me then do it for yourself  \ www.nccnet.co.uk/~sixie/   \
    \ If not for me then do it for the world \ pine.shu.ac.uk/~cjohnso0/  \
     \                   -- Stevie Nicks      \                            \






>This is a vchkpw problem...not a qmail problem. Fix is below...if you don't 
>mind getting your hands mucky :)

ok .. I'll give it a try :)

Why is vchkpw invoked when delivering mail ?

-Roger





- "Roger O. Svenning" <[EMAIL PROTECTED]>:

| Here's what maillog says about the failed delivery. to [EMAIL PROTECTED]
| Sending mail to [EMAIL PROTECTED] works (as said earlier) fine.
| 
| Feb  6 13:58:07 pop qmail: 918309487.484501 starting delivery 1822: msg 101 to local 
|[EMAIL PROTECTED]
| Feb  6 13:58:07 pop qmail: 918309487.541671 delivery 1822: failure: 
|ROS:popmail:intrafish.no/Reason_for_failure:_/Unknown_local_POP_user_ROS_(#5.1.1)/
| 
| Anyone got any ideas why this is happening.

This is not a qmail issue.  The delivery program (probably running
from ~alias/.qmail-intrafish.no-default) is at fault:  It should
convert the recipient address to lower case before looking up the user
in the database.  If it can't or won't, let the shell do it:
something like LOCAL=`echo $LOCAL tr A-Z a-z` should do the trick -
depending on whether the delivery program looks at the environment or
gets the recipient address on a command line.

- Harald




- "Bryan White" <[EMAIL PROTECTED]>:

| [...] When it fails the message is redirected to another machine
| that is running sendmail and from there picked up via POP3.  At this
| end the "To:" header will sometimes be correct, somtimes be blank,
| and sometimes be missing.  At this point the "Delivered-To:" header
| does contain the desired address but I am not seeing this in
| ezinesub.

Because the Delivered-To: line is not presented on stdin to programs.
You'll find it in $DTLINE instead.  RTFM qmail-command(8).

| Why don't I always get a "To:" header?

qmail doesn't add a To: header field if there isn't one there already.
(Exception: qmail-inject adds "Cc: recipient list not shown: ;" if
there is neither a To: field or a Cc: field, but you are not invoking
qmail-inject, either directly or indirectly.)

| I am not always clear on what headers are getting added where but
| obviously qmail knows the recipient address.  Is there an
| alternative way of getting this info like an environment variable?

Delivered-To: lines are added on final delivery as well as when
forwarding mail.

The envelope recipient is in $RECIPIENT, and its components can be
found in other environment variables.  RTFM qmail-command(8).

- Harald




Hi

Just wanted to inform the list that Chris's solution worked.
The flaw was in vchpw's vedlivermail.

-Roger





hi folks!

i was searching for source-debs (debian packages) of qmail 1.03 
but i only found the 1.01 and 1.02 ones. is there a 1.03 package?

thanx in advance!






Hi, this query may not be directly regarding qmail, but it addresses
e-mail issues nevertheless...

I got a spam mail from someone. Out of curiousity i checked the headers
of the mail and this is what i got:

......
Received:
                  from pomcm009106.netvigator.com by mail.scmp.com with
SMTP
                  (Microsoft Exchange Internet Mail Service Version
5.0.1460.8) id
                  12HY8YTS; Sat, 6 Feb 1999 01:51:59 +0800
         Received:
                  from nosc.cjkmh.mhul.com [21.22.23.24] by smart.com.uk

                  (FTGate 2, 1, 1, 0); Fri, 05 Feb 99 20:07:53 +0800
.......

note the IP: 21.23.24.24 is obviously not the correct IP and the host
name has also been faked...smart.com.uk doesn't/cannot exist.

My question is, how can you fake a mailserver with such information?

anyone?
--
Omer Ansari
Network Engineer,
Supernet PDSL
PK.

Digital Fingerprint:
A641 2DCB D180 4ACD CA00  DC4E 1698 847B E3CA A88F






On Sat, Feb 06, 1999 at 09:19:42PM +0500, Omer Ansari wrote:
> Hi, this query may not be directly regarding qmail, but it addresses
> e-mail issues nevertheless...
> 
> I got a spam mail from someone. Out of curiousity i checked the headers
> of the mail and this is what i got:
> 
> ......
> Received:
>                   from pomcm009106.netvigator.com by mail.scmp.com with
> SMTP
>                   (Microsoft Exchange Internet Mail Service Version
> 5.0.1460.8) id
>                   12HY8YTS; Sat, 6 Feb 1999 01:51:59 +0800
>          Received:
>                   from nosc.cjkmh.mhul.com [21.22.23.24] by smart.com.uk
> 
>                   (FTGate 2, 1, 1, 0); Fri, 05 Feb 99 20:07:53 +0800
> .......
> 
> note the IP: 21.23.24.24 is obviously not the correct IP and the host
> name has also been faked...smart.com.uk doesn't/cannot exist.
> 
> My question is, how can you fake a mailserver with such information?

You can add any arbitrary headers you like to a mail message. Just prepare a
message with a bunch of fake headers, and send it on its way.

For example:

[cjohnson@mail cjohnson]$ /var/qmail/bin/qmail-inject
Received: from somejackass.com (1.2.3.4.5.6) by openrelay.com (10.4.2.lmnop.4) with 
ZMTP
Message-ID: <12345.54321>
Date: Tuesday
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Check these headers!

Hiya!
^D
[cjohnson@mail cjohnson]$

Run that, and you'll find yourself with a message in your inbox with a forged
Received line.

Chris




I changed the .pinerc file :

sendmail-path=/var/qmail/bin/qmail-inject [EMAIL PROTECTED]

Thanks.

On Sat, 9 Jan 1999, Mohanan P G wrote:

> Date: Sat, 9 Jan 1999 09:55:44 +0530 (IST)
> From: Mohanan P G <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: pine and qmail-inject
> 
> Hello,
> We are using qmail-v1.03 and pine 4.04 in RedhatLinux 5.2 for our
> mailing. pinerc has "sendmail -oem -oi -t" in its sendmail-path
> and sendmail is a link to /var/qmail/bin/sendmail. Is there any
> way to use qmail-inject instead ?
> Thanks in advance.
> --pgm 
> ===========================================================
> P G Mohanan                   E-Mail :[EMAIL PROTECTED]
> Systems Manager                       Phone  :91-824-475984
> Central Computer Centre                           Ext 301 (Off)
> K R E C Surathkal             Fax    :91-824-476090
> Srinivasnagar PO              Grams  :KARENG
> D K , Karnataka                       Telex  :0832-298 KREC IN
> INDIA 574 157                         
> ===========================================================
> 
> 





Hello,

        I was wondering if a QMAIL RPM is available for Linux (RH or Caldera, etc)?

-Bill





On Sat 1999-02-06 (10:42), Bill Parker wrote:
> Hello,
> 
>       I was wondering if a QMAIL RPM is available for Linux (RH or Caldera, etc)?

Yup, there are several (4 if I remember correctly). My two favourite are:

the Memphis RPM:

  ftp://moni.msci.memphis.edu/pub/qmail

and the Summersoft RPM:

  ftp://ftp.engr.uark.edu/pub/qmail/qmail-1.03

You might also like to look at:
  
  http://rucus.ru.ac.za/qmail/memphis.html

and
  
  http://rucus.ru.ac.za/qmail/summersoft.html

for help on installing these. (Note the these docs are out of date. 
I did update them but I can't find the new versions :). For example,
David Summers' rpm now includes dot-forward and fastforward, so you don't
need to install those).

I'd recommend the Summersoft RPM is you want a basic sendmail-compatible
setup that uses inetd.

The Memphis RPM is more fully featured, since it uses the daemontools and
ucspi-tcp packages. It has nice initscripts too. This is what I use.

The other two that I know of are by Mr Sam and Bruce Guenter. You should be
able to find links to them on http://www.qmail.org/.

  - Keith

> -Bill

-- 
Keith Burdis - MSc (Com Sci) - Rhodes University, South Africa  
Email   : [EMAIL PROTECTED]
WWW     : http://www.rucus.ru.ac.za/~keith/
IRC     : Panthras                                          JAPH

"Any technology sufficiently advanced is indistinguishable from a perl script"

Standard disclaimer.
---


Reply via email to