tcp wrappers and webmail

1999-06-02 Thread jasonf


Hello Again,

I think I'm finally getting qmail set up like I want. I'm using Maildir
access and got tcpserver to work instead of inetd. I'm curious, is there
any way to get tcp wrappers to work? I can do it with inetc, but not
tcpserver.

While I'm at it, is there any possible way to create a web-based email
client that doesn't use pop for mail access? I'd like to set up a web mail
reader that could do direct Maildir access w/o being some major security
hole. Is it possible?

Thanks Again,
Jason




Random Qmail Questions

1999-05-27 Thread jasonf


DISCLAIMER: Please forgive me if these are totally pathetic question.
Believe it or not, I have read through the docs, and still haven't figured
things out.

First Question: I've set up qmail to run in Maildir mode. All of my users
now have their pretty little ~/Maildir/ set up. Right now I've got pine
aliased to pinq so that everything will work. I notice that when a user
starts pine, it automatically creates a Mailbox instead of using the
Maildir. Does maildir2mbox do this automatically, or do I have something
set up wrong?

Second Question: I can't seem to send mail to root. Every time I try, a
message ends up in the logs stating:
delivery x: deferral: Unable_to_chdir_to_maildir._(#4.2.1)
I think I have all my permissions set correctly. What could be the
problem? Also, I get the same error message when I send mail to a certain
user, but it waits a second and delivers the mail to that user anyway.
Weird..

Third Question: While looking through the FAQ, I've noticed a lot of mailer
bashing. Under the questions "How to I get x mailer to work with qmail?"
there always seems to be some mention of how that mailer is insecure,
unreliable, and basically worthless. Yet, I don't see any mention of what
one is supposed to use instead. What is the preferred MUA for DJ Bernstein
dittoheads? Is there a mailer with native Maildir support?

Fourth Question: Last question I promise. While looking through the docs,
I've seen lots of recommendations to switch over to various programs,
programs to replace things such as syslog and inet. I've noticed that all
of these replacement programs seem to be in the beta stage. How reliable
are they currently? I'm a bit wary of using beta software to replace
something as important as my syslog and inet! I just wanted to ask before
I try.

Thanks for putting up with all my lame questions.
Regards,
Jason



Re: Random Qmail Questions

1999-05-27 Thread jasonf


 Pine only groks mailboxes, so maildir2mbox moves the messages from a maildir
 to an mbox for Pine's benefit.  In the longer run, consider running an IMAP
 server that handles maildirs.

I realized that it didn't like Maildir, but I thought you could set what
file it used as it's mbox by setting the MAILTMP variable. I've got my
MAILTMP set as something else entirely, yet it insists on using Mailbox.
Why would I want to set up an IMAP server? I don't currently have one
running. The way I see it, the less open ports I've got, the better.

 That's a feature, qmail doesn't want to run as root which it would have to
 do.  Use ~alias/.qmail-root to send root's mail somewhere else.

Ah thank you. I knew I had forgotten to ask something. I aliases work
under qmail. I've got some aliases under people's home directories, so
they can accept mail from other addresses, but I haven't figured out how
the ~alias/.qmail-x works. Do I need to put the address to forward to in
the /.qmail-root file? Is it as simple as that?

 
 People say nice things about mutt.  The rest of us make do with worthless
 unreliable MUAs.

Glad you brought up mutt. I've been wanting to switch to it for some time
now. Unfortunately I haven't found an editor that works with it too well.
It was using vi, but vi seems to forget to wrap the text, so it sends
everything on this one long line. I tried using pico as well, but it sits
there and asks me what file I want to save it as etc., which is just a
pain. BTW, does mutt use Maildir, or will I have to set up a mutq filter
for it as well?

 More reliable than the things they replace.  Dan's definition of beta
 is along the lines of "not known to be bug-free" rather than the more
 popular "runs well enough that maybe the users will debug it for us."
 Like most bits of qmail, tcpserver is really nice once you believe that
 it really is fast and nail down its typical three-mile long command line.

Thanks, I'm into anything that'll save me some memory and a few CPU
cycles. I'll have to give them a try.

Regards,
Jason 




dialup w/ qmail

1999-05-26 Thread jasonf


Greetings all,

I just got finished (mostly) setting up qmail on a server I'm preparing to
put on the net. Until I get my FQDN I'm using a standard ppp connection
and just have localhost.localdomain in all my control files. This allows
me to send mail to others on the server, as well as send mail to other
hosts when I connect it w/ ppp. However, since I don't have a real domain,
I can't seem to receive anything. I try to send mail to the server from a
remote host, and it gripes that the address (whataver.ppp-mfc.etc..) isn't
in the rcpthosts file. I also can't seem to receive pop mail (via
fetchmail) due to the same problem.

Once I get the domain set up, the first problem should go away. However,
I'm not too sure about the second.

Any Ideas?

Thanks,
Jason



Re: dialup w/ qmail

1999-05-26 Thread jasonf


 People should not be addressing mail directly to your server, unless
 it has a sufficiently stable presence on the Internet (static IP,
 DDNS, etc.). They should be sending mail to you c/o your ISP.

Well that's fine. Once I get the static IP/domain I'll add that to the
rcpthosts and all will be well. I was just checking to see if I could send
to it from a remote host while online. Sendmail used to let me do it, but
then again it'd let a person get away with murder if they wished :)

 I'll guess that they say, "localhost" is not in rcpthosts. You could
 just add it; alternately run fetchmail with "-S
 localhost.localdomain", or add "smtphost localhost.localdomain" to
 your .fetchmailrc file. Presumably, "localhost.localdomain" IS in your
 rcpthosts.

That's the basic idea of it. I added the -S option and it worked great.
Hey it wasn't until just recently I realized that fetchmail runs through
the local mail server (duh@me). 

BTW, I notice (as I download 1718 messages from my remote server) that the
hard drive seems to run awfully hard during qmail operations. It's only for
a split second (after flushing each message) but it's somewhat loud. Is
that possibly because qmail writes to the drive asap instead of caching it
in memory or something? I've got Maildir access currently set up, so I
thought maybe the more frequent hd writes had to do with being in my
/home/ directory.

You mentioned setting up a .fetchmailrc. I've never managed to figure out
the syntax. What does a basic .fetchmailrc look like? I'd like to set up a
little cron script to dial up my ISP, make sure it connects, download all
my POP mail and then hangup afterwards. Unfortunately, that'd require me
learning how to write cron scripts as well.

I apologize for all the lame newbie questions. Mailer daemons are not
something I've dabbled with before. I've always just left my system with
whatever defaults it came with and never gave it a second thought.
Switching over to qmail has been a learning experience for me...one that
I'm not regretting.

Jason



rcpthosts

1999-05-12 Thread jasonf


Ok, I sort of asked this question before, but I'm going to try again, this
time with a little more info.

I try to use fetchmail to download mail from another server. While running
fetchmail, it dies saying "fetchmail: can't even send to user!" (user
being whoever I'm logged in as. Later, I received an email to my localhost
from the "fetchmail-daemon" saying "Some addresses were rejected by the
MDA fetchmail sends to" with a Diagnostic-Code: user: 533 sorry, that
domain isn't in my list of allowed rcpthosts (#5.7.1).

What do I need to do to get around this?

THanks,
Jason




More Info (was Re: rcpthosts)

1999-05-12 Thread jasonf

 You still haven't given enough information. What's in rcphosts,
 locals, and your .fetchmailrc (less passwords, of course)? How about a 
 sample of one of those fetchmail-daemon bounces, including the
 complete header?
 
 -Dave


For the time being, my system only has a dialup connection, so all that's
in my rcpthosts and locals is localhost.localdomain. As far as the
.fetchmailrc, I'm actually just typing in it at the command line
"fetchmail -p POP3 -a -u user host.net".

As for the fetchmail bounce, I've attatched the complete message.

Thanks for being so patient,
Jason 



-- Forwarded message --
From: FETCHMAIL-DAEMON@localhost
To: [EMAIL PROTECTED]

Some addresses were rejected by the MDA fetchmail forwards to.


--om-mani-padme-hum-2139-2123-926460989
Content-Type: MESSAGE/DELIVERY-STATUS; CHARSET=US-ASCII
Content-ID: [EMAIL PROTECTED]
Content-Description: 

Reporting-MTA: dns; localhost

Final-Recipient: rfc822; jason
Last-Attempt-Date: Tue, 11 May 1999 16:16:29 -0600 (MDT)
Action: failed
Status: j.0.0
Diagnostic-Code: jason: 553 sorry, that domain isn't in my list of allowed rcpthosts 
(#5.7.1)

--om-mani-padme-hum-2139-2123-926460989
Content-Type: TEXT/RFC822-HEADERS; CHARSET=US-ASCII
Content-ID: [EMAIL PROTECTED]
Content-Description: 

To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
Date: 11 May 99 17:15:00 -0500
Subject: co
Message-ID: [EMAIL PROTECTED]

--om-mani-padme-hum-2139-2123-926460989--




Re: More Info (was Re: rcpthosts)

1999-05-12 Thread jasonf


 [ snip ]
 
 --om-mani-padme-hum-2139-2123-926460989
 Content-Type: MESSAGE/DELIVERY-STATUS; CHARSET=US-ASCII
 Content-ID: [EMAIL PROTECTED]
 Content-Description: 
 
 Reporting-MTA: dns; localhost
 
 Final-Recipient: rfc822; jason
 Last-Attempt-Date: Tue, 11 May 1999 16:16:29 -0600 (MDT)
 Action: failed
 Status: j.0.0
 Diagnostic-Code: jason: 553 sorry, that domain isn't in my list of allowed
  rcpthosts (#5.7.1)
 
 Unless RFC1894 has been updated, recently, fetchmail's DSNs are horribly
 broken.  Write ESR and tell him to fix his buggy code.
 
 -- 
 Sam
 

Is that to say that there's not particularly wrong with my qmail
configuration? Is there some other way to recieve POP3 mail that will work
fine w/ qmail?
Jason