similar to: Bounced message after update

On 02/18/2017 10:24 PM, Robert L Mathews wrote: > On 2/17/17 1:38 PM, chaouche yacine wrote: > >> Seems wrong to me too, Robert. If you put your private key inside >> your certificate, won't it be sent to the client along with it ? > > No; any SSL software that uses the file will extract the parts it needs > from it and convert them to its internal format for future

I'm using the fwdmsa package to identify deviant cases in a Mokken scale analysis. I've run into a problem., separate from the one I posted previously. The problem comes with items that are "easy" by IRT standards. A good scale should include a range of difficulties; yet when I include "easy" items in a forward search I continuously run into the problem that these items

Census from 1990 california in USA. It?s a data frame with data from 20640 zones from Calif?rnia. Zones are chosen as being geograficly near, wich one with 1500 persons (mean). For each zone are provided several informations in the colums from data frame: - longitude e latitude from the geografic centre - median age of houses in the zone (housingMedianAge) - total number of houses in the na zone

> That's one of the reasons I don't like Let's Encrypt, with one year certs it is easier to look at the certs and see what is going to expire in the coming month needing a new private key. I use dehydrated (with Cloudflare DNS challenges) and as far as I know, it seems to generate a new private key every time. All newly generated certs are generated with the timestamp in the

Dear R users, experimenting with the lm function in R, I've encountered some behaviour I don't understand with my limited knowledge of regression. I made a data-'set' of three measurements (see syntax below). Using lm (linear model) to fit the regression-line, I expected to find an intercept of 2.0 and a slope of 0, but in fact the slope is slightly below zero. Amazed by

I saw another thread about this topic, but I did not understand the solution. . . I recently discovered my bounced messages were not getting delivered. Obviously since I was not getting any messages, I thought everything was fine. Anyway, my maillog has entries similar to below for bounced messages: Mar 29 10:48:09 firewall postfix/pipe[9089]: 19565807: to=<myuser at my.domain>,

Hi, I found the following in my logfiles: The failure is not reproducable at the moment. System is delivering mails to mailboxes with no problems at all. It is a production installation with medium load. dovecot --version: 1.1.7 OS: Linux (Gentoo/x86 stable) - grsec enabled kernel deliver.log: deliver(user at example.tld): Panic: file istream-tee.c: line 144 (i_stream_tee_read): assertion

I upgraded to Dovecot 2.3.0.1 as advised, but it still seems broken. In the Postfix log I now see: Mar? 6 13:49:03 myhost amavis[7165]: (07165-10) K00VtLRHdrYw FWD from <admin at mydomain.tld> -> <"@"@mydomain.tld>, BODY=7BIT 250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as B8CA22DA1B37 Mar? 6 13:49:03 myhost amavis[7165]: (07165-10) Passed CLEAN

I wrapped the LDA command in a script. I can see that Postfix passes "@@mydomain.tld" as the -d argument, without quotes. I then adapted the script to specifically replace this address with "@"@mydomain.tld, but this results in the following error message by Dovecot: ??? auth: Info: userdb(?): Username character disallowed by auth_username_chars: 0x22 (username:

Please help.. I have been searching for two days trying everything that I can find to solve this problem. Let's do the setup. Single ADS Domain, Primary and Backup Domain Controllers Windows 2000 Advanced Server SP4 FreeBSD 4.8 Samba 3 (custom build with (./configure -with-pam -with-winbind --with-winbind-auth-challenge)) smb.conf build with SWAT # Global parameters [global]

I'm failing to understand how getrusage() works, which is a bit perplexing, because it doesn't seem like it would be terribly complicated. I've attached the code. My aim is to verify that I can use getrusage() to do (admittedly crude) instrumentation of which functions in my program are allocating lots of memory[1]. So I figure I can call getrusage() at various points and look at

On 15/04/2019 12:59, Larry Rosenman via dovecot wrote: > forgot to reply all. > > ---------- Forwarded message --------- > From: *Larry Rosenman* <larryrtx at gmail.com <mailto:larryrtx at gmail.com>> > Date: Mon, Apr 15, 2019 at 5:58 AM > Subject: Re: SOLR/Index? > To: John Fawcett <john at voipsupport.it <mailto:john at voipsupport.it>> > > >

Op 7-3-2018 om 15:40 schreef Stephan Bosch: > > > Op 7-3-2018 om 13:46 schreef Philipp Berger: >> I wrapped the LDA command in a script. I can see that Postfix passes >> "@@mydomain.tld" as the -d argument, without quotes. >> I then adapted the script to specifically replace this address with >> "@"@mydomain.tld, but this results in the

Hi, I use Dovecot 2.0.13 on OpenBSD 5.0 When i try to send emails i have the following error in /var/log/maillog Jan 5 11:23:49 mail50 postfix/pipe[29423]: D951842244C: to=, relay=dovecot, delay=0.02, delays=0.01/0/0/0.01, dsn=5.3.0, status=bounced (command line usage error. Command output: deliver: unknown option -- n Usage: dovecot-lda [-c ] [-a ] [-d ] [-p ] [-f ] [-m ] [-e] [-k] ) Jan 5

I just installed Postfix, MySQL, and Dovecot. Everything is working great (IMAP, POP, SMTP) except that I can't get incoming mail to deliver properly. Incoming mail logs the following: Feb 2 13:23:52 mail postfix/qmgr[2187]: CE0D41F0263: from=<mhoppes@[redacted]>, size=650, nrcpt=1 (queue active) Feb 2 13:23:52 mail postfix/pipe[3594]: CE0D41F0263: to=<mhoppes@[redacted]>,

Hi Timo, some time ago (2007-03-24 and following) I asked whether it was intended that Dovecot deliver bounces mails (by terminating with status 89) if the deliver version is older than the rest of the dovecot installation. You replied that it was a bug, and that it had been fixed in <URL:http://dovecot.org/list/dovecot-cvs/2007-March/008346.html>. When I upgraded from Dovecot 1.0.2 to

Hi, I'm trying to get dovecot's LDA 'deliver' to deliver mails that come in through a postfix daemon on the same box. I'm talking about dovecot version 1.0.rc15 (on CentOS 5 as Linux-VServer guest on a CentOS 5 host). Configuration ------------- # /etc/dovecot.conf ssl_cert_file: /etc/pki/selfmade/server.crt ssl_key_file: /etc/pki/selfmade/server.key login_dir:

Op 6-3-2018 om 14:34 schreef Philipp Berger: > I upgraded to Dovecot 2.3.0.1 as advised, but it still seems broken. In > the Postfix log I now see: > > Mar? 6 13:49:03 myhost amavis[7165]: (07165-10) K00VtLRHdrYw FWD from > <admin at mydomain.tld> -> <"@"@mydomain.tld>, BODY=7BIT 250 2.0.0 from > MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as

Op 7-3-2018 om 13:46 schreef Philipp Berger: > I wrapped the LDA command in a script. I can see that Postfix passes > "@@mydomain.tld" as the -d argument, without quotes. > I then adapted the script to specifically replace this address with > "@"@mydomain.tld, but this results in the following error message by > Dovecot: > > ??? auth: Info: userdb(?):

Seems wrong to me too, Robert. If you put your private key inside your certificate, won't it be sent to the client along with it ? Bastian, are you using an old version of thunderbird ? googling for "SSL alert number 42" gave me two results indicating a bug in thunderbird versions 31,32 and 33. You can check these links if you wish : *