[xmail] Re: Bug in command line parsing
Yeah, you can bet I'll be more careful with command-line parameters in the future :) But guys, let's kill this thread It's pointless. It's true that Xmail has some less-than-good error messages, but I've got Xmail on three separate networks on eight different servers, and I can tell you that it's an excellent product -- and I'm sure there are lots of folks on this list who have even more experience with it and have even more installs of it, and they would agree with me too. And yes, I also agree that better error messages is really, really low on the priority list -- I said as much in my original post -- and I'm sure that Davide would agree with me that good error messages are a good thing and maybe at some point he'll have the desire or opportunity to go back and take a look at improving some of them. But he can't do that if we, the collective users of the software, don't give him adequate feedback on what error messages need improving, or what error conditions need more or better trapping and handling. The main reason I posted my original note was so that OTHER PEOPLE would know about this very tiny bug -- and that it would hopefully save someone else a few hours of chasing their tail over a similar problem. Anyway, I bet I've accomplished that and all of us will be very careful with formatting command-line parameters in the future :) > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Davide Libenzi > Sent: Thursday, January 23, 2003 4:37 PM > To: XMail mailing list > Subject: [xmail] Re: Bug in command line parsing > > > > On Thu, 23 Jan 2003, Andreas Hansson wrote: > > > > > > However you titled your email "Bug in command line > parsing" and it > > > is NOT > > a "bug". > > > > In my opinion, freezing up due to an invalid command line option > > instead of printing/logging an error message or at least > refusing to > > start IS a bug. It's not what well-behaving software should do. > > Unfortunately there seems to be a lot of cases where xmail will > > proceed and fail in some random and hard to debug way instead of > > printing an error message as soon as the problem can be detected. > > Inside an application like Photoshop, I would have to agree. > This is a server software, meant to be used by ppl that know > what they're doing. After you spent 8 hours because of the > use of a bad parameter, the next time I'm pretty sure you > will be more carefull in touching configurations. Or you will > stop using XMail ( natural selection ). And both are good > things. Different is the validaion of parameters coming from > the clients, that must be strongly validated to avoid security flaws. > > > > - 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: Another question.
If you are not getting them back from other servers then it's probably because you don't have AllowNullSender enabled (1) in your server.tab file. Bill >-- >From: Brandon Wittenburg[SMTP:[EMAIL PROTECTED]] >Sent: Thursday, January 23, 2003 7:08 AM >To:[EMAIL PROTECTED] >Subject: [xmail] Re: Another question. > > >slackl wrote: > >>I have setted up an XMail and it is not generating confirmation receipts and >>delivery notifications upon receiving an emails, which request them. >> >>Is this normal and how should I enable this feature if it possible ? >> >> >This is a feature of a mail client, not a mail server. When you send an >email that request confirmation of delivery, it is the person to whom >you are sending's mail client software that will send the delivery >notification -- and only then if that person decides to send the >confirmation (depending on the software). > >So your XMail is operating normally. > >Regards, > >Brandon > >> >> > >- >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: imap roadmap
Davide wrote: > > I started by trying to do a separate module but became a mess and required > also the standard XMail to be heavily changed. About 4 months ago a > changed route towards a single package. I can't give you an ETA because > the time I can dedicate in doing so widely changes. The fact that I have > reports of users that successfully integrated othe IMAP servers do not > force me to sweat to hit a given release date. > Is running external software that messes with xmail's mailbox files "supported"? I thought you didn't want other programs to touch xmail's files, but perhaps that was only for the mail spool and the hashed configuration files? Andreas - 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: Bug in command line parsing
> However you titled your email "Bug in command line parsing" and it is NOT a "bug". In my opinion, freezing up due to an invalid command line option instead of printing/logging an error message or at least refusing to start IS a bug. It's not what well-behaving software should do. Unfortunately there seems to be a lot of cases where xmail will proceed and fail in some random and hard to debug way instead of printing an error message as soon as the problem can be detected. > Please don't tell David what to do. He is providing us with free, top quality, supported, mail server software. Davide provides us with free, fast, and pretty well supported mail server software. Especially this list is very helpful. I don't see anything wrong in pointing at things that could be improved. Especially when you're not trying to force him to fix it right away, just suggesting to do it sometime in the far future. Andreas - 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: Bug in command line parsing
> A) As a note to anyone in the future who has this problem > -- it's one of those head-scratching-what-did-I-do-wrong > problems that hopefully someone will avoid because I posted this. However you titled your email "Bug in command line parsing" and it is NOT a "bug". > just tuck it into your "to do when hell freezes over" list :) Please don't tell David what to do. He is providing us with free, top quality, supported, mail server software. - 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] XMail integration
Is there any way to integrate XMail with other services, more specifically a RADIUS server, either have the RADIUS use the same users as XMail or the other way around? So when a user changes a password both are updated? - 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] error message
what wants to say this error message " [<02>] The reason of the delivery failure was: The maximum number of delivery attempts has been reached " Thank you for your assistance - 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: Another question.
slackl wrote: >I have setted up an XMail and it is not generating confirmation receipts and delivery >notifications upon receiving an emails, which request them. > >Is this normal and how should I enable this feature if it possible ? > > This is a feature of a mail client, not a mail server. When you send an email that request confirmation of delivery, it is the person to whom you are sending's mail client software that will send the delivery notification -- and only then if that person decides to send the confirmation (depending on the software). So your XMail is operating normally. Regards, Brandon > > - 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] Another question.
I have setted up an XMail and it is not generating confirmation receipts and delivery notifications upon receiving an emails, which request them. Is this normal and how should I enable this feature if it possible ? - 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: Bug in command line parsing
I didn't think you COULD omit the space -- it was pure human (as in, me) error But realistically, I think at some point it would be a good idea to have stronger parsing of that command-line to either handle this or generate an error to the user -- whatever makes sense design-wise. The alternative of just dying on the first write to a logfile isn't a good thing :) I posted this for two reasons, though: A) As a note to anyone in the future who has this problem -- it's one of those head-scratching-what-did-I-do-wrong problems that hopefully someone will avoid because I posted this. And B) Maybe in some later version, you could deal with this -- just tuck it into your "to do when hell freezes over" list :) > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Davide Libenzi > Sent: Thursday, January 23, 2003 7:49 AM > To: [EMAIL PROTECTED] > Subject: [xmail] Re: Bug in command line parsing > > > > On Tue, 21 Jan 2003 [EMAIL PROTECTED] wrote: > > > > > In Xmail V1.11 (I assume this is so in other versions), I > ran across a > > minor bug in how Xmail parses its command-line on start-up. > > > > If you DO NOT put in a space after the -Mr flag (which > controls the # > > of hours it takes the logs to rotate), the Xmail service > will die the > > first time it tries to write to any log. > > > > So, a command line that contains "-Mr24" will kill the application; > > "-Mr 24" works just fine, of course. > > > > This may be different under Linux -- this was tested under Windows > > 2000 Server. > > > > Obviously, this is not a security issue in any way nor is it really > > much of a problem -- unless, of course, you run into yourself and > > spend an hour scratching your head over it :) > > This is an "As Designed". Where did you read that you can > omit the space between the switch and the parameter ? > > > > - 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] imap roadmap
hello davide, just wondered when you plan to add imap support. just a question :-) soenke. -- Binary/unsupported file stripped by Ecartis -- -- Type: application/x-pkcs7-signature -- File: smime.p7s - 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]
