Here's an odd one: @40000000477c1866206baccc delivery 30202: deferral: /usr/bin/maildrop:_Unable_to_create_a_dot-lock_at_/var/vpopmail/./.maildir/25184.0.ark.//
I see a few of these... aside from the usual "Unable to create log file" error that maildrop kicks out for aliases or emails that don't belong to actual accounts. Any ideas? > On Jan 2, 2008, at 11:13 AM, Matthew Goodman wrote: >> My customers use Qmailadmin to administer their email boxes. For some >> reason, when they create an account using Qmailadmin, unless they >> "Enable >> Spam Detection" a .qmail file is NOT created. Is this normal >> behavior from >> what you know of it? I suppose this might be the wrong list, but >> again, >> Qmailadmin's behavior does not explain why after the upgrade >> Vpopmail has >> a problem delivering mail. > > > This is normal behavior -- if email should just be placed in the > user's Maildir, no .qmail file is necessary. > > It sounds like your vdelivermail is having problems. Have you > checked the qmail-send logs? It should be showing you why there's a > temp failure. > > I am personally using 5.4.20 on my system, and according to the CVS > logs, vdelivermail in 5.4.26 is the same as in 5.4.20. > > -- > Tom Collins - [EMAIL PROTECTED] > Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ > QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/ > > > > > > !DSPAM:477c18c2310546724113822!
