|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Wietse Venema (wietse_at_porcupine.org)
Date: Mon Sep 02 2002 - 10:06:00 CDT
The exit status codes that you refer to are part of the MTA to
application interface. The values of the exit status codes are
defined in /usr/include/sysexits.h.
sysexits.h has no code for "user mailbox over quota". However, if
procmail would be willing to emit such text to stdout or stderr,
then Postfix would be happy to send it back to the originator (*).
Wietse
(*) As with many things, the text is limited to avoid run-away
problems. Postfix collects up to 4 kbyte of command output when
delivering mail to an external command.
Jim Worke:
> Hi,
>
> I'm using procmail and blackhole with postfix. Everything went smoothly,
> except in the bounced messages that need tuning.
>
> For procmail, when the user is overquota, the error given back to postfix is
> 73, which is "can't create user output file". Does anyone know what code to
> return to postfix such that the error given back to the sender is something
> similar to "User's mailbox is overquota".
>
> Similarly for blackhole, any bounce would give an error to the sender as:
>
> <user1
test.com> user unknown. Command output: SPAM detected.
>
> I believe this is because of wrong error code returned to postfix? Because
> user1 do exist and the command output is correct, which the email was
> detected as a SPAM and thus bounced. But the "user unknown" phrase, I think
> it's the error code?
>
> Anyone can shed a light on this?
>
> Thank you
> -
> To unsubscribe, send mail to majordomo
postfix.org with content
> (not subject): unsubscribe postfix-users
>
>
-
To unsubscribe, send mail to majordomo
postfix.org with content
(not subject): unsubscribe postfix-users
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]