Welcome to the mailbox user forum

New Topic

mailbox user forum Topic Problem E-mail: Setup

Mail received via BCC address field is not being actioned correctly by Rule.

GregB shared this problem ago

Published

I have simple mail management rules running that forwards specified received mail into an external account.

Then "Files Into" a nominated local folder. This is working OK when the specified address is in the To or CC address fields.But when the specfied address is in the BCC (Blind Copy) field, it is parsed correctly and forwarded OK but is not filed into the specified folder.

The "file into" action moves the mail, but no idea where to.

(And it does not appear in the spam folder)

The Open-Xchange 8 "Copy Into" action is documented

But I can't find any information on the "File Into" action, documentation, or syntax.

Is this a mailbox.org customisation ?

Anybody have any insight into "File Into" or idea why the mail is going into a black hole ?

many thanks

The same problem 0

Replies (2)

zapata ●

You are aware that the Bcc: header is not part of received e-mails?

"file into" (sieve: fileinto) moves the e-mail to a folder and "copy into" (fileinto :copy) moves a copy of an e-mail to a folder and processes further rules (or keep the e-mail in the INBOX). In both cases you have to select a destination folder.

So maybe another rule is processing the e-mail. You can view your rules with a sieve editor.

Reply URL

GregB ●

Thanks for the reply zapata. This issue started a month ago.

Previously when this address was included in a BCC group it was sucessfuly filed into the correct folder.

Currently BCC'd mail arrives in my inbox and is forwarded successfully to a 3rd party secure mail system.

So the header with the embedded hidden BCC address is being parsed and actioned.

But the following "file into" rule fails to move the BCC'd mail into the correct folder.

I have now found a specific BCC related field in the rule conditions under mail address.

But the syntax again is not clear. Will do some testing with this and see if this resolves the issue.

But I would have expected a disfunctional rule to "do nothing" instead of moving the received email into a black hole.

Also strangly, I have noticed that the pull down for setting the "file into" folder shows the folder root Inbox as fully capitalised "INBOX", which would be inconsistent with the actual path. But the other rules function, so it may not be an issue.

So I created some test emails containg two relevant BCC addresses. Both were received and forwarded and the relevent file into rules ignored. The upside is that the mails were retained in Inbox and not deleted. The only obvious difference being that the mail that disappeared were MS Client generated and my test mails are Linux Client generated.

I'll request a few more BCC test mails from various business sources and see what arrives.

As long as these BCC mails are forwarded OK, this is more of a curious annoyance than a critical problem.

many thanks for the help

URL

GregB ●

Update. Testing Observations.

When a target address is included manually in a MS Exchange BCC field:

The mail is recieved by mailbox and forwarded to a 3rd party secure mail service.

But the "file into" rule fails, leaving the mail in the Inbox.

When a target address is included in a group in a MS Exchange BCC field:

The mail is recieved by mailbox and forwarded to a 3rd party secure mail service.

But the mail vanishes. It is not retained in the inbox and is not filed into a folder.

Note. Have only tested using small businesses that have outsourced to Cloud Based MS Office & Mail

When a target address is included manually in a mailbox BCC field:

The mail is received by mailbox and forwarded to a 3rd party secure mail service.

But the "file into" rule fails, leaving the mail in the Inbox.

When a target address is included manually in a gmail BCC field:

The mail is recieved by mailbox and forwarded to a 3rd party secure mail service.

The "file into" rule fails, leaving the mail in the Inbox.

The disapearing mail issue appears to only impact cloud based MS Exchange Group mail, when sent BCC.

Also interesting that on another account, which still uses the previous rules set with the "copy into" and "redirect to" actions, that everything works OK, except for target addressed mails sent BCC included in a MS Exchange group.

The "copy into" rule fails, the "redirect" rule works, but the mail is retained in the Inbox.

I am going to park this for a week or two, then take another look.

thanks to all for reading and commenting

URL

zapata ●

Do you use

cd8e14b77f59dad64aa28fec0b05bcc7

as condition?

URL

GregB ●

Hello zapata. No. I had assumed "To" was exclusive to the primary "To" field.

Instead I have been adding conditions for To and CC fields plus have been testing [email address/header/bcc]

But it has made no difference. And my focus has been on the "actions" instead.

The headers show what looks like the right handling sequences between the agents with only the contents of the MS groups hidden. I am in the middle of a pfSense to OPNsense migration so my head is in a different space. I'll come back to this again i a week or two. Or when I discover another missing mail :-)

Thanks again

Files:

Reply URL