EMailSenderNodeConfiguration2
Namespace: Meshmakers.Octo.MeshAdapter.Nodes.Load
Configuration for node SendEMail@2.
v1 carries exactly one attachment, described by four sibling properties, and offers no way
to reference it from the body. A billing dispatch therefore spends its only slot on the
invoice PDF and cannot also carry the community logo the template wants to show (AB#2570).
v2 replaces the four properties with a list, and lets an entry declare a
EMailAttachment.ContentId so the body can address it as cid:<id>.
public record EMailSenderNodeConfiguration2 : PathNodeConfiguration, INodeConfiguration, IEquatable<NodeConfiguration>, IPathNodeConfiguration, IEquatable<PathNodeConfiguration>, IEquatable<EMailSenderNodeConfiguration2>
Inheritance Object → NodeConfiguration → PathNodeConfiguration → EMailSenderNodeConfiguration2
Implements INodeConfiguration, IEquatable<NodeConfiguration>, IPathNodeConfiguration, IEquatable<PathNodeConfiguration>, IEquatable<EMailSenderNodeConfiguration2>
Properties
ServerConfiguration
Well-known name of the EMailSenderConfiguration entity associated with the pipeline.
public string ServerConfiguration { get; set; }
Property Value
SubjectPath
Path to the subject line.
public string SubjectPath { get; set; }
Property Value
ToPath
Path to the recipient address or array of addresses.
public string ToPath { get; set; }
Property Value
CcPath
Path to a CC address or array of addresses.
public string CcPath { get; set; }
Property Value
CcAddresses
Literal CC addresses. Used INSTEAD of EMailSenderNodeConfiguration2.CcPath when non-empty, not in addition to it - same precedence as v1.
public ICollection<string> CcAddresses { get; set; }
Property Value
BccPath
Path to a BCC address or array of addresses.
public string BccPath { get; set; }
Property Value
BccAddresses
Literal BCC addresses. Used INSTEAD of EMailSenderNodeConfiguration2.BccPath when non-empty, not in addition to it - same precedence as v1.
public ICollection<string> BccAddresses { get; set; }
Property Value
Attachments
Files to attach. An entry with a EMailAttachment.ContentId is linked into the HTML body instead of being listed as a separate file.
public List<EMailAttachment> Attachments { get; set; }
Property Value
BodyFormat
What the body at Path actually is.
v1 ran Markdig over every body regardless. A NotificationTemplate carries a RenderingType
for exactly this decision, and it used not to reach the sender at all, because
GetNotificationTemplate@1 forwarded only subject and body - so a template declaring PLAIN
was still sent as converted HTML. That was not only cosmetic: an author writing "A)" got
an ordered list, and a literal {netto=100} was absorbed into the enclosing tag as
an HTML attribute by Markdig's generic-attributes extension. The node now forwards it via
RenderingTypeTargetPath, which EMailSenderNodeConfiguration2.BodyFormatPath reads.
public BodyFormats BodyFormat { get; set; }
Property Value
BodyFormatPath
Path to a NotificationTemplate's RenderingType, as written by
GetNotificationTemplate@1. When it resolves, it wins over
EMailSenderNodeConfiguration2.BodyFormat - the template says what it is, the node should not overrule
it. Plain renders as text, Html goes through Markdig, anything else falls back.
public string BodyFormatPath { get; set; }
Property Value
ReplyToPath
Path to a Reply-To address. A tenant usually sends from a no-reply mailbox while wanting answers to reach its own contact address.
public string ReplyToPath { get; set; }
Property Value
ReplyToAddress
Literal Reply-To address, used when EMailSenderNodeConfiguration2.ReplyToPath is not set.
public string ReplyToAddress { get; set; }
Property Value
Path
public string Path { get; set; }
Property Value
Description
public string Description { get; set; }
Property Value
Constructors
EMailSenderNodeConfiguration2()
Caution
Constructors of types with required members are not supported in this version of your compiler.
public EMailSenderNodeConfiguration2()