Note to all, this problem was caused because the maildrop.log file hit
2 gigs. MIght want to add this to the faq.

Thanks,
Erik

On 8/3/07, Kyle Quillen <[EMAIL PROTECTED]> wrote:
>
>
> On 8/3/07, Jake Vickers <[EMAIL PROTECTED]> wrote:
> > Kyle Quillen wrote:
> > > Hey all,
> > >
> > > Since I sent the last email i have tried reinstalling maildrop and it
> > > does not seem to help.
> > >
> > > still getting this in the logs.
> > >
> > > @4000000046b38f513219283c delivery 1691: deferral:
> maildrop:_signal_0x19/
> > > @4000000046b38f51321933f4 status: local 3/10 remote 77/300
> > > @4000000046b38f513293a3b4 delivery 1692: deferral:
> maildrop:_signal_0x19/
> > > @4000000046b38f513293ab84 status: local 2/10 remote 77/300
> > > @4000000046b38f513412b234 delivery 1693: deferral:
> maildrop:_signal_0x19/
> > > @4000000046b38f513412f49c status: local 1/10 remote 77/300
> > > @4000000046b38f5135202a94 delivery 1694: deferral:
> maildrop:_signal_0x19/
> > > @4000000046b38f513520558c status: local 0/10 remote 77/300
> > >
> > >
> > > the strange part is that all my forwarders still work fine.  But I am
> > > assuming that this is because the forwarders get processed before
> > > maildrop takes over?
> > >
> > > is there a way to take maildrop out of the equation to at least get
> > > this temp backup and running
> > >
> >
> > Do the users affected have the mailfilter script enabled?  What does the
> > .qmail-default file look like?  I know this error popped up from time to
> > time when a user was over quota and the system was trying to send them a
> > bounce....
>
>
> This is what my .qmail file looks like
>
> &[EMAIL PROTECTED]
> |/var/qmail/bin/preline /usr/bin/maildrop -A 'Content-Filter:
> maildrop-toaster' /etc/mail/mailfilter
>
>
> thanks
> q
>
>
>
>

---------------------------------------------------------------------
     QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to