On 22/05/2004, at 9:02 PM, Sven Jacobs wrote:
On Saturday 22 May 2004 01:20, Phillip Hutchings wrote:
So what does that mean? It's not suited for local mail delivery? A
lot
of
programs send mails to xyz@localhost addresses, fetchmail or cron for
example. Do I have to use another MTA for my purpose?
They do? Could have fooled me, because the always seem to send to the
address I tell them to...
Well, which one is better: Setting x programs to not send to
@localhost or
changing the behavior of one program (namely Courier) to accept those
mails.
What is so bad about accepting not fully qualified domain names for
local
delivery, nobody will be hurt. As long as they are set up in locals,
Courier
should accept those domains. That's a logical behavior and would ease
the
setup of local mail delivery.
It suggests that the administrator has not undertaken proper
configuration of the program in question. I have never seen a message
sent to @localhost, even when accepting defaults. Albeit I don't use
fetchmail, but surely piping though sendmail is a better choice for
local delivery.
But I don't think that it shoud be the job of the administrator to
patch
Courier. The patch should go into the next Courier release. I, for
example,
am using Gentoo. I would have to adjust an Gentoo ebuild (similiar to
an RPM
packet) or work around the package manager of Gentoo, which are both
not very
fine solutions.
It's not that hard, just compile put the patch in to the right place
and change the ebuild to run the patch. Can't remember the syntax
offhand. Anyway, if you supply the patch to enable the functionality
Sam may include it, but don't hold your breath for someone to code it.
I've been lurking on this list for many months now and you're the first
I can remember asking for this...
9 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: Courier for l...
