Small Footprint Media

Thanks for the response. That was not the behavior we were experiencing.

It was creating post slugs using page slugs that already existed. And the content of the post was the content of the preexisting page. Not the content of the email.

As it turns out the ‘title’ and ‘subject’ of the email were identical to the page ‘title’. This appears to be where the issue was.

It was resolved by changing the ‘title’ and the ‘subject’ of the email to be different than the preexisting page ‘title’. The result was that the slugs of the post and the page are now different and the email content is displayed.

I am pretty sure it was the ‘title’ change, not the ‘subject’ change that worked afaict.

Quick follow on – It appears you are already identifying from addresses that are not in the Authorized Addresses list because I received the following email. But you are allowing the email to be created as a draft page. Seems like it could simply not process anything not in the list prior to posting it. Not sure where this email slots into your processing sequence? Thanks Mark

If you wish to allow posts from this address, please add [email protected] to the registered users list and manually add the content of the email found below.

Otherwise, the email has already been deleted from the server and you can ignore this message.

If you would like to prevent postie from forwarding mail in the future, please change the FORWARD_REJECTED_MAIL setting in the Postie settings panel

The original content of the email has been attached.

Hi

1. Yes if activated it displays the whole page with Divi modules. If deactivated it displays just the header and footer.
2. Version 2.8.12
3. We are not using custom rules for this or any other plugin that should affect page display. If the server is configured with this it must be a default setting because we have not modified any server settings.
4. Strangely today 8/16/25 the bat-12-project page construct is displaying with W3TC avtivated. I cannot explain why this is the case. We are going to deactivate W3TC for the next bat-12-project page create process to see if there is an issue occuring during the page create process.
5. We will review your other suggestions.

Thanks M

I enabled ban post blank headers.

There is no entiry in Permanent block list,

Thanks

Update here.

It turns out there was a conflict with a setting in W3 Total Cache plug in that was the primary issue here. It was resolved by disabling Cache Preload > Automatically prime the page cache.

The strange thing is that deactivating WP All In One Security also resolved the issue. Which is why I thought it was All In One Security to start.

Cannot explain the interaction between W3 Total Cache and WP All In One Security but there is something there that is connected to this issue with Divi.

Thanks!

Thanks!

Thanks will try that.