Hey Mark
Well, I guess I misunderstand you, and it's a bit hard for me to write
it down in words what I try to reply.
I still cannot figure out what your role is in this scenario. Do you
serve one-man-businesses or do you speak about larger comapnies? I don't
get why log-in credentials need to be saved on your system. Such should
never leave the businesses own server.
So, I have my domain for private use. The mail for my domain is handled
on my root server. If I would think about starting my own business,
maybe get some friends for customer support in, I would setup a general
business address on my root, like supp...@cryptearth.de. The only access
to this would be managed by a CMS back-end wich is used by my staff by
its front-end. So my staff may have internal e-mail-addresses used for
internal communication, but all e-mails going out to customers only goes
through the CMS wich uses the support address as sender. There would be
no relation between the staff member wich wrote the message nor would
the access credentials be stored on each system used by staff but only
once at the CMS back-end.
On the other side, I know a former colleague wich made his living by
offering a small online shop offering individual LEGO parts. It would
total overkill for him to get his own domain or even his own mail-server
like me, so he uses a small webspace and an personalized e-mail-account
provied by its ISP. So he works with a simple mail-client (like outlook
or thunderbird) instead of a complex CMS.
Maybe I'm not the best to reply as I maybe didn't understood your
question or your current situation. I guess also that you're serving
others with a service instead of trying to setup for your own is what
get's over my competence.
I'll give your question another read, maybe I come up with another reply.
Matt
Am 16.04.2019 um 18:29 schrieb Mark Gordon:
Thanks for the reply Matt.
So we may have a customer that uses microsoft 365 or gmail for their
internal email. We can setup each used (customer service person or sales
person) with their own email address in the system. The system will send
the email using their authentication just like any other email client would
we store the password encrypted in our servers. If the user changes their
credentials they need to change their credentials on our system as well...
just like they would on any other email client. And that works fine. Some
users have multiple outbound from addresses if the customers has multiple
websites or brands they are selling from. Also they may have generic from
addresses that any use can send from such as "sa...@xyz.com" or "
i...@xyz.com", as you said in your reply. Many sales people and customer
service people with small companies like to send email with their own email
address but some do use the generic system wide addresses.
Our system can also have one or more relay email senders that can send
email for any email address. Then the individual credentials don't need to
be setup for each user of the system. We can manage the credentials
externally from the individual users and if they change their email
password it does not affect our system. In the past we have used
mailgun.com for this. You can simply create one account to do all the
sending of email for the entire system. Then you don't get the support
calls that someone's email stopped working because they changed their
password.
We have legacy customers that are used to this setup because in the past
many smtp servers were setup so you could send using any from address on
the server and the from address would be different than they authentication
address (account). Now gmail/office 365 and most other smtp servers no
longer allow this. So one day no email was going out anymore and we had to
setup and maintain individual email accounts for all users of the system.
There are plenty of services that can do this and mailgun is doing a good
job. I was just looking to see if we could offer this to our customers. I
setup a james system a while ago and it seemed like you had to be managing
all the email for the domain to get the outbound stuff to work. I guess I
need to take another look. After I get back into it maybe I will have some
more specific config questions related to where I got stuck last time.
Thanks again for the quick reply (sorry for the wall of text).
-Mark
On Tue, Apr 16, 2019 at 9:06 AM cryptearth <cryptea...@cryptearth.de> wrote:
Hey Mark
Sure, James can be set up this way as any other mail-server. But: Why?
Customer management systems (CMS for short) split into two parts:
front-end: the interface your staff members uses - and the back-end wich
does all the database stuff and outside world communication.
So, your back-end should already set up with a common address used for
outgoing mail independent from wich staff member the message was sent.
It sounds more like your CMS needs serious re-work in terms of how it
works under the hood then try to relay mails to "solve the symptom".
Matt
Am 16.04.2019 um 17:55 schrieb Mark Gordon:
Is it possible to setup James as a relay to send emails to and from
people
that are not setup with an account inside James? That is just use a
generic account to send email for all from addresses?
The use case is to send out transnational email for ecommerce. I
currently
use an email smtp provider to send out transactional emails (order
confirmations/shipment confirmations etc). I have a single account with
this provider that sends mail for all the customer service people.
The from addresses will be from email addresses are handled by a
different
email system like gmail. All this system is doing is just sending the
emails out. The thing is I would rather not create an address on the
James
system for every customer service person. I would rather have a single
authenticated account that is sending out all the email.
Thanks,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
