Rajesh,
I actually have been following that thread a bit as it did seemed to
relate to my problem. I am using the stock QmailToaster, but I guess I
could modify the qmail-toaster rpm and reinstall?
I come from a Debian background and am pretty to new RPM package
management. If I was to reinstall the qmail-toaster RPM after modifying
it, would I just run it with `rpm -Uvh --replacefiles --replacepkgs
qmail-toaster.rpm`? I think I just need to comment out #define
CHKUSER_RCPT_MX and rebuild, but rebuilding and reinstalling
QmailToaster makes me nervous.
Am I going in the right direction? Any guides for this?
Thanks again,
Josh
On 12/25/2012 11:32 AM, Josh Bowling wrote:
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]
