On 09/06/2014 10:04 PM, Rajesh M. wrote:
there are so many pin pricks
We continue to do our best to mimize this. We've still some progress to make in this area.
example : if user does not enable smtp authentication the message given is : sorry the domain is not on my list of allowed rcpthosts -- which my customers dont understand. i would have a more friendly message like "please enable smtp authentication"
I agree this is a better message, and don't have a problem with making this the 'stock' QMT. I'll see about making a patch for this in the next qmail release.
Better yet, you could do this yourself. All you'd need to do is create the appropriate patch file. Then, if you don't have permissions to push to the qmail project on github, you could create a pull request for me to include it in the package. You could also make the appropriate changes to the spec file for this, and include that in the pull request as well. I'd much rather see you doing this (and learning to do if if you don't yet know how) than rebuilding packages that already exist, as it would accomplish a better result for both you and the rest of the QMT community.
chkuser settings checking for valid email id and valid mx for authenticated users creates more problems. so what i did was create two seperate tcp.smtp files one called tcp.smtp and another called tcp.smtp.submission -- authenticated users will not have checks for email format and mx checks ... if an authenticated user via submission port sends an email with a wrong format then email bounces back after it gets into the queue.
Ever since the submission port was added to QMT, I too have thought that these should be separate files. I wasn't the project owner at that time though, so it wasn't done this way. Rather than changing this here and now though, I'm targeting to make the change to when qmail-smtp is migrated to run under xinetd. Creating tcp.smtp.submission would become obsolete at that time, and I'm thinking the few changes the better.
(if spamdyke is used then i would like to have two seperate configuration files one for port 25 email and the other for smtp authenticated email.)
There will be separate spamdyke configurations for port 25 and 587 once spamdyke is configured to handle authentication. This too will probably be implemented with qmail-smtp under xinetd, which is on the front burner at this time.
another issue : MS outlook adds single quotes and brackets to email ids. so many a user gets something like this in their address book. <'[email protected]'> ie single quotes and brackets now when qmail tries to send this email it removes the < > (brackets) but keeps the single quotes and email sending fails with error sorry could not find host : somedomain.com' note the single quote at the end of the domain name .. if possible pl modify qmail so that brackets and quotes are stripped off.
This is the first I've heard of this behavior. If someone would care to submit a patch, I'd be happy to include it. To be honest though, this isn't high on my list at this time.
if possible pl incorprate the above points in the new versions which provide for maximum flexiblity.
Most of these will be included in the next releases.
unfortunately we cannot code but we can test on large production systems and give our feedback to you and document the steps in a systematic manner for all to use.
You too can code. That's why we have the sources on github now. :) (I realize coding isn't in everyone's skill set though.)
I certainly appreciate everyone's testing and feedback too, and their community participation in general. This is key to making this project successful.
thanks very much for your help
You're certainly welcome. -- -Eric 'shubes' --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
