Topic: Inbox problems

[Stefano]

no, don't edit it

office$ seems a machine account.. do you have/had any windows client named office joined to your server?

[Paperguides]

Office if the name of my windows workstation.

[ReetP]

Tony,

you still haven't told us exactly what you DID do - I know that you have only told us half the story to get in the muddle that you have.

Were you trying to manually copy stuff from a backup ? Why didn't you do a standard backup/restore ?

Leaping in to try and fix something that we do not understand the cause of will probably make matters worse rather than better.

Please go right back and describe EXACTLY what you did with the old server to backup your data, and what you then did with the installation on the new server.

B. Rgds
John

[Paperguides]

I am confused.  The server was working perfectly correctly (as far as I could tell) until I caused it to run out of disk space.  I have never tried to copy any system files 'by hand' only ever done a backup -> restore using the SME web interface.

[Stefano]

Well, if so, you have a problem somewhere, because what I see here is a messer server

[Paperguides]

One step I forgot was resetting broken trust which maent the share was no accessible on my system.

Before I could restore from the shared on my workstation I needed to remove the system from the domain to a workgroup, reboot, rejoin the domain and reboot.  The share was then accessible and the restore completed without error.

Is this relevant?

[Stefano]

Did you do a full restore on a production server?

[ReetP]

I am confused.  The server was working perfectly correctly (as far as I could tell) until I caused it to run out of disk space.  I have never tried to copy any system files 'by hand' only ever done a backup -> restore using the SME web interface.

I'll put it simple terms. It's a bit like algebra.

We currently have 5 = 3 + x

We know 5 = wrong permissions on you mail directories

We know 5 is you managed to run your sik out of space by copying some files across (but we don't know where they came from - were they part of a backup or a.n. other reason)

The issue is the missing x

We know that you would not expect permissions to change just because you ran out of space. So there must be something else in there that we do not know about.

We also have seen lots of similar instances when the user misses out some vial piece of information that they consider irrelevant, but actually explains the whole scenario.

So, can you retrace your path, and answer the question that I asked right at the start. Describe exactly the events prior to the issue. So far it looks like:

You had an old server.

You did a backup to USB

You installed a v9 on a new server

You restored from the USB including all your mail and documents

You then decided to plug in another drive with a various documents that you had stored on it from somewhere, and started to copy them on to the server. That filled the server drive. What happened on the server, and what did you do at that point ?

I'm not trying to be difficult, but the issues you have described so far are not explained by your actions, and neither would they occur if your drive fills up, so the presumption is that something else MUST have happened or action been taken that we do not know about.

B. Rgds
John

[ReetP]

One step I forgot was resetting broken trust which maent the share was no accessible on my system.

And slowly but surely we move towards the root causes of the issue....

Is this relevant?

It may be, or may not, but we need to know everything to be able to tell.....

[Paperguides]

Thank you both for your patience  I really appreciate it.

From memory, which may be incomplete

1) change config on router to disconnect the mail server from Internet.

2) run SME backup to windows share on my win 10 workstation.

3) on completion, disconnect server from network. rebuild from DVD.

4) configure server as previously i.e. same name, IP address, domain.

5) run yum update from console

6) logon from web interface.  set remote access, windows domain name and domain controller.

7) Configure workstation backup as before.

try restore - fails due to permissions.

9) move workstation of of domain to workgroup, reboot

10) login windows as local admin, rejoin domain, reboot

11) login to windows domain

12) attempt restore from web page - success.

13) reconfig router for email link.

14) check email


I think that covers it............

[ReetP]

Thank you both for your patience  I really appreciate it

NP. Just bear with us - the questions we ask have a purpose.....

From memory, which may be incomplete

Yeah, my grey cells seem to be on permanent holiday ! But something is better than nothing.

2 ) run SME backup to windows share on my win 10 workstation.
4 ) configure server as previously i.e. same name, IP address, domain.
5 ) run yum update from console
6 ) logon from web interface.  set remote access, windows domain name and domain controller.
7 ) Configure workstation backup as before.
8 ) try restore - fails due to permissions.
9 ) move workstation of of domain to workgroup, reboot
10 ) login windows as local admin, rejoin domain, reboot
11 ) login to windows domain
12 ) attempt restore from web page - success.
14 ) check email

I think that covers it............

And that is a lot more like it.....

I don't think you needed to do No 6 as the restore should do all the heavy lifting for you.

And No 8 sets the alarm bells ringing.

i can't do more tonight. Others may take a look - if not Stefano might drag his sorry butt out of bed in the morning and join in He knows much more about Windoze nonsense than me.

At least now we have a better idea of what happened and when. If you remember anything else then please fill us in.

Do you still have your original backup ?

B. Rgds
John

[Stefano]

i can't do more tonight. Others may take a look - if not Stefano might drag his sorry butt out of bed in the morning and join in He knows much more about Windoze nonsense than me.

theorically speaking, Stefano is on vacations but

Paperguides: first of all, SME is "just" linux and this give us many, many tools to solve problems.
in your case I see some issues that can't be easily solved from here.

IMO, since your server is for you (one man band, IIUC), you have no contribs installed and few clients in your lan, you'd start from scratch..

- how many clients do you have in your lan?
- how many users in your server?
- how much data in your server?

your mails are not lost and they can be recovered quite easily, but you must exit from the SME way of doing things..

please answer to my questions above, tomorrow, depending on your answers, I'll suggest you how to proceed (gevie you a plan, then you'll decide if follow it)

[ReetP]

theorically speaking, Stefano is on vacations but

Still........ ??????

 

Hot here !

[Stefano]

Still........ ??????

no, again

[ReetP]

no, again

You lucky.....

https://youtu.be/-5i1cJIwE7M