Skip to content

Commit

Permalink
Fixes #349 - Changed directory for unprocessable mails
Browse files Browse the repository at this point in the history
  • Loading branch information
ralf401 committed Sep 15, 2023
1 parent e036b08 commit 759e051
Showing 1 changed file with 6 additions and 5 deletions.
11 changes: 6 additions & 5 deletions admin/console/other-useful-commands.rst
Expand Up @@ -18,8 +18,8 @@ Reprocess unprocessable mails

When Zammad encounters a mail it cannot parse (e.g. due to a parser bug or a
malformed message), it will store the mail in
``tmp/unprocessable_mail/<ID>.eml``, give up on attempting to parse the mail,
and will warn on the monitoring page that there are unprocessed mails.
``var/spool/unprocessable_mail/<ID>.eml``, give up on attempting to parse the
mail, and will warn on the monitoring page that there are unprocessed mails.

To force Zammad to reattempt to parse those mails, run the following command:

Expand All @@ -28,11 +28,12 @@ To force Zammad to reattempt to parse those mails, run the following command:
>> Channel::EmailParser.process_unprocessable_mails
In case of a malformed message (e.g. an invalid email address in one of the
header fields), you may need to manually edit the mail before Zammad can process it.
header fields), you may need to manually edit the mail before Zammad can process
it.

If Zammad fails to process the message, it will remain in the
``tmp/unprocessable_mail`` folder; otherwise it will be removed after it has
been parsed successfully.
``var/spool/unprocessable_mail`` folder; otherwise it will be removed after it
has been parsed successfully.

Add translation
---------------
Expand Down

0 comments on commit 759e051

Please sign in to comment.