Cryptic message for end users
Hello, I have a postoffice system based on Postfix+MySQL+Courier-IMAP+Courier-authlib+Maildrop. I have enable quota checking with maildrop. When quota is overcame then Postfix get a permanent error by maildrop and generates a bounce with the following informations: The message is 'as-is' reported by the MTA of the sender, to the sender. This message is clearly too technical for end user which claim that mail system has a fault! Could I configure Postfix so that the message generated by Postfix when the quota is exceeded, is easier to understand by end user? Or is a matter of maildrop? Thanks, rocsca
Re: Cryptic message for end users
* Rocco Scappatura : > Hello, > > I have a postoffice system based on > Postfix+MySQL+Courier-IMAP+Courier-authlib+Maildrop. > > I have enable quota checking with maildrop. > > When quota is overcame then Postfix get a permanent error by maildrop > and generates a bounce with the following informations: > > exists maildrop: maildir over quota.> > > The message is 'as-is' reported by the MTA of the sender, to the sender. > > This message is clearly too technical for end user which claim that mail > system has a fault! > > Could I configure Postfix so that the message generated by Postfix when > the quota is exceeded, is easier to understand by end user? Or is a > matter of maildrop? The latter. It even says so: maildirmake: /pathto/user/: File exists maildrop: maildir over quota. the script you're invoking at delivery time is broken -- Ralf Hildebrandt Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.computerbeschimpfung.de We have joy, we have fun, we have Linux on our Sun!
RE: Cryptic message for end users
Thanks Ralph,
> > I have a postoffice system based on
> > Postfix+MySQL+Courier-IMAP+Courier-authlib+Maildrop.
> >
> > I have enable quota checking with maildrop.
> >
> > When quota is overcame then Postfix get a permanent error by maildrop
> > and generates a bounce with the following informations:
> >
> > File
> > exists maildrop: maildir over quota.>
> >
> > The message is 'as-is' reported by the MTA of the sender, to the
> sender.
> >
> > This message is clearly too technical for end user which claim that
> mail
> > system has a fault!
> >
> > Could I configure Postfix so that the message generated by Postfix
> when
> > the quota is exceeded, is easier to understand by end user? Or is a
> > matter of maildrop?
>
> The latter. It even says so:
>
> maildirmake: /pathto/user/: File exists
> maildrop: maildir over quota.
>
> the script you're invoking at delivery time is broken
What you mean precisely? How I can find the mistake?
Here my maildrop conf file:
log "test -d $HOME$DEFAULT"
`test -d $HOME$DEFAULT`
if ($RETURNCODE != 0)
{
log "mkdir -p $HOME$DEFAULT"
`mkdir -p $HOME$DEFAULT`
log "rmdir $HOME$DEFAULT"
`rmdir $HOME$DEFAULT`
}
log "/usr/local/courier/bin/maildirmake $HOME$DEFAULT"
`/usr/local/courier/bin/maildirmake $HOME$DEFAULT`
log "/usr/local/courier/bin/maildirmake -q $MAILDIRQUOTA $HOME$DEFAULT"
`/usr/local/courier/bin/maildirmake -q $MAILDIRQUOTA $HOME$DEFAULT`
.
.
.
TO "$HOME$DEFAULT"
rocsca
Re: Cryptic message for end users
* Rocco Scappatura :
Error 1: maildirmake: /pathto/user/: File exists
Error 2: maildrop: maildir over quota.
> What you mean precisely? How I can find the mistake?
>
> Here my maildrop conf file:
>
> log "test -d $HOME$DEFAULT"
> `test -d $HOME$DEFAULT`
> if ($RETURNCODE != 0)
> {
> log "mkdir -p $HOME$DEFAULT"
> `mkdir -p $HOME$DEFAULT`
> log "rmdir $HOME$DEFAULT"
> `rmdir $HOME$DEFAULT`
> }
>
> log "/usr/local/courier/bin/maildirmake $HOME$DEFAULT"
> `/usr/local/courier/bin/maildirmake $HOME$DEFAULT`
Either the line above
> log "/usr/local/courier/bin/maildirmake -q $MAILDIRQUOTA $HOME$DEFAULT"
> `/usr/local/courier/bin/maildirmake -q $MAILDIRQUOTA $HOME$DEFAULT`
Or the line above is causing error 1!
> .
> .
> .
> TO "$HOME$DEFAULT"
This causes error 2
--
Ralf Hildebrandt
Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155
http://www.computerbeschimpfung.de
postfix-users@postfix.org: The list that makes you think!
RE: Cryptic message for end users
Thanks Ralph,
> * Rocco Scappatura :
>
> Error 1: maildirmake: /pathto/user/: File exists
> Error 2: maildrop: maildir over quota.
>
> > What you mean precisely? How I can find the mistake?
> >
> > Here my maildrop conf file:
> >
> > log "test -d $HOME$DEFAULT"
> > `test -d $HOME$DEFAULT`
> > if ($RETURNCODE != 0)
> > {
> > log "mkdir -p $HOME$DEFAULT"
> > `mkdir -p $HOME$DEFAULT`
> > log "rmdir $HOME$DEFAULT"
> > `rmdir $HOME$DEFAULT`
> > }
> >
> > log "/usr/local/courier/bin/maildirmake $HOME$DEFAULT"
> > `/usr/local/courier/bin/maildirmake $HOME$DEFAULT`
> Either the line above
>
> > log "/usr/local/courier/bin/maildirmake -q $MAILDIRQUOTA
> $HOME$DEFAULT"
> > `/usr/local/courier/bin/maildirmake -q $MAILDIRQUOTA $HOME$DEFAULT`
> Or the line above is causing error 1!
>
> > .
> > .
> > .
> > TO "$HOME$DEFAULT"
>
> This causes error 2
I will write a more relaible conf from maildrop for the matter of error 1.
While I remove line cousing error 2.
BTW, still Brixen next summer? ;-)
rocsca
RE: Cryptic message for end users
Hello,
> Error 1: maildirmake: /pathto/user/: File exists
> Error 2: maildrop: maildir over quota.
>
> > What you mean precisely? How I can find the mistake?
> >
> > Here my maildrop conf file:
> >
> > log "test -d $HOME$DEFAULT"
> > `test -d $HOME$DEFAULT`
> > if ($RETURNCODE != 0)
> > {
> > log "mkdir -p $HOME$DEFAULT"
> > `mkdir -p $HOME$DEFAULT`
> > log "rmdir $HOME$DEFAULT"
> > `rmdir $HOME$DEFAULT`
> > }
> >
> > log "/usr/local/courier/bin/maildirmake $HOME$DEFAULT"
> > `/usr/local/courier/bin/maildirmake $HOME$DEFAULT`
> Either the line above
>
> > log "/usr/local/courier/bin/maildirmake -q $MAILDIRQUOTA
> $HOME$DEFAULT"
> > `/usr/local/courier/bin/maildirmake -q $MAILDIRQUOTA $HOME$DEFAULT`
> Or the line above is causing error 1!
>
> > .
> > .
> > .
> > TO "$HOME$DEFAULT"
>
> This causes error 2
Ok Ralph, I have solved the two holes in conf file of Maildrop. Now I get the
following over quota message:
< posta.sttspa.it #5.7.0 x-unix; maildrop: maildir over quota.>
Which is still not completely 'human-readble'.
Is it possible to do so that Postfix produce a custom message based on the
error code returned by maildrop?
Thanks,
rocsca
Re: Cryptic message for end users
Rocco Scappatura: [ Charset UTF-8 unsupported, converting... ] > Ok Ralph, I have solved the two holes in conf file of Maildrop. Now I get the > following over quota message: > > < posta.sttspa.it #5.7.0 x-unix; maildrop: maildir over quota.> > > Which is still not completely 'human-readble'. The error message is produced by maildrop, so this is perhaps not the right mailing list. For example, maildrop could export an appropriate enhanced status code; 5.7.0 means "other or undefined security status" which makes little sense here. > Is it possible to do so that Postfix produce a custom message > based on the error code returned by maildrop? A universal error message translator would be an interesting project, but I am not sure that Postfix is the right place. Wietse
RE: Cryptic message for end users
Wietse, > > Ok Ralph, I have solved the two holes in conf file of Maildrop. Now I > get the following over quota message: > > > > < posta.sttspa.it #5.7.0 x-unix; maildrop: maildir over > quota.> > > > > Which is still not completely 'human-readble'. > > The error message is produced by maildrop, so this is perhaps not > the right mailing list. > > For example, maildrop could export an appropriate enhanced status > code; 5.7.0 means "other or undefined security status" which makes > little sense here. > > > Is it possible to do so that Postfix produce a custom message > > based on the error code returned by maildrop? > > A universal error message translator would be an interesting > project, but I am not sure that Postfix is the right place. Very clear. Thanks, rocsca
