@pete-s In the US they tend to say "as short as possible." Email is always a legal quagmire and the best thing to do is to delete is as quickly as possible. Which, of course, can't be that fast. So we are generally talking 1-2 years. But you rarely want to keep it longer not because it likely contains details of people breaking the law, but because a legal discovery request is extremely expensive and a great way to attack even otherwise honorable businesses. It's a huge cost you can leverage against someone that they can only reasonably mitigate by not having much email to go through.
Man - that would be so awesome. But even if management did agree that - you'd have people that would be looking for ways to maintain the data for a much longer period - like printing and saving in a cabinet.. shudder.
I like many of the replies I get about cleaning out email. "Why, its free!" "Why, my 50 GB of email is nothing when we have 16TB drives for $200" "Why do I have to remove email older than 13 years, it isn't hurting anyone" "Why would I do that, I may need it later (Medicare Newsletters prior to 2010)" and the list goes on and on.
Then my next question is - if something is so important that you need to keep it - why is it in email in the first place? Why can't you get that data someplace else more related to whatever it is you're saving it for? (That said, I realize that other documentation for something simply don't exist).
Don't you dare get me started down this path. I had HUGE arguments about this with an ex-employee over the period of 10 years. The user could not/would not understand her email box is not a document database / DMS. The last I counted, she had over 300 different nested folders in her email.
Now that the user is gone, their mail copied to a shared mailbox for management to hunt/search and waste their time with if they choose.
It probably easier to have retention policy in place from the start.
If you know email retention is time-limited, you'd have to come up with some other way to store things.
But some people are just hopeless no matter what...
For a few people to use? or for an entire organization and forced through policies?
For a small organization where everyone would change their email signature themselves or have an admin do it for them.
If we had the html for one email signature it would be simple to create a script that would create the individual email signatures.
For a relatively small group of people, most companies we work with just have one decision maker create their own, then distribute it to everyone else.
The decision makers usually can't figure out how, so we (IT) hold their hand through the process.
Use their e-mail program of choice.
Do it in HTML.
Use standardize fonts (This doesn't mean don't use fancy fonts, it means use fonts that are likely in most OSes.)
Send it around with cut and paste instructions, asking each employee to edit the Name, Title and phone extension accordingly.
For groups under 25, we just do it, it's faster for to just do it than to teach 22 people about signatures. 🙂
That messages means a lot of things but yeah Whitelist on their Spam Filter end, Adding your IP to your SPF record, check if there is anything on the body of the message triggering the block on their end (i.e. URL or site link).
It is Office 365 with Exchange - I have created all the records that Microsoft wanted me to.
So, just to be clear, this is 100% not on my end, correct?
It shouldn't be on your end, the message is coming from the recipient's end server.