can this fix the email issues?

[Synthohol]

hey just an idea, isnt there a way to build a sub compact terminal type computer running linux and an email server program which a lot are free i believe and set it up to forward or relay email from copiers that will never have the TLS/SSL that 365 requires.
gotta be a way to make one for under a hundred bucks.
install on a clients network and config it just for the copier to use.
no more app passwords or firmware dancing.

just an idea.

[Slammers]

On the one hand, yes.

On the other hand, no.

It introduces another random can of worms to manage and diagnose.

In this situation, personally, the client would either have to upgrade their device or scan to a USB stick.
If they were admant that scanning to email must continue and refused an upgrade I would be discussing with accounts.
I understand that many of you support charities/non-profits but there has to be a point where you lay it out, in black in white, that their device is too old to perform securely and they will have to use USB until they can procure a newer device.

[Synthohol]

honestly, and ive done this a few times, find an old laptop running XP and setup scan folders on it and use as an smb file server.
thats where i got the idea for a linux based smtp relay/server. i dont believe it will require maintenance like an Exchange server.

[Slammers]

Could be worth investigating for clients that agree to it.

I would draw the line at an XP machine running on my network though ahaha. You can still scan to folder on Win 11 with ancient MFDs if you change the LMCompatibilityLevel to allow NTLMv1 and configure SMBv1. This would have to be isolated though.

[Synthohol]

the biggest issue with win 11 is most dont support local accounts out of the box.
sharing a folder with a M$ logon or PIN# never worked for me not once.
i dont touch security standards on a customers PC in fear of liability.
i dont even add exceptions to firewalls anymore. let your paid IT guy do it.

[ThisPete]

the biggest issue with win 11 is most dont support local accounts out of the box.
sharing a folder with a M$ logon or PIN# never worked for me not once.
i dont touch security standards on a customers PC in fear of liability.
i dont even add exceptions to firewalls anymore. let your paid IT guy do it.

SMB and PIN has never worked for us either.. we will willingly create a new user, but get the customer to choose a password and make them fully aware that any breeches aren't our fault/responsibility...

[mojorolla]

Check this out:
Raspberry Pi Email Server using Citadel - Pi My Life Up

[Duplicator]

hey just an idea, isnt there a way to build a sub compact terminal type computer running linux and an email server program which a lot are free i believe and set it up to forward or relay email from copiers that will never have the TLS/SSL that 365 requires.
gotta be a way to make one for under a hundred bucks.
install on a clients network and config it just for the copier to use.
no more app passwords or firmware dancing.

just an idea.

Yes.

That is exactly what we are doing. We have customers paying for an email relay hosted by us. So we have to come up with something that will keep working.

We have been through 3 of these with different email hosters over the years. This time I had had enough and decided I had better do it myself. The hardest part has been calling every last customer and trying to get them to open the remote support tool without them thinking you are a scammer.


All you need is a way to run virtual machines, a Linux install DVD, and some IT knowledge to get it going. In some cases it may be "free" by using existing resources. There is a script that will do it all for you: https://www.iredmail.org/

the biggest issue with win 11 is most dont support local accounts out of the box.
sharing a folder with a M$ logon or PIN# never worked for me not once.
i dont touch security standards on a customers PC in fear of liability.
i dont even add exceptions to firewalls anymore. let your paid IT guy do it.

We got totally out of doing SMB. Too many permissions issue. Too many server changes from the contracted IT people. Too hard to reach the right people.

[Synthohol]

each customer would foot their own unit bill, let them buy it outright.
just for copier use only, not host an smtp server yourself.

[Duplicator]

each customer would foot their own unit bill, let them buy it outright.
just for copier use only, not host an smtp server yourself.

The problem is if you don't host it, getting stuff like DKIM, DMARC, SPF, and reverse DNS right is almost impossible. Some places won't even accept the mail in some cases if you don't have all 4 of those just right.

As far as the customer specific stuff goes, Konicas can use Office 365 still, they just have to use the org specific address. In other words myGreatCompany.mail.protection.outlook.com
IT just needs to register their static public IP with the Office 365 control panel so that the Microsoft end knows where it is coming from. Then just turn auth off on the Konica. It's only the main public relay (smtp.office365.com) that is being given the O-Auth treatment.

[Synthohol]

times like this im glad im retired