phein4242B
Ask your engineers to configure a local mta that authenticates and forwards all mail. Next, reconfigure all apps.
Ask your engineers to configure a local mta that authenticates and forwards all mail. Next, reconfigure all apps.
So what research did you already do? If you didnt, its better to ask some account or sales person this question…
Have a look at mailcow if you’re new to MTA’s. Use that and a (sub)domain to figure out how to set things up. Once youre satisfied with the setup, reconfigure your domain on the new MTA. Use a mailclient with $yourformat and imap support to import your old email.
And above all, dont be discouraged by the naysayers that think its an impossible task; Its not, but it is complicated to get right bc all the parts involved ;-)
It all depends on what you do with the box, how the applications you run utilize the cpu (single vs multithreaded/multiprocess but also stuff like cpu cache utilization. if you profile the workload that you want to run (see if its cpu, memory or io bound for instance) will help you in figuring out what works best for you.
what error message are you getting?
ngircd has the concept of a global password. Distribute this password and you’ve got a simple psk based acl mechanism
Read the changelogs from 1.5.3 to 1.5.5 and see if you need to take additional steps