Hello guys, As I use postfix and I have implemented a feature for checking the aliases, I was wondering if I could do the same with the quotas. It will sure speed up the process and overcome all problems with the communication between dbmail and the MTA. However I am still not certain it is possible. Nevertheless, dbmail should have the feature to warn the users itself about the full mailbox. We have two possibilities:
1. DBMail warn the user BEFORE the mailbox becomes full, at a certain predefined volume left. 2. DBMail sends a warning to the user the moment it receives an attempt from the MTA which will fill it up. Since dbmail is the one limiting the size it should not be a problem for it to do it :) However, if it is possible to implement the check in the MTA itself then it should send the message (and it will probably not fill the box). As a conclusion, I think temporary failure is good in the following cases: 1. DBMail sends TEMPFAIL to the MTA and a warning to the user and the sender. 2. MTA sends a warning to the sender with TEMPFAIL, keeps the msg in the retry queue and sends a warning to the user. Of course, any working and meaningful combination of those would also do the trick. Please tell me what you think guys. -- Best regards, Bobby [EMAIL PROTECTED] Saturday, May 22, 2004, 3:40:10 AM, you wrote: RA> Feargal Reilly wrote: >> Have a look in the dbmail-dev archives for the thread from >> Febuary called "MTA return codes from dbmail-stmp", that may >> provide you with some of the background. RA> Hmm, but I cannot see the changes proposed in that thread, unless those were RA> to disable dbmail's internal bouncing while not implementing the return RA> codes to allow the MTA to do them... >> IIRC, it was decided over-quota should be a temporary failure as >> the recipient may clear his mailbox within the retry period. I >> think that's in line with other MDAs. RA> I don't think that is very common, I usually get those bounce messages RA> immediately. It is not very likely that a user will clear the mailbox RA> reasonably fast, especially since he isn't notified, and an MTA cannot RA> inject a message to the user about it either (since it's full). I also RA> recall discussion in RFCs, or similar, suggesting this to be a permanent RA> error, but my memory could fail me. RA> Someone should at least send a warning to sender. >> I believe a decision was also made that the error messages are up >> to the MTA, not dbmail. RA> There is at least code left in dbmail's source for generating them. RA> As far as I can see, there is no way for the MTA to know what kind of error RA> happened. dbmail-smtp only returns EX_TEMPFAIL and dbmail-lmtpd a "450 ... RA> TEMP FAIL"; not enough for the MTA to generate a informative bounce message. RA> Unless I've missed something, there is no way the MTA can distinguish RA> between "mailbox full" and any of the numerous other kinds of temporary RA> failures (dns, db, network, etc). RA> The bottom line, if this is the way dbmail now works, how are we supposed to RA> use quotas? RA> Regards, RA> Robert Andersson RA> _______________________________________________ RA> Dbmail mailing list RA> [email protected] RA> https://mailman.fastxs.nl/mailman/listinfo/dbmail
