From: Patrick Beart [mailto:[EMAIL PROTECTED]
>
> >From: Patrick Beart [mailto:[EMAIL PROTECTED]
> >>
> >> I'm having problems with mail delivery to a new account on my
> >> server(s). The messages bounce with a "513 relay denied" error.
> >> (see below)
> >>
> >> The guy who set this up (the Courier Mail server) disappeared
> >> on me and didn't provide much documentation on how all of this
> >> is configured. Thus, I'm scrambling to sort it out. I'd
> >> appreciate any suggestions on WHERE to look on the system (RH
> >> 7.2 Pro, with Courier 0.40).
> >
> >I would suggest going to http://www.courier-mta.org and reading
> >the Installation document and the FAQ. Based on the information
> >you gave, your config directory is in /etc/courier, so most of the
> >config files referenced in those documents will be in that
> >directory. This also probably indicates that Courier was
> >installed from RPMs, so you can keep that in mind while reading
> >the Installation document.
>
>
> Thanks, but I've TRIED reading the FAQ and the docs on Courier. I
> find them somewhat suitable for people (read: Geeks) that work with
> mail servers on a regular basis, and highly confusing and
> inadequate for everyone else (read: novices like me). This is by NO
> means any criticism toward Sam. It's simply an issue, I suspect,
> with being-too-close-to-the-subject-matter. My admin found that,
> once sufficient knowledge was acquired, the docs DID help quite a
> bit. It's that "steep learning curve" thing, again. ;-)
>
> I also checked the list archive for "513 relay" errors and only
> found 2 posts.
>
> I'm not opposed to "RTFM". However, in Courier's case, there isn't
> one! Even my admin - the guy who disappeared on me, after all of
> this was setup - took several months to get this all figured out
> ... and HE does deal with this stuff (mostly Windows NT and such)
> on a regular basis.
Yes, there is a somewhat steep learning curve and Courier's
documentation is a bit scattered. That's why I also gave you some
pointers on where to start with this particular problem.
Courier is the first mailserver that I ever tried configuring. I ran
into a couple of problems that I was able to get help with from this
list, but I didn't find it overly complex. I would suggest starting
with the Installation document. It walks you through installing the
software and configuring the major bits. It will help you learn
about the various configuration files and the different ways that the
server can be set up.
> >You've also got virtual users set up through userdb. Check out
> >the output of 'userdb -show [EMAIL PROTECTED]' and compare it
> >to the userdb settings for an account that works properly.
>
>
> This didn't work for me. Perhaps I'm reading it incorrectly. This
> is what I got:
>
> -----
> [EMAIL PROTECTED] root]# userdb -show [EMAIL PROTECTED]
> /etc/courier/userdb: not a file.
>
> [EMAIL PROTECTED] root]# clientdomain.com.userdb -show [EMAIL PROTECTED]
> bash: clientdomain.com.userdb: command not found
> ------
>
> The actual contents of /etc/courier/userdb/ are:
>
> lrwxrwxrwx 1 root root 85 May 17 14:24
> clientdomain.com.userdb ->
> /home/domains/clientdomain.com/courier/conf/clientdomain.com.userdb
Ah...Your userdb is a directory instead of a simple file. In that
case, the syntax is a bit more complex. Try this:
userdb -show clientdomain.com.userdb/[EMAIL PROTECTED]
or
userdb -show -f /etc/courier/userdb/clientdomain.com.userdb
[EMAIL PROTECTED]
One of these should work. My userdb is a single file, so this just
comes from reading the userdb man page.
> Viewing the contents of the actual directory (and not the pointer),
> at /home/domains/... shows that the file,
> "/home/domains/clientdomain.com/courier/conf/clientdomain.com.userdb"
> is EMPTY.
> --> What process inserts data into this userdb file?
The userdb program manages the userdb file/directory. Do you have
any functioning email accounts on the server? If you can't find them
listed in a file under the userdb directory, you may be using a
different method for authentication. MySQL maybe? I use userdb
myself, so if you're using something else, you will need to find
someone else to help you figure it out.
> >Also, if this is a new domain for the mail server, you will need to
> >list it in one of the files under /etc/courier/esmtpacceptmailfor.dir
> >(to allow Courier to accept mail for the domain) and
> >/etc/courier/hosteddomains (to tell Courier to deliver the mail
> >locally).
>
>
> The path, /etc/courier/esmtpacceptmailfor.dir lists the following:
>
> -rw-r--r-- 1 root root 231 May 17 14:13 hosted
> -rw-r--r-- 1 root root 14 Feb 21 16:22 locals
> -rw-r--r-- 1 root root 17 Mar 29 18:37 relays
> -rw-r--r-- 1 courier courier 0 Feb 22 15:13 webadmin
>
> The domain, "clientdomain.com", is listed in the "hosted" file.
That sounds good, but maybe the server doesn't know about it yet.
Try running 'makeacceptmailfor'. This will take all the stuff listed
in that directory and move it to the database that the server
actually uses.
If the domain is listed here, you should not get any relaying denied
messages for emails going to that domain.
> >...snip... Once you have a general idea of how the
> >server is configured, we can help you out with more specific
> >questions.
>
> What information or data do I need to provide that would be
> more helpful??
Nothing in particular with this problem other than what I mentioned above.
Bowie
-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
