Search results

Why shouldn't the rules do it with 6.2.5? See not reason for your question... You can safely skip the SA restart line (like you already did!), as it's not required by PMG default install, only when you use the additional miltered setup.... @heutger and @Stoiko Ivanov : And I really wonder, why...

As for your Point 5: 1. Timeouts are not program crashes! 2. You mean the normal DCC timeout you specify by your own within SA Configfile init.pre.in here? Its per default 8 seconds and this should be enough to obtain the DCC result, i can only imange of this scenarios, to run into timeouts...

@Stoiko Ivanov thanks for the hint, just did it: See here for the Enhancement Request KAM-Update.

Thanks, yes, its one attempt to work around the "issue". will it cleanup the cache on the fly, with no manually service requests? Seems that i have overlooked it before ;(

@Stoiko Ivanov: you know the caching lifetime value used in PMG? As i have some strange behaviour. When i wipe UNSED E-Mail-Addresses (which existsts before and where as VRFY recipient verification was successful!) SMTP VRFY won't work as expected anymore, because of Postfix cache system thinks...

@Stoiko Ivanov: Just a small, but good PMG feature would be: Any change to get an KAM-Update (e. g. daily update task) integrated with PMG by default? As you already do with the SA-Ruleset? Would be great, as you have integrated an KAM Ruleset, but it needs currently manually update efforts. So...

@Alejandro Lengua Vega i recommend you buy the subscription, which suits best to your needs, if you have a commercial PMG instance up and running and subscription level should be chosen how mission critical it is...

It's a mess with Exchange above 2010 Versions with enabled verification. If just one address is not existing when to want to receive an e-mail with multiple recipients, exchange will reject all e-mails :D You can start reading form here...

Don't know if there is any for it...

As already quoted some posts before: https://pyzor.readthedocs.io/en/release-1-0-0/introduction.html#license https://pyzor.readthedocs.io/en/release-1-0-0/about.html#history https://readthedocs.org/projects/pyzor/downloads/pdf/latest/ https://github.com/SpamExperts/pyzor...

@Stoiko Ivanov This should explain your connection / timeout "issue" with the nc command, which is literally none ;) https://cwiki.apache.org/confluence/display/SPAMASSASSIN/NetTestFirewallIssues Pyzor Pyzor uses both udp and tcp port 24441. It looks as though the client communicates with the...

Thanks again. But just for my notes: When having before the queue activated: AND when configured SA spam score 3 level is 3. And this score is of 3 reached as defined spam score level by an legitime E-Mail, will the E-Mail getting delivered to the receipient or not? If not, will the sender...

@Stoiko Ivanov Thanks for reply. @tom yes, i can also follow your side of view. MS triggering to change anything, the effort you can save... @Stoiko Ivanov: Regarding the before the queue filtering method thing you proposed: Just for my understanding and check out if your suggestion is an...

Barracuda mail products, vamsoft or nospam for instance does it and use ldap or active directory for gaining the required valid user addresses. So the the appliance itself can directly reject itself on smtp level as its knows all valid addresses... Just for my understanding and check out if...

Its only the huge workaround with this additional Transport on exchange Server side. All exchange Server before Version 2013, works fine out if the box. But why not implementIng Verification on SMTP Level with given LDAP user Base in PMG side? SO THIS WOULD WORK AND ALWAYS NDEPENDENTLY OF THE...

Using this weblink you supplied, this is exactly NOT what is intended, as this is AFTER SMTP-Level --> SMTP Connection, so PMG already accepted the mails and MUST generate the separate NDR! --> Leading to backscatter problem. PMG itself should directly reject such invalid recipient on...

Thanks for fast response, have edited my previous posting, with many links, pointing to the exchange problem starting with exchange 2013 version. Leading to this problem: When recipient filtering on a Mailbox server detects one invalid or blocked recipient in a message that contains other valid...

@Stoiko Ivanov @tom Sorry for that. But don't find any other more fitting thread, therefore i post it in here ;) Having PMG doing the SMTP Verification directly on SMTP Level would be very good feature (other products on the markt have these feature). Because the Problem is that e. g...

Ist dei Regel denn überhaupt noch im Regelwerk aktiv und passt diese?

Its already out of the Box updating itself...