

In efforts to get things a bit more automated and at same time not filling up your queue too fast I've decided to write this powershell script. The only problem with this solution is that when you push out 1200 emails to replay folder you will get a large queue of emails. you can remove PAUSE if you're sure what you're doing. This makes sure you can see your results before continuing. Don't think it will change much but you can always try.Ĭd C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Replay REM This part should be used only to retry reprocessing BAD files. Move "C:\Program Files (x86)\GFI\MailEssentials\EmailSecurity\FailedMails\*.eml" "C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Replay\" cmd file and execute following: REM Processing FilesĬd C:\Program Files (x86)\GFI\MailEssentials\EmailSecurity\FailedMails While doing this manually is one way you can actually script this a bit. But do not worry, this usually means the email format is bad and therefore it wouldn't pass to Exchange anyways. If that happens… well you're out of luck. If things go wrong the file extension will change from. If everything is ok, you should notice the file extension changing from. eml and putting them inĬ:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Replay folder. You can do that by renaming file extension from. TXT files are your standard emails we can simply pass them to Exchange to be reprocessed. PROP can be freely deleted (you can leave them for gfi to verify things) Fortunately the fix is pretty simple.įiles.


While generally the issue should be resolved with vendor and can be caused by one of antivirus engines breaking things… the real issue has to be fixed as over 500 emails were stopped before being deliverd.Īctually this 500 emails became 1200 in just few hours.
