similar to: NSD zone file GENERATE directive

On 3/20/23 13:41, Anand Buddhdev via nsd-users wrote: > Hi Robert, > > NSD doesn't understand the GENERATE directive. You'll have to create > your zone files using a script or template engine. Understood but certainly not helpful with large dynamic IPv6 PTR's... Not that dynamic hosts NEED PTR's, but would still be nice to have. -- inoc.net!rblayzor XMPP:

Hi Robert, NSD doesn't understand the GENERATE directive. You'll have to create your zone files using a script or template engine. Regards, Anand On 20/03/2023 16:29, Robert Blayzor via nsd-users wrote: > BIND has a handy feature $GENERATE directive in zone files that allows > you to handle large ranges of things like PTR/A records without having > to actually create long

Per RFC 8501 seciont 2.2 https://datatracker.ietf.org/doc/html/rfc8501 I have attempted to use a wildcard on a /64 boundary within a zonefile for NSD, but it doesn't not appear to work. PTR lookups fail... tested with, ie: $ORIGIN 1.1.0.0.8.5.1.b.2.2.5.2.ip6.arpa. * PTR my.fqdn.net. Did not work... or would you have to use? (not tested) *.*.*.*.*.*.*.*.*.*.*.* PTR .... --

Robert Blayzor via nsd-users writes: > > NSD doesn't understand the GENERATE directive. You'll have to create > > your zone files using a script or template engine. > Understood but certainly not helpful with large dynamic IPv6 PTR's... > Not that dynamic hosts NEED PTR's, but would still be nice to have. lex(1) is your friend. For managing our reverse ip6

On Sat, 28 Dec 2019 17:02:09 +0100 richard lucassen via nsd-users <nsd-users at lists.nlnetlabs.nl> wrote: > The problem is (was) that I used "include:" statements in nsd.conf > to load zone information. Apparently nsd does not reread the include > files upon a SIGHUP. I scripted everything into 1 file and a HUP > rereads the zone info now. Wrong, I made a mistake it

We have the requirement to provide SSL on some IP addresses, but not others on our servers. Providing SSL is the easy part and we're able to use multiple SSL certificates now. (thanks Timo!) All is working ok, but we several IP hosts that do not require SSL and do not have valid certificates. While we can limit access via a firewall ACL to TLS connect ports (993/995) we can't do so on

Does (or can) the ability to use expansion variables in Dovecot's log_path exist? ie: log_path = /var/log/dovecot/dovecot-%Y%m%d -- Robert Blayzor INOC, LLC rblayzor at inoc.net http://www.inoc.net/~rblayzor/

Samba organizers might want to look into this: [ns1:~] dig 150.73.70.66.relays.osirusoft.com ; <<>> DiG 9.2.2 <<>> 150.73.70.66.relays.osirusoft.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28005 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 13 ;; QUESTION SECTION:

Is there a way to configure Dovecot to perhaps filter/enforce which passwords are accepted before authenticating? Ie: Reject immediately (without a database lookup) if password is not X characters in length? ? -- Robert inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP Key: 78BEDCE1 @ pgp.mit.edu

I have configured autoexpunge on some folders: namespace inbox { inbox = yes location = mailbox Junk { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Trash { auto = subscribe autoexpunge = 2 weeks special_use = \Trash } prefix = separator = / } After adding these and restarting, logging in and out several times, I still see messages

This may be more of a CPanel issue than Dovecot but CPanel uses Dovecot and not sure if this is a knob we have available in Dovecot or we need to reach out to Cpanel directly to see if this is some custom code they added to their distros. Anyway, W/R/T emails sent with dtails/ + addresses ie: foo+bar at mydomain.com And with LDA/LMTP, in Cpanel by default the detials part, in this case

On 1/1/2015 4:17 PM, Robert Blayzor wrote: > On Jan 1, 2015, at 9:58 AM, Robert Blayzor <rblayzor.bulk at inoc.net> wrote: >>> Hmm. This smells like a bug. I notice that your modification times of >>> the .sieve and .svbin file are exactly the same (that is somewhat >>> unusual). I'm looking at a potential bug that would explain your problem. >>>

In reading the Dovecot NFS WIKI entry: http://wiki2.dovecot.org/NFS It mentions a FreeBSD NFS client caching bug. I believe that bug only exists pre-8.x ? It seems that a patch in the PR notes was MFC'd and made it into 8.x at some point. (at least I checked the source in 8.3 and it was there). So I assume that FreeBSD 8.x mitigates the issue? Maybe not? So our deployment is multi

I have searching for the best way to tell if a Dovecot user is idle by finding the last time they have logged in. Right now the best way I can tell is to do something like "touch" a file in the users homedir via a post login exec. This seems like a LOT of overhead, to accomplish such a simple task, especially if your doing a lot of dozens of logins per second. Is there an

I have a rather busy Apache 2.2 server; tons of small & some large requests. It's a standard Dell 2650 server using the bge (broadcom) network driver. I seem to have a rather strange problem where after just a day or so Apache just stops processing new connections. You can connect to port 80, but trying to get Apache to process any data just hangs. There is nothing strange in

> On Dec 22, 2015, at 9:49 AM, Dominik Breu <dominik at dominikbreu.de> wrote: > the autoexpunge feature only removes mails wich have the \Delete Flag so no deletion of mails wich doesn't have this Flag(see https://tools.ietf.org/html/rfc4315#section-2.1 or http://wiki2.dovecot.org/Tools/Doveadm/Expunge) > > you could run a cron job with a doveadm move comando to move the

On Dec 22, 2015, at 2:56 PM, Teemu Huovila <teemu.huovila at dovecot.fi> wrote: > > The autoexpunge feature does not check the \Deleted flag. > > Are any errors logged in "doveadm log errors"? Could you post your complete output of doveconf -n please. That?s what I thought. If I run expunge from doveadm manually, it will work as expected. I just never seem to get

Hi, I'm doing some quick tests with nsd-4.0.0b5 and (rc2). And found something strange when changing (nsd-control reconfig) one zone from: zone: name: 10.in-addr.arpa zonefile: /zones/empty.zone to zone: name: 10.in-addr.arpa request-xfr: 192.168.122.12 NOKEY allow-notify: 192.168.122.12 NOKEY zonefile: /zones/slave/10.rev and doing nsd-control reconfig. After

Currently pigeonhole supports reject which would generate a NDR for each message. (If I understand the current documentation) Using Dovecot LMTP it would be more optimal to kick a 5xx back to the primary MTA to reject the delivery rather than generating more back scatter NDRs. Anyone know if this is possible now (to forgo the NDR)'s or do we need to wait for ereject ? If so, how much work

On Jan 13, 2015, at 8:30 PM, Reindl Harald <h.reindl at thelounge.net> wrote: > > so what you want in your OP is just DISCARD in a sieve script and there is no point in "Using Dovecot LMTP it would be more optimal to kick a 5xx back" when the desired result is DISCARD > > why do you want the burden of keep the SMTP session with the client open until the mail is