Re: securing pop3 sessions

2000-05-24 Thread Bob Rogers

   From: "Len Budney" <[EMAIL PROTECTED]>
   Date: Wed, 24 May 2000 15:38:53 -0400

   [EMAIL PROTECTED] wrote:
   > 
   > What's the best way on the server side to prevent passwords from being
   > sent as clear text over the network for a pop3 session?

   I'm afraid the best way is also the only way, and it doesn't exist. You
   cannot use POP3 without sending passwords in the clear.

   Len.

Why not require APOP?

            -- Bob Rogers



Forward to multiple people?

2000-05-21 Thread Bob Rogers

   From: "Snowcrash" <[EMAIL PROTECTED]>
   Date: Sat, 20 May 2000 19:23:01 -0500

   I'm running Qmail with Vpopmail from inter7.com  and I'd like to know
   how I would forward one e-mail address to mutiple people.  For example
   messgaes sent to [EMAIL PROTECTED] are sent to [EMAIL PROTECTED], [EMAIL PROTECTED] and
   [EMAIL PROTECTED]  Probably an easy question but I'm just not getting it...

   Thanks in advance,
   Daniel Daley
   [EMAIL PROTECTED]

In ~alias/.qmail-support:

[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]


        -- Bob Rogers



help with smtp

2000-05-09 Thread Bob Rogers

   From: Lael Heinig <[EMAIL PROTECTED]>
   Date: Tue, 09 May 2000 12:06:12 -0700

   Hi,

   I am trying to use the qmail-smtpd program.  Every time I try to
   specify the recipient, I get the following message:

   553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)

   I did a man on the qmail-smtpd program and it mentions something about a
   rcpthosts file.  How do I set that up.

With a text editor.

   Is that my problem?

   Thanks,
   Lael Heinig

Yes.  http://www.flounder.net/qmail/qmail-howto.html#14

    -- Bob Rogers



Re: Lowercasing non-ASCII chars?

2000-05-09 Thread Bob Rogers

   From: Peter van Dijk <[EMAIL PROTECTED]>
   Date: Tue, 9 May 2000 15:08:03 +0200

   On Mon, May 08, 2000 at 11:42:37PM -0400, Bob Rogers wrote:
   [snip RFC822 disallows 8-bit stuff]

   This is not relevant. RFC822 talks only about headers+body. The issue in
   this discussion is the SMTP (thus RFC821) addressing.

But SMTP address syntax is a subset of mail header address syntax, by
design.  So if 822 doesn't allow something, 821 certainly won't, am I
right?  I quoted 822 because I am more familiar with it.

            -- Bob Rogers



Re: fw: qmail-inject

2000-05-09 Thread Bob Rogers

   From: [EMAIL PROTECTED]
   Date: Tue, 9 May 2000 08:53:33 +0200

   > Bob Rogers (Mon 08.0500-23:47):

   > Not here, but that may not mean much.  My guess is that mutt is
   > expecting the named program to be sendmail-compatible and is passing it
   > extra options, but qmail-inject is not taking sendmail options.  Try
   > 
   >set sendmail="/var/qmail/bin/sendmail"

   ok, thorough procedure requires me to try.  but i checked with the original
   sendmail and qmail's wrapper for qmail-inject of the same name:  neither
   takes "-B".

Hmm.  On my Red Hat 6.0 system, "man sendmail" (for the sendmail 8.9.3
version originally installed) explains "-B" as follows:

 -Btype  Set the body type to type. Current legal values [are]
 7BIT or 8BITMIME.

And my local /var/qmail/bin/sendmail (qmail 1.03) does ignore -B:

rgr> /var/qmail/bin/sendmail -t
to: rogers
subject: test

foo bar
rgr> /var/qmail/bin/sendmail -t -Bfoo
to: rogers
subject: test

more testing.
rgr> 

I got both of these test messages.  So, as long as you use
/var/qmail/bin/sendmail, this looks like an unrelated mutt configuration
problem, eh?  Maybe *you* have to specify the "-t" explictly . . . ?
But I've never used mutt, so that's just a guess.

-- Bob Rogers



fw: qmail-inject

2000-05-08 Thread Bob Rogers

   From: [EMAIL PROTECTED]
   Date: Mon, 8 May 2000 18:14:49 +0200

   every once in a while, but rarely, i get "qmail-inject: illegal option -- B"
   when handing off a mail for outbound delivery.  the number is "100".  i let
   mail be handled by (this is .muttrc of mutt):

   set sendmail="/var/qmail/bin/qmail-inject"   # how2deliver
   set sendmail_wait=15

   =nothing= makes a mail so flagged by the "sendmail" option leave my
   machine.  whats wrong?  there is no "-B" option anywhere!

Not here, but that may not mean much.  My guess is that mutt is
expecting the named program to be sendmail-compatible and is passing it
extra options, but qmail-inject is not taking sendmail options.  Try

   set sendmail="/var/qmail/bin/sendmail"

instead.

-- Bob Rogers



Lowercasing non-ASCII chars?

2000-05-08 Thread Bob Rogers

   From: =?iso-8859-1?Q?Mikko_H=E4nninen?= <[EMAIL PROTECTED]>
   Date: Mon, 8 May 2000 21:49:22 +0300

   . . .

   And yes, I know it's not a good idea to use 8bit characters in the
   email addresses.  I'm not planning to use these addresses except as a
   safety catch in case someone happens to use them by accident...

   Regards,
   Mikko

To belabor what is perhaps obvious by now, RFC822 forbids 8-bit
characters in the local-part of an address (or anywhere else, for that
matter).  The key lines are as follows:

 atom=  1*
 CHAR=  ; (  0-177,  0.-127.)

I haven't actually seen this particular violation in use; has anybody
else?

        -- Bob Rogers




Re: QMail Performance Question & Miscellaneous Issues

2000-05-07 Thread Bob Rogers

   From: "Steve Wolfe" <[EMAIL PROTECTED]>
   Date: Sat, 6 May 2000 21:22:30 -0600

   . . .
   > Another question is about the Mail header. What is the header that I
   should
   > add into a generated email so that undelivered/bounced emails go to this
   > specific email address instead? For example, I send an email to
   > [EMAIL PROTECTED], it will by default bounce back to my sending
   > account. How do I make it bounce to another account instead? Should I use
   > Errors-To:, or Undeliverables-To: or any other header?

 I've heard of "Bounce-to:" being used, but I'm not hip on the RFC's like
   others on the list. : )

   steve

I probably don't qualify as "RFC-hip", but I'd like to be, so this query
prompted me to do some digging.  The only thing I could find was a
mention of "Errors-To:" in RFC2076.  Here's what RFC2076 says (bottom of
page 10):

 Address to which notifications   Errors-To:,Non-standard,
 are to be sent and a request to  Return-discouraged.
 get delivery notifications.  Receipt-To:
 Internet standards recommend,
 however, the use of RCPT TO and
 Return-Path, not Errors-To, for
 where delivery notifications are
 to be sent.

So the "official" word would seem to be "use the envelope FROM address."
I know that many mailing lists use "Errors-To:", but I'm not sure what
percentage of mailers actually use this header.  (Of course, qmail does
not, nor does the one sendmail installation to which I have access.)
[At the top of p11 are a handful of X.400 delivery-related headers,
which are probably even less widely implemented.]

-- Bob Rogers



qmail installation

2000-05-07 Thread Bob Rogers

   From: "Daniel" <[EMAIL PROTECTED]>
   Date: Sun, 7 May 2000 11:49:03 +0700

   Hi, 

   1)
   I have installed Slackware 7.0 with kernel 2.2.13 without procmail
   and fetchmail, then I install qmail-1.03. Could qmail work without those
   two tools (procmail or fetchmail)?

Yes (though, for the sake of full disclosure, I have no personal
experience with either).

   2)
   If I have installed qmail, then I telnet to mail.domain.com 25/110 is
   work well, but I can't get the mail from that server, what's wrong?
   (In this case I have installed/copied procmail and fetchmail from pkgtool)

I can't tell.  Is mail.domain.com your machine, or your ISP's server?
If the latter, are you talking about POPping mail off that server via
fetchmail, or having the server hand it off to yours via SMTP?

   Should I re-configure/re-installed qmail again?

Reinstallation is the knee-jerk response of customer support staff when
faced with the task of supporting flaky software.  In the case of qmail,
reinstallation won't do you any good unless you know that the problem is
caused by something that requires it.

   3)
   Does Microsoft Outlook, Outlook Express, Netscape Messenger,
   Eudora(mail reader for MS Windows), can work with Maildir?

   Thank you

   Daniel

Turns out it doesn't matter, as long as Windows users POP their mail,
since qmail-pop3d supports maildir.

    -- Bob Rogers



URGENT ! Erased /var/qmail !!!

2000-05-07 Thread Bob Rogers

   From: [EMAIL PROTECTED]
   Date: Sun, 7 May 2000 14:34:59 +0200 (MET DST)

   Hi !

   I erased /var/qmail !!!

   What must I do please ?

   I already did :

   mkdir /var/qmail
   make setup check
   put a backup of /var/qmail/control/*

   What to do next ? Thanks !!!

I think that should have pretty much taken care of reinstallation.  You
will need to replace any system-wide aliases in the ~alias/ directory
(e.g. for postmaster, root, abuse, etc.), though.  And, if I were you,
I'd start it up by going through the testing sequence in the qmail
installation instructions.

    -- Bob Rogers




Does Qmail handle mbx

2000-05-03 Thread Bob Rogers

   From: "Steve Quezadas" <[EMAIL PROTECTED]>
   Date: Wed, 3 May 2000 16:26:07 -0700

   Any way to get qmail to handle mbx format?

   - Steve

If this is "mbox" format, it's trivial (see "man dot-qmail").  If this
is something else, we need a better reference.

        -- Bob Rogers




Re: dot-qmail: write to mbox named after current year & month

2000-05-02 Thread Bob Rogers

   From: Rogerio Brito <[EMAIL PROTECTED]>
   Date: Tue, 2 May 2000 02:32:47 -0300

   On May 01 2000, lewst wrote:
   > What is the easiest way to have qmail deliver an incoming message to
   > an mbox named after the current year and month without having to
   > manually adjust the .qmail each month?  For example, "mbox.2000-05".

   Essentially, something like this would do the trick:

   | preline cat >> ./mbox.`date +%Y-%m`

   Notice that I said *essentially*. You'd have to substitute cat
   with something that takes care of locks to avoid concurrent
   writes to the same message and that works gracefully under
   circumstances of failure.

   If there isn't such a program, you'd have to write your own
   here.

How about a cron job that does the following at appropriate intervals:

echo "./mbox.`date '+%Y-%m'`" > .temp; mv -f .temp .qmail

Since no special code need be run at delivery time, this should be quite
robust.


-- Bob Rogers



patch send of all addresses in CC field

2000-05-02 Thread Bob Rogers

   From: "Yuan P Li" <[EMAIL PROTECTED]>
   Date: Tue, 2 May 2000 18:38:41 -0400

   Hi,

   (1)
   I often have 20 or 30 email addresses in the CC field to the
   same domain. For example,
   CC: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] ...

   I noticed that qmail send to those addresses one by one. Can
   I instruct qmail to send the message all at once? 

No.

   If I have 20 addresses in CC field, this would increase the spead by
   ~20, right?

Not necessarily.  See the thread titled '"Multi-RCPT vs. Single RCPT
delivery" - logic error?' that started 28 April.

   (2)
   Also, how can limit the number of addresses a use can put
   in the CC and BCC field?

There is no parameter to control this, since it would be trivial to
defeat.  A user who wants to override the limits can send a message with
X recipients, then change the headers to resend it to a different X
recipients, then change them again . . .

   (3)
   How can I delete the messages waiting in the quene?

Use "touch" -- see http://cr.yp.to/qmail/faq/admin.html#rejuvenate for
the complementary problem.

   Thank you for your help.

   Sincerely,
   Peter

    -- Bob Rogers



send mail to remote hosts...

2000-04-30 Thread Bob Rogers

   From: <[EMAIL PROTECTED]>
   Date: Sun, 30 Apr 2000 21:06:57 + (GMT)

   . . .  I would like to configure it so that it will accept mail from
   anyone whos "mail from:" is mail.santiago.cl or santiago.cl,
   regardless where they are in the world.

   Thanks again...
   Marcelo

That would be one way of implementing "selective" relaying, but it
wouldn't turn out to be very selective, since anyone can claim to be
"[EMAIL PROTECTED]" and thereby get their spam relayed.  And qmail
would not be able to prevent it, because there is no way to validate the
sender address.

   Instead, see http://www.palomine.net/qmail/selectiverelay.html for a
solution based on IP addresses, which makes it harder to spoof.

        -- Bob Rogers



virtual domain hosting

2000-04-29 Thread Bob Rogers

   From: Vishwanath Paranjape <[EMAIL PROTECTED]>

   hi all
   i am trying to setup virtual domains using qmail
   i installed qmail on redhat 6.0 and its working ok
   but i tried to setup virtual domains 
   i read the complete documentation along with the distribution
   my virtualdomains files is as follows

   domain1.com:jim

   but the mail addressed to
   [EMAIL PROTECTED]
   bounces back
   saying "no such mailbox"

   but the mail addressed to 
   [EMAIL PROTECTED]
   gets delivered to [EMAIL PROTECTED]


   please help
   vish

So what does ~jim/.qmail-carol contain?

            -- Bob Rogers



HELP: Can't send via Mail.app on NeXT

2000-04-28 Thread Bob Rogers

   From: Michael Friendly <[EMAIL PROTECTED]>
   Date: Wed, 26 Apr 2000 08:53:29 -0400 (EDT)

   I had an open mail-relay with an older version of sendmail,
   and got qmail installed on my system.

   Now, I can send mail from pine, but not from Mail.app.  I can't
   get any help locally, so I'm hoping someone can help me sort this out.

   When I send from Mail.app, I get 
   replies from the mailer-daemon like this:

Hi. This is the qmail-send program at hotspur.psych.yorku.ca.
I'm afraid I wasn't able to deliver your message to the following
addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

>:
Sorry, I couldn't find any host named mathstat.yorku.ca>. (#5.1.2)

   Does this message number give any clue to what is wrong?

It looks like Mail.app may be passing "Georges Monette
<[EMAIL PROTECTED]>" as the "-f" parameter to sendmail, which
the real sendmail would reparse, but qmail-inject takes to be just the
address part.  Try messing with the "Sender" controls in Mail.app.

-- Bob



Qmail privacy

2000-04-25 Thread Bob Rogers

   From: "Kent Nilsen" <[EMAIL PROTECTED]>
   Date: Tue, 25 Apr 2000 13:57:27 +0200

   Hello,

   I'm running qmail 1.01, which has been working perfectly for me. 
   But once in a while a message double-bounces, and the message 
   ends up in my mailbox.

   The problem is that the entire message, including the text of the 
   mail and any attachments, ends up in my mailbox, which again 
   means I can read other peoples mail if it qmail doesn't know where 
   to send it.

   I can of course just be quiet about it and delete the mail as soon 
   as I see it's not for my eyes, but it's still not fair to my users as I 
   can potentially read private mail, and it's probably breaking some 
   privacy law?

There are confidentiality issues, certainly, but you should be educating
your users that the only way to guarantee email privacy is to use PGP or
equivalent -- in which case you would get content you couldn't decrypt.
(Users also need to use valid return addresses when they send things,
whether or not they want you to see their bounces.)

   I see some others here have had double bounces end up in their 
   mailbox. Do you have access to the entire message as well? Any 
   tips how to fix the "problem"?

   Kent R. Nilsen

I'm of the opinion that it's better left alone.  It is usually helpful
for the user to see the content of their own bounces (in the single
bounce case) in order to help discover what needs resending, and it's
always helpful for sysadmins to see the content of double bounces so
that they can distinguish spam from misconfigured local users.

   Speaking of which, I notice that your "from" address and your
"reply-to" address are different . . . ?

-- Bob Rogers



DNS setup

2000-04-25 Thread Bob Rogers

   From: "Steve Peace" <[EMAIL PROTECTED]>
   Date: Tue, 25 Apr 2000 09:58:34 -0400

   . . . I know that I need to have entries the files in
   /var/qmail/control, but I am not certain what entries, and what files
   need to be changed.

/var/qmail/control/locals and /var/qmail/control/rcpthosts -- put your
new domain(s) there.

   If I had more time, I would love to figure it out more on my own, but
   the wonderful world of business dictates that everything be done by
   yesterday.  Any help would greatly be appreciated.

   Steve Peace

This is the F-est of FAQs; it has been asked three or four times in the
last few weeks.  People tend to ignore repetitive posts, and so you are
likely to get faster response by checking the archives.

   P.S.  This list is great resource and everyone has been extremely
   helpful to a qmail newbie like myself.

No argument here.

            -- Bob Rogers



Group Emailing w/qmail

2000-04-22 Thread Bob Rogers

   From: Bill Parker <[EMAIL PROTECTED]>
   Date: Sat, 22 Apr 2000 10:25:00 -0700

   Hi All,

   Does something like a group e-mail exist in qmail, example

   group is sports

   in sports group is:

   larry, mike, pete, greg

The conventional term is "mailing list" or "distribution list."

   so sending an email to [EMAIL PROTECTED] would deliver to
   all of those people...

Put their addresses in ~alias/.qmail-sports, one per line.  For further
details, do "man dot-qmail".  Note that this allows anyone on the planet
to send to [EMAIL PROTECTED]

   is this something handled on the client end, or with qmail

Could be either.  Or neither; for large lists, mailing list management
programs such as ezmlm (see http://www.ezmlm.org/) are more robust and
easier to maintain.

            -- Bob Rogers





Re: qmail + Redhat6.2 + emacs rmail - outgoing messages

2000-04-20 Thread Bob Rogers

   From: Erich <[EMAIL PROTECTED]>
   Date: Thu, 20 Apr 2000 09:00:16 -0700 (PDT)

   Do you know a way to find out which is the case with RedHat 6.2?
   There is no more active sendmail on the system, and I would like to
   make sure that /bin/mail isn't attempting local deliveries.

   e

I can vouch that the Red Hat 6.0 /bin/mail uses sendmail.  Just do

echo Testing | /bin/mail $USER

and see whether or not it goes to /var/spool/mail/$USER, or your qmail
drop.

-- Bob



Re: qmail + Redhat6.2 + emacs rmail - outgoing messages

2000-04-20 Thread Bob Rogers

   From: Erich <[EMAIL PROTECTED]>
   Date: Wed, 19 Apr 2000 21:17:52 -0700 (PDT)

   > I assume you mean your return address?  What is the value of the
   > user-mail-address emacs variable? . . .

   Well, that did the trick.  However, that line shouldn't be necessary.
   I still feel that if emacs is using the system MTA, which as you point
   out is sendmail, which is actually a link to qmail/bin/sendmail, then
   sendmail should do the right things to put in the correct From: and
   Return-Path: lines.

Well, to my mind, the "right thing" is to leave them alone, since I want
to set them in emacs; a user's preferred "From:" address often has
nothing to do with her user ID or the name of the local host.  In fact,
at the point where the sendmail-send-it function actually calls
sendmail, there is this comment:

;; Always specify who from,
;; since some systems have broken sendmails.
;; unless user has said no. 

So, by default, emacs sets up the "From:" header and envelope sender,
and tells sendmail to leave them alone.

   But the "unless user has said no" part reflects a hook:  If you put
in your .emacs file

(setq message-from-style 'system-default)

then sendmail-send-it will give sendmail free rein.  So the usual
qmail-inject environment variables should work (though I haven't tried
this).

   I haven't customized emacs at all.

Then you don't know what you're missing.  ;-}

   This work-around is fine, but I really think I'm missing some part of
   the configuration.

I don't consider this a workaround; this is an important step in
configuring emacs as your MUA.  The fact that emacs has a default that
works for some people, so the step is sometimes optional, doesn't change
the nature or the importance of the step.  After all, you have to tell
Netscape who you are (user name & email address) before Netscape will
let you send email.  You are taking the default behavior of sendmail as
gospel, and it just ain't so.

   There was a discussion on this list about a month ago about the
difference between "injection agents" and "transport agents", and what
they were allowed to do to headers.  In my opinion, the MUA should take
full responsibility for the headers, and transport/injection agents
should only supply defaults for the benefit of low-powered MUAs.  RFC822
appears to imply that this is the right thing.

   Also, there should be some kind of functioning executable in
   /bin/mail.  I just don't know what to put there on this system.

   Maybe I should have gotten Correl Linux, which comes with qmail
   instead of rotten old sendmail.

   e

That would have left you in the same boat, or worse, since this is
really an MUA configuration issue than an MTA configuration issue
(ignoring religious skirmishing over who's responsible for what).
Besides, somebody said Corel doesn't ship qmail configured anyway.

-- Bob Rogers



Cannot send e-mail to the domain

2000-04-19 Thread Bob Rogers

   From: <[EMAIL PROTECTED]>
   Date: Wed, 19 Apr 2000 14:55:14 -0700

   I am not sure what is going on I can not send e-mail to my work
   server which is running exchange and it is only server that I cannot
   send e-mail as far as I can tell. message that I get:

Is there some reason you needed to send the same message from three
different addresses over the space of four hours?  How come you didn't
try doing something new in that time, like telnet from the affected
machine to port 25 on the destination?

    -- Bob Rogers



qmail + Redhat6.2 + emacs rmail - outgoing messages

2000-04-19 Thread Bob Rogers

   From: Erich <[EMAIL PROTECTED]>
   Date: Wed, 19 Apr 2000 17:24:26 -0700 (PDT)

   I followed the instructions and got qmail installed fairly easily on
   my RedHat6.2 box.  It is the best MTA . . .

No arguments here.

   The problem is when I send email using emacs rmail.  It comes out
   without a domain.

I assume you mean your return address?  What is the value of the
user-mail-address emacs variable?  (How to find this?  Type
"user-mail-address " into the *scratch* buffer, then type "C-u C-x C-e",
and see what it inserts.)  If you don't like it, change it by putting

(setq user-mail-address "[EMAIL PROTECTED]")

in your .emacs file (and type C-x C-e with the cursor after the ")" in
order to get it to happen immediately).

   I assume the problem is because I don't have a working /bin/mail of
   any kind.  I followed the instructions in REMOVE.binmail, and it said,
   chmod 0 /bin/mail, and then make sure that "mail" still invokes a
   usable mailer.  I can't find a usable mailer to replace it with.
   Should I just turn it back on, but not as a setuid program maybe?  But
   that would probably break local delivery.  What should I do?

If you haven't customized emacs mail, C-x m sends using sendmail
(/usr/lib/sendmail, I think), and not /bin/mail.  So, if you've
correctly installed the pseudo-sendmail wrapper for qmail-inject, it
should just work.  That said, I have a friend for whom C-x m never
worked after he installed qmail, and we never managed to figure out why
not.

   Thanks,

   e

I'd be happy to help you, but this is really not a qmail question (or
even an rmail question), so further correspondence should be off-list.

-- Bob Rogers





Re: Re[2]: backup mail server

2000-04-18 Thread Bob Rogers

   From: Andy Bradford <[EMAIL PROTECTED]>
   Date: Tue, 18 Apr 2000 08:55:46 -0600

   Yes seriously.  Most MTA's will queue email for at least 3 days, so 
   unless your hardware failure lasts that long then you should be 
   fine.

   Andy

But not always.  My ISP (which shall remain nameless -- ;-) bounced an
email I sent myself from work after trying to deliver it for less than
an hour.  To add insult to injury, the only reason they couldn't deliver
it was because of their own internal outage -- an outage that lasted
five hours.  So I am considering an alternate MX myself.  (Yes, I know;
a better solution would be to get another ISP.)

            -- Bob Rogers



Re: Check timestamps

2000-04-18 Thread Bob Rogers

   From: "Jose de Leon" <[EMAIL PROTECTED]>
   Date: Tue, 18 Apr 2000 13:24:47 -0700

   What exactly do you mean by "not really reliable"?  Do you mean sometimes
   the cur dir timestamps and sometimes it doesn't?  Or do you mean that the
   timestamp itself may be off a few minutes?  If it is off a few minutes, I
   can work with that.

I think he means that it is too easy to update the access timestamp by
accident, e.g. by doing a backup.

        -- Bob Rogers



Qmail config: getting closer additional info

2000-04-18 Thread Bob Rogers

   From: [EMAIL PROTECTED]
   Date: Tue, 18 Apr 2000 14:02:06 -0700

   When testing reciving mail as documented in TEST.receive, I follow
   the steps as follows but when I log in to the user's account and type
   the '$mail' command I receive "no mail for user" . . .

Quoting TEST.receive here is not useful; all we need to know is that the
telnet session was successful.

   My original message follows:

   In testing my senmail config, I follow the steps documented in
   TEST.deliver with the following results:

   1.   When I send to a local user from the root account via the  "echo to: me |
   /var/qmail/bin/qmail-inject" command,
   I see the success message in the /var/loq/qmail dir log file. But, when I log
   into the machine as that user and type the mail command, the response is " no
   mail for user".

Probably because mail is looking in the wrong place (since you state
below that you are using ~/Maildir/ delivery).  Or, it might not have
been delivered; what do the logs say?

   2.   When I send to my hotmail account via "echo to: [EMAIL PROTECTED] |
   /var/qmail/bin/qmail-inject", account I see an empty message in my hotmail
   account. But when I send to my account at my employer (at work) from my new
   qmail box at home (on separate domain)via the " echo to: [EMAIL PROTECTED]
   | /var/qmail/bin/qmail-inject" command, I don't receive the test message from my
   lotus notes client (at work).

Again, is it still in the queue?  What do the logs say?

   This is probably the answer to #2 but I'm not sure:  I can traceroute from
   the qmail box to 'hotmail.com' but the traceroute to 'candle.com' fails to
   finish. All I see is a repeated "***".

No, this just means one of the routers/firewalls along the way filters
out ICMP packets.

   Prior to running the test, I converted to Maildir from mailbox and
   changed the rc file to reflect this as well as run:
   %maildirmake $HOME/Maildir  AND
   %maildirmake $HOME/Maildir in existing user's directory

Eh?

   In any case, "mail" is about as primitive an MUA as you could find.
You're better off using ls & cat -- especially with maildirs!  (Which
you will need for POP anyway.)

-- Bob Rogers



Re: Another (slightly different) cr lf question

2000-03-26 Thread Bob Rogers

   From: Uwe Ohse <[EMAIL PROTECTED]>
   Date: Sat, 25 Mar 2000 13:21:42 +0100

   On Fri, Mar 24, 2000 at 04:47:18PM -0800, thomas wrote:

   > We have IMAP clients accessing these files directly off the unix box, 
   > and they miss the cr

   Hm - strange. 

   Question to the knowing: aren't IMPA servers supposed to translate
   the local line end conventions to CR/LF before sending the articles
   over the wire?

   Regards, Uwe

It shouldn't be possible to do it any other way; no sane client or
server should be willing/able to mess with the TCP line-end convention.
Perhaps the original poster meant the following:

We have MUAs [which are also IMAP clients] that access these files
directly off the unix box [using file access], . . .

Doesn't seem likely, but the original statement struck me as somewhat
ambiguous . . .

        -- Bob Rogers




Re: Bounce Loops?

2000-03-18 Thread Bob Rogers

   From: Bruno Wolff III <[EMAIL PROTECTED]>
   Date: Thu, 16 Mar 2000 13:16:57 -0600

   . . . It is debatable whether or not adding an alias for
   MAILER-DAEMON is useful. Double bounce replies shouldn't be sent back
   to MAILER-DAEMON and humans should send requests to the postmaster if
   the problem is something a postmaster can help with.

Users reply to the damnedest things.  If an MTA is configured to
generate mail from "rumpelstiltskin", then it ought to be configured to
accept mail for "rumpelstiltskin" as well.

        -- Bob Rogers



[Unable_to_chdir_to_maildir (#4.2.1)]

2000-03-10 Thread Bob Rogers

   From: Dewald Strauss <[EMAIL PROTECTED]>
   Date: Fri, 10 Mar 2000 09:20:57 +0200

   > I sent a mail from the console (echo test | mail [EMAIL PROTECTED]) 
   > and right after that these messages started to appear.
   > Did I break something by doing this, or is it just coincidence ?

Probably.  But whom did you really send it to?  You imply that you
expect to receive it yourself, but that doesn't narrow it down very
much.  It could be to yourself, or one of your aliases, or a system
account aliased to you.  Give us the actual address, and the contents of
all relevant .qmail* files.

   (My theory is that it's a bad alias.  I shot myself in the foot this
way last month, but got a different message because I was using mbox
format, so I can't yet tell whether you've done the same.)

        -- Bob Rogers



Re: Slightly OT: Bcc - who is repsonsible

2000-03-06 Thread Bob Rogers

   From: Anand Buddhdev <[EMAIL PROTECTED]>
   Date: Mon, 6 Mar 2000 17:59:43 +0300

   . . .

   There is some description of how the Bcc: field is to be handled in RFC
   822, but it's very ambigious. Here's the relevant section:

   4.5.3.  BCC / RESENT-BCC

   This field contains the identity of additional  recipients  of
   the  message.   The contents of this field are not included in
   copies of the message sent to the primary and secondary  reci-
   pients.   Some  systems  may choose to include the text of the
   "Bcc" field only in the author(s)'s  copy,  while  others  may
   also include it in the text sent to all those indicated in the
   "Bcc" list.

   At the end of the day, Bcc: is a feature of the mail client, and the MTA
   does not need to bother with it . . .

The way I read this, the MTA is enjoined *not* to bother with it.
Here's my reasoning:

   1.  Realistically, only the MUA can document the behavior of mail
header fields such as BCC to the user, because the MUA is the only place
where the user gets to exert control over message delivery.

   2.  Therefore, only the MUA can make the choice describe above.

   3.  So "some systems" must mean the MUAs.  (Or possibly the
"injector" used by the MUA, but with the same degree of user control.)

   4.  Therefore, and especially since the MTA may be somewhere in the
middle of a long chain of relays from sender to recipient, the MTA
cannot arbitrary change this choice by dropping a BCC header.

   This seems to be the consensus of the list -- that headers are
untouchable after "injection" -- but I wanted to point out how RFC822
supports this.

-- Bob Rogers



problems with qmail-pop3d (fwd)

2000-03-05 Thread Bob Rogers

   From: Vincent Danen <[EMAIL PROTECTED]>
   Date: Sat, 4 Mar 2000 23:16:58 -0700 (MST)

   Not sure if anyone got this, but as an update I re-created the Maildir's
   for all of my users.  I think I had originally done "maildirmake
   ~/Maildir" which might have been the problem... did it this time as
   "maildirmake $HOME/Maildir" and now when I connect with fetchmail it tells
   me it is unable to scan $HOME/Maildir as opposed to the other error
   message.  One step in the right direction, I think, but now I'm really
   stumped.  Why would it be unable to scan?

Let me ask a silly question: Does each owner own his/her ~/Maildir/
tree?

            -- Bob Rogers



/home/rogers/Mailbox:_access_denied

2000-02-12 Thread Bob Rogers

   I just started the process of installing qmail last night, and I'm
having trouble with local mbox delivery.  It has the distinct smell of a
common problem, but I can't seem to find anything in the FAQ (or
elsewhere), and my eyes are getting bleary from reading the mailing
list, so please bear with me.

   I'm on Red Hat 6.0, with VM 6.75 under emacs 20.3 as my MUA:

   Here's what I see in /var/log/maillog when qmail tries to deliver an
enqueued message to my ~/Mailbox file:

Feb 12 10:34:47 hostname qmail: 950369687.686971 starting delivery 39: msg 110876 
to local [EMAIL PROTECTED]
Feb 12 10:34:47 hostname qmail: 950369687.687264 status: local 1/10 remote 0/20
Feb 12 10:34:48 hostname qmail: 950369688.156477 delivery 39: deferral: 
Unable_to_open_/home/rogers/Mailbox:_access_denied._(#4.2.1)/
Feb 12 10:34:48 hostname qmail: 950369688.156733 status: local 0/10 remote 0/20

This has been going on all night.  It appeared to happen at first after
reading the previous batch of messages in VM (which uses movemail), but
deleting the file and recreating it doesn't fix the problem.  Is this a
locking issue?  What am I missing here?

   FWIW, I would like to stick to mbox format, rather than Maildir,
since my needs are simple . . .

   Thanks in advance,

        -- Bob Rogers