[xmail] Re: Error message since updating to 1.20
Yes I agree that $mailroot/spool/local and $mailroot/spool/temp are documented and exist in distribution, but the problem occurs when someone wants to clear out the spool they kill all the folders under $mailroot/spool Yes I agree, if you don't know what your doing (and you kill too many folders) then you deserve to have pain. The problem is that these individuals then create noise here wanting help fixing, when a simple check in xmail will create the folders as well as the numbered folders at xmail start, and there is less noise. This also improves the appearance of the stability of Xmail when it fixes up after dumb mistakes. I suppose if the error message that occurred was a little more specific - ie. Error - Mailroot/spool/local folder missing would do just the same. Less noise = more IMAP coding. grin Rob :-) _ Censorship can't eliminate evil; it can only kill freedom. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Wednesday, 16 June 2004 2:27 AM To: [EMAIL PROTECTED] Subject: [xmail] Re: Error message since updating to 1.20 On Tue, 15 Jun 2004 [EMAIL PROTECTED] wrote: We have ALWAYS had to make those DIR manaually. Xmail has never made them for us. Only the numbered ones does it make. Yes, the numberred ones. Tell me again why would you remove directories from the XMail structure? They *are* in the supplied MailRoot and they are documented to be required. - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Error message since updating to 1.20
I knew XMail recreated the numbered folders on start-up. I took if for granted that as it recreated the numbered folders it would also recreate the other two. I found the problem when I compared the problematic XMail server to the other one which was still running fine. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Arends Sent: 16 June 2004 09:37 To: [EMAIL PROTECTED] Subject: [xmail] Re: Error message since updating to 1.20 Yes I agree that $mailroot/spool/local and $mailroot/spool/temp are documented and exist in distribution, but the problem occurs when someone wants to clear out the spool they kill all the folders under $mailroot/spool Yes I agree, if you don't know what your doing (and you kill too many folders) then you deserve to have pain. The problem is that these individuals then create noise here wanting help fixing, when a simple check in xmail will create the folders as well as the numbered folders at xmail start, and there is less noise. This also improves the appearance of the stability of Xmail when it fixes up after dumb mistakes. I suppose if the error message that occurred was a little more specific - ie. Error - Mailroot/spool/local folder missing would do just the same. Less noise = more IMAP coding. grin Rob :-) _ Censorship can't eliminate evil; it can only kill freedom. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: Wednesday, 16 June 2004 2:27 AM To: [EMAIL PROTECTED] Subject: [xmail] Re: Error message since updating to 1.20 On Tue, 15 Jun 2004 [EMAIL PROTECTED] wrote: We have ALWAYS had to make those DIR manaually. Xmail has never made them for us. Only the numbered ones does it make. Yes, the numberred ones. Tell me again why would you remove directories from the XMail structure? They *are* in the supplied MailRoot and they are documented to be required. - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Error message since updating to 1.20
I found what the problem was. The two folders that were not numbered under the /spool directory were missing. I created them then everything worked fine. Thanks, Alex -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: 14 June 2004 17:36 To: [EMAIL PROTECTED] Subject: [xmail] Re: Error message since updating to 1.20 On Mon, 14 Jun 2004, Alex Young wrote: Hi, I keep receiving an error message when trying to send emails and I am stuck to what the problem may be. It wasn't doing this on version 1.18 so I don't know if something has changed to cause this error. Requested action aborted: (-19) local error in processing I looked up the error code and it says; ERR_FILE_OPEN (-19) Unable to open file Which file can it not open? Does it happen right on connection? Try to match your MAIL_ROOT directory structure with the reference one that is listed inside the doc. - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Error message since updating to 1.20
This error has been seen before, is it possible / wise to have xmail create them if they are not there at start up? Your thoughts Davide ? Rob :-) _ Censorship can't eliminate evil; it can only kill freedom. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Young Sent: Tuesday, 15 June 2004 5:55 PM To: [EMAIL PROTECTED] Subject: [xmail] Re: Error message since updating to 1.20 I found what the problem was. The two folders that were not numbered under the /spool directory were missing. I created them then everything worked fine. Thanks, Alex -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: 14 June 2004 17:36 To: [EMAIL PROTECTED] Subject: [xmail] Re: Error message since updating to 1.20 On Mon, 14 Jun 2004, Alex Young wrote: Hi, I keep receiving an error message when trying to send emails and I am stuck to what the problem may be. It wasn't doing this on version 1.18 so I don't know if something has changed to cause this error. Requested action aborted: (-19) local error in processing I looked up the error code and it says; ERR_FILE_OPEN (-19) Unable to open file Which file can it not open? Does it happen right on connection? Try to match your MAIL_ROOT directory structure with the reference one that is listed inside the doc. - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Error message since updating to 1.20
On Wed, 16 Jun 2004, Rob Arends wrote: This error has been seen before, is it possible / wise to have xmail create them if they are not there at start up? Your thoughts Davide ? It does, when it boots. My policy on this is: If you want to manually screw up with the internal folder structure, you *have* to suffer. - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Error message since updating to 1.20
We have ALWAYS had to make those DIR manaually. Xmail has never made them for us. Only the numbered ones does it make. - Original Message - From: Rob Arends [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, June 15, 2004 8:36 AM Subject: [xmail] Re: Error message since updating to 1.20 This error has been seen before, is it possible / wise to have xmail create them if they are not there at start up? Your thoughts Davide ? Rob :-) _ Censorship can't eliminate evil; it can only kill freedom. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Young Sent: Tuesday, 15 June 2004 5:55 PM To: [EMAIL PROTECTED] Subject: [xmail] Re: Error message since updating to 1.20 I found what the problem was. The two folders that were not numbered under the /spool directory were missing. I created them then everything worked fine. Thanks, Alex -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Davide Libenzi Sent: 14 June 2004 17:36 To: [EMAIL PROTECTED] Subject: [xmail] Re: Error message since updating to 1.20 On Mon, 14 Jun 2004, Alex Young wrote: Hi, I keep receiving an error message when trying to send emails and I am stuck to what the problem may be. It wasn't doing this on version 1.18 so I don't know if something has changed to cause this error. Requested action aborted: (-19) local error in processing I looked up the error code and it says; ERR_FILE_OPEN (-19) Unable to open file Which file can it not open? Does it happen right on connection? Try to match your MAIL_ROOT directory structure with the reference one that is listed inside the doc. - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Error message since updating to 1.20
On Tuesday 15 June 2004 12:22, [EMAIL PROTECTED] wrote: We have ALWAYS had to make those DIR manaually. Xmail has never made them for us. Only the numbered ones does it make. What OS are you using? They are created correctly for me on Linux. Jeff - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Error message since updating to 1.20
Davide Libenzi wrote: On Tue, 15 Jun 2004 [EMAIL PROTECTED] wrote: We have ALWAYS had to make those DIR manaually. Xmail has never made them for us. Only the numbered ones does it make. Yes, the numberred ones. Tell me again why would you remove directories from the XMail structure? They *are* in the supplied MailRoot and they are documented to be required. A little off topic, but somewhat related (directories, and Xmail's behavior if they're missing). For us that have been using Xmail for a lng time, the directory for each domain under *cmdaliases* doesn't always exists, since they weren't created by older versions of xmail... This only causes problems when removing domains (or at least I think that's the only problem). Not a big deal, but it did throw me for a bit. The change log when upgrading to 1.2 did say you needed to make the cmdaliases directory, but I don't recall it saying making a directory for each existing domain under it was required... If it's not required no error should happen on removal of a domain that's missing it. - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Error message since updating to 1.20
On Tue, 15 Jun 2004, John Kielkopf wrote: For us that have been using Xmail for a lng time, the directory for each domain under *cmdaliases* doesn't always exists, since they weren't created by older versions of xmail... This only causes problems when removing domains (or at least I think that's the only problem). Not a big deal, but it did throw me for a bit. The change log when upgrading to 1.2 did say you needed to make the cmdaliases directory, but I don't recall it saying making a directory for each existing domain under it was required... If it's not required no error should happen on removal of a domain that's missing it. You are not required to create domain directories inside cmdaliases. XMail simply checks for the existance of files, and if it doesn't find them, it proceeds with local lookup (mailusers.tab). - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Error message since updating to 1.20
Davide Libenzi wrote: On Tue, 15 Jun 2004, John Kielkopf wrote: For us that have been using Xmail for a lng time, the directory for each domain under *cmdaliases* doesn't always exists, since they weren't created by older versions of xmail... This only causes problems when removing domains (or at least I think that's the only problem). Not a big deal, but it did throw me for a bit. The change log when upgrading to 1.2 did say you needed to make the cmdaliases directory, but I don't recall it saying making a directory for each existing domain under it was required... If it's not required no error should happen on removal of a domain that's missing it. You are not required to create domain directories inside cmdaliases. XMail simply checks for the existance of files, and if it doesn't find them, it proceeds with local lookup (mailusers.tab). But, if you delete a domain that is missing that directory, you get an error. - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Error message since updating to 1.20
On Tue, 15 Jun 2004, John Kielkopf wrote: Davide Libenzi wrote: On Tue, 15 Jun 2004, John Kielkopf wrote: For us that have been using Xmail for a lng time, the directory for each domain under *cmdaliases* doesn't always exists, since they weren't created by older versions of xmail... This only causes problems when removing domains (or at least I think that's the only problem). Not a big deal, but it did throw me for a bit. The change log when upgrading to 1.2 did say you needed to make the cmdaliases directory, but I don't recall it saying making a directory for each existing domain under it was required... If it's not required no error should happen on removal of a domain that's missing it. You are not required to create domain directories inside cmdaliases. XMail simply checks for the existance of files, and if it doesn't find them, it proceeds with local lookup (mailusers.tab). But, if you delete a domain that is missing that directory, you get an error. No wait. XMail does create domain directories inside cmdaliases when you create a domain with the CTRL interface. - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Error message since updating to 1.20
Davide Libenzi wrote: On Tue, 15 Jun 2004, John Kielkopf wrote: Davide Libenzi wrote: On Tue, 15 Jun 2004, John Kielkopf wrote: For us that have been using Xmail for a lng time, the directory for each domain under *cmdaliases* doesn't always exists, since they weren't created by older versions of xmail... This only causes problems when removing domains (or at least I think that's the only problem). Not a big deal, but it did throw me for a bit. The change log when upgrading to 1.2 did say you needed to make the cmdaliases directory, but I don't recall it saying making a directory for each existing domain under it was required... If it's not required no error should happen on removal of a domain that's missing it. You are not required to create domain directories inside cmdaliases. XMail simply checks for the existance of files, and if it doesn't find them, it proceeds with local lookup (mailusers.tab). But, if you delete a domain that is missing that directory, you get an error. No wait. XMail does create domain directories inside cmdaliases when you create a domain with the CTRL interface. Yes, but older versions of Xmail ( 1.2 ) didn't, so many of my older domains don't have these directories. - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Error message since updating to 1.20
On Tue, 15 Jun 2004, John Kielkopf wrote: Yes, but older versions of Xmail ( 1.2 ) didn't, so many of my older domains don't have these directories. Ok, I'll put a check in 1.21 ... - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Error message since updating to 1.20
Yes, but older versions of Xmail ( 1.2 ) didn't, so many of my older domains don't have these directories. Ok, I'll put a check in 1.21 ... Thanks! - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Error message since updating to 1.20
On Mon, 14 Jun 2004, Alex Young wrote: Hi, I keep receiving an error message when trying to send emails and I am stuck to what the problem may be. It wasn't doing this on version 1.18 so I don't know if something has changed to cause this error. Requested action aborted: (-19) local error in processing I looked up the error code and it says; ERR_FILE_OPEN (-19) Unable to open file Which file can it not open? Does it happen right on connection? Try to match your MAIL_ROOT directory structure with the reference one that is listed inside the doc. - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
