Search results

Du kannst ja mal damit spielen und Deine Ergebnisse mitteilen: Image Cerberus es gibt mehrere Plugins.

Wipe whole cache of browser.

Isn't is using System user root Password as default? Try to ssh and login with your password, after granted access type passwd and enter a new one... Reboot and try again?

@Stoiko Ivanov I think it is not so exotic, when you have more internal SMTP-Servers ready to accept the e-mails from PMG? use case one system fails it will automatically using the other internal smtp-server... so can be intended for the internal mailflow server failover... Postfix example...

@Stoiko Ivanov Just comes form the discussion in here, not directly adressing it, but wouldn't this feature should also be nice to have, a failover server for the relay "transport" entries: Deliveries via SMTP or LMTP support multiple destinations (Postfix >= 3.5)...

I must revise my answer a bit, that all accepted e-mails have BAYES_00. I have searched withing the tracking center for BAYES Strings and also found some matches for: So only SA scored mails having SA score of 3 oder more, have different BAYES_ WEIGHT Levels like this ones: SA score=3/5...

Thanks for your reply. No, as written both Bayes and awl are tuned on, like pmg default are... So is manuell Execution of sa-learn required? Or will all handeled automatically?

And here my "bayes" stripped results from running command sa-learn -D --dump magic: Jul 31 12:06:59.227 [9507] dbg: bayes: tie-ing to DB file R/O /root/.spamassassin/bayes_toks Jul 31 12:06:59.227 [9507] dbg: bayes: tie-ing to DB file R/O /root/.spamassassin/bayes_seen Jul 31 12:06:59.228...

@Stoiko Ivanov Seems also for me the same, always getting the BAYES_00 -1.9 Scoring, but have configured it to be on: and AWS have always positives values like this AWL(1.130) range starting from 0.7 i would say ... These are my switches configured on GUI-side (PMG defaults) use_awl...

Its only clamav heuristic, its no normal virus detected, so no block at all. default score is 3, so maybe increase it. and setup an rule, where as st certain spam score level e-mail is blocked and admin notified aswell.

Correct... And for point 2: yes, Its hard rejected with SMTP CODE 554 for me. And also the explaination is given within the NDR, so nothing more to handle there: e. g. 554 5.7.1 <use@yourdomain.de>: Recipient address rejected: Rejected by SPF: 35.238.96.225 is not a designated mailserver for...

PMG als also accept all E-Mails coming from servers having NO configured SPF record. Also when you have "User SPF" active. But when you setup an SPF record for an E-Mail Domain, it must be correctly configured, when checking SPF with PMG. and i won't change my point of view ;)

I always keep my "Use SPF" on. otherwise legitme Mail-Server-/ E-Mail-Domain operators won't learn how to properly setup their SPF-record. They have to options, remove SPF record oder setup it correctly.

Can confirm this max. processing times, too ;)

Einfach mal das Handbuch / die Doku lesen, dann beantwortet sich die Frage von selbst ;)

Just customize your postfix config... Therefore just customize your postfix config / use template system...

Alles was sog. NGN-Firewalls in punkto SSL/TLS Interception / Inspection machen, kann es beeinflussen...

Buy a sufficient subscription (like standard level) to get business critical support before you constantly post such things. Think about it, and it was weekend!

@heutger @Stoiko Ivanov PMG currently use restart for the daily sa-update routine. In one of the Apache RuleUpdates Docs you have mentioned restart on one side , and reload on other SA 3.4.x SA-update document. Very strange divergence... So what is actually the best way without the lowest...

Could be an approch, but will only work for users that use the spam quarantine on PMG, so not any benefits for all, that do just tagging the SPAM.