search for: toorop

...1:55 auth: Debug: client in: AUTH 1 PLAIN service=imap secured lip=184.106.217.69 rip=178.32.33.247 lport=143 rport=33875 Aug 27 14:11:55 auth: Debug: client out: CONT 1 Aug 27 14:11:56 auth: Debug: client in: CONT 1 AHRvb3JvcEByZXNwdWJsaWNhLmZyAG11cnBoeTI1 Aug 27 14:11:56 auth: Debug: vpopmail(toorop at respublica.fr,178.32.33.247): lookup user=toorop domain=respublica.fr Aug 27 14:11:56 auth: Info: vpopmail(toorop at respublica.fr,178.32.33.247): unknown user Aug 27 14:11:58 auth: Debug: client out: FAIL 1 user=toorop at respublica.fr Aug 27 14:11:58 auth: Debug: client in: AUTH 2 PLAIN serv...

...lport=143 rport=1130 Feb 20 13:15:06 auth(default): Info: client out: CONT 1 PDI5NzIzNTE1MTI1MTA3NjAuMTI2NjY2ODEwNkBkZXY+ Feb 20 13:15:07 auth(default): Info: client in: CONT 1 dG9vcm9wQHJlc3B1YmxpY2EuZnIgOTczNjdjMzE3NWE1MWY2YzJhNDY0OTNlNDMzZGZhZDQ= Feb 20 13:15:07 auth(default): Info: vpopmail(toorop at domain.tld,82.245.64.126): lookup user=toorop domain=domain.tld Feb 20 13:15:07 auth(default): Info: password(toorop at domain.tld,82.245.64.126): Generating CRAM-MD5 from user 'toorop at domain.tld@', password '' Feb 20 13:15:07 auth(default): Info: password(toorop at domain...

...D5 service=imap secured lip=184.106.217.69 rip=178.32.33.247 lport=143 rport=49099 Aug 28 10:59:49 auth: Debug: client out: CONT 1 PDM3MjI0MzQ4NjQzNTI3NjUuMTI4Mjk5MzE4OUByYWNrc3BhY2UuZGVkaW1haWwuZXU+ Aug 28 10:59:49 auth: Debug: client in: CONT<hidden> Aug 28 10:59:49 auth: Debug: vpopmail(toorop at respublica.fr,178.32.33.247): lookup user=toorop domain=respublica.fr Aug 28 10:59:49 auth: Debug: client out: OK 1 user=toorop at respublica.fr Aug 28 10:59:49 auth: Debug: master in: REQUEST 1 2211 1 e4920e51f96ae453663098df19c5b374 Aug 28 10:59:49 auth: Debug: vpopmail(toorop at respublica...

...mail.com 2009-04-20 16:06:44.982424500 delivery 6356: failure: Connected_to_209.85.219.1_but_sender_was_rejected./Remote_host_said:_555_5.5.2_Syntax_error._1si7169155ewy.101/ 2009-04-20 16:06:44.982502500 status: local 0/10 remote 0/80 Is there something to do to fix that probleme ? Thanks. -- Toorop <O> http://www.flickr.com/photos/toorop/

...it that resolves it (see https://github.com/NLnetLabs/nsd/pull/346 ), but we may need to discuss if and how to resolve it first. First I'd like to know if your configuration is similar in that the CNAME or DNAME target does contain an allow-query list. Op 03-07-2024 om 10:52 schreef Willem Toorop via nsd-users: > Hi Jamie, > > I can reproduce, but only if the target zone of the DNAME (or CNAME > which behaves the same) matches a zone with an allow-query option that > doesn't match the querier. > > For example with the following config in nsd.conf: > > zone:...

Dear all, NSD 4.11.0rc1 pre-release is available: https://nlnetlabs.nl/downloads/nsd/nsd-4.11.0rc1.tar.gz sha256 7594d014199585c24f6593649bfc657078d411a3f09eb31192a35a7c031c028f pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.11.0rc1.tar.gz.asc Version 4.11.0rc1 sees various small features and bugfixes. One notable feature is that configuration can be reloaded and evaluated on SIGHUP, when

Hi list, We are observing strange behavior of nsd v3.2.9 acting as slave DNS server. The environment is set up as follows: 0. We are using 172.16.0.0/16 subnet; 1. Primary Master server at 172.16.100.114; 2. Slave server at 172.16.100.115. The config file is in /etc/nsd-dns-slave.conf; 3. There may be also other Master servers im the given subnet. Now I want to permit DNS NOTIFY messages to

Dear all, We have an emergency quick-fix release, version 4.11.1 for NSD. NSD 4.11.1 is available: https://nlnetlabs.nl/downloads/nsd/nsd-4.11.1.tar.gz sha256 696e50052008de4fa7ab1d818d5b77eb63247eea2f0575114c9592ff9188a614 pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.11.1.tar.gz.asc NSD version 4.11.0 had a serious bug in which applying updates to zones (and other modifications that require a

Dear all, NSD 4.11.0 is available: https://nlnetlabs.nl/downloads/nsd/nsd-4.11.0.tar.gz sha256 93956d90d45ffa9f84f8ca2f718a42105e4236d094ce032211849f1a12cdc158 pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.11.0.tar.gz.asc Version 4.11.0 sees various small features and bugfixes. One notable feature is that configuration can be reloaded and evaluated on SIGHUP, when enabled with the new

Op 04-01-2025 om 17:10 schreef Otto Retter via nsd-users: > Hi all, > > I'm running NSD 4.9.1 on OpenBSD 7.6. I recently upgraded from OpenBSD > 7.5, which I believe had NSD 4.8.0 in base, and did not see this > behavior prior. Thanks Otto, Indeed, NSD 4.8.0 did not log this condition as an error message and just proceeded if the old-main would quit. With 4.9.0 reloading