Its only one single TAB for any account.
Its true that its valid for non-hosted domains (relaying).
smtpaccess.dat was owned by root, which is now changed to daemon:daemon =
even world had read rights bedore chaning.
I''ll wait and see what happend for my users.
Tnx so far.
----- Original Message -----
From: "Rodrigo Severo" <rodrigo.lists@...>
To: "Lars Holmstr=F6m" <lars.holmstrom@...>
Sent: Thursday, May 29, 2003 11:43 AM
Subject: Re: [courier-users] Relaying denied
Lars Holmstr=F6m wrote:
> Some of my users got "513 Relaying denied.:" listed in maillog.
> They all use OE6. SOme of them sit on the same subnet and som eon
> another subnet as the courier 0.42.2
> They all have an entry in /etc/courier/smtpaccess/default
> <ipaddress> allow,RELAYCLIENT
> 172.24.1.176 allow,RELAYCLIENT
You must have one and only one <tab> between the IP address and the
allow keyword. Check that.
> May 28 23:45:45 mail2 courieresmtpd:
> <mailto:patrik.gunnarsson@...>>: 513
> Relaying denied.
> After they have been inserted here Ive run "makesmtpaccess"
Are you sure smtpaccess.dat is readable by the couriersmtpd process?
Change it's owner to the user courier is running as if in doubt.
> 1) Do I have to restart courier afterwards ?
> 2) Even after having restart courierI got the same problem. Even some
> users have reported that they do not always got the relaying denied, b=
> only sometimes.
Probably only when they try to send a message to a domain you don't host=
> Can some one give me a hint for what the probem is and how to correct
> it, or is there anything I can do in order to trace this in detail ?
I can't think of any thing else.
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
courier-users mailing list