Already in place.
Dave M
On 12/8/2014 6:32 PM, Eric Shubert wrote:
Of course you want MX pointing to barracuda. It's submissions (which
don't use MX) that you want going directly to QMT (port 587).
-
To unsubscribe,
Thanks eric, will change mine and report back.
Dave M
On 12/8/2014 6:57 PM, Eric Shubert wrote:
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,
Hi Eric, my results
Note 1.2.3.4 replaced with real IP
Error:
* qmailctl cdb*
Reloaded /etc/tcprules.d/tcp.smtp
tcprules: *fatal: unable to parse this line:
On 12/09/2014 09:59 AM, Eric Shubert wrote:
Not at this time. Once we have spamdyke running on the submission port
you *could* do this. I'd strongly recommend against it though. I know
some users who do this intentionally (and not maliciously).
Thank you for the reply and advice.
--
I'm going to ask the stupid question. What are you using to edit
this file?
SYS wrote:
Hi Eric, my results
Note 1.2.3.4 replaced with real IP
Error:
qmailctl cdb
Reloaded /etc/tcprules.d/tcp.smtp
tcprules: fatal: unable to
vi
On 12/9/2014 9:55 AM, Cecil Yother, Jr. wrote:
I'm going to ask the stupid question. What are you using to edit this
file?
SYS wrote:
Hi Eric, my results
Note 1.2.3.4 replaced with real IP
Error:
* qmailctl cdb*
Reloaded /etc/tcprules.d/tcp.smtp
tcprules: *fatal: unable to parse this
I want to add the rules in KAM.cf to my Spamassassin. I came accross
this rule set but do not know how to get it to be read my Spamassassin.
Is it as easy as copying it over to /etc/mail/spamassassin and it will
automatically be used, or is there something I need to do to make those
rules
Thanks for everyones reply on this. The issue was actually a corrupt
Windows 8.1 install. This issue manifested itself by causing issues with
a few other applications as well.
Thanks,
Gilbert
On 12/6/2014 11:28 AM, Eric Shubert wrote:
I would try that first. I appears to met that MS sets up