Predefined __Macro__fields

[Manfred Muschiol]

Hello,

if I create a mailaction "Notify", I will be presented by the standards:

[...]
Proxmox Notification:

Sender: __SENDER__
Receiver: __RECEIVERS__
Targets: __TARGETS__
[..]

But if the notify mail arrives, the content of __Receivers__ and __Targets__ are mostly/always the same.

This is not very usefull.

Instead I shoudl see a list of all mentiones receivers.

This means a

__to__
__CC__

where it is visible what are the intended receivers of this mail, so called the content of the TO and CC-Fields.

__targets__ is ok, because different rules will match for differnet receivers even they are in the same mail.

Is it possible to define such macros by hand? Or a macro with parameter where I can fill in the wanted mailheader-fields?

I test this for a archiving solution, beause a simple BCC-Object is not enough for archiving, because it is hard to parse the qualification strings out of the mailheaders, so this fields should be moved to a standard part of a mail attached wiht the original mail.

If I only use a BCC Object, I am not able to "classifiy" the mail going to the archive.

Kind regards
-mm-

 

[dietmar]

Hello,
Instead I shoudl see a list of all mentiones receivers.

This means a

__to__
__CC__

where it is visible what are the intended receivers of this mail, so called the content of the TO and CC-Fields.

__targets__ is ok, because different rules will match for differnet receivers even they are in the same mail.

Is it possible to define such macros by hand? Or a macro with parameter where I can fill in the wanted mailheader-fields?

no

I test this for a archiving solution, beause a simple BCC-Object is not enough for archiving, because it is hard to parse the qualification strings out of the mailheaders, so this fields should be moved to a standard part of a mail attached wiht the original mail.

If I only use a BCC Object, I am not able to "classifiy" the mail going to the archive.

Well, I think for archive purposes you want to know who really received that mail, and that are the envelope receivers (__RECEIVERS__).

Both TO and CC Fields are content fields. In many cases (spam) they contain absolute nonsense, and are unrelated to mail delivery.

Do you really want to rely on such fields? Isn't it better to use __RECEIVERS__ for archiving?

 

[Manfred Muschiol]

Archiving

Hello,

the archiving process is behind all spamcheckings.

Due to the (surely realy stupid) legal demands in germany, we must archive every mail we have successfully received. Successfully in this terms means "mails relayed to the endusermailbox".

In this case, the to and cc-fields are more or less true, or the subject is tampered with *possible spam*.

But regardless of this. If we have to retrieve mails out from the archive, we should see, who else have got this mail. It is not enough, if only 2 partners are visible, but the receviers are a lot of other people.

Now, if we don´t use the bcc action, we lost the information, who are the other receivers of this mail.

Kind regards

-mm-

 

[dietmar]

Any serious mail archiving solution does allow you do get all those informations. So what kind of archiving solution do you have?

- Dietmar