trigger sieve after redirect to achieve compliance to German law #2350
Unanswered
derStephan
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I want to have a GoBD compliant setup where I put every incoming or outgoing mail into an archive.
The requirement is to make a copy of all inbound and outbound in a secure place in case you have to proove that you are not involved in corruption.
My approach is to have a sieve script at data stage:
The script in else makes a copy to another mailbox:
godb_mailweiterleitung:
redirect :copy "[email protected]";The script with the condition should only run in the archive mailbox and flag the mail as seen.
gobd_mailablage:
require["imap4flags"]; setflag "\\seen";The first one is running alright. But the one with the condition is never triggered. In fact, the redirect does not even show up in trace log. So I am assuming, that local redirect is not really an SMTP step. Is that correct?
Where can I trigger a sieve script after local redirect? Flagging the mail as seen is only the beginning, later it should sort mails into folders by year/month. And it should be deduplicated.
If I get this to work, I will happily share my results. Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions