search for: allycomm

...entifies location Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 Component: nft Assignee: pablo at netfilter.org Reporter: netfilter at allycomm.com At least when "include" is employed, the error message returned when "interval overlaps with previous one" can fail to properly identify the file/line of the source of the overlap. Noted on nftables master branch after commit 0b3ccd27e12d1df442aa3eac40a2ccb63d6c6407 Aut...

...nd the like Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: nft Assignee: pablo at netfilter.org Reporter: netfilter at allycomm.com Objective -- define in a single location a list of ports to be used in initializing sets and in rules Result -- no "obvious" way to do this Expected -- define would either be a straight textual substitution, or would be able to accept a notation appropriate for defining sets, maps,...

...error messages Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: critical Priority: P5 Component: nft Assignee: pablo at netfilter.org Reporter: netfilter at allycomm.com If an identifier (at least for define and chain) is present in a file processed by nft, the error message returned does not appear to describe either the cause of the problem, nor the proper location in the file. As such, it is exceptionally difficult to find and resolve the case of the probl...

...active state Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: critical Priority: P5 Component: nft Assignee: pablo at netfilter.org Reporter: netfilter at allycomm.com At least as the man page describes, the output of # nft list ruleset > ruleset.prod should be parseable by # nft -f ruleset.prod and provide restoration of the state at the time. "Note that contrary to what one might assume, the output generated by export is not parseable...

...its context Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: nft Assignee: pablo at netfilter.org Reporter: netfilter at allycomm.com Observed Behavior: ================== nftables.conf:3:1-14: Error: Could not process rule: Operation not supported flush ruleset ^^^^^^^^^^^^^^ (when a chain with an snat expression was placed into a prerouting-hook chain through a copy-paste error in chain creation) Expected Behavior: ===...

On Tue, 21/11/17, Jeff Kletsky <dovecot at allycomm.com> wrote: > On 11/20/17 1:58 PM, Someone wrote: > > > I've been struggling with this on and off for a while now. Upon > > attempting to install Dovecot on Ubuntu 17.04 I get the following errors [...] > "Hint: Some lines were ellipsized, use -l to show i...

...negative numbers Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: nft Assignee: pablo at netfilter.org Reporter: netfilter at allycomm.com To replicate: define PRI_DEFRAG = -400 results in the error nftables.conf:22:24-24: Error: syntax error, unexpected - define PRI_DEFRAG = -400 ^ Expected behavior: Could "define" a negative number (as opposed to a string) Possible work around: d...

...identifier names Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 Component: nft Assignee: pablo at netfilter.org Reporter: netfilter at allycomm.com I understand that some of the functionality within nftables requires identifiers to be available within kernel structures and that there needs to be a "reasonable" limit on the lengths of those identifiers. Unfortunately, these limits are not only poorly documented, but also result...

https://bugzilla.netfilter.org/show_bug.cgi?id=1184 Bug ID: 1184 Summary: disable implicit concatenating of elements of sets with flag interval Product: nftables Version: unspecified Hardware: x86_64 OS: All Status: NEW Severity: enhancement Priority: P5 Component:

...defined variable Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 Component: nft Assignee: pablo at netfilter.org Reporter: netfilter at allycomm.com To Replicate: * Create an nft file that contains define PRI_FILTER = 0 table inet global { chain prerouting { type filter hook prerouting priority $PRI_FILTER policy drop } * "execute" using nft -f <that_file> Observed Behavior: tmp:4:46-46: Erro...

...borting Product: nftables Version: 0.9.x Hardware: x86_64 OS: Debian GNU/Linux Status: NEW Severity: major Priority: P5 Component: nft Assignee: pablo at netfilter.org Reporter: netfilter at allycomm.com I was pleased to read that v0.9.7 provided support for implicit chains. That feature provides the ability to enhance readability of rule sets by exposing the "jump-to" chain's contents at the point of the jump. Unfortunately, I found that nesting causes a parsing failure that is...

...bles incorrect Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: critical Priority: P5 Component: nft Assignee: pablo at netfilter.org Reporter: netfilter at allycomm.com Observed behavior: ================== No matter what the documentation says, it appears that NAT statements can't be in an "inet" table. The error messages are unhelpful in deducing this. Expected behavior: ================== * NAT statements could be present in inet tables...

...type set" Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 Component: nft Assignee: pablo at netfilter.org Reporter: netfilter at allycomm.com Observed Behavior: ================== Use of sets within a vmap result in the error message: BUG: invalid range expression type set nft: expression.c:1037: range_expr_value_low: Assertion `0' failed. Aborted Expected Behavior: ================== Could use both anonymous and named sets...

...g newline at EOF Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: nft Assignee: pablo at netfilter.org Reporter: netfilter at allycomm.com Created attachment 509 --> https://bugzilla.netfilter.org/attachment.cgi?id=509&action=edit Files to reproduce missing-newline behavior; no subdirectory If a file used by an "include" statement does not have a newline at its end, it will cause a parse/lex issue that is repo...

I'm struggling to achieve the kind of filtering with sieve that I was able to do with procmail. TL;DR I'd like a way to loop through a set of (address, destination) pairs in sieve so that I can maintain the (address, destination) pairs in one place and not have to explicitly write scores of nearly identical [...] if address :matches ["From", "Sender",

I often use the same set of header names when doing an 'address' comparison. I would prefer to be able to specify that once, then re-use it in several places. As an example set "address_mailman_fields" "\"To\", \"Cc\", \"From\", \"Errors-To\""; if address :domain :matches ["${address_mailman_fields}"]

On 11/27/17 2:41 AM, Bruce wrote: > Debian stretch. > Dovecot 2.2.27 > > I was working with a document that references the imapsieve plugin.? > It references the /etc/dovecot/conf.d/90-imapsieve.conf file. > > The only reference I've found for it is > https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve#Configuration. > > I've got

There are a couple things that show up on the Upgrading/2.1 wiki page that would be useful to have on pages describing dsync (Tools/Dsync, Migration/MailFormat, Tools, perhaps others): * dsync was merged into doveadm * You can't dsync 2.0.x to/from 2.1.x That second point is especially "interesting" to me as it seems that Apple MacOS X Server is still on 2.0.16, at least from

I (finally) moved over to Maildir storage here and would like to implement some "scripts" to manage taking actions on emails manually identified as misclassified as spam/ham. After reading through the Dovecot 2 description of how it works to try to see how it interacts with other processes changing the files. I'm concerned that I would be corrupting the message indexes if I just

I'm in the process of moving from LDA to LMTP (Postfix upstream) prior to a transition off `nix accounts to virtual accounts and am stumped by LMTP reporting ??? dovecot: lmtp(10019, jeff at example.com): Error: Relative home directory paths not supported: 0 LDA does /not /have any problems with PAM or passwd-file passdb/userdb and the ubiquitous definition of ??? mail_location =