Hey guys,
I worked it out, very simple...
Log in as root.
Create the following: (where '~/' is your qmail directory, usually /var/qmail)
'~/alias/Maildir'
'~/alias/Maildir/cur'
'~/alias/Maildir/new'
'~/alias/Maildir/tmp'
'chown -R alias /var/qmail/alias/Maildir'
'chgrp -R qmail /var/qmail/ali
John Gonzalez/netMDC admin wrote:
> My local deliver to postmaster/root/mailer-daemon isnt working either, now
> that i check it..
For easy checking you can create a test name that
is not used on your system
I have set up '.qmail-test' and put "&sys_admin_name"
in the file to re-direct messag
[EMAIL PROTECTED] wrote:
> On Wed, Apr 19, 2000 at 10:45:47AM -0700, Anthony White wrote:
>
> Well, the log files would be definitive on this matter. You could
> turn off the forwarding for a while and see what happens.
I guess I could try sending mail to these to check...
>
[EMAIL PROTECTED] wrote:
> On Wed, Apr 19, 2000 at 10:13:36AM -0700, Anthony White wrote:
> > During my initial tests I had no forwarding set up for
> > '~/alias/.qmail-postmaster' or '~alias/.qmail-root'.
> >
> > Any mail to these accounts
Hi there,
I have a successfully running qmail setup. However I initially
used mbox (/Mailbox) configuration. Since it is not
necessary for our users to use MUA's on the server
itself (All access is via POP) I decided to use './Maildir/'
and changed everything accordingly.
During my initial tes
Jeff Dilcher wrote:
> I am having a bit of trouble with the following instruction:
>
> According to the README.var-qmail:
>
> ---
>
> 4) Get the package qmail-1.03-102memphis.src.rpm from this directory.
>This package does not contain the qmail sources; it contains a
>tarbal
I have a quick question about moving a complete working
qmail setup to a new disk drive.
My server has outgrown itself and now needs to be put on
larger drives.
Are there any problem moving ./Maildir/ directories
in the users home dirs to a new drive?
Are there any issues moving qmail itself?
Hi there,
Here comes the final installment on my problems with
sending mail to certain domains.
The problem, as mentioned, was that our domain name
records were set up as non-authoritative. I don't
know how our ISP managed that, but they have changed
the records so that the DNS records are auth
Hi there,
As promised, the explanation to my domain issues.
The ISP holding our domain name records has
set the DNS up as non-authoritative by mistake.
No one can tel me how that happened but we
believe that it happened in conjunction with
a migration of DNS to an other server (Machine).
Now a
Thanks to all who have replied to my "Sender domain must resolve"
problem.
I am not an expert on DNS and our DNS records are held by
a company that has been sold twice over the last 6 months
with resulting staff changes.
Me "barking up the wrong tree" and them going through lots of
changes make
Duncan Watson wrote:
> On Fri, Apr 14, 2000 at 11:14:55AM -0700, Aaron L. Meehan wrote:
> > Quoting Duncan Watson ([EMAIL PROTECTED]):
Why is is so difficoult, why am I getting conflicting messages
as to where the problem is?
> >
> > Even our qmail server (with UCE patches) would reject his
Duncan Watson wrote:
> > All mail sent is shown to come from 'mail.movielink.net.au' with
> > the IP of the firewall. That IP currently resolves to 'mail.movielink.net.au'
> > which does not match with <[EMAIL PROTECTED]> and the error 451 is
> > sent back to us.
> >
> > Should I have that IP
Chris Johnson wrote:
>
> Your name servers appear to be broken:
There is no record pointing to the domain itself. It points
to 'mail.movielink.net.au'
All our incomming mail comes via one IP into a firewall, gets port
forwarded to the mailserver and is processed.
We have no problems receivi
Hi there,
I have a very specific problem sending mail to certain domains that
do reverse verification of mail. They come up with
From: <[EMAIL PROTECTED]> Error, sender domain must resolve...
delivery deferred...
I have set up qmail so it masquerades all mail to come from
'[EMAI
14 matches
Mail list logo
