mukil / dm4-mail Goto Github PK

Sending mails via professionally administrated mail services is probably the best way to go with this send mail utility, esp. for a multi-user setup.

Mail
-> From is currently a "Composition" but we also have a Sender Assoc Type
-> Tois currently a "Composition" but we also have a Recipient Assoc Type

To avoid having two distinct associations for expressing the same relation between entities we will investigate how to switch the implementation to "Custom Association Types", which is available since 4.6.

As it looks to me the Assoc Type Sender (composite, childTopic=E-Mail Address) was used to express at least the following relations:

• a "Contact" (=Person or Institution) relating somehow to a User Account
• a "Contact" (=Person or Institution) for a somehow related Signature
• a "Contact" (=Person or Institution) as Sender of a Mail (possibly duplicating? the Composition of "From" to "Mail")

See #11

The current "attachments" realization requires users to always "Upload" the files they want to sent (to their selected file-repo).

DeepaMehtaUtils.stringsToJson(errors.get(mailError));

As of 4.7 filerepos can run either be configured to "global" (one) or "per-workspace" (many).
The latter case is not yet supported by this implementaiton.

As of DeepaMehta 4.7 "acService.getCreator()" is no longer.
The proper "fallback" solution would be to user the first "Signature" for the authenticated user.

Just editing the "Signature" topic and re-assigning the Person fixes this.

Currently "dm4.mail.signature" is related via "Many" but that cardinality should be "One".

As of DeepaMehta 4.8 this workaround won't be needed anymore.
See https://trac.deepamehta.de/ticket/908

Especially for sending mails to mail services which have set "strict parameters" for SMTP clients (Postfix stands here exemplary for any mail service) like http://www.postfix.org/postconf.5.html#smtpd_helo_required