Toshiba e-3511 email issues

Hello everyone.
We have a big toshiba copier in our office, shared through CUPS to a windows domain, and a part of it isn't working. Problems started when I attempted to setup department codes to restrict access to colour printing, everything worked well before that. We never had much luck with it, it seemed to make us wait 10 minutes after sending a print job before it would go through.

Then it just stopped working at all. I tracked the problem to CUPS. the printer's status was set to Stopped, though how I'm not sure. I started it again and printing works fine, however the scan to email function is not functional. Whenever it attempts to send a scanned email, it says Failed to send email.

Why this is I'm not sure. What could have gone wrong?

It uses a remote email server we control, with eukhosting. But it doesn't seem that anything is changed there, the problem seems most likely to be in the office.

Any ideas on what could cause this issue?

the only thing I can see that might be wrong, is that in topaccess it's login for the email server is copier+roshni.org.uk rather than copier@roshni.org.uk which is the copier's email account. But I tried changing that and it didn't help so I've reverted it for now.

 

Hi, WarKirby.

Just had a look at your website: kudos to you for your efforts.

As far as the CUPS issue, I have no idea - never worked on it. The one thing that jumps out at me, though, is your statement "Problems started when I attempted to setup department codes to restrict access to colour printing, everything worked well before that." Any way you can revert to a prior status, and start from scratch? Might help identify the problem(s).

I know that's a pretty generic suggestion - just trying to get a handle on it.

 

Hi Caliban, thank you for answering.
Luckily, we've solved the problem now. Turns out it was nothing to do with the department codes, but an error on our part. With a bit of research I figured out that the printer has built in logging and error codes (telling me that would have been helpful) and it gave an error code which means "invalid 'from' email address".

Upon discovering that, we realised that we'd recently deleted the email address it uses on our email server. Have now rerouted it to another one and everything is perfect. :wave

 

Good job - glad you got it. :major