I should also note that I'll probably want all of the mail for [root,
postmaster, mailer-daemon]@ to go to [EMAIL PROTECTED]
Don't know if I'll need to set up those addresses in ~users/assign, or if
!alias/.qmail-other-com-root, etc would catch them.
On another note, anyone know why checkpoppass
Since the user receiving the mail must OWN the directory it is finally
delivered to, symlinks won't work. Forwarding is your best option. :)
On Tue, 2 Feb 1999, Matt Garrett wrote:
> D'oh!
> That would help, wouldn't it.
> Okay, problem solved. Next problem.
>
> I still can't seem to deliver m
D'oh!
That would help, wouldn't it.
Okay, problem solved. Next problem.
I still can't seem to deliver mail for [EMAIL PROTECTED], even though I have
~alias/.qmail-[root, postmaster, mailer-daemon] all set up to be
"./operator/Maildir/" and ~alias/operator is a symlink to /home/me, on which
I hav
Use the protocol correctly and it will work. :)
220 plutonium.mayod.nb.net ESMTP
EHLO mayod.nb.net
250-plutonium.mayod.nb.net
250 8BITMIME
MAIL FROM:<[EMAIL PROTECTED]>
250 ok
RCPT TO:<[EMAIL PROTECTED]>
250 ok
DATA
354 go ahead
testing
.
250 ok 917968202 qp 10149
QUIT
221 plutonium.mayod.nb.
I've fixed my DNS CNAME snafu and my ~control/locals, and now when I
`telnet me.domain.com smtp`
HELO
MAIL [EMAIL PROTECTED]
RCPT [EMAIL PROTECTED]
DATA
Subject: Test message.
testing
.
QUIT
and then look in the qmail logs on me.domain.com, it shows an accepted
connection and...
starting deliver
