hi josh well we just discussing this in a separate thread
the idea is to have a separate tcp.cdb file for your authenticated users who use submission port so that you can have different chkuser rules for them. pl take a look at this post http://www.mail-archive.com/[email protected]/msg35074.html and also goe thru all the posts with the subject client gets "you are breaking our security rules" when sending 300 invoices to thier clients note : we have recompiled qmail-toaster rpm (takes just around 10 minutes and goes perfectly safe) so that we can enable / disable chkuser using the starting variable. i dont know if the stock qmailtoaster allows this. if you have difficulties pl revert. rajesh > Rajesh, > > We are using 587 for SMTP. Only authenticated users can send as well > (don't want to become a SPAM server). Does the port number have > something to do with it? Not sure what the connection is? > > Thanks, > > Josh > > On 12/25/2012 11:28 AM, Rajesh M wrote: >> josh >> >> we faced similar issues and were able to solve the same. our customers >> used port 587 ie submission port for sending out emails. >> >> are your users are using submission port ie port 587 for sending out >> emails ? >> >> rajesh >> >> >> >>> I recently switched out my companies FreeBSD + Qmail/Vpopmail setup >>> with >>> a CentOS + QmailToaster setup and it has worked as expected except for >>> a >>> single problem that keeps coming up: invalid rcpt MX domain. When I do >>> a manual MX dig command on these domains they in fact do not have >>> proper >>> MX records setup, but our customers have always been able to send to >>> these domains in the past when we were using vanilla Qmail/Vpopmail on >>> FreeBSD. Is there any workaround or fix so our servers will attempt to >>> send an email even if the domain doesn't have MX records? >>> >>> Thanks in advance. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: >>> [email protected] >>> >>> >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
