G
Guest
1. I have an offsite E-Mail Server in another Country running SENDMAIL
2. If Sendmail receives mail from an untrusted domain it appends a SENDER
tag to the email header. This tag will always contain the name of my server.
Example:Sender: <[email protected]>
3. Outlook (XP) will neatly sort my inbox on the FROM: field properly
4. The Rules Wizard will NOT use the FROM: Field even when directed to do
so. It always defaults to the SENDER: field instead.
I need either:
1. A way to strip the Sender Tag from the headers
OR
2. A way to force Outlook to use the FROM: field when setting up rules.
This BUG became a problem when my Email provider moved to a more secure
server system that uses the SENDER: field to back track SPAM. All of my
existing RULES that are set up for specific clients (about two hundred in
all) stopped working as OUTLOOK now thinks all the mail is coming from the
SENDER: instead of from the FROM:
VERY FRUSTRATED HERE. And Seriously considering changing to a NON Microsft
E-Mail program to solve this problem. Not good considering my company is a
Microsoft Partner.
https://partner.microsoft.com/US/program/levels/certifiedpartner/
2. If Sendmail receives mail from an untrusted domain it appends a SENDER
tag to the email header. This tag will always contain the name of my server.
Example:Sender: <[email protected]>
3. Outlook (XP) will neatly sort my inbox on the FROM: field properly
4. The Rules Wizard will NOT use the FROM: Field even when directed to do
so. It always defaults to the SENDER: field instead.
I need either:
1. A way to strip the Sender Tag from the headers
OR
2. A way to force Outlook to use the FROM: field when setting up rules.
This BUG became a problem when my Email provider moved to a more secure
server system that uses the SENDER: field to back track SPAM. All of my
existing RULES that are set up for specific clients (about two hundred in
all) stopped working as OUTLOOK now thinks all the mail is coming from the
SENDER: instead of from the FROM:
VERY FRUSTRATED HERE. And Seriously considering changing to a NON Microsft
E-Mail program to solve this problem. Not good considering my company is a
Microsoft Partner.
https://partner.microsoft.com/US/program/levels/certifiedpartner/