search

CustodesTechnologia / System

The repository devoted to plan, organize and execute work items pursuant to the System
0 stars 2 forks source link

Email alias mapping #28

Open sibomots opened 2 years ago

sibomots commented 2 years ago

For each email role (alias) define the behavior:

Ingress:

mail sent to alias_x goes to addressA, addressB, etc..

mail sent to alias_y goes to addressP, addressQ, etc..

Egress:

mail appears sent by alias_z goes to addressX, addressY, etc...

etc..

Are there any cases where destinations (right side of alias mapping) is also an alias? like:

mail sent to alias_w goes to alias_x, and address_R

Are any of the address_TBD hosted on the site? or are all address_TBD third party addresses? a mix?

Brother-Tyler commented 2 years ago

If I'm reading this correctly, we could have (and these are hypothetical)...

Administrator@bolterandchainsword.com

Email sent TO that account can go to the personal email addresses of each of the admins

AND

Admins can send emails from their personal accounts via the B&C (as opposed to using their normal email provider) and they will look like they came FROM the @B&C account

Similarly, we could set up Herald@bolterandchainsword.com with the same effects (only with the Heralds' personal email addresses).

Correct? If so, that would work.

I'm a bit more foggy on the previous email setup. We had email addresses that worked at one time, but those stopped quite some time ago. Argos and/or Kurgan can probably provide much better information on how the email system used to work.

sibomots commented 2 years ago

I'll take each question one at a time.

BroT> If I'm reading this correctly, we could have (and these are hypothetical)...

Administrator@bolterandchainsword.com

Email sent TO that account can go to the personal email addresses of each of the admins

S> Yes, mail sent to Administrator@bc can go to any alias(es) or address(es) you want. BroT> AND

BroT> Admins can send emails from their personal accounts via the B&C (as opposed to using their normal email provider) and they will look like they came FROM the @b&C account

S> This requires that BC supports "POP" like mail boxes. The mail sent by JoeAdmin intended to appear sent from @bc would need to route through the mail processing on BC which means that BC has to establish a POP box (IMAP, APOP, etc..) Just a system issue.

S> JoeAdmin would need to be given credentials to allow this. Part of a system issue.

BroT> Similarly, we could set up Herald@bolterandchainsword.com with the same effects (only with the Heralds' personal email addresses).

S> For Hearld@Bc to receive email, see first response. It's a simple alias for ingress of messages. S> For sending mail from Hearald@bc requires (again) a POP/IMAP/whatever account setup on BC.

Correct? If so, that would work. S> Yes

I'm a bit more foggy on the previous email setup. We had email addresses that worked at one time, but those stopped quite some time ago. Argos and/or Kurgan can probably provide much better information on how the email system used to work

sibomots commented 2 years ago

small / sporadic / limited use email is fine. No hassle.

but for any case where the BC wants to send out 10's of thousands of emails? Won't happen. Puts a red light on us as spam-source. And the blowback from bounced email and response handling would bury the server.

sibomots commented 2 years ago

Need the list of aliases/groups

Brother-Tyler commented 2 years ago

In the long-term, will we be able to modify aliases/groups through the AdminCP? Or will this always require mucking around with code? The accessibility of the work will drive how far we go. If it's accessible to the average mook (like me) via the AdminCP, I'd like to extend it to the mods. If it's not accessible and/or requires above average technical know-how, we'll limit it to the admins.