[ms office - 2016] OUTLOOK - Account name (alias) being marked as spam...

[Koldov]

Any Outlook gurus out there...?

 

Long story short, I have a 'personal' LGfL email account ([email protected] - which is a bit of a mouthful) to which I added a shorter alias ([email protected] - we own domain.org.uk) through the LGfL admin settings on their support site. This alias now seems to be detected a spam (a couple of suppliers and support companies haven't received recent emails and found them in the spam folder).

 

Unfortunately a long time ago (I can't remember exactly), when I set up Outlook on my PC I think I chose the 'alias' as the account name and it sends mail as this (but obviously all mail goes through the LGfL account).

 

So, two questions really as I'm not an Outlook expert:

 

1. Is there anyway to stop my 'alias' being classified as spam by external mail servers..?

 

or

 

2. Can I somehow change the way Outlook has set-up the account with the alias to actually use the LGfL mail account without deleting the account and mail..?

 

or

 

3. If I just delete the account in Outlook, am I right in thinking that if I add in the LGfL account and also get it to open the 'alias' account mailbox I will still receive all the mail for both, but not be able to send as the 'alias'.

 

I'm a bit confused because Outlook seems to know it is just an alias, looking at the .OST it is actually named with the LGfL account (so I can't add the LGfL account in seperately because it already exists).

 

[chaplic]

My guess would be domain.org.uk specifies what servers are allowed to send as it via a SPF record, and that doesn't include the LGFL servers. Or paradoxically, there's no SPF records for domain.org.uk and recipients are viewing the emails with suspicion.

[Koldov]

I'd forgotten all about this really...

 

I came up with two issues that I couldn't surmount:

 

1. I can't delete the erroneous 'alias' account within Outlook as it tells me it is the 'Primary' account, I did a bit of internet research but didn't come up with anything (other than deleting all the other accounts first, or completely uninstalling outlook).

 

2. There is the option of 'send as' but if I choose the 'proper' LGfL account to 'send as' in the dropdown box, the email is undeliverable...

 

"This message could not be sent. Try sending the message again later, or contact your network administrator. You do not have the permission to send the message on behalf of the specified user. Error is [0x80070005-0x0004dc-0x000524]."

 

So what you said about SPF records makes sense, but also not (to me anyway, as I'm no email expert), considering the 'alias' is an alias of an LGfL email account...

 

In any case, I decided to create a different email account with our other 3rd party email provider as part of changing everything to a generic IT Support account (in case I ever leave).

Edited January 10, 2022 by Koldov

[Koldov]

Interestingly, as this has piqued my interest again I have sent a message from the 'alias' to my personal account on our other 3rd party email provider and the 'generic' IT Support email account I created (with the same provider).

 

The email to my personal named account came through OK, but the email to the Support email account was classified as junk...

 

 

It says it was "marked as spam using a junk filter other than the Outlook Junk E-Mail filter", so that means it wasn't anything on my end that put it into the junk folder, but the same filter on the 3rd party provider that is used for my personal account (which let the email through)...

 

EDIT: Anyway I've classified it as 'not junk' in Outlook, and now it is delivered to the inbox, but this doesn't help with external suppliers or support contractors who have email filters that seem to be getting triggered...

Edited January 10, 2022 by Koldov

[chaplic]

You can create a new outlook profile by clicking on start...run and entering

 

outlook /profiles

 

This is neither here-nor-there to the mail being delivered to spam.

 

It is almost certainly the server you are using to send email is not authorised to do so.

 

Theres a reasonable message header analyser at Email Header Analyzer, RFC822 Parser - MxToolbox

 

Failing that post the headers here suitably redacted.