I'm not sure what AUTH=0 does. I'm also unsure about
ALLOW_INSECURE_AUTH=0. I wasn't aware that this option even existed, and
am pretty sure that's the defualt value if it does. I'd ditch these, but
keep REQUIRE_AUTH=0. Your tcp.submission file should be:
127.:allow,RELAYCLIENT="",DKSIGN="/var/qmail/control/domainkeys/%/private",NOP0FCHECK="1"
1.2.3.4:allow,BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",QMAILQUEUE="/var/qmail/bin/qmail-queue",NOP0FCHECK="1",REQUIRE_AUTH=0
:allow,BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",QMAILQUEUE="/var/qmail/bin/qmail-queue",NOP0FCHECK="1",REQUIRE_AUTH=1
(be careful of line wrap - there are 3 lines here)
The 127.: line is for squirrelmail. As long as it's using port 25, you
don't need it here. You might want to change your SM config to
authenticate though (see wiki), in which case you don't need the 127.:
line in either tcp.* file.
Do *not* use the relayclient parameter, as that would allow someone to
use your barracuda as a relay (open relay), unless barracuda is checking
for local domains somehow and rejecting non-local email (which I doubt).
For the qmailctl script, after )cdb you should have:
cdb)
tcprules /etc/tcprules.d/tcp.smtp.cdb /etc/tcprules.d/tcp.smtp.tmp
< /etc/tcprules.d/tcp.smtp
chmod 644 /etc/tcprules.d/tcp.smtp*
echo "Reloaded /etc/tcprules.d/tcp.smtp"
# build cdb for submission
tcprules /etc/tcprules.d/tcp.submission.cdb
/etc/tcprules.d/tcp.submission.tmp < /etc/tcprules.d/tcp.submission
chmod 644 /etc/tcprules.d/tcp.submission*
echo "Reloaded /etc/tcprules.d/tcp.submission"
Don't forget to change the submission/run file by removing the
REQUIRE_AUTH=1 parameter, and change the tcp.X.cdb file name.
That should do it! (I think)
--
-Eric 'shubes'
On 12/08/2014 09:38 AM, SYS wrote:
I created as Eric suggester a tcp.submission file, added this:
127.:allow,RELAYCLIENT="",DKSIGN="/var/qmail/control/domainkeys/%/private",NOP0FCHECK="1"
:allow,AUTH=0,REQUIRE_AUTH=0,ALLOW_INSECURE_AUTH=0.RELAYCLIENT="1.1.1.1"
Do I have the sytax correct is the first question,
Then edited the qmailctl file and added this: under existing section
cdb)
tcprules /etc/tcprules.d/tcp.submission.cdb
/etc/tcprules.d/tcp.submission.tmp < /etc/tcprules.d/tcp.submission
chmod 644 /etc/tcprules.d/tcp.submission*
echo "Reloaded /etc/tcprules.d/tcp.submission"
Run qmailctl cdb
gives errors,
/usr/bin/qmailctl: line 124: queue: command not found
/usr/bin/qmailctl: line 125: alrm: command not found
/usr/bin/qmailctl: line 126: hup: command not found
/usr/bin/qmailctl: line 127: HELP: command not found
/usr/bin/qmailctl: line 128: syntax error near unexpected token `;;'
/usr/bin/qmailctl: line 128: ` ;;'
When I remove what I added, re run qmailctl cdb, all is good.
Dave M
On 12/8/2014 9:05 AM, SYS wrote:
I think I found that, let me play and will post back
Dave M
I think the best solution for this is to create an account in QMT for
barracuda to use for relaying, then configure barracuda to
authenticate on port 587.
If you can't configure barracuda to authenticate, there is another
way. I think the problem is that even if you set REQUIRE_AUTH=0 in
tcp.smtp file for barracuda's ip, the run script will clobber that
back to REQUIRE_AUTH=1. The solution is to use a separate
tcp.submission file for submissions (which will be happening in a
future release). Then REQUIRE_AUTH can be set in tcp.submission (=0
for selected, =1 for default), and remove the variable from the
submission/run file. Don't forget to change the tcp_cdb filename in
the submission/run file, and you should also add the tcp.submission
file to the qmailctl script to build the cdb for it.
Thanks.
---------------------------------------------------------------------
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]
