Ok, this speaks to a problem I've been futzing with for a while now: How to provide a list of valid dbmail users to sendmail. You see, I'd like to be using dbmail to handle the aliased users on the server I run, but not stop the local mail from using the default system of delivery (sendmail->procmail->local mail spool). This means that I have two options: 1) Let sendmail send all unrecognised users to dbmail (yeck!!) 2) Find some decent way to supply sendmail with an updated file in the same format as aliases.db based on the dbmail user/delivery alias list. I'd prefer to do the second, and as I'm out of lightweight ideas for it, I figured I'd throw this out on the list now as it seems to be related to the issue hitherto replied.
If there is a really cool way to make sendmail process the pending "67" return value, then somebody please tell me about it--and by all means help this guy with a standard return value! In any case, having my problem sorted out will make it possible at long last to post and out-of-the-box solution for those of us whom are brave (or insane) enough to be running sendmail and to want a dbmail backend (full or partial, as the case may be). > > ______________________________________________________________________ > From: Michael Häusler <[EMAIL PROTECTED]> > To: DBMAIL Developers Mailinglist <dbmail-dev@dbmail.org> > Subject: Re: [Dbmail-dev] Nonexisting aliases or invalid entries in > deliver_to only cause temporary failures > Date: Tue, 23 Nov 2004 14:28:45 +0100 > > Hello, > > >> in DBMail 2.0.0 a call to dbmail-smtp -d > [EMAIL PROTECTED] > >> results in a temporary failure (exit code 75) instead of no such > user > >> (exit code 67), which causes the mta (e.g. Postfix) to redeliver > over > >> and over again. I had several thousand mails stuck in the mail > queue > >> due to this behaviour :-( > > >> Is there a reason for dbmail not to return code 67 in this case? > > *hopes not* Having this fixed and returning the right data would be > > really spiffy, IMHO. -sc > > I am a bit relieved that I am not the only one with this problem. > > The current behaviour is a real problem, because of two reasons: > > a) as Sean explained, the sender of such an email gets no immediate > response, that his mail could not be delivered. > > b) I get much spam to randomly generated email addresses at my domain. > These mails were not simply thrown away, as they would have been with > a > response of "no such user". They stick in the mail queue and create > *huge* amounts of unnecessary delivery attempts, which severely > degrades > perfomance. It rendered our mail server almost unusable. > > Imho this should be addressed before 2.0.1. > > Best regards, > Michael > > -- |^^^ | | |^^| |^^^ Drew Northup, N1XIM |^^| | |^^^ \ / /^^\ /^^~ |__ | | | | | suoc.syr.edu |__| | |___ \/ |__| |__ | | | | | | savannah.nongnu.org/ | | | /\ | | | \ ___| |__| |__| |___ projects/plex86/ | |___ |___ / \ \__/ \__/
