3 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: Maildrop 1.3....
FromSent OnAttachments
Jaroslaw J. PysznyJul 3, 2001 12:51 pm.patch
Sam VarshavchikJul 3, 2001 2:38 pm 
Charlie WattsJul 5, 2001 1:00 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Re: Maildrop 1.3.3 patch (EX_NOUSER and maildrop: signal 0x0B )Actions...
From:Charlie Watts (cewa@frontier.net)
Date:Jul 5, 2001 1:00:27 pm
List:net.sourceforge.lists.courier-users

On Tue, 3 Jul 2001, Sam Varshavchik wrote:

Jaroslaw J. Pyszny writes:

I've problem with unknow virtual user, because maildrop sends EX_TEMPFAIL (message stays in queue) - I think correct is to send EX_NOUSER and bounce message.

If the mail address is invalid, your mail server should be returning the message as undeliverable, instead of trying to deliver mail to a nonexistent address. Fix your mail server's configuration.

Sam is right, really, for a few reasons.

What you want to do is teach postfix about your users as well, so that postfix can bounce the mail during the SMTP session, instead of accepting the mail and then later bouncing it.

When you have a lot of users, it can be a -large- load on your server to accept mail for _any@mydomain.com, and then have to bounce much of it later. Bouncing mail means you are sending - often to non-existant hosts, etc. It's also mildly rude to claim to accept mail you can't really deliver.

But: Your patch looks like it should work; Especially on a small scale. I've done the same in the past, before I taught postfix about my local users.

Lemme know if you need help with the postfix side.

-- Charlie Watts cewa@frontier.net Frontier Internet Systems Janitor and Network Plumber http://www.frontier.net/