Le 19 avr. 2014 à 20:01, Viktor Dukhovni a écrit :

> On Sat, Apr 19, 2014 at 07:01:45PM +0200, Axel Luttgens wrote:
> 
>>      action=REJECT Mailbox is unavailable
>> 
>> This is then what I get in the SMTP conversation:
>> 
>>      554 5.7.1 <END-OF-MESSAGE>: End-of-data rejected: Mailbox is unavailable
>> 
>> Where does this substring "<END-OF-MESSAGE>: End-of-data rejected: " come 
>> from?
> 
> This is how "REJECT" is implemented.
> 
>    /*
>     * REJECT means NO. Use optional text or generate a generic error
>     * response.
>     */
>    if (STREQUAL(value, "REJECT", cmd_len)) {
>        dsn_split(&dp, "5.7.1", cmd_text);
>        return (smtpd_check_reject(state, MAIL_ERROR_POLICY,
>                                   var_map_reject_code,
>                                   smtpd_dsn_fix(DSN_STATUS(dp.dsn),
>                                                 reply_class),
>                                   "<%s>: %s rejected: %s",
>                                   reply_name, reply_class,
>                                   *dp.text ? dp.text : "Access denied"));
>    }

Hello Viktor,

Once again, thank you very much for your patience with such a lazy guy (aka 
"me").

Indeed, I have to confess I didn't think to check the source code: I'm 
currently a bit in a hurry, since I have to set up a workaround for a quota 
policy server that should work and that doesn't for some obscure reasons I'm 
trying to discover since several months...


>> Can it be avoided?
> 
> No.

Well... This is perhaps the opportunity for a feature request?

Such messages are liable to be shown in a MUA user interface.
But end-users often tend not to read such messages, especially when they are a 
bit complicated, too technical.
Would there be an easy way, I mean without rewriting a bunch of code, to avoid 
such frightening tech pieces ("<END-OF-MESSAGE>", "End-of-data"...)?

Wishing you a nice evening,
Axel


Reply via email to