Ok, so it appears that Exchange online accounts experience the same problems and MS is looking to "fix" this problem as it is changing the messages and causing the DMARC failures as seen here:

https://blogs.msdn.microsoft.com/tzink/2016/05/19/why-does-my-email-from-facebook-that-i-forward-from-my-outlook-com-account-get-rejected/

So my question is to the Mercury32 developers, can you also do this so that I can effectively use the basic forwarding and Aliases functions in Mercury32?  Our users use the "Forward file" setting so that they can set their own forwarding themselves and I don't have to be involved. 

If not, I will have no choice but to move to some other platform as the way our user operate we need to use this type of forwarding as they have an use multiple email addresses.

Thanks,

MP

Hi

I have a rule set up that forwards mail received by some staff members to their Google apps Gmail account.

The mail is received fine but for some, Google's mail servers refuse delivery because the message fails the original sender's DMARC policy. This is received by the original recipient and by our postmaster account:

--- Problems not related to specific addresses in the message:
   550 Message from username@lloydsbanking.com failed sender's DMARC
policy
   *** username@lincsheritage.org.test-google-a.com

The senders think their mail has not been delivered at all, not realising it is just the Google Apps Gmail account that has not received the message (as I understand it). Does anyone know if there is a way around this, please?

Thanks

[quote user="Greenman"]

Hi

I have a rule set up that forwards mail received by some staff members to their Google apps Gmail account.

The mail is received fine but for some, Google's mail servers refuse delivery because the message fails the original sender's DMARC policy. This is received by the original recipient and by our postmaster account:

--- Problems not related to specific addresses in the message:
   550 Message from username@lloydsbanking.com failed sender's DMARC
policy
   *** username@lincsheritage.org.test-google-a.com

The senders think their mail has not been delivered at all, not realising it is just the Google Apps Gmail account that has not received the message (as I understand it). Does anyone know if there is a way around this, please?

Thanks

[/quote]

If this is the same as the Yahoo Mailing List problem from April 2014, then you can't just forward the mail.  You need to change the sender to ensure that it doesn't break the DMARC policy.

I have had to unsubscribe yahoo addresses from my mailing lists because of this (although I am working on a Mercury policy to get around this.)

Thanks, Paul

These messages are not part of a Mercury mailing list or any other mailing/distribution etc., list.

Some of our staff need to work in local authority offices. The local authorities do not allow IMAP connections to our mail server at our office, but they do allow http connections to Google Apps services. So, these staff (there are only a couple), have Google Apps Gmail accounts. I have configured Mercury to forward mail addressed to these users to their Google Apps accounts so they can manage their mail while at the local authority offices.

Do you know how to change the sender's address? Looking at the Mercury manual and the options available from the filtering dialog, the only other options are Copy and Move. Copy and Move won't work because the dialog's Action field asks for local addresses.

[quote user="Greenman"]

These messages are not part of a Mercury mailing list or any other mailing/distribution etc., list.[/quote]

It is likely to be a similar problem.

[quote]Some of our staff need to work in local authority offices. The local authorities do not allow IMAP connections to our mail server at our office, but they do allow http connections to Google Apps services. So, these staff (there are only a couple), have Google Apps Gmail accounts. I have configured Mercury to forward mail addressed to these users to their Google Apps accounts so they can manage their mail while at the local authority offices.

Do you know how to change the sender's address? Looking at the Mercury manual and the options available from the filtering dialog, the only other options are Copy and Move. Copy and Move won't work because the dialog's Action field asks for local addresses.

[/quote]

As you have discovered, the standard "forward message" filter doesn't change the From: address of the message.  The methods I use to get around this problem are currently all manual :(

[quote user="PaulW"]

As you have discovered, the standard "forward message" filter doesn't change the From: address of the message.  The methods I use to get around this problem are currently all manual :(

[/quote]

Ah, thanks, Paul. How do you do that? I can't access mail messages for other members of staff, and to compound the issue, the affected account belongs to one of the senior managers. Does your manual method require accessing the message directly?

[quote user="Greenman"][quote user="PaulW"]

As you have discovered, the standard "forward message" filter doesn't change the From: address of the message.  The methods I use to get around this problem are currently all manual :(

[/quote]

Ah, thanks, Paul. How do you do that? I can't access mail messages for other members of staff, and to compound the issue, the affected account belongs to one of the senior managers. Does your manual method require accessing the message directly?

[/quote]

Yes. I send them to another mailbox and forward them manually, so that isn't ideal for you by the sound of it.

Thanks - I'd not thought of that. But, as you say, I can't, and don't want to, see other people's mail. Do we know if the ability to forward as another user might be a feature that will be introduced to the next version of Mercury?

[Edit]
Ha! Just re-reading that I can see all sorts of potential for abuse so probably not.

Hi,

Well I appear to have the same issue.  With these DMARC implementations, it basically renders FORWARDING RULES in Mercury useless.  

Does anyone have a solution other than manually editing headers in emails?

This is nuts....fight spam and completely wreck the ability to forward emails to other accounts?

Thanks,

MP 

[quote user="Mrpush"]

Hi,

Well I appear to have the same issue.  With these DMARC implementations, it basically renders FORWARDING RULES in Mercury useless.  

Does anyone have a solution other than manually editing headers in emails?

This is nuts....fight spam and completely wreck the ability to forward emails to other accounts?

Thanks,

MP 

[/quote]

Since posting this I discovered that our issue was the result of a lack of configuration options from our business email filtering provider's service. Since migrating to a new provider we have been able to configure their settings so that the strict controls usually applied to messages where delivery is controlled through DMARC are relaxed. However, our issue only related to deliveries to a Google Apps (G-Suite) address.

Mercury/32 and DMARC are doing the job they are supposed to do. If you use a 3rd party email filtering service, you may be able to configure delivery options so that deliveries to particular address from domains using DMARC are forwarded without infringing the DMARC policy.

Hi,

Well I don't use any 3rd party forwarding service, is it out of line to ask if/why Mercury32 could not provide this functionality?   These dmarc rules have effectively made both the forwarding and aliases functionality in Mercury32 useless for us.   

Any way a Mercury32 rule can rewrite the header to make these emails "follow" the dmarc rules?  I need some automated process, and I can't believe this is not a huge problem for everybody so how in the world is everyone else coping with this?  

I can't get any emails from one account forwarded to another without being rejected. (of course some do go through but not if originally from Aol or Yahoo accounts etc)

Thanks,

MP

I've just had a look at our provider's rule and it simply allows the delivery of these messages based on the recipient address. They obviously have a lot more going on behind the scenes than is visible to us mere mortals.