Patching qmail

Small modification

Radu March 29, 2023 07:55

Hello 

Please modify the 

gunzip -c ../roberto-netqmail-1.06.patch-latest.gz | patch

with 

gunzip -c ../roberto-netqmail-1.06.patch-2023.03.01.gz |patch 

Or save wget with latest . 

Reply | Permalink

Small modification

Roberto Puzzanghera Radu March 29, 2023 12:34

Corrected. Thank you

Reply | Permalink

can not send email to special domain

Jacky March 26, 2023 07:46

Hi roberto puzzanghera 

After applied the latest patch. I could not send email account with domain s--and--s.net

The error is "553 5.1.3 sorry, mailbox syntax not allowed ". I think 「--」 is not accepted. 

Before updated the latest patch. I used 2022.05.22 patch.

$ telnet 172.24.4.23 25
Trying 172.24.4.23...
Connected to 172.24.4.23.
Escape character is '^]'.
220 mail.local Welcome to SMTP server ESMTP
AUTH LOGIN
334 VXNlcm5hbWU6
xxxxx
334 UGFzc3dvcmQ6
xxxxx
235 ok, go ahead (#2.0.0)
mail from:test@mail.local
250 ok
rcpt to:test@s--and--s.net
553 5.1.3 sorry, mailbox syntax not allowed 
quit
221 mail.local Welcome to SMTP server
Connection closed by foreign host.

Reply | Permalink

can not send email to special domain

Roberto Puzzanghera Jacky March 26, 2023 13:22

I cannot reproduce the issue. And I remember that we cured it here...

can you double check that you are actually applying the latest patch?

Reply | Permalink

can not send email to special domain

Jacky Roberto Puzzanghera March 26, 2023 19:29

hi roberto puzzanghera 

Yes, I tried to compile again with the lastest patch. but the same is displayed.

In chkuser_settings.h , i uncommented 383 line and recomplied again everything is going well

#define CHKUSER_DISABLE_VARIABLE "RELAYCLIENT"

Reply | Permalink

can not send email to special domain

Roberto Puzzanghera Jacky March 26, 2023 20:19

Do you have CHKUSER_SENDER_NOCHECK_VARIABLE defined as RELAYCLIENT?

Reply | Permalink

can not send email to special domain

Jacky Roberto Puzzanghera March 27, 2023 07:04

Yes ,I have #define CHKUSER_SENDER_NOCHECK_VARIABLE "RELAYCLIENT" in chkuser_settings.h too.

Reply | Permalink

can not send email to special domain

Roberto Puzzanghera Jacky March 27, 2023 11:06

Weird... This option would be sufficient to let RELAYCLIENT send even garbage in the domain syntax. 

My tests work as expected. And if I disable RELAYCLIENT from tcprules mails with the double hyphen are sent anyway

Reply | Permalink

can not send email to special domain

Jacky Roberto Puzzanghera March 27, 2023 11:44

Thank you roberto puzzanghera

Now I can not figure out the problem. So I will run qmail with this setting. 

#define CHKUSER_DISABLE_VARIABLE "RELAYCLIENT"

Reply | Permalink

can not send email to special domain

Ali Erturk TURKER Jacky March 27, 2023 12:53

Hi Jacky

Unfortunately you are playing with the wrong knobs. Please undo what you did.

The patch Roberto mentioned previously corrected "check_sender_address_format()" function.

But you are bitten by "check_rcpt_address_format()" function.

Please search this function after patching, and comment out the lines below as follows:

/*
 } else {
if (strstr (domain->s, "--") != NULL)
return 0;
*/

Reply | Permalink

can not send email to special domain

Roberto Puzzanghera Ali Erturk TURKER March 27, 2023 14:44

Thanks Ali. Patch updated

Reply | Permalink

can not send email to special domain

Jacky Roberto Puzzanghera March 28, 2023 10:55

Hi roberto puzzanghera and Ali Erturk TURKER 

Thank you very much!

I applied the latest patch. Everything is going well.

Appreciated

Reply | Permalink

STARTTLS/SMTPS AUTH header fix for qmail-smtpd

Ali Erturk TURKER March 12, 2023 12:19

Hi Roberto,

As you will see here the qmail-auth patch sets the protocol string as "ESMTPA", even though the user is authenticated via starttls/smtps. We need a patch like this to correct the headers generated by qmail-smtpd (which should cleanly apply on your combined patch). After the patch, the mail headers will change from "ESMTPA" to "ESMTPSA" and the

ssl_cipher used will be provided as follows:

Before patch:

Received: from unknown (HELO ?172.16.10.2?) (turkerali@xxxxxx.xxx@172.16.10.2)
    by xxx.xxxxxx.com with ESMTPA; 10 Mar 2023 20:33:57 -0000

After patch:

Received: from unknown (HELO ?172.16.10.2?) (turkerali@xxxxxx.xxx@172.16.10.2)
    by xxx.xxxxxx.com with ESMTPSA (TLS_AES_128_GCM_SHA256 encrypted, authenticated); 12 Mar 2023 12:32:03 -0000

Feel free to test and share on your website.

Regards,

AET

Reply | Permalink

STARTTLS/SMTPS AUTH header fix for qmail-smtpd

Roberto Puzzanghera Ali Erturk TURKER March 12, 2023 13:33

Thank you, Ali. Added

Reply | Permalink

qmail-remote CRLF patch on steroids

Ali Erturk TURKER March 1, 2023 10:01

Hi Roberto,

Bruce Guenter (a qmail guru) has written a patch which offers the exact same functionality of your qmail-remote CRLF patch, while providing 10x less CPU usage for qmail-remote. He accomplishes this by reading the message in 4K chunks (instead of byte-by-byte) while substituting the control characters, and pushing the mail to the remote mail server.

That makes perfect sense, as almost all major filesystems in use today (ext4, btrfs, xfs) default to 4K blocksize.

I modified his patch so that it applies cleanly on your combined patch. Feel free to download from this link, test and share on your website.

Reply | Permalink

qmail-remote CRLF patch on steroids

Roberto Puzzanghera Ali Erturk TURKER March 1, 2023 15:59

Hi Ali, thanks for the advise. Patch added

Reply | Permalink

vpopmail needed?

Dimi February 28, 2023 20:59

Hi Roberto,

Thank you for putting together the combined patch that adds so many useful feature to netqmail-1.06.

Will the combine patch work without vpopmail? I would like to use it on servers where I do not have mysql and vpopmail installed.

Reply | Permalink

vpopmail needed?

Roberto Puzzanghera Dimi March 1, 2023 04:51

No, it has vpopmail as a prerequisite 

Reply | Permalink

qmail-rfc2821 patch does not cover implicit TLS (SMTPS) connections.

Ali Erturk TURKER February 27, 2023 09:51

Hi Robert

As you will see here, if the remote port is given as "465" in control/smtproutes file, qmail-remote automatically switches to implicit TLS ("SMTP over TLS" or "smtps"). I believe qmail-rfc2821 patch appeared before the qmail-tls support, therefore it does not cover implicit TLS (SMTPS) connections. Since I am a fan of implicit TLS connections myself, (due to STARTTLS MitM attacks), I created this patch. Feel free to test and share on your website.

Reply | Permalink

qmail-rfc2821 patch does not cover implicit TLS (SMTPS) connections.

Roberto Puzzanghera Ali Erturk TURKER February 27, 2023 14:36

Do you think that it shoukd be like this?

# ifdef TLS 
- if (tls_init())
+ if (tls_init()) { 
   if (smtps) { 
       code = smtpcode(); 
       if (code >= 500 && code < 600) quit("DTLS Connected to "," but greeting failed"); 
       if (code >= 400 && code < 500) return; /* try next MX, see RFC-2821 */ 
       if (code != 220) quit("ZTLS Connected to "," but greeting failed"); 
   } 
 /* RFC2487 says we should issue EHLO (even if we might not need 
    * extensions); at the same time, it does not prohibit a server 
    * to reject the EHLO and make us fallback to HELO */ 
   code = ehlo(); 
+ } 
# endif

Reply | Permalink

qmail-rfc2821 patch does not cover implicit TLS (SMTPS) connections.

Ali Erturk TURKER Roberto Puzzanghera February 27, 2023 14:49

Hi Roberto,

I also removed 2 lines from tls_init() to move the connection checks to smtp() function,

to make the code consistent with the previous qmail-rfc2821 patch. Please check my patch again.

It should apply cleanly on your combined patch.

AET

Reply | Permalink

qmail-rfc2821 patch does not cover implicit TLS (SMTPS) connections.

Roberto Puzzanghera Ali Erturk TURKER February 27, 2023 14:58

Yes, I see those other two lines removed.

But I don't understand why in your patched file this line

code = ehlo();

is no longer inside the if (tls_init())

Reply | Permalink

qmail-rfc2821 patch does not cover implicit TLS (SMTPS) connections.

Anonymous Roberto Puzzanghera February 27, 2023 15:07

Hi Roberto,

Probably there is a misunderstanding. My patch does not replace the qmail-rfc2821 patch.

My patch should be applied on top of your latest combined patch (netqmail-1.06 v. 2023.02.24).

After patching, qmail-remote.c should look like this. Please check and let me know if you have any questions.

Regards

AET

Reply | Permalink

qmail-rfc2821 patch does not cover implicit TLS (SMTPS) connections.

Roberto Puzzanghera Anonymous February 27, 2023 15:15

Exactly. What I don't understand is why that last

code = ehlo();

before your patch is inside the if (tls_init()) block

  if (tls_init())
 /* RFC2487 says we should issue EHLO (even if we might not need 
    * extensions); at the same time, it does not prohibit a server 
    * to reject the EHLO and make us fallback to HELO */ 
   code = ehlo();

while after your patch it is outside the same block

if (tls_init())
if (smtps) {
code = smtpcode();
if (code >= 500 && code < 600) quit("DTLS Connected to "," but greeting failed");
if (code >= 400 && code < 500) return; /* try next MX, see RFC-2821 */
if (code != 220) quit("ZTLS Connected to "," but greeting failed");
}
/* RFC2487 says we should issue EHLO (even if we might not need
* extensions); at the same time, it does not prohibit a server
* to reject the EHLO and make us fallback to HELO */
code = ehlo();

Reply | Permalink

qmail-rfc2821 patch does not cover implicit TLS (SMTPS) connections.

Anonymous Roberto Puzzanghera February 27, 2023 15:42

Hi Roberto

You are %1000000000000 right.

First I created the patch on my win10 machine and it's exactly how you suggested.

Then I manually created it again on my linux vm to rebase it on your combined patch, and screwed up.

I revised the patch , should be OK now.

Reply | Permalink

qmail-rfc2821 patch does not cover implicit TLS (SMTPS) connections.

Roberto Puzzanghera Anonymous February 27, 2023 16:17

Impossible not to have at least a bug when you develop on Windows :-)

Patch updated

Reply | Permalink

qregex patch needs to be corrected

Ali Erturk TURKER February 24, 2023 06:11

Hi Roberto

At some point in time, Luca Franceschini had renamed control/badmailto and control/badmailtonorelay files to control/badrcptto and control/badrcpttonorelay files in:

qmail-smtpd.8
qmail-smtpd.c

Unfortunately this patch overlooked these files, which still contain the old naming scheme.

README.qregex
qmail-control.9
qmail-smtpd.8
qmail-showctl.c

The above files should also be updated accordingly.

Regards,

Ali Erturk TURKER

Reply | Permalink

qregex patch needs to be corrected

Roberto Puzzanghera Ali Erturk TURKER February 24, 2023 06:38

corrected. Thank you

Reply | Permalink

Timeout Log

Jacky November 15, 2022 00:53

Hi roberto puzzanghera 

Today, I got many error in SMTP log. 

Can you tell me the meaning of「reason=alarmtimeout 」 . And how can I tunning any qmail 's parameter to fix it ?

2022-11-14 19:40:42.017547500 mail1 qlogenvelope: result=rejected code=451 reason=alarmtimeout detail= helo=xxx mailfrom=xxx@163.com rcptto= relay=no rcpthosts= size=148766 authuser= authtype= encrypted= sslverified=no localip=xxxx localport=25 remoteip=xxxxx remoteport=16847 remotehost=m12-15.163.com qp=3063 pid=2630

Reply | Permalink

Timeout Log

Roberto Puzzanghera Jacky November 16, 2022 10:40

Hi Jacky,

it is an error belonging to the timeoutread function of qmail-smtpd, which doesn't have any comment inside. It is triggered when the client does not provide some of the mandatory commands in time, such as helo, mailfrom, rcptto etc. When I have this error I can always see a missing helo, or a missing mailfrom or rcptto just like when the client didn't provide them in time. You can see that rcptto is empty also in your example.

I don't think that this is your server's renponsibility. Anyway you can try to increase the "timeoutsmtpd" time in your control/timeoutsmtpd if you have set it to a very short time interval. It defaults to 1200s (20 minutes), which is a very long time.

You can reproduce that logline by connecting to your server, not providing the helo or mailfrom or rcptto commands and letting the remote server close the connection after the timeout (of course it's better to shorten it modifying your control/timeoutsmtpd file).

Reply | Permalink

Timeout Log

Jacky Roberto Puzzanghera November 17, 2022 08:10

I  increased timoutsmtpd to 600 second. Until now I did not get any alarmtimeout log anymore. 

Thank you roberto puzzanghera

Reply | Permalink

Get size of message via environment variable

Jacky July 2, 2022 15:03

Hi roberto puzzanghera 

I am trying to write a qmail-spp plugin to deny the message that over size limit of our partner mail server.

So can I get size of message via environment variable like TCPREMOTEHOST ?

Reply | Permalink

Get size of message via environment variable

Roberto Puzzanghera Jacky July 2, 2022 16:37

Hi,

I'm not sure that the environment variables visible for qmail-smtpd will be directly visible inside a qmail-spp program. You can see which variables you have in the readme file at point 5 https://notes.sagredo.eu/files/qmail/patches/qmail-spp/README. I don't recall if/where the size of the incoming message is stored, but you can easily print those variables to find out where it is.

Reply | Permalink

Get size of message via environment variable

Anonymous Roberto Puzzanghera July 6, 2022 07:00

Hi roberto puzzanghera 

I will try to set enviroment MAILSIZE in qmail-smtpd.c

I have one more question. Is there limit maximum of allowed recipients(To,Cc or Bcc). I try to send 1000 recipients

but it does not work well

I dont set CHKUSER_RCPTLIMIT variable. 

Reply | Permalink

Get size of message via environment variable

Roberto Puzzanghera Anonymous July 6, 2022 10:54

yes, look at the concurrencylocal and concurrencyremote config files (http://www.lifewithqmail.org/lwq.html#configuration)

edit: be sure not to have set limits here for that particular account https://notes.sagredo.eu/en/qmail-notes-185/limiting-the-number-of-emails-sent-by-a-given-auth-userdomainip-231.html

Reply | Permalink

incoming maximum number of recipients allowed

luchris May 31, 2022 03:53

 Hi Roberto and all,

Recently one of my domains keep getting 550_5.5.3_sorry,_reached_maximum_number_of_recipients_allowed_in_one_session_(chkuser) when someone sent more than 20 recipients to them. How and where do i increase this limit?

Thank you

Reply | Permalink

incoming maximum number of recipients allowed

Roberto Puzzanghera luchris May 31, 2022 08:04

Hi, just edit control/concurrencyincoming and restart qmail

Reply | Permalink

qmail-smtpd: read failed (hang up before quit cmd)

Gabriel Torres May 22, 2022 16:32

Hi Roberto,

I see a lot of messages like this from time to time in the smptd log. I don't know if this is something we should worry about or it is normal and safe to ignore.

Thank you in advance!

 qmail-smtpd: read failed (hang up before quit cmd)

Reply | Permalink

qmail-smtpd: read failed (hang up before quit cmd)

Roberto Puzzanghera Gabriel Torres May 23, 2022 15:17

I recorded a qmail-smtpd session just to be sure what that messages means:

2022-05-22 20:13:44.267014500 tcpserver: pid 27286 from 199.249.230.87 
2022-05-22 20:13:44.357670500 tcpserver: ok 27286 smtp.sagredo.eu:10.0.0.4:25 tor38.quintex.com:199.249.230.87::37602 
2022-05-22 20:14:04.363400500 27286 > 220 smtp.sagredo.eu ESMTP^M 
2022-05-22 20:14:06.787104500 27286 < [EOF] 
2022-05-22 20:14:06.787172500 qmail-smtpd: read failed (hang up before quit cmd): (null) from 199.249.230.87 to (null) helo > 
2022-05-22 20:14:06.787488500 27286 > [EOF] 
2022-05-22 20:14:06.787591500 tcpserver: end 27286 status 256

It is an issue due to the fact that the client closed the connection unexpectedly without sending the quit command. Tecnically it is something that should not happen, so the read error.

PS often this happens after the client received a reject message from our qmail. I've just modified the error messages in the patch of may 22 from "hang up before quit cmd" to "client closed the connection before the quit command"

Reply | Permalink

Failed after apply roberto-netqmail-1.06.patch-2022.02.13

Bruno Ribas May 13, 2022 15:30

Hello,

After apply the patch roberto-netqmail-1.06.patch-2022.02.13, i got this error:

compilation terminated.
make: *** [: srs.o] Erro 1

Reply | Permalink

Failed after apply roberto-netqmail-1.06.patch-2022.02.13

Roberto Puzzanghera Bruno Ribas May 13, 2022 15:35

Did you install libsrs2 first?

If yes please post the entire error string

Reply | Permalink

Failed after apply roberto-netqmail-1.06.patch-2022.02.13

Anonymous Roberto Puzzanghera May 17, 2022 18:57

Thanks, I installed libsrs2 and the process advanced a little further, changing the error message:

make: *** [Makefile:1674: qmail-remote.o] Erro 1

Reply | Permalink

Failed after apply roberto-netqmail-1.06.patch-2022.02.13

Roberto Puzzanghera Anonymous May 17, 2022 19:32

Can you provide the entire error string, please?

Reply | Permalink

Failed after apply roberto-netqmail-1.06.patch-2022.02.13

Bruno Ribas Roberto Puzzanghera May 19, 2022 20:23

This is the complete output after I run the command 'make setup check'

Makefile:156: aviso: sobrescrevendo os comandos para o alvo 'base64.o'
Makefile:152: aviso: ignorando comandos antigos para o alvo 'base64.o' 
Makefile:239: aviso: sobrescrevendo os comandos para o alvo 'byte_cspn.o'
Makefile:235: aviso: ignorando comandos antigos para o alvo 'byte_cspn.o' 
Makefile:255: aviso: sobrescrevendo os comandos para o alvo 'byte_rcspn.o'
Makefile:251: aviso: ignorando comandos antigos para o alvo 'byte_rcspn.o' 
Makefile:1845: aviso: sobrescrevendo os comandos para o alvo 'qmail-todo'
Makefile:1831: aviso: ignorando comandos antigos para o alvo 'qmail-todo' 
Makefile:1853: aviso: sobrescrevendo os comandos para o alvo 'qmail-todo.o'
Makefile:1839: aviso: ignorando comandos antigos para o alvo 'qmail-todo.o' 
Makefile:2172: aviso: sobrescrevendo os comandos para o alvo 'spf.o'
Makefile:2154: aviso: ignorando comandos antigos para o alvo 'spf.o' 
Makefile:2177: aviso: sobrescrevendo os comandos para o alvo 'spfquery'
Makefile:2160: aviso: ignorando comandos antigos para o alvo 'spfquery' 
Makefile:2184: aviso: sobrescrevendo os comandos para o alvo 'spfquery.o'
Makefile:2167: aviso: ignorando comandos antigos para o alvo 'spfquery.o' 
Makefile:2222: aviso: sobrescrevendo os comandos para o alvo 'str_cpyb.o'
Makefile:2218: aviso: ignorando comandos antigos para o alvo 'str_cpyb.o' 
Makefile:2311: aviso: sobrescrevendo os comandos para o alvo 'strsalloc.o'
Makefile:2306: aviso: ignorando comandos antigos para o alvo 'strsalloc.o' 
./compile qmail-remote.c
qmail-remote.c: In function ‘dropped’:
qmail-remote.c:128:7: error: ‘ssl_err_str’ undeclared (first use in this function)
128 | if (ssl_err_str) { out((char *)ssl_err_str); out(" "); }
| ^~~~~~~~~~~
qmail-remote.c:128:7: note: each undeclared identifier is reported only once for each function it appears in
qmail-remote.c: In function ‘ssl_timeoutread’:
qmail-remote.c:158:10: warning: implicit declaration of function ‘ERR_error_string’ [-Wimplicit-function-declaration]
158 | out(ERR_error_string(ERR_get_error(), buf)); out("\n");
| ^~~~~~~~~~~~~~~~
qmail-remote.c:158:27: warning: implicit declaration of function ‘ERR_get_error’; did you mean ‘SSL_get_error’? [-Wimplicit-function-declaration]
158 | out(ERR_error_string(ERR_get_error(), buf)); out("\n");
| ^~~~~~~~~~~~~
| SSL_get_error
In file included from qmail-remote.c:7:
qmail-remote.c: At top level:
substdio.h:12:64: warning: initialization of ‘int (*)()’ from incompatible pointer type ‘ssize_t (*)(int, void *, size_t)’ {aka ‘long int (*)(int, void *, long unsigned int)’} [-Wincompatible-pointer-types]
12 | #define SUBSTDIO_FDBUF(op,fd,buf,len) { (buf), 0, (len), (fd), (op) }
| ^
qmail-remote.c:231:17: note: in expansion of macro ‘SUBSTDIO_FDBUF’
231 | substdio ssin = SUBSTDIO_FDBUF(read,0,inbuf,sizeof inbuf);
| ^~~~~~~~~~~~~~
substdio.h:12:64: note: (near initialization for ‘ssin.op’)
12 | #define SUBSTDIO_FDBUF(op,fd,buf,len) { (buf), 0, (len), (fd), (op) }
| ^
qmail-remote.c:231:17: note: in expansion of macro ‘SUBSTDIO_FDBUF’
231 | substdio ssin = SUBSTDIO_FDBUF(read,0,inbuf,sizeof inbuf);
| ^~~~~~~~~~~~~~
qmail-remote.c: In function ‘quit’:
qmail-remote.c:350:30: error: ‘smtps’ undeclared (first use in this function); did you mean ‘smtpto’?
350 | if (state & TLS_ST_OK || (!smtps && state & TLS_ST_BEFORE))
| ^~~~~
| smtpto
qmail-remote.c: In function ‘smtp’:
qmail-remote.c:585:13: warning: implicit declaration of function ‘strcasecmp’ [-Wimplicit-function-declaration]
585 | if (strcasecmp(fqdn,commonName)){
| ^~~~~~~~~~
qmail-remote.c:622:9: warning: implicit declaration of function ‘b64encode’ [-Wimplicit-function-declaration]
622 | if (b64encode(&auth_smtp_plain,&slop)) temp_nomem();
| ^~~~~~~~~
make: *** [Makefile:1674: qmail-remote.o] Erro 1

Reply | Permalink

Failed after apply roberto-netqmail-1.06.patch-2022.02.13

Roberto Puzzanghera Bruno Ribas May 19, 2022 20:33

did you installed openssl? which version?

can you post which version of gcc and which os you have?

Reply | Permalink

Failed after apply roberto-netqmail-1.06.patch-2022.02.13

Bruno Ribas Roberto Puzzanghera May 23, 2022 17:52

OpenSSL Version:

OpenSSL 1.1.1n  15 Mar 2022

In 'gcc -v' the result is this:

gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/10/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 10.2.1-6' --with-bugurl=file:///usr/share/doc/gcc-10/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-10 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-10-Km9U7s/gcc-10-10.2.1/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-10-Km9U7s/gcc-10-10.2.1/debian/tmp-gcn/usr,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-mutex
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.2.1 20210110 (Debian 10.2.1-6)

And my OS is Debian 11.3

Reply | Permalink

Failed after apply roberto-netqmail-1.06.patch-2022.02.13

Roberto Puzzanghera Bruno Ribas May 23, 2022 18:45

ssl_err_str was defined around line 72 of qmail-remote.c, isn't it?

did you get any error during the patch process?

Reply | Permalink

Implement reject null senders patch only for port 465 or 587

Jacky February 25, 2022 14:15

Hi roberto puzzanghera 

In this qmail patch can I apply reject null senders only for special port (465 or 587) with environment variable  ?

Reply | Permalink

Implement reject null senders patch only for port 465 or 587

Roberto Puzzanghera Jacky February 25, 2022 14:48

try this patch defining REJECTNULLSENDERS in your run file https://notes.sagredo.eu/files/qmail/patches/roberto-netqmail-1.06/roberto-netqmail-1.06.patch-2022.02.25.gz

let me know

Reply | Permalink

Implement reject null senders patch only for port 465 or 587

Jacky Roberto Puzzanghera February 25, 2022 15:14

Hi roberto puzzanghera 

Thank your patch.
After apply new patch I got this error below.

# telnet 127.0.0.1 587
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
421 unable to read controls (#4.3.0)
Connection closed by foreign host.

# openssl s_client -connect localhost:587 -starttls smtp
CONNECTED(00000003)
didn't found starttls in server response, try anyway...
write:errno=32
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 38 bytes and written 25 bytes
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
Protocol : TLSv1.2
Cipher : 0000
Session-ID:
Session-ID-ctx:
Master-Key:
Key-Arg : None
Krb5 Principal: None
PSK identity: None
PSK identity hint: None
Start Time: 1645801919
Timeout : 300 (sec)
Verify return code: 0 (ok)
---

Reply | Permalink

Implement reject null senders patch only for port 465 or 587

Roberto Puzzanghera Jacky February 25, 2022 15:36

try downloading again now

Reply | Permalink

Implement reject null senders patch only for port 465 or 587

Jacky Roberto Puzzanghera February 25, 2022 23:17

Hi roberto puzzanghera 

Everything is fine. Thank you very much.

P/s: I think if add ipv6 support this patch is the best patch for qmail.

Reply | Permalink

Implement reject null senders patch only for port 465 or 587

Roberto Puzzanghera Jacky February 26, 2022 07:21

Yes, I think because this is the only maintained patch published on the internet!

Ipv6 would be great! Which patch are you testing?

Reply | Permalink

Implement reject null senders patch only for port 465 or 587

Jacky Roberto Puzzanghera February 26, 2022 10:02

I tested this patch roberto-netqmail-1.06.patch-2022.02.25.gz 

and implemented to one production server for workload test.

Reply | Permalink

Implement reject null senders patch only for port 465 or 587

Roberto Puzzanghera Jacky February 26, 2022 13:06

I'm not sure that ipv6 can work without patching the core of qmail...

Reply | Permalink

Implement reject null senders patch only for port 465 or 587

Jacky Roberto Puzzanghera February 26, 2022 13:34

Exactly,

I just applied tcpserver for ipv6 only . incomming email is fine(RBL is not working well) ,

but outgoing does not work.

Reply | Permalink

Implement reject null senders patch only for port 465 or 587

Roberto Puzzanghera Jacky February 26, 2022 16:23

I guess that the rblsmtpd program by eh embedded in ucspi-tcp6 will work

I think that also at least spf and moreipme have to patched.

If you want to help, can you test the Manvendra's ipv6 patch here https://sourceforge.net/projects/indimail/files/netqmail-addons/qmail-dkim-1.0/ against Saout's spf?

Reply | Permalink

Implement reject null senders patch only for port 465 or 587

Jacky Roberto Puzzanghera February 27, 2022 06:21

this patch with name dkim+spf+ipv6.patch-1.14.gz right?

If you need one machine with ipv6 let me know.

Reply | Permalink

Implement reject null senders patch only for port 465 or 587

Roberto Puzzanghera Jacky February 27, 2022 07:57

yes, this one. At a certain point Manvendra added ipv6 to the original dkim patch, but I've never found the time to add it to my patch.

I would install it on a vanilla qmail and test it as is. Then I would install the spf patch (https://notes.https://notes.sagredo.eu/files/qmail/patches/qmail-spf-rc5.patchsagredo.eu/files/qmail/patches/qmail-spf-rc5.patch) on top of it and test spf.

Thanks for the collaboration and for the possibility to use a machine of yours. This month I don't have free time because I have to migrate this server.

We can continue this discussion on ipv6 in private via mail if you like (contact button on the top of this page).

Reply | Permalink

not-qmail?

Ryan February 17, 2022 03:14

Hey Robert,

Long time reader, first time caller.  Recently came across the not-qmail project (GH/not-qmail/not-qmail), from some former qmail users who went over to postfix and came back.  Was wondering if you'd taken a look at their work, or if you think net-qmail is still the best base for qmail?

Reply | Permalink

not-qmail?

Roberto Puzzanghera Ryan February 17, 2022 09:57

Hi Ryan, certainly a combined patch based on the qmail legacy like mine can't represent the future of qmail and one day we'll have to look at some of those qmail successors like not-qmail. I've never played with not-qmail but I have a big respect for such an ambitious project, and the fact that it comes from qmail gurus like Manvendra Bhangui and the others sounds like a garantee for me. But, as their wishlist says, most common features still have to be implemented, so let's give them their time.

Nowadays, if I'd have to use in production a qmail successor, I'd rather consider Manvendra's indimail (it has everything) and Erwin Hoffmann's s/qmail (very active and complete)

Reply | Permalink

Got error with netqmail-1.06 v. 2022.02.10 

Jacky February 13, 2022 14:43

Hi roberto puzzanghera 

I tried to apply newest patch combined patch for netqmail-1.06 v. 2022.02.10

but got some error below. Can you check it for me. is it displayed only on my server?

./compile qmail-smtpd.c
In file included from tls.h:4:0,
from qmail-smtpd.c:36:
qmail-smtpd.c: In function ‘tls_init’:
qmail-smtpd.c:2351:28: error: ‘SSL_OP_NO_RENEGOTIATION’ undeclared (first use in this function)
SSL_CTX_set_options(ctx, SSL_OP_NO_RENEGOTIATION);
^
qmail-smtpd.c:2351:28: note: each undeclared identifier is reported only once for each function it appears in
make: *** [qmail-smtpd.o] Error 1

Reply | Permalink

Got error with netqmail-1.06 v. 2022.02.10 

Roberto Puzzanghera Jacky February 13, 2022 14:59

can you try with this one please? https://notes.sagredo.eu/files/qmail/patches/roberto-netqmail-1.06/roberto-netqmail-1.06.patch-2022.02.13.gz

Reply | Permalink

Got error with netqmail-1.06 v. 2022.02.10 

Roberto Puzzanghera Jacky February 13, 2022 14:48

Hi, which version of openssl do you have?

Reply | Permalink

Got error with netqmail-1.06 v. 2022.02.10 

Jacky Roberto Puzzanghera February 13, 2022 19:17

Hi,

I am using openssl version below. Is it old?

OpenSSL 1.0.2k-fips  26 Jan 2017

Reply | Permalink

Got error with netqmail-1.06 v. 2022.02.10 

Roberto Puzzanghera Jacky February 13, 2022 19:36

openssl is now at v. 1.1.

The patch that I linked above should solve your problem. Let me know.

Reply | Permalink

Got error with netqmail-1.06 v. 2022.02.10 

Jacky Roberto Puzzanghera February 14, 2022 11:13

Hi roberto puzzanghera

When i tried to apply the link you gave to me. I got some text below.

what should i do? Just enter to countinue?

# gunzip -c ../roberto-netqmail-1.06.patch-2022.02.13.gz |patch
The next patch would delete the file CHANNELS, which does not exist!  Assume -R? [n]

Reply | Permalink

Got error with netqmail-1.06 v. 2022.02.10 

Roberto Puzzanghera Jacky February 14, 2022 11:40

Sorry, the patch that I uploaded yesterday is corrupted. Please download it again and retry

Reply | Permalink

Got error with netqmail-1.06 v. 2022.02.10 

Jacky Roberto Puzzanghera February 15, 2022 00:42

Hi Roberto Puzzanghera 

Thank you very much .

I applied new patch successfully.

Until now everything is good.

Reply | Permalink

qmail-smtp get 100% of CPU

Jacky January 23, 2022 14:54

Hi roberto puzzanghera 

Yesterday, I updated the latest this patch. After that i faced the problem with qmail-smtpd process.

It made my CPU to 100% . Did you have the same issue? Do you have any advice for me to check my server?

Send and receive e-mail is ok.

Tasks: 717 total,   2 running, 581 sleeping,   0 stopped,   0 zombie

%Cpu(s):  6.5 us,  0.2 sy,  0.0 ni, 93.3 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st

KiB Mem : 65429236 total, 24054772 free,  2695836 used, 38678628 buff/cache

KiB Swap:  8388604 total,  8344368 free,    44236 used. 58790728 avail Mem

PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                                                                                      

17142 vpopmail  20   0   43068   4764   4176 R 100.0  0.0   8:28.19 qmail-smtpd                                                                                                  

21070 root      20   0  164140   5152   3804 R   0.7  0.0   0:00.06 top 

Reply | Permalink

qmail-smtp get 100% of CPU

Roberto Puzzanghera Jacky January 23, 2022 15:19

Hi Jacky, no I don't have the same problem.

What do you have in the tcpserver: status line?

2022-01-23 16:16:37.153586500 tcpserver: status: 1/200

PS If I understand well, you are one of the most ancient commentators of this place :-) 

Reply | Permalink

qmail-smtp get 100% of CPU

Jacky Roberto Puzzanghera January 23, 2022 16:24

Hi roberto puzzanghera 

Thank you for your reply ! It is my qmail-smtpd in status line.

2022-01-24 01:17:40.458419500 tcpserver: ok 26702 mail1.xxx.com:172.24.xxx.xxx:25 service.axxx.xxx:209.141.xxx.xxx::45762
2022-01-24 01:17:41.066480500 tcpserver: end 26549 status 2562022-01-24 01:17:41.066481500 tcpserver: status: 15/600
2022-01-24 01:17:41.722767500 tcpserver: end 26593 status 256
2022-01-24 01:17:41.722767500 tcpserver: status: 14/600
2022-01-24 01:17:41.841063500 tcpserver: status: 15/600
2022-01-24 01:17:41.841284500 tcpserver: pid 26723 from 107.16xxx.xxx
2022-01-24 01:17:42.313190500 tcpserver: end 26588 status 256
2022-01-24 01:17:42.313191500 tcpserver: status: 14/600
2022-01-24 01:17:42.854308500 tcpserver: status: 15/600
2022-01-24 01:17:42.854440500 tcpserver: pid 26726 from 134.73.xxx.xxx
2022-01-24 01:17:42.854926500 tcpserver: ok 26726 mail1.xxx.com:172.24.xxx.xxx:25 :134.73.xxx.xxx::61096
2022-01-24 01:17:43.897306500 tcpserver: status: 16/600
2022-01-24 01:17:43.897474500 tcpserver: pid 26727 from 151.52.xxx.xxx
2022-01-24 01:17:43.990919500 tcpserver: ok 26652 mail1.xxx.com:172.24.xxx.xxx:25 :107.16xxx.xxx::54474

Reply | Permalink

qmail-smtp get 100% of CPU

Roberto Puzzanghera Jacky January 23, 2022 19:10

Are the servers' date and time correct? 

Secondly, I would try to see what smtpd is doing with strace

Reply | Permalink

qmail-smtp get 100% of CPU

Jacky Roberto Puzzanghera January 24, 2022 02:01

Hi roberto puzzanghera 

This is my strace qmail-smtpd. I used "strace -fp 24210" command. i

strace: Process 24210 attached
brk(NULL) = 0x840000
brk(NULL) = 0x840000brk(0x83c000) = 0x83c000
brk(NULL) = 0x83c000
write(1, "\26\3\1\0001\2\0\0-\3\1\223\310\"\312Q\0\202\321\223\303.b;}\245I'\276\225\313\344"..., 4095) = 4095
read(0, 0x810c43, 5) = -1 EAGAIN (Resource temporarily unavailable)fcntl(0, F_GETFL) = 0x802 (flags O_RDWR|O_NONBLOCK)
fcntl(0, F_SETFL, O_RDWR) = 0fcntl(1, F_GETFL) = 0x2 (flags O_RDWR)
fcntl(1, F_SETFL, O_RDWR) = 0select(2, NULL, [1], NULL, {tv_sec=60, tv_usec=0}) = 1 (out [1], left {tv_sec=59, tv_usec=999997})
write(1, "454 TLS connection failed: timed"..., 47) = 47
brk(NULL) = 0x83c000brk(NULL) = 0x83c000
brk(0x83a000) = 0x83a000brk(NULL) = 0x83a000
brk(NULL) = 0x83a000brk(NULL) = 0x83a000
brk(0x836000) = 0x836000brk(NULL) = 0x836000
brk(NULL) = 0x836000brk(NULL) = 0x836000brk(0x82b000) = 0x82b000
brk(NULL) = 0x82b000select(3, NULL, [2], NULL, {tv_sec=60, tv_usec=0}) = 1 (out [2], left {tv_sec=59, tv_usec=999996})
write(2, "qmail-smtpd: read failed (tls co"..., 114) = 114
exit_group(1) = ?+++ exited with 1 +++

Reply | Permalink

qmail-smtp get 100% of CPU

Roberto Puzzanghera Jacky January 24, 2022 10:04

you have a TLS connection failure, I guess in your submission service. Can you check your TLS certificate state in this way

openssl s_client -starttls smtp -crlf -connect localhost:587 -cert /var/qmail/control/servercert.pem -key /var/qmail/control/servercert.pem -state

Reply | Permalink

qmail-smtp get 100% of CPU

Jacky Roberto Puzzanghera January 26, 2022 12:06

Hi roberto puzzanghera 

Sorry for late reply . 

I added recordio command before qmail-smtpd in config file to get more detail log. but no TLS error log .

I changed qmail-smtpd/run config [/usr/local/bin/softlimit -m 10000000]->][/usr/local/bin/softlimit -m 200000].

So after 2 days everything is ok. and my server 's cpu is sage now. I think softlimit is over-spec . Thank you for your kindly support.

I am still trying to get qmail using IPv6 . Have a nice day.

Reply | Permalink

qmail-smtp get 100% of CPU

Jacky Roberto Puzzanghera January 24, 2022 10:48

Here is command 's result on my server. I am using "SMTPD_GREETDELAY" for greeting delay too.

Maybe this make server resouce is higher than normal? I will remove SMTPD_GREETDELAY option.

openssl s_client -starttls smtp -crlf -connect localhost:587 -cert /var/qmail/control/servercert.pem -key /var/qmail/control/servercert.pem -state
CONNECTED(00000003)
SSL_connect:before/connect initialization
SSL_connect:SSLv2/v3 write client hello A
SSL_connect:SSLv3 read server hello A
depth=2 C = BE, O = GlobalSign nv-sa, OU = Root CA, CN = GlobalSign Root CA
verify return:1
depth=1 C = BE, O = GlobalSign nv-sa, CN = AlphaSSL CA - SHA256 - G2
verify return:1
depth=0 CN = *.no1-serxxx.com
verify return:1
SSL_connect:SSLv3 read server certificate A
SSL_connect:SSLv3 read server key exchange A
SSL_connect:SSLv3 read server done A
SSL_connect:SSLv3 write client key exchange A
SSL_connect:SSLv3 write change cipher spec A
SSL_connect:SSLv3 write finished A
SSL_connect:SSLv3 flush data
SSL_connect:SSLv3 read server session ticket A
SSL_connect:SSLv3 read finished A
---
Certificate chain
0 s:/CN=*.no1-serxxx.com
i:/C=BE/O=GlobalSign nv-sa/CN=AlphaSSL CA - SHA256 - G2
1 s:/C=BE/O=GlobalSign nv-sa/CN=AlphaSSL CA - SHA256 - G2
i:/C=BE/O=GlobalSign nv-sa/OU=Root CA/CN=GlobalSign Root CA
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIGRzCCBS+gAwIBAgIMTy0J+wRHU1/6EtfPMA0GCSqGSIb3DQEBCwUAMEwxCzAJ
BgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIwIAYDVQQDExlB
bHBoYVNTTCBDQSAtIFNIQTI1NiAtIEcyMB4XDTIxMDYxMTA4MDQwOFoXDTIyMDcx
MzA4MDQwOFowHTEbMBkGA1UEAwwSKi5ubzEtc2VydmVyMjguY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqTXFrhHBizsjq4CCBeTADUN/7bl1F2yc
xHfWiptQzGTnY3ohDCbnsY4/pYqh3AX6/e5ay5++XHHsDlnh9hKFHwEDoBV8f2Jx
NGVChH1JLwGTXEzseeEse76JkqZQj4K6ImxrUvieS4OisN0BTxtkFQ1cazAwHCL1
CjtIoULJK6keoIdZ24H6bNjKX/stmqb6sUp2ttHQOnzTojbZ4dmqqtI/fhfN0dLn
SQrq1aV0owfkgplMS48whjRjfRvuCLGDYy1vl4hpbhBTEQgv4TKxR/cEozAMwDJD
Rhqj2Gujn7CRnlN37ywptBSKStQD9Jsjx2WsNnkSlZMPIaj4dhe1oQIDAQABo4ID
VjCCA1IwDgYDVR0PAQH/BAQDAgWgMIGJBggrBgEFBQcBAQR9MHswQgYIKwYBBQUH
MAKGNmh0dHA6Ly9zZWN1cmUyLmFscGhhc3NsLmNvbS9jYWNlcnQvZ3NhbHBoYXNo
YTJnMnIxLmNydDA1BggrBgEFBQcwAYYpaHR0cDovL29jc3AyLmdsb2JhbHNpZ24u
Y29tL2dzYWxwaGFzaGEyZzIwVwYDVR0gBFAwTjBCBgorBgEEAaAyAQoKMDQwMgYI
KwYBBQUHAgEWJmh0dHBzOi8vd3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkv
MAgGBmeBDAECATAJBgNVHRMEAjAAMD4GA1UdHwQ3MDUwM6AxoC+GLWh0dHA6Ly9j
..
-----END CERTIFICATE-----
subject=/CN=*.no1-serxxx.com
phaSSL CA - SHA256 - G2
---
No client certificate CA names sent
Peer signing digest: SHA512
Server Temp Key: ECDH, P-256, 256 bits
---
SSL handshake has read 3605 bytes and written 450 bytes
---
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
Protocol : TLSv1.2
Cipher : ECDHE-RSA-AES256-GCM-SHA384
Session-ID: AB98869F6AA62BD90D91E8F6EAFDB4B0EFD014FFD6019560C21242593A9CF8E9
Session-ID-ctx: 
Master-Key: CFB1310D7B82FCA44346348EB4C2D57FF53E4AFB7A63C7BDA61F772F8DDC2FB73A2C95E1A1EC03CFF52A4186C7748F62
Key-Arg : None
Krb5 Principal: None
PSK identity: None
PSK identity hint: None
TLS session ticket lifetime hint: 300 (seconds)
TLS session ticket:
0000 - 37 05 25 6f d9 34 73 41-dd c7 fb 5c b7 61 00 21 7.%o.4sA...\.a.!
0010 - e2 dd 4f 35 c3 f5 86 12-d8 59 39 97 b2 db 66 ec ..O5.....Y9...f.
0020 - 5f e4 70 39 8f 54 e9 46-55 a9 41 6f d6 dd 3b b1 _.p9.T.FU.Ao..;.
0030 - 0a f1 49 64 3e 68 30 fe-ba 93 df 39 da 1a 8d bb ..Id>h0....9....
0040 - 5c 76 e0 5f 34 83 33 b1-d8 67 c2 81 9b 75 bd 79 \v._4.3..g...u.y
0050 - 09 11 bb a0 56 d8 3b a3-e6 fe f2 b5 48 40 2f 43 ....V.;.....H@/C
0060 - 9f f4 0e 25 36 db e0 e4-39 1b 69 be 02 0b 6f 79 ...%6...9.i...oy
0070 - 9e fa 8b 20 73 ff 60 0f-54 cc c4 e9 dc e7 f9 26 ... s.`.T......&
0080 - c9 11 b9 93 7c 40 92 57-2c 1c 2a fc c1 c5 8c fb ....|@.W,.*.....
0090 - 14 34 b3 1d 0f e4 cf 58-d0 0b a4 18 25 61 d6 c3 .4.....X....%a..

Start Time: 1643020850
Timeout : 300 (sec)
Verify return code: 0 (ok)
---
250 SIZE 20480000

Reply | Permalink

qmail-smtp get 100% of CPU

Roberto Puzzanghera Jacky January 24, 2022 11:19

No, greetdelay will not engage your cpu, just absorbs spammers' resources :-)

First of all consider an update of your openssl server or disable the connections with SSL 3.0, because of the POODLE vulberability. Anyway your certificate seems ok.

Can you check the logs (both smtpd and submission) and look for those "454 TLS connection failed"? Can you do

openssl s_client -starttls smtp -crlf -connect yourserver.tld:25/587

from remote, using the port that advertise STARTTLS?

Reply | Permalink

Problem of check sender email address with ~ character

Jacky January 5, 2022 07:08

Hi roberto

Today I faced the problem with WBErbxishu_citizen~micro_205_0_0@abc.com

When i remove [~] character everything is ok. So I wonder if we can add exception of [~] character in chckuser.

I checked patch is uncommented [~] character . But it does not work . Can you please check it ?

+#define CHKUSER_ALLOW_SENDER_CHAR_5 '*'
+#define CHKUSER_ALLOW_SENDER_CHAR_6 '^'
+#define CHKUSER_ALLOW_SENDER_CHAR_7 '~'

Reply | Permalink

Problem of check sender email address with ~ character

Roberto Puzzanghera Jacky January 5, 2022 08:08

Hi Jacky, WBErbxishu_citizen~micro_205_0_0@abc.com works here...

Reply | Permalink

Problem of check sender email address with ~ character

Jacky Roberto Puzzanghera January 5, 2022 09:30

Hi roberto

telnet mail-xxx.xxx-xxxx.com 25
Trying 158.101.69.33...
Connected to mail-xxx.xx-xxx.com.
Escape character is '^]'.
220 mail.no1-xxx.com Welcome to SMTP server ESMTP
ehlo
250-mail.no1-xxx.com Welcome to SMTP server
250-STARTTLS
250-PIPELINING
250-8BITMIME
250-AUTH LOGIN PLAIN CRAM-MD5
250 SIZE 20480000
mail from: <WBErbxishu_citizen~micro_205_0_0@biem.eco-serv.jp>
553 5.1.7 sorry, mailbox syntax not allowed (chkuser)
mail from: <WBErbxishu_citizen?micro_205_0_0@rbiem.eco-serv.jp>
553 5.1.7 sorry, mailbox syntax not allowed (chkuser)
mail from: <WBErbxishu_citizen~micro_205_0_0@rbiem.eco-serv.jp>
553 5.1.7 sorry, mailbox syntax not allowed (chkuser)

I deployed newest patch but it does not work for me.

do you have any advice for me.

Reply | Permalink

Problem of check sender email address with ~ character

Roberto Puzzanghera Jacky January 5, 2022 10:00

weird... it's seems like you're not using the same chkuser...

I would check the chkuser's source code in order to verify that you are using the same patch. Check these lines https://notes.sagredo.eu/files/qmail/patches/roberto-netqmail-1.06/2021.06.19_patch.diff

Did you restart qmail after last compile/install?

Reply | Permalink

Problem of check sender email address with ~ character

Anonymous Roberto Puzzanghera January 5, 2022 13:46

hi  Roberto

Thank you for your advice.

I figured out my problem. This issue is in my qmail-smtp run config is still using old qmail-smtpd file . i am terribly sorry.

Thank you very much.

Reply | Permalink

Problem with latest patch

Adebola Ajiboye October 25, 2021 21:29

Hello Roberto

Thank you for your excellent work, time and support of this patch. 

The latest patch builds fine. I can send outgoing mail. However, problems with vdelivermail leaves mail in the queue, perpetually deffered with database_down errors. Have spent a day troubleshooting this new build and could not locate the issue, hoping you can point me in the right direction. 

Here is what I have:

## -> mlcat send

2021-10-25 16:05:54.914534500 delivery 2: deferral: vdelivermail:_deferred,_database_down/

I have double-checked all the usual suspects... queue looks good, brand new build anyways, still not sure what's missing here. Any pointers is much appreciated. Thank you.

Thank you very much.

Reply | Permalink

Problem with latest patch

Roberto Puzzanghera Adebola Ajiboye October 26, 2021 18:13

Hi, I had a look at the source code

   /* if the database is down, deferr */ 
   if ( verrori == VA_NO_AUTH_CONNECTION ) 
       vexiterr (EXIT_DEFER, "vdelivermail: deferred, database down");

it seems that it cannot connect to your mysql. So, double check your mysql connection/priviledges and your vpopmail/mysql configuration

Reply | Permalink

qmail outgoing ip with Ipv6 support

jacky August 27, 2021 21:02

Hi all,

I search "Ipv6" keyword on this page but can not find the answer.

So qmail can send email to other mail server with IPv6 support or not?

I use tcpserver daemon to run qmail.

Reply | Permalink

qmail outgoing ip with Ipv6 support

Roberto Puzzanghera jacky August 27, 2021 21:05

Not with this qmail patch.

Edit: Only ucspi-tcp6 is ipv6 ready

Reply | Permalink

qmail outgoing ip with Ipv6 support

Anonymous Roberto Puzzanghera August 27, 2021 22:16

Hi Roberto

I will install ucspi-tcp6 and try to send and receive with IPv6

Reply | Permalink

add qmail-spp to this patch

Jaky August 27, 2021 13:47

Sorry , anyone can help me install qmail-spp http://qmail-spp.sourceforge.net/doc/ with this patch?

Reply | Permalink

add qmail-spp to this patch

Roberto Puzzanghera Jaky August 27, 2021 17:58

Hi, it should be quite easy to add the patch that was built for the old Bill Shupp's combined patch. But you should do it by hand because the qmail-smtpd.c from Shupp's patch is very different from mine

Reply | Permalink

add qmail-spp to this patch

jacky Roberto Puzzanghera August 27, 2021 20:55

Hi Roberto ,

Thank you for your reply. I will try to add by hand .

Reply | Permalink

add qmail-spp to this patch

Roberto Puzzanghera jacky August 27, 2021 21:01

Remember that those two qmail-qpp files are new and can be copied from a vanilla qmail  patched with the same patch.

Then you only have to take care of the makefile, which is easy to adjust,  and qmail-smtpd.c, where you just have to put those  new lines in the right place

Reply | Permalink

"TLS connect failed" on netqmail-tls 1.06.20110119_1

Andreas Bachmann July 8, 2021 14:34

Hi Roberto,

My qmail installation (netqmail-tls 1.06.20110119_1 over the FreeBSD ports) can't send mails to Microsoft (and others) anymore for a few month. qmail tries to send it for a week and then give up. I read that Microsoft (and others) rejects TLSv1.0 now and accepts only TLSv1.2.

I just checked the last FreeBSD port. It uses the latest Frederik Vermeulen's patch (https://inoa.net/qmail-tls/netqmail-1.06-tls-20200107.patch). But I couldn't find any version number like TLSv1.0, TLSv1.1, TLSv1.2, etc.

• Does it not depend on qmail but on OpenSSL?
• So the patch from f.vermeulen will work with TLSv1.2?

Reply | Permalink

TLS connect failed

Roberto Puzzanghera Andreas Bachmann July 8, 2021 18:31

I think that the latest version will work with all TLS versions, I just remember that the SSLv3 support was removed after POODLE was spotted, but I'm not sure. You should contact the author of the patch for further informations

Or you can install the latest tls patch and test the connection against microsoft using openssl as explained in this guide

Reply | Permalink

expanding allowed characters in mail adresses

Thomas June 18, 2021 19:33

Hi Roberto,

in the patch there are a range of characters that are allowed in the mail address. The CHKUSER_ALLOW_RCPT_CHAR_* variables are used in the functions check_sender_address_format and check_rcpt_address_format in chkuser.c.

Our server with your latest patch rejects mails because of the address includes slashes. I really have no idea why people are thinking this is a good idea :)

2021-06-14 14:41:18.754723500 qlogenvelope: result=rejected code=553 reason=chkusersender detail=senderformat helo=**************** mailfrom=SRS0=R/yv=LI=**************** rcptto= relay=no rcpthosts= size= authuser= authtype= encrypted=tls sslverified=no localip=**************** localport=25 remoteip=**************** remoteport=56562 remotehost=**************** qp= pid=4456
2021-06-14 15:07:27.879168500 CHKUSER rejected sender: from <SRS0=R/yv=LI=****************|remoteinfo/auth:|chkuser-identify:> remote <helo:|remotehostname:****************|remotehostip:****************> rcpt <> : invalid sender address format

What do you think about either replace f.e. #define CHKUSER_ALLOW_RCPT_CHAR_9 '#' (because of '#' is also declared in the 2 functions ) or (my favorite) patch the 2 functions to declare the rest of the allowed characters?

&& (user->s[x] != '#')
&& (user->s[x] != '/')
and so on ...

As I understand the rfc the allowed characters are: !#$%&'*+-/=?^_`.{|}~

Regards Thomas

Reply | Permalink

expanding allowed characters in mail adresses

Roberto Puzzanghera Thomas June 18, 2021 20:34

Hi Thomas,

I think we can patch to define a CHKUSER_ALLOW_RCPT/SENDER_CHAR_11 for the slash character, so that those addresses will be allowed even when CHKUSER_ALLOW_RCPT_SRS is not defined. I'll do it in the following days.

Reply | Permalink

expanding allowed characters in mail adresses

Thomas Roberto Puzzanghera June 24, 2021 18:50

This will be good. I am awaiting your patch :)

Reply | Permalink

expanding allowed characters in mail adresses

Roberto Puzzanghera Thomas June 24, 2021 18:54

The patch is already in place ;)

Reply | Permalink

expanding allowed characters in mail adresses

Thomas Roberto Puzzanghera July 8, 2021 19:00

Oh. I did not realise this. Thank you :)

Reply | Permalink

RSA/DH keys

Eric Broch June 11, 2021 01:57

Hi Roberto,

I noticed the change of RSA/DH keys (rsa4096.pem/dh4096.pem) to length 4096 created by 'update_tmprsadh.sh', but the code has not changed, qmail-smtpd.c still only opens the rsa/dh pem files (below) of 2048 and 1024 length:

FILE *in = fopen("control/rsa2048.pem", "r")
FILE *in = fopen("control/dh2048.pem", "r") 
FILE *in = fopen("control/dh1024.pem", "r");

This may be a stupid question by how does qmail utilize these new keys?

Eric

Reply | Permalink

RSA/DH keys

Roberto Puzzanghera Eric Broch June 11, 2021 21:04

Hi Eric, 

yes, you are right. Actually I'm not using the self signed cert and didn't realized the problem.

Reply | Permalink

RSA/DH keys

Ali Erturk TURKER Roberto Puzzanghera January 30, 2023 11:39

Hi Roberto,

Thanks for your great website. I really learn a lot from you.

In your combined patch, below code from "qmail-smpt.c" looks buggy, and may cause performance issues when using TLS.

The statement "if (keylen == 2048)" will always fail and an ephemeral key will be created on every request, instead of using the static one:

+RSA *tmp_rsa_cb(SSL *ssl, int export, int keylen)
+{
+ ;
+
+ if (!export) keylen = 4096;
+ if (keylen == 2048) {
+ FILE *in = fopen("control/rsa4096.pem", "r");
+ if (in) {
+ rsa = PEM_read_RSAPrivateKey(in, NULL, NULL, NULL);
+ fclose(in);
+ if (rsa) return rsa;
+ }
+ }

Reply | Permalink

RSA/DH keys

Roberto Puzzanghera Ali Erturk TURKER January 30, 2023 13:14

Hi Ali, thanks for your comment.

I don't remember much of that piece of code, but I see that it's different from the original tls patch here

+if (!export) keylen = 4096;
-if (!export) keylen = 2048;
if (keylen == 2048) {

I think it was changed when there was a request to icreasethe  RSA key and DH parameters to 4096 bit.

Unfortunately I'm very busy these days and I can't play with this before a couple of weeks. If you already know how to correct this, please post your solution

Reply | Permalink

RSA/DH keys

Ali Erturk TURKER Roberto Puzzanghera January 30, 2023 17:00

Hi again Roberto,

If you consider the file it tries to open is named rsa4096.pem, "keylen == 2048" is meaningless there,

and this bug will cause the creation of a temporary key in every request, which is a bad thing (TM).

The fix is pretty straightforward (build tested):

diff -ruN netqmail-1.06/qmail-smtpd.c netqmail-1.06-fixed/qmail-smtpd.c
--- netqmail-1.06/qmail-smtpd.c 2023-01-30 17:01:57.920116546 +0400
+++ netqmail-1.06-fixed/qmail-smtpd.c 2023-01-30 17:03:03.752370617 +0400
@@ -2156,7 +2156,7 @@
RSA *rsa;

if (!export) keylen = 4096;
- if (keylen == 2048) {
+ if (keylen == 4096) {
FILE *in = fopen("control/rsa4096.pem", "r");
if (in) {
rsa = PEM_read_RSAPrivateKey(in, NULL, NULL, NULL);

Reply | Permalink

RSA/DH keys

Roberto Puzzanghera Ali Erturk TURKER January 30, 2023 17:06

Thank you. I'll correct as soon as possible

Reply | Permalink

Key too small

Anonymous March 19, 2021 08:51

Debian 10 after update openssl have error

TLS_connect_failed:_error:141A318A:SSL_routines:tls_process_ske_dhe:dh_key_too_small

Reply | Permalink

Key too small

Roberto Puzzanghera Anonymous March 19, 2021 20:36

which version of openssl? what do you have in your /etc/ssl/openssl.cnf -> default_bits? do you get the error if you put default_bits=2048?

Reply | Permalink

Key too small

Anonymous Roberto Puzzanghera March 20, 2021 18:22

yes i have
default_bits = 2048

Reply | Permalink

Key too small

Roberto Puzzanghera Anonymous March 20, 2021 18:27

What openssl version? Do you have any hint to exactly reproduce the issue?

Reply | Permalink

Key too small

Martin Sluka Roberto Puzzanghera October 1, 2022 07:18

This problem is caused by target domains which do not support current encryption standards.

Some current examples for such domains are foni.net or versanet.de.

You can use https://www.checktls.com/TestReceiver to find out if a certain domain is affected; in the test output you should then see something like this:

Of course the best way to solve this would be that the administrators of the target domain update their configuration. However, since we are currently experiencing this problem with a bunch of target domains since upgrading our system, I am currently looking for a workaround how we can still/again send e-mails to them encrypted until they have done so.

I find it interesting that sending an e-mail to these domains still works when I use "swaks -tls …" on the same system. But qmail refuses to talk to them. Any hints?

Or even:

Reply | Permalink

Key too small – Workaround

Martin Sluka Martin Sluka October 1, 2022 12:32

FYI: My current workaround is now:

cat /var/qmail/control/tlsclientciphers 
DEFAULT:!DH

I'm a bit afraid, however, that this might cause TLS problems with other target servers.

Reply | Permalink

Key too small – Workaround

Roberto Puzzanghera Martin Sluka October 1, 2022 12:35

Ok, thanks for your hint. Let us know if this causes problems with other servers

Reply | Permalink

Key too small

Roberto Puzzanghera Martin Sluka October 1, 2022 09:40

I didn't checked, but I think tls won't work if you disable SSL and leave active only TLS-1.x in your openssl configuration.

Reply | Permalink

Key too small

Anonymous Roberto Puzzanghera March 22, 2021 07:33

OpenSSL 1.1.1d 10 Sep 2019

Reply | Permalink

Error in qmail recompiling

Andy_GC December 18, 2020 18:11

Hi,

I'm using Debian 10.7.0-amd64. Installation followed step-by-step with your directions.

During last recompiling (chkuser options included) I've got such errors

./compile chkuser.c
In file included from chkuser.c:43:
chkuser_settings.h:54:1: error: unknown type name ‘define’
define CHKUSER_STARTING_VARIABLE "CHKUSER_START"
^~~~~~
chkuser_settings.h:54:34: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before string constant
define CHKUSER_STARTING_VARIABLE "CHKUSER_START"

When chkuser all variables commented, recompilling qmail without any errors.

Reply | Permalink

Error in qmail recompiling

Roberto Puzzanghera Andy_GC December 18, 2020 18:14

please post your chkuser_settings.h somewhere (not here, 'cause it's too long), so that I can check the syntax

Reply | Permalink

Error in qmail recompiling

Andy_GC Roberto Puzzanghera December 18, 2020 19:44

I don't see my reply with link to my chkuser_settings.h so here post the part that generate errors

/*
* Uncomment the following line if you want chkuser to work depending on a VARIABLE setting
* VALUE HERE DEFINED is the name of the variable
* Values admitted inside the variable: NONE | ALWAYS | DOMAIN
* NONE = chkuser will not work
* ALWAYS = chkuser will work always
* DOMAIN = chkuser will work depending by single domain settings
* CHKUSER_STARTING_VARIABLE cannot be defined together with CHKUSER_ALWAYS_ON
* if CHKUSER_STARTING_VARIABLE is defined, and no variable or no value is set, then chkuser is disabled
*/
define CHKUSER_STARTING_VARIABLE "CHKUSER_START"

Reply | Permalink

Error in qmail recompiling

Roberto Puzzanghera Andy_GC December 18, 2020 20:39

You should not delete that hash # which goes before define, because in C language it's not intended as a character for comments. So it will be

#define CHKUSER_STARTING_VARIABLE "CHKUSER_START"

If you want to comment out a line, do like this

/* #define CHKUSER_STARTING_VARIABLE "CHKUSER_START" */

Reply | Permalink

Error in qmail recompiling

Andy_GC Roberto Puzzanghera December 19, 2020 09:32

Thx very much.

I don't know C language, in bash # is a comment so my misunderstunding.

Reply | Permalink

Compilation error qmail with path and vpopmail

Bodan December 3, 2020 10:47

Hi,

I have problem with compiling vpopmail and qmail with your patchset.
I can not compile qmail with chkuser because he required vpopmail:

./compile chkuser.c
chkuser.c:38:10: fatal error: vpopmail.h: No such file or directory
38 | #include "vpopmail.h"
| ^~~~~~~~~~~~
compilation terminated.
make: *** [Makefile:334: chkuser.o] Error 1

I can not compile vpopmail because he reqired qmail:

configure: error: Unable to find your qmail-newu file, specify --enable-qmail-newu=/full/path/to/qmail-newu

Reply | Permalink

Compilation error qmail with path and vpopmail

Roberto Puzzanghera Bodan December 3, 2020 14:12

Please take the time needed to read these pages.

You must compile vanilla qmail, not the patched one, and then compile vpopmail on top of it. Then patch and  recompile

Reply | Permalink

Last pacth fail to compile

Ruben October 26, 2020 18:34

Hi Roberto.

I'm using your directions to build some qmail servers. Pretty good job, sure.

Now I'm trying to update one of the servers, and receive a compilation error.  I only have modified the chkuser_settings.h uncommenting the setting that you have noted.  I was using the patch from 26-Aug-2018 before without those modification to this file, just apply patch and compile. My system is a Centos 7.5.1804.

./compile chkuser.c
In file included from chkuser.c:43:0:
chkuser_settings.h:306:1: error: nombre de tipo ‘define’ desconocido
define CHKUSER_RCPT_MX
^
chkuser_settings.h:313:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘define’
define CHKUSER_SENDER_FORMAT
^
chkuser_settings.h:313:1: error: nombre de tipo ‘define’ desconocido
make: *** [chkuser.o] Error 1

Reply | Permalink

Last pacth fail to compile

Roberto Puzzanghera Ruben October 26, 2020 19:12

Hi Ruben, can you post the content of line 306?

Reply | Permalink

please take this into consideration related to qmail vulnerabilities

C July 27, 2020 00:15

I am a qmail fan and i like your website ... used it to install qmailservers several times

please take this into consideration add the pach in your bundle if possible: https://cxsecurity.com/issue/WLB-2020050189

Thanks in advance

Reply | Permalink

please take this into consideration related to qmail vulnerabilities

Roberto Puzzanghera C July 27, 2020 13:15

Thank you. Patch added

Reply | Permalink

Only Single E-mail Delivered

kittonian June 16, 2020 19:55

I ran across a situation I did not know existed until yesterday when I was building an e-mail webapp and I'm hoping you can help explain and/or solve this.

When I send an e-mail to two aliases that both resolve to the same user account, only a single message gets delivered.

For example:

To: foo@bar.com

CC: foo2@bar.com

Both of these addresses are .qmail-foo and .qmail-foo2 inside the bar.com domain directory. Inside these files is the same real user's e-mail address so that they are forwarding accounts only.

If I send that e-mail to both of those aliases, only the latter gets delivered (i.e. the headers show that it was delivered to foo2@bar.com, even though qmail logs that it should be sending two e-mails and both the To and Cc headers are present).

If I change the message to send to foo@bar.com and bar@yahoo.com everything gets delivered properly. I read about someone else seeing the same thing with EXIM and while I'm sure it's a cool feature to limit bandwidth, it cause me hours of trying to nail down a problem with my code that didn't exist. So, I'd love to be able to disable this feature if possible. Thanks!

Reply | Permalink

Only Single E-mail Delivered

kittonian kittonian June 16, 2020 21:24

Never mind. This was traced out and qmail is working just fine, as is Vpopmail. It appears that Apple Mail is automatically deleting duplicate messages delivered to the same inbox.

Reply | Permalink

rcptcount in qmail-smtpd.c

Alexandre Fonceca April 24, 2020 22:28

I had some customers that create several emails in offline mode and when they connect, their outlook starts sending the emails saved in the outbox but some times gives the maxrcpt error (like when the mail has more rcpt to than "control/maxrcpt").

I noted that Outlook sends all emails sequentially, in a single connection, giving a rset after each message sending. But rcptcount is not reset.

to get around this, I had to add:

rcptcount = 0;

within the void smtp_rset function in qmail-smtpd.c

this solved the problem, so the maxrcpto error only occurs if you exceed the limit "control/maxrcpt" in the same email, but not in multiple messages sequentially.

regards,

void smtp_rset(arg) char *arg;
{
seenmail = 0; /* seenauth = 0; RFC 5321: retain authentication */
mailfrom.len = 0; rcptto.len = 0;
rcptcount = 0; // add by me
out("250 flushed\r\n");
}

Reply | Permalink

rcptcount in qmail-smtpd.c

Roberto Puzzanghera Alexandre Fonceca April 25, 2020 14:43

Thanks for the advise, I've updated my patch.

After speaking with Luca Franceschini, my italian friend who authored qlogenvelope and heavily modified the qmail-smtpd stuff, I patched as follows

void smtp_rset(arg) char *arg;
{
seenmail = 0; /* seenauth = 0; RFC 5321: retain authentication */
mailfrom.len = 0; rcptto.len = 0;
+rcptcount = 0;
+envelopepos = 1;
out("250 flushed\r\n");
}

Luca suggested also to add envelopepos = 1 just to set qlogenvelope as we are after an HELO/EHLO. 

It's not clear WHEN outlook is going to RSET the session, hopefully not after the data has been sent, in that case we should also verify that the total size of the message is reset as well, not to exceed the 'datalimit' for multiple messages. 

Reply | Permalink

Chkuser configuration

kittonian February 15, 2020 20:01

I am using your previous patch (Dec 8, 2019) and chkuser and vpopmail are playing nicely. I am not using Mysql with vpopmail, just file based.

When I installed your latest patch (Jan 11, 2020) I could send e-mails out but could not receive anything. All messages failed back to the sender with a failure notice stating "sorry, no mailbox here by that name (chkuser)"

I stopped all qmail services and installed the previous version I kept as a backup, just in case I had issues with the new patch, and everything is back and working.

So, it would be great to get this resolved.

That being said, I am having a major issue with how qmail is processing e-mails prior to sending through SpamAssassin. This is an old system and I am using Qmail-Scanner to connect SA and Qmail. It works just fine, but Qmail is apparently stripping out certain portions of the e-mail because two things are occurring:

1. None of my whitelist_from_rcvd or whitelist_auth lines work.

We tested this against a postfix system and used the entire text of the e-mail against SpamAssassin on this server, and sure enough whitelisting worked as it should. DKIM headers are missing and who knows what else.

2. Every e-mail gets tagged with no rDNS, even though obviously Yahoo, Gmail, etc. all have correct PTR entries for their domain names. Again, when the same e-mail from postfix was tested on this server, SA had no issues finding the rDNS for the sender's domain.

Thanks!

Reply | Permalink

Chkuser configuration

Roberto Puzzanghera kittonian February 15, 2020 20:42

This is strange as the latest modifications did not touch qmail-smtpd.c, where chkuser acts and concerns only ssl (diff here). Can you post your run and tcp.smtp files?

Concerning the qmail-scanner issue, I replaced it with simscan ages ago and I don't even remember how it works, I'm sorry.

Reply | Permalink

Chkuser configuration

kittonian Roberto Puzzanghera February 15, 2020 22:11

The good news is that I finally solved my whitelisting and rdns issue by removing the -H flag from my /service/qmail-smtpd/run file (i.e. /usr/bin/tcpserver -v -R -l "$LOCAL"). That re-enabled dns lookups and everything started working properly again on that front. The other issue with chkuser is still a problem of course so I'm using your previous patch as mentioned above.

This is my /service/qmail-smtpd run file

#!/bin/sh

QMAILDUID=`id -u qmaild`
NOFILESGID=`id -g qmaild`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SOFTLIMIT=`cat /var/qmail/control/softlimit`
LOCAL=`head -1 /var/qmail/control/me`

# This enables greetdelay for qmail-smtpd
export SMTPD_GREETDELAY=20
export DROP_PRE_GREET=1

# This enables chkuser
export CHKUSER_START=ALWAYS

# DKIM - SURBL configuration
# DKIMQUEUE and SURBLQUEUE are front-ends of qmail-queue
export SURBL=1 # Comment out to disable SURBL filtering
export QMAILQUEUE=/var/qmail/bin/surblqueue # executes surblfilter
export SURBLQUEUE=/var/qmail/bin/qmail-dkim # executes qmail-dkim afer sublfilter
export DKIMQUEUE=/var/qmail/bin/simscan # simscan is executed after qmail-dkim
# DKIM verification. Use carefully 
#export DKIMVERIFY="FGHKLMNOQRTVWjp"
# This is to avoid verification of outgoing messages
export RELAYCLIENT_NODKIMVERIFY=1

# This turns off TLS on port 25
export DISABLETLS="1"

# Requires that authenticated user and 'mail from' are identical
#export FORCEAUTHMAILFROM="1"

# rcptcheck-overlimit. Limits the number of emails sent by relayclients
#export RCPTCHECK=/var/qmail/bin/rcptcheck-overlimit.sh
#export RCPTCHECKRELAYCLIENT="1"

# This enables simscan debug
#export SIMSCAN_DEBUG=4

exec /usr/local/bin/softlimit -m "$SOFTLIMIT" \
/usr/bin/tcpserver -v -R -l "$LOCAL" \
-x tcp.cdb -c "$MAXSMTPD" \
-u "$QMAILDUID" -g "$NOFILESGID" 0 25 \
/var/qmail/bin/qmail-smtpd \
/home/vpopmail/bin/vchkpw /bin/tru 2>&1

This is my /service/qmail-smtpd/tcp file

# rules for qmail-smtpd see tcprules(1)
127.:allow,RELAYCLIENT="",QS_SPAMASSASSIN="",QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue"
:allow,QS_SPAMASSASSIN="",QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue"
:allow,DKVERIFY="DEGIJKfh,CGHIJMQRkl",AUTH_UNSET_DKVERIFY=""

Reply | Permalink

Chkuser configuration

Roberto Puzzanghera kittonian February 15, 2020 22:21

you should run qmail-smtpd as vpopmail, not qmaild

Secondly, assigning QMAILQUEUE to qmail-scanner in your tcp.smtp certainly prevents dkim to sign your outgoing mails.

Reply | Permalink

Chkuser configuration

Anonymous Roberto Puzzanghera February 15, 2020 22:28

I use a qmail-remote wrapper script so that my outgoing messages are signed, which works perfectly.

Not sure about running as vpopmail as your previous patch works just fine. It's only the new patch that seems to break chkuser against vpopmail.

Reply | Permalink

Chkuser configuration

Roberto Puzzanghera Anonymous February 16, 2020 12:27

So how can chkuser check users' existence without vpopmail priviledges?

I guess that in your previous installation you enabled CHKUSER_ENABLE_UIDGID before compiling, in order to run qmail-smtpd with a user diffrerent from vpopmail (look here).

Reply | Permalink

Chkuser configuration

Anonymous Roberto Puzzanghera February 16, 2020 14:51

Nope. I compared the previous chkuser_settings.h with the new one and the new one has quite a bit more code in it. However, the exact same lines were commented out in both.

Here are the variables that are commented out in both:

ALWAYS_ON
ENABLE_UIDGID
SPECIFIC_BOUNCING
VGET_REAL_DOMAIN
ENABLE_VALIAS
ENABLE_USERS_EXTENSIONS
ENABLE_MAILMAN_LISTS
ACCEPT_NULL_SENDER
ENABLE_NULL_SENDER_WITH_TCPREMOTEHOST
EXTRA_MUSTAUTH_VARIABLE

Reply | Permalink

Chkuser configuration

kittonian Anonymous June 16, 2020 20:53

My apologies that I did not come back and post the solution to this issue, which btw, is still present in your latest patch.

Here's how to solve it:

nano chkuser_settings.h

Look for the line
#define CHKUSER_STARTING_VARIABLE "CHKUSER_START"

Comment out this line by:

/*
#define CHKUSER_STARTING_VARIABLE "CHKUSER_START"
*/

Reply | Permalink

Chkuser configuration

Roberto Puzzanghera kittonian June 16, 2020 21:30

Not defining CHKUSER_STARTING_VARIABLE completely disables chkuser, unless you have CHKUSER_ALWAYS_ON defined. I don't think this is what we want

Reply | Permalink

Chkuser configuration

kittonian Roberto Puzzanghera June 17, 2020 21:48

Makes sense, however this is the only way I can get qmail to compile and install with your latest patches, and everything works just fine for me. If chkuser was disabled, wouldn't vpopmail fail to send and deliver messages?

Reply | Permalink

Chkuser configuration

Roberto Puzzanghera kittonian June 17, 2020 22:32

chkuser is disabled in this way, and even though qmail/vpopmail can work without it you'll get an increase of spam. chkuser and vpopmail can work together with my configuration, which is the same suggested by the author, i.e. running qmail as vpopmail

Reply | Permalink

qmail-send concurrency issue

Gabriel Torres January 7, 2020 11:26

Hi Roberto,

We have an old issue here that we were never able to understand or fix.

We have concurrencyremote set to 120

When sending out a newsletter to 400,000 subscribers, the number of concurrent connections always drops to less than 10.

Right now we are sending our newsletter and here is what we have:

@400000005e146a3a2ef8509c status: local 0/40 remote 7/120 suppl0 0/1 suppl1 2/5 suppl2 0/1

See how we only have 7 concurrent connections going on.

But if we use qmailctl to check the queue, we still have a huge number of queued emails:

messages in queue: 135384
messages in queue but not yet preprocessed: 135305

I was never able to understand what causes this behavior of qmail-remote not going anywhere close to the concurrencyremove limit. I did a Google search several times, found other people with the same issue, but no solution or any hint of how to debug this or what might be causing it.

If you have any pointers on how to start debugging this I'd appreciate it.

Thank you in advance!

Reply | Permalink

qmail-send concurrency issue

Roberto Puzzanghera Gabriel Torres January 8, 2020 17:43

Hi Gabriel,

I don't know exactly what can be the cause, but the CHANNELS file (CAVEATS) reminds us that <<concurrencyremote, concurrencysupplX, etc are each subject to the hard limit in conf-spawn, which in turn is bounded by per-process limits>>... anyway your concurrency seems to be very low.

Reply | Permalink

chkuser

ChangHo.Na November 30, 2019 03:21

Hi.

MariaDB log:

[Warning] Aborted connection 58 to db: 'vpopmail' user: 'vpopmail' host: 'localhost' (Got an error reading communication packets)
# The client connected successfully but terminated improperly (and may relate to not closing the connection properly)

chkuser_settings.h:

#define CHKUSER_DB_CLEANUP

chkuser.c:

void chkuser_cleanup (int exit_value) {
#if defined CHKUSER_DB_CLEANUP
    vclose (); /* can't call function */
#endif
    _exit (exit_value);
}

Modify:

#define CHKUSER_DB_CLEANUP -> #define CHKUSER_DB_CLEANUP 1

or

#if defined CHKUSER_DB_CLEANUP -> #ifdef CHKUSER_DB_CLEANUP

Thank you.

Reply | Permalink

chkuser

Roberto Puzzanghera ChangHo.Na November 30, 2019 20:29

Thanks for your comment.

I have CHKUSER_DB_CLEANUP defined as well, but I've never seen such an error. How can I reproduce it?

Reply | Permalink

chkuser

ChangHo.Na Roberto Puzzanghera December 2, 2019 01:38

chkuser.h

#ifdef TLS_H
#undef _exit
#define _exit(value) { if (ssl) ssl_free(ssl); chkuser_cleanup(value); }
#else
#define _exit(value) chkuser_cleanup(value) /* can't override _exit() function */
#endif

------------------

My Test

chkuser.c

add: #include

void chkuser_cleanup (int exit_value) {
    syslog(LOG_NOTICE, "[NOTICE: %s][__LINE__ : %d] %s", __FILE__, __LINE__, __FUNCTION__);

...

}

check: /var/log/message

result: nothing

---------------------

Below is executed correctly.

int chkuser_realrcpt (stralloc *sender, stralloc *rcpt) {
...
 retstat = realrcpt (sender, rcpt);
#if defined CHKUSER_DB_CLEANUP
 syslog(LOG_NOTICE, "[NOTICE: %s][__LINE__ : %d] %s", __FILE__, __LINE__, __FUNCTION__);
 vclose();
#endif

switch (retstat) {

...

Did I test it?

Thank you.

Reply | Permalink

chkuser

Roberto Puzzanghera ChangHo.Na December 3, 2019 12:18

while compiling I get

chkuser.c:1049:9: error: 'LOG_NOTICE' undeclared (first use in this function)
 syslog(LOG_NOTICE, "[NOTICE: %s][__LINE__ : %d] %s", __FILE__, __LINE__, __FUNCTION__);

Reply | Permalink

chkuser

ChangHo.Na Roberto Puzzanghera December 3, 2019 16:56

add #include <syslog.h>

Reply | Permalink

chkuser

Roberto Puzzanghera ChangHo.Na December 3, 2019 18:51

I can confirm that the code inside the chkuser_cleanup function is not executed. But I don't get any mariadb error

Reply | Permalink

chkuser

ChangHo.Na Roberto Puzzanghera December 7, 2019 22:10

Hi.

I found the cause of the problem.

tls.h

#define _exit ss_exit

chkuser.h

/* Called before tls.h is called. */
#ifdef TLS_H
#undef _exit
...
#endif

Solutions:

qmail-smtpd.c line 77 #ifdef block:

#ifdef TLS
...
#endif

move to before  this line.

#include "chkuser.h"

Now works correctly.

Thank you.

Reply | Permalink

chkuser

Roberto Puzzanghera ChangHo.Na December 8, 2019 08:46

Thank you. Patch updated

Reply | Permalink

chkuser

ChangHo.Na Roberto Puzzanghera December 4, 2019 00:34

MariaDB 10.x version: log warning messages.

MariaDB version 5.X : warning messages are not logged.

Anyway, I think vclose() function should be executed

Thank You.

Reply | Permalink

chkuser

ChangHo.Na Roberto Puzzanghera December 1, 2019 14:43

Sorry ^^

Maybe it's a different matter.

I will write again if I find the cause.

Thank you.

Reply | Permalink

qlogenvelope: reason=authnotmailfrom

nic November 20, 2019 03:31

Hi Roberto,

Can you tell me what qlogenvelope: result=rejected code=503 reason=authnotmailfrom detail means?

Reply | Permalink

qlogenvelope: reason=authnotmailfrom

Roberto Puzzanghera nic November 20, 2019 14:48

It means that the user who did the authentication is different from the one in the mailfrom field. This is because you have

export FORCEAUTHMAILFROM=1

in your run file

Reply | Permalink

qlogenvelope: reason=authnotmailfrom

Anonymous Roberto Puzzanghera November 20, 2019 15:14

Thank you, Roberto

Reply | Permalink

Bug with Received: line

Gabriel Torres July 6, 2019 06:33

Hi Roberto,

I found a bug caused by your patch. The header from received emails are, for some reason, filling with '0' where there should be the server name. Let me explain.

In the header of receiving emails, I see:

Received: from unknown (HELO somedomain.com) (a.b.c.d)
 by 0 with SMTP; 5 Jul 2019 19:08:08 -0300

Note the "by 0" part. It should read:

Received: from unknown (HELO somedomain.com) (a.b.c.d)
 by mail.ourdomain.com with SMTP; 5 Jul 2019 19:08:08 -0300

Digging this further, the function that fills that part is received() found in received.c. The variable called "local" (which is a copy of the TCPLOCALHOST variable) is somehow being deleted or misconfigured somewhere.

I made a temporary fix by hardcoding our FQDN there, but obviously we need to investigate this further to find out where exactly this variable is being transformed into a zero.

I hope you can investigate this. I will try to take a look at this myself later, even though I am not too familiar with the C language.

Thank you in advance.

Cheers,

Gabriel.

Reply | Permalink

Bug with Received: line

Roberto Puzzanghera Gabriel Torres July 7, 2019 16:01

got it! 0 was the value of TCPLOCALHOST (in this case, set using the -l option to tcpserver). For example:

 /usr/local/bin/tcpserver -v -H -R -l "yourdomain.tld"

Reply | Permalink

Bug with Received: line

Roberto Puzzanghera Roberto Puzzanghera July 7, 2019 18:31

it's worth to mention that djb's tcpserver documentation suggests to use "-l 0" as a choice

-l localname: Do not look up the local host name in DNS; use localname for the environment variable $TCPLOCALHOST. A common choice for localname is 0. To avoid loops, you must use this option for servers on TCP port 53.

Btw, I modified my documentation passing the content of control/me as suggested by life with qmail

Reply | Permalink

Bug with Received: line

Gabriel Torres Roberto Puzzanghera July 10, 2019 20:35

Perfect. This makes much more sense than using using 0. By using 0, SpamCop isn't able to parse the email headers, so reporting spam to SpamCop with spamassassin -r doesn't work. Please take a look here to fully understand how I found out that this Received: line was malformed: http://forum.spamcop.net/topic/39031-resolvednbspmailhost-configuration-problem-identified-internal-ip-as-source/

Reply | Permalink

Bug with Received: line

kittonian Gabriel Torres June 16, 2020 18:48

I had this exact same issue and apparently it has to do directly with the -H option in the tcpserver line. That is what prevents reverse DNS lookups. I took out -H and all is well (at least I think so, lol).

Reply | Permalink

Bug with Received: line

Roberto Puzzanghera kittonian June 17, 2020 17:33

Thanks for the hint. I modified my configuration accordingly

Reply | Permalink

Bug with Received: line

Gabriel Torres kittonian June 16, 2020 22:41

Many thanks, this tip of removing the -H was really helpful!

Before:

Received: from unknown (HELO mail-lj1-f179.google.com) (209.85.208.179)

After:

Received: from mail-lj1-f174.google.com (209.85.208.174)

Reply | Permalink

Bug with Received: line

Roberto Puzzanghera Gabriel Torres July 6, 2019 09:48

I think this is because the server IP is hidden by this patch (as you know 0 stands for localhost) https://notes.sagredo.eu/files/qmail/patches/qmail-hide-ip-headers.patch

Actually we can get rid of this patch as explained here https://lists.gt.net/qmail/users/126552 

Try to revert it and please let me know.

PS did you have the time to play with my new testing patch with the qmail-channels? look here

Reply | Permalink

Bug with Received: line

Roberto Puzzanghera Roberto Puzzanghera July 6, 2019 13:07

sorry, that patch has nothing to do with it... I'll do some checks and let you know

Reply | Permalink

Bug with Received: line

Gabriel Torres Roberto Puzzanghera July 6, 2019 15:53

Hi,

Forgot to mention that the same issue happens in the SPF line as follows. I also had to manually edit and hardcode our server name in spf.c

It is showing:

Received-SPF: none (0: domain at email.invisionpower.com does not designate permitted sender hosts)

Whereas it should be:

Received-SPF: none (mail.ourdomain.com: domain at email.invisionpower.com does not designate permitted sender hosts)

Regarding the other patch, I need some time when our server isn't sending our newsletters to try it out... :) I will probably have the time to do so during this coming week! I will let you know and appreciate your effort!

Gabriel.

Reply | Permalink

Pay attention to permissions for DKIM signing

Gabriel Torres June 24, 2019 18:51

If your outgoing emails aren't being DKIM-signed, please check permissions of the folder /usr/local/etc/domainkeys/ and below. With me, I had to change ownership manually to qmailr.

"When you create a key for a domain.net it will be stored in the /usr/local/etc/domainkeys/domain.net folder. The folder will be owned by qmailr (the user running qmail-remote) if you sign at qmail-remote level or vpopmail, which is the user who runs qmail-smtpd, if you decide to sign at qmail-smtpd level. My script changes the owner to qmailr by default"

Reply | Permalink

softlimit error message

Gabriel Torres June 19, 2019 04:38

If you get the following error at /var/log/qmail/smtpd/current

/var/qmail/bin/qmail-smtpd: error while loading shared libraries: libdl.so.2: failed to map segment from shared object

Simply increase the value present in /var/qmail/control/softlimit

Here I added 64000000 and is working fine

Reply | Permalink

qmail-channels

Gabriel Torres June 18, 2019 17:10

Hi Roberto,

Try adding this patch: http://www.thesmbexchange.com/eng/qmail-channels_patch.html

This is something we need to slow down delivery to certain ISPs, so emails will be correctly delivered. (We run a weekly newsletter.)

Cheers.

Reply | Permalink

qmail-channels

Roberto Puzzanghera Gabriel Torres June 18, 2019 19:44

nice patch, but... I don't have the time to accomplish personal requests...

Reply | Permalink

qmail-channels

Gabriel Torres Roberto Puzzanghera June 18, 2019 23:13

Hi Roberto,

Maybe this will help other people as well? Anyway, I made a donation to you earlier today via Paypal. Keep up the nice job of keeping this website up-to-date.

Cheers,

Gabe.

Reply | Permalink

qmail-channels

Roberto Puzzanghera Gabriel Torres June 19, 2019 08:13

Thank you very much for your donation and contributions. I'll take a deeper look at this patch, but it seems to me that it's too much invasive, as it completely changes the logic of the qmail queue...

Reply | Permalink

qmail-channels

Gabriel Torres Roberto Puzzanghera June 25, 2019 20:19

The thing is, we run a newsletter with 400,000 subscribers, and some email providers complain that we are sending too many emails at the same time. For example:

2019-06-24 19:33:47.462279500 delivery 34301: deferral: 200.147.36.13_does_not_like_recipient./Remote_host_said:_450_4.7.1_<xxxxxxxxxx@bol.com.br>:_Recipient_address_rejected:_MX-AFL-02_-_Too_many_messages,_try_again_later./Giving_up_on_200.147.36.13./

So it would be great to have a way to limit the number of emails sent out based on the destination domain.

It doesn't need to be this specific patch, just something to think about.

Thanks!

Reply | Permalink

qmail-channels

Roberto Puzzanghera Gabriel Torres June 26, 2019 18:29

you have a testing patch embedding qmail-channels here. Can you test the channels functionality please?

I configured it not to create additional channels, so you have to edit conf-channels and increase the number of qmail-rspawn processes to be created (it was 22 before my adjustment)

PS thanks for helping me improve this guide

Reply | Permalink

qmail-channels

Gabriel Torres Roberto Puzzanghera July 10, 2019 21:10

Hi Roberto,

I finally had the time to install this patch and configure qmail-channels. Now I need to wait until we send out our next newsletter to see if qmail is separating emails in separate queues based on the destination domain. I should have a detailed analysis for us within the next couple of days. Stay tuned!

Many thanks for integrating this patch for me! :)

After my original message, Yahoo is now also refusing our newsletters because we are sending too many emails at the same time:

@400000005d24ae9631f30a6c delivery 417355: deferral: Connected_to_67.195.228.94_but_sender_was_rejected./Remote_host_said:_421_4.7.0_[TSS04]_Messages_from_XXXXXXXX_temporarily_deferred_due_to_user_complaints_-_4.16.55.1;_see_https://help.yahoo.com/kb/postmaster/SLN3434.html/

So I have high hopes that this patch will fix this issue.

Cheers,

Gabriel.

Reply | Permalink

qmail-channels

miz Gabriel Torres July 11, 2019 14:22

Hello Gabriel,

delivering mails to yahoo has always been difficult. I'm not familiiar with the qmail channel patch, but you have to limit the number of mails per second in order to avoid the block.

In postfix this can be achieved in the following way: https://serverfault.com/questions/56719/postfix-stagger-rate-limit-outbound-mail

Hope this might help !

Reply | Permalink

qmail-channels

Roberto Puzzanghera miz July 11, 2019 15:21

It seems that yahoo accepts a maximum of 20 msg per connection, so this patch should do the trick... look here https://help.yahoo.com/kb/SLN3433.html

Reply | Permalink

qmail-channels

Gabriel Torres Roberto Puzzanghera July 12, 2019 15:33

Hi Roberto,

The qmail-channels patch you integrated in your patch worked like a charm to fix the yahoo issue described above. We could use the postfix solution you linked above, but it would only work in our webserver (where postfix is used to accept and send emails to our email server, which is running qmail), whereas with qmail-channels we have the solution valid for all emails sources in our setup, which is best.

The configuration of qmail-channels is quite simple. After applying the patch, and before compiling qmail, we need to edit conf-channels and add the total number of queues we want. The default is 2, meaning local and remote. As I wanted two additional queues (two group of domains we wanted to limit the delivery rate), I changed that to 4 and compiled qmail.

Then, we need to add the configuration files at /var/qmail/control:

suppls0 - the list of domains for this group. In my case:

bol.com.br

zipmail.com.br

suppls1 - the list of domains for this group. In my case:

yahoo.com
ymail.com
yahoo.co.uk
yahoo.com.br
yahoo.fr
yahoo.de
yahoo.es
yahoo.cn
yahoo.it
yahoo.co.jp
yahoo.com.au
yahoo.in
yahoo.com.ar
yahoo.com.mx
yahoo.no
yahoo.ie
yahoo.com.es
yahoo.ca
yahoo.co.nz
yahoo.gr
yahoo.com.vn
yahoogrupos.com.br
yahoo.se
yahoo.dk
yahoo.ro
yahoo.co.in
yahoomail.com
yahoo.co.id
yahoo.com.sg
yahoo.com.ph

concurrencysuppl0 - with the number of simultaneous outgoing emails for the domain group "0"

concurrencysuppl1 - with the number of simultaneous outgoing emails for the domain group "1"

Restarted qmail and voilá!

Thank you for all your help. Our qmail server is now "perfect".

Cheers.

Reply | Permalink

qmail-channels

Roberto Puzzanghera Gabriel Torres July 12, 2019 15:58

Great! Can you share your control/concurrencysuppl* files please? Suitable concurrency values could be useful to someone else...

Reply | Permalink

qmail-channels

Gabriel Torres Roberto Puzzanghera July 13, 2019 14:59

Hi Roberto,

I am still testing the numbers. I have concurrencysuppl0 with 1 and concurrencysuppl1 with 10 right now. According to what the other user posted above, we could increase the Yahoo queue up to 20.

Another note: I had to increase the softlimit configuration. Otherwise I would get the infamous "qq temporary problem" at /var/log/qmail/smtpd/current

Cheers

Reply | Permalink

ChangHo.Na April 25, 2019 06:09

Hi,

Latest stable combined patch for netqmail-1.06 v. 2019.04.09

My OpenSSL  Version: 1.0.2k

Error send mail.

Modify file: qmail-smtpd.c

before:

2331 #if OPENSSL_VERSION_NUMBER >= 0x10100000L 
2332 /* support ECDH */
2333 SSL_CTX_set_ecdh_auto(ctx,1);
2334 #endif

after:

OPENSSL_VERSION_NUMBER >= 0x10002000L

Please check!

Reply | Permalink

Roberto Puzzanghera ChangHo.Na April 25, 2019 15:43

Thank you!!! Corrected

Reply | Permalink

hardcoded llinks to /home/vpopmail

GoofY April 10, 2019 02:56

I've installled vpopmail to a different folder (in my case /var/vpopmail).

While running make in the netqmail dir I encountered an error in chkuser.c, it couldn't find the vpopmail.h file, I edited this to /var/vpopmail/include, which worked for that part.

But after continueing I got more errors:

./load qmail-smtpd chkuser.o dns.o rcpthosts.o commands.o timeoutread.o \
strerr.a wildmat.o qregex.o \
timeoutwrite.o ip.o ipme.o ipalloc.o strsalloc.o control.o \
tls.o ssl_timeoutio.o ndelay.a -L/usr/local/ssl/lib -lssl -lcrypto \
constmap.o received.o date822fmt.o now.o qmail.o spf.o cdb.a \
fd.a wait.a datetime.a getln.a open.a sig.a case.a env.a stralloc.a \
alloc.a substdio.a error.a strerr.a str.a fs.a auto_qmail.o base64.o policy.o \
`head -1 /home/vpopmail/etc/lib_deps` `cat dns.lib` \
`cat socket.lib`
head: cannot open '/home/vpopmail/etc/lib_deps' for reading: No such file or directory
chkuser.o: In function `realrcpt':
/usr/local/src/netqmail-1.06/chkuser.c:746: undefined reference to `vget_assign'
/usr/local/src/netqmail-1.06/chkuser.c:875: undefined reference to `vauth_getpw'
/usr/local/src/netqmail-1.06/chkuser.c:906: undefined reference to `format_maildirquota'
/usr/local/src/netqmail-1.06/chkuser.c:906: undefined reference to `vmaildir_readquota'
chkuser.o: In function `chkuser_cleanup':
/usr/local/src/netqmail-1.06/chkuser.c:462: undefined reference to `vclose'
collect2: error: ld returned 1 exit status
Makefile:1757: recipe for target 'qmail-smtpd' failed
make: *** [qmail-smtpd] Error 1

So I ended up creating a symlink (ln -s /var/vpopmail /home) , after that  'make' succeeded.

PS THNX for ur effort with this tutorial/toaster.

Reply | Permalink

hardcoded llinks to /home/vpopmail

Roberto Puzzanghera GoofY April 10, 2019 07:36

Have you tried to modify this line on top of the Makefile?

VPOPMAIL_HOME=/home/vpopmail

Reply | Permalink

Still require libdomainkeys-0.69.diff

Tony Fung April 8, 2019 09:10

Hi,

I just compile libdomainkeys with patch "libdomainkeys-openssl-1.1.patch" but result with underneath error when running make:

./libdomainkeys.a(dns_txt.o): In function `dns_text':
dns_txt.c:(.text+0x25): undefined reference to `__res_query'
dns_txt.c:(.text+0xa1): undefined reference to `__dn_expand'
dns_txt.c:(.text+0xfc): undefined reference to `__dn_expand'
collect2: error: ld returned 1 exit status
make: *** [dktest] Error 1

When apply the missing patch "libdomainkeys-0.69.diff" and compile again, it did success.

Is the patch "libdomainkeys-openssl-1.1.patch" not completed or mistake to remove the patch "libdomainkeys-0.69.diff" from download and step?

Reply | Permalink

Still require libdomainkeys-0.69.diff

Roberto Puzzanghera Tony Fung April 8, 2019 12:46

Yes, we have to apply that patch as well. Thanks for letting me know

Reply | Permalink

Cant compile libdomainkeys

Madzel February 19, 2019 08:45

gcc-6.1 -DBIND_8_COMPAT -O2 -o makeheader makeheader.c
./makeheader domainkeys.h
gcc-6.1 -DBIND_8_COMPAT -O2 -c dktest.c -I.
gcc-6.1 -DBIND_8_COMPAT -O2 -c domainkeys.c -I.
domainkeys.c:123:14: Fehler: Feld »mdctx« hat unvollständigen Typen
 EVP_MD_CTX mdctx; /* the hash */
 ^~~~~
domainkeys.c: In Funktion »dkheaders«:
domainkeys.c:1285:5: Warnung: Typkonvertierung in Zeiger von Ganzzahl anderer Breite [-Wint-to-pointer-cast]
 (void *)dk_headers(dk, dk->headers);
 ^
domainkeys.c: In Funktion »dk_free«:
domainkeys.c:2155:3: Warnung: Implizite Deklaration der Funktion »EVP_MD_CTX_cleanup« [-Wimplicit-function-declaration]
 EVP_MD_CTX_cleanup(&dk->mdctx);
 ^~~~~~~~~~~~~~~~~~
domainkeys.c:2162:6: Warnung: »ERR_remove_state« ist veraltet [-Wdeprecated-declarations]
 ERR_remove_state(0);
 ^~~~~~~~~~~~~~~~
In file included from /usr/include/openssl/evp.h:13:0,
 from domainkeys.c:27:
/usr/include/openssl/err.h:260:1: Anmerkung: hier deklariert
 DEPRECATEDIN_1_0_0(void ERR_remove_state(unsigned long pid))
 ^
Makefile:23: recipe for target 'domainkeys.o' failed
make: *** [domainkeys.o] Error 1

Any idea?

Reply | Permalink

Cant compile libdomainkeys

Roberto Puzzanghera Madzel February 19, 2019 08:55

Try to apply the patch linked on top of this page. Let me know if it solves.

Reply | Permalink

Cant compile libdomainkeys

Madzel Roberto Puzzanghera February 19, 2019 10:23

The patch was applied already.

Reply | Permalink

Cant compile libdomainkeys

Roberto Puzzanghera Madzel February 19, 2019 18:47

sorry if I ask... but this is an error which comes when you don't apply this patch https://notes.sagredo.eu/files/qmail/patches//libdomainkeys-openssl-11.patch. Can you confirm that this is the patch you applied?

Reply | Permalink

Cant compile libdomainkeys

Madzel Roberto Puzzanghera February 20, 2019 07:24

 Yes, i used the linked openssl patch. I have all downloaded data deletetd and repeated the whole procedure again:

root@threepwood:~/libdomainkeys# wget https://notes.sagredo.eu/files/qmail/patches/libdomainkeys-openssl-11.patch
--2019-02-20 08:18:47-- https://notes.sagredo.eu/files/qmail/patches/libdomainkeys-openssl-11.patch
Auflösen des Hostnamen »notes.sagredo.eu (notes.sagredo.eu)«... 91.121.144.116
Verbindungsaufbau zu notes.sagredo.eu (notes.sagredo.eu)|91.121.144.116|:443... verbunden.
HTTP-Anforderung gesendet, warte auf Antwort... 200 OK
Länge: 1091 (1,1K) [text/plain]
In »»libdomainkeys-openssl-11.patch«« speichern.

libdomainkeys-openssl-11.patch 100%[==========================================================================================================================================>] 1,07K --.-KB/s in 0s

2019-02-20 08:18:47 (11,8 MB/s) - »»libdomainkeys-openssl-11.patch«« gespeichert [1091/1091]

root@threepwood:~/libdomainkeys# patch < libdomainkeys-openssl-11.patch
patching file domainkeys.c
root@threepwood:~/libdomainkeys# vi Makefile
root@threepwood:~/libdomainkeys# make
gcc-6.1 -DBIND_8_COMPAT -O2 -o makeheader makeheader.c
./makeheader domainkeys.h
gcc-6.1 -DBIND_8_COMPAT -O2 -c dktest.c -I.
gcc-6.1 -DBIND_8_COMPAT -O2 -c domainkeys.c -I.
In file included from domainkeys.c:27:0:
domainkeys.c: In Funktion »dk_sign«:
domainkeys.c:510:16: Warnung: Übergabe des Arguments 1 von »EVP_DigestInit« von inkompatiblem Zeigertyp [-Wincompatible-pointer-types]
 EVP_SignInit(&dk->mdctx, dklib->md);
 ^
/usr/local/include/openssl/evp.h:555:12: Anmerkung: »EVP_MD_CTX * {aka struct evp_md_ctx_st *}« erwartet, aber Argument hat Typ »EVP_MD_CTX ** {aka struct evp_md_ctx_st **}«
 __owur int EVP_DigestInit(EVP_MD_CTX *ctx, const EVP_MD *type);
 ^~~~~~~~~~~~~~
domainkeys.c: In Funktion »dk_verify«:
domainkeys.c:548:18: Warnung: Übergabe des Arguments 1 von »EVP_DigestInit« von inkompatiblem Zeigertyp [-Wincompatible-pointer-types]
 EVP_VerifyInit(&dk->mdctx, dklib->md);
 ^
/usr/local/include/openssl/evp.h:555:12: Anmerkung: »EVP_MD_CTX * {aka struct evp_md_ctx_st *}« erwartet, aber Argument hat Typ »EVP_MD_CTX ** {aka struct evp_md_ctx_st **}«
 __owur int EVP_DigestInit(EVP_MD_CTX *ctx, const EVP_MD *type);
 ^~~~~~~~~~~~~~
domainkeys.c: In Funktion »dkhash«:
domainkeys.c:942:26: Warnung: Übergabe des Arguments 1 von »EVP_DigestUpdate« von inkompatiblem Zeigertyp [-Wincompatible-pointer-types]
 EVP_DigestUpdate(&dk->mdctx, dk->hash_buff, dk->hash_buff_len);
 ^
In file included from domainkeys.c:27:0:
/usr/local/include/openssl/evp.h:546:12: Anmerkung: »EVP_MD_CTX * {aka struct evp_md_ctx_st *}« erwartet, aber Argument hat Typ »EVP_MD_CTX ** {aka struct evp_md_ctx_st **}«
 __owur int EVP_DigestUpdate(EVP_MD_CTX *ctx, const void *d,
 ^~~~~~~~~~~~~~~~
domainkeys.c:968:28: Warnung: Übergabe des Arguments 1 von »EVP_DigestUpdate« von inkompatiblem Zeigertyp [-Wincompatible-pointer-types]
 EVP_DigestUpdate(&dk->mdctx, dk->hash_buff, dk->hash_buff_len);
 ^
In file included from domainkeys.c:27:0:
/usr/local/include/openssl/evp.h:546:12: Anmerkung: »EVP_MD_CTX * {aka struct evp_md_ctx_st *}« erwartet, aber Argument hat Typ »EVP_MD_CTX ** {aka struct evp_md_ctx_st **}«
 __owur int EVP_DigestUpdate(EVP_MD_CTX *ctx, const void *d,
 ^~~~~~~~~~~~~~~~
domainkeys.c:990:24: Warnung: Übergabe des Arguments 1 von »EVP_DigestUpdate« von inkompatiblem Zeigertyp [-Wincompatible-pointer-types]
 EVP_DigestUpdate(&dk->mdctx, dk->hash_buff, dk->hash_buff_len);
 ^
In file included from domainkeys.c:27:0:
/usr/local/include/openssl/evp.h:546:12: Anmerkung: »EVP_MD_CTX * {aka struct evp_md_ctx_st *}« erwartet, aber Argument hat Typ »EVP_MD_CTX ** {aka struct evp_md_ctx_st **}«
 __owur int EVP_DigestUpdate(EVP_MD_CTX *ctx, const void *d,
 ^~~~~~~~~~~~~~~~
domainkeys.c: In Funktion »dkheaders«:
domainkeys.c:1289:5: Warnung: Typkonvertierung in Zeiger von Ganzzahl anderer Breite [-Wint-to-pointer-cast]
 (void *)dk_headers(dk, dk->headers);
 ^
domainkeys.c: In Funktion »dk_end«:
domainkeys.c:1753:22: Warnung: Übergabe des Arguments 1 von »EVP_DigestUpdate« von inkompatiblem Zeigertyp [-Wincompatible-pointer-types]
 EVP_DigestUpdate(&dk->mdctx, dk->hash_buff, dk->hash_buff_len);
 ^
In file included from domainkeys.c:27:0:
/usr/local/include/openssl/evp.h:546:12: Anmerkung: »EVP_MD_CTX * {aka struct evp_md_ctx_st *}« erwartet, aber Argument hat Typ »EVP_MD_CTX ** {aka struct evp_md_ctx_st **}«
 __owur int EVP_DigestUpdate(EVP_MD_CTX *ctx, const void *d,
 ^~~~~~~~~~~~~~~~
domainkeys.c:1956:27: Warnung: Übergabe des Arguments 1 von »EVP_VerifyFinal« von inkompatiblem Zeigertyp [-Wincompatible-pointer-types]
 i = EVP_VerifyFinal(&dk->mdctx, md_value, md_len, publickey);
 ^
In file included from domainkeys.c:27:0:
/usr/local/include/openssl/evp.h:623:12: Anmerkung: »EVP_MD_CTX * {aka struct evp_md_ctx_st *}« erwartet, aber Argument hat Typ »EVP_MD_CTX ** {aka struct evp_md_ctx_st **}«
 __owur int EVP_VerifyFinal(EVP_MD_CTX *ctx, const unsigned char *sigbuf,
 ^~~~~~~~~~~~~~~
domainkeys.c: In Funktion »dk_getsig«:
domainkeys.c:2065:21: Warnung: Übergabe des Arguments 1 von »EVP_SignFinal« von inkompatiblem Zeigertyp [-Wincompatible-pointer-types]
 EVP_SignFinal(&dk->mdctx, sig, &siglen, pkey);
 ^
In file included from domainkeys.c:27:0:
/usr/local/include/openssl/evp.h:616:12: Anmerkung: »EVP_MD_CTX * {aka struct evp_md_ctx_st *}« erwartet, aber Argument hat Typ »EVP_MD_CTX ** {aka struct evp_md_ctx_st **}«
 __owur int EVP_SignFinal(EVP_MD_CTX *ctx, unsigned char *md, unsigned int *s,
 ^~~~~~~~~~~~~
domainkeys.c: In Funktion »dk_free«:
domainkeys.c:2162:19: Warnung: Übergabe des Arguments 1 von »EVP_MD_CTX_free« von inkompatiblem Zeigertyp [-Wincompatible-pointer-types]
 EVP_MD_CTX_free(&dk->mdctx);
 ^
In file included from domainkeys.c:27:0:
/usr/local/include/openssl/evp.h:536:6: Anmerkung: »EVP_MD_CTX * {aka struct evp_md_ctx_st *}« erwartet, aber Argument hat Typ »EVP_MD_CTX ** {aka struct evp_md_ctx_st **}«
 void EVP_MD_CTX_free(EVP_MD_CTX *ctx);
 ^~~~~~~~~~~~~~~
domainkeys.c:2170:6: Warnung: »ERR_remove_state« ist veraltet [-Wdeprecated-declarations]
 ERR_remove_state(0);
 ^~~~~~~~~~~~~~~~
In file included from /usr/local/include/openssl/evp.h:13:0,
 from domainkeys.c:27:
/usr/local/include/openssl/err.h:260:1: Anmerkung: hier deklariert
 DEPRECATEDIN_1_0_0(void ERR_remove_state(unsigned long pid))
 ^
gcc-6.1 -DBIND_8_COMPAT -O2 -c dns_txt.c
gcc-6.1 -DBIND_8_COMPAT -O2 -c -o dktrace.o dktrace.c
rm -f libdomainkeys.a
ar cr libdomainkeys.a domainkeys.o dns_txt.o dktrace.o
ranlib libdomainkeys.a
(if make dnstest >/dev/null 2>&1; then echo -lresolv; else echo ""; fi) >dns.lib
rm -f dnstest
(if make socktest >/dev/null 2>&1; then echo -lsocket -lnsl; else echo ""; fi) >socket.lib
rm -f socktest
gcc-6.1 -DBIND_8_COMPAT -O2 -o dktest dktest.o -L. -ldomainkeys -lcrypto `cat dns.lib` `cat socket.lib`
./libdomainkeys.a(dns_txt.o): In function `dns_text':
dns_txt.c:(.text+0x25): undefined reference to `__res_query'
dns_txt.c:(.text+0xae): undefined reference to `__dn_expand'
dns_txt.c:(.text+0x151): undefined reference to `__dn_expand'
collect2: Fehler: ld gab 1 als Ende-Status zurück
Makefile:10: recipe for target 'dktest' failed
make: *** [dktest] Error 1
root@threepwood:~/libdomainkeys#

Reply | Permalink

Cant compile libdomainkeys

Roberto Puzzanghera Madzel February 27, 2019 08:46

Are you using openssl or libressl?

Reply | Permalink

Cant compile libdomainkeys

Roberto Puzzanghera Madzel February 20, 2019 19:45

I suspect that your compiler is not recognizing your openssl version.

Try to apply this patch, which is specific for openssl-1.1 without any version recognizer https://notes.sagredo.eu/en/qmail-notes-185/patching-qmail-82.html#comment1207

Reply | Permalink

So sad and disapointing :-(

Stumpi February 11, 2019 18:56

 It will not compile with OpenSSL 1.0.2 and above, so Qmail will ever get TLS1.3 support. After more than 12 years of using Qmail it is now time to change to Exim or PostFix, i guess. Sad and disapointing...

Reply | Permalink

So sad and disapointing :-(

Roberto Puzzanghera Stumpi February 19, 2019 20:02

try to compile using the test patches linked on the top of this page, which should solve all the compilation breaks against openssl-1.1

Reply | Permalink

So sad and disapointing :-(

Roberto Puzzanghera Stumpi February 11, 2019 23:02

It compiles with v. 1.0.2 here. I would not say that it will **ever** get tls 1.3 support. I'm confident that someone will solve this at some point. 

Other qmail distributions as s/qmail and indimail are already openssl-1.1 compliant, because they are mainteined by senior C programmers, so I would suggest to give them a chance before deciding to leave qmail 

Reply | Permalink

Patch netqmail1.06

Charles January 24, 2019 09:39

Hello,

I have installed netqmail-1.06 and I found the patch qmail on your website, and interest to try but have error like this:

./load qmail-qmtpd rcpthosts.o control.o constmap.o \
 received.o date822fmt.o now.o qmail.o cdb.a fd.a wait.a \
 datetime.a open.a getln.a sig.a case.a env.a stralloc.a \
 alloc.a substdio.a error.a str.a fs.a auto_qmail.o
./compile qmail-smtpd.c
qmail-smtpd.c: In function ‘setup’:
qmail-smtpd.c:239: error: ‘maxrcpt’ undeclared (first use in this function)
qmail-smtpd.c:239: error: (Each undeclared identifier is reported only once
qmail-smtpd.c:239: error: for each function it appears in.)
qmail-smtpd.c:303: error: ‘rejectrelaytest’ undeclared (first use in this functi on)
qmail-smtpd.c:307: error: ‘rejnsmf’ undeclared (first use in this function)
qmail-smtpd.c:316: error: ‘greetdelay’ undeclared (first use in this function)
qmail-smtpd.c:318: error: ‘drop_pre_greet’ undeclared (first use in this functio n)
qmail-smtpd.c:320: error: ‘protocol’ undeclared (first use in this function)
qmail-smtpd.c:322: error: ‘spfbehavior’ undeclared (first use in this function)
qmail-smtpd.c:327: error: ‘spflocal’ undeclared (first use in this function)
qmail-smtpd.c:329: error: ‘spfguess’ undeclared (first use in this function)
qmail-smtpd.c:331: error: ‘spfexp’ undeclared (first use in this function)
qmail-smtpd.c:331: error: ‘SPF_DEFEXP’ undeclared (first use in this function)
qmail-smtpd.c:336: error: ‘remoteip4’ undeclared (first use in this function)
qmail-smtpd.c:404: error: ‘forcetls’ undeclared (first use in this function)
qmail-smtpd.c:405: error: ‘smtps’ undeclared (first use in this function)
qmail-smtpd.c: In function ‘smtp_helo’:
qmail-smtpd.c:504: error: ‘seenmail’ undeclared (first use in this function)
qmail-smtpd.c: In function ‘smtp_ehlo’:
qmail-smtpd.c:517: error: ‘seenmail’ undeclared (first use in this function)
qmail-smtpd.c: In function ‘smtp_rset’:
qmail-smtpd.c:521: error: ‘seenmail’ undeclared (first use in this function)
qmail-smtpd.c: In function ‘smtp_mail’:
qmail-smtpd.c:527: error: ‘flagbarf’ undeclared (first use in this function)
qmail-smtpd.c:528: error: ‘seenmail’ undeclared (first use in this function)
qmail-smtpd.c: In function ‘smtp_rcpt’:
qmail-smtpd.c:535: error: ‘seenmail’ undeclared (first use in this function)
qmail-smtpd.c:537: error: ‘flagbarf’ undeclared (first use in this function)
qmail-smtpd.c: In function ‘spfreceived’:
qmail-smtpd.c:645: error: ‘spfbehavior’ undeclared (first use in this function)
qmail-smtpd.c: In function ‘acceptmessage’:
qmail-smtpd.c:706: error: ‘strnum’ undeclared (first use in this function)
qmail-smtpd.c:715: error: ‘sslog’ undeclared (first use in this function)
qmail-smtpd.c: In function ‘smtp_data’:
qmail-smtpd.c:729: error: ‘seenmail’ undeclared (first use in this function)
qmail-smtpd.c:731: error: ‘envelopepos’ undeclared (first use in this function)
qmail-smtpd.c:739: error: ‘protocol’ undeclared (first use in this function)
qmail-smtpd.c: At top level:
qmail-smtpd.c:758: error: redefinition of ‘authin’
qmail-smtpd.c:111: note: previous definition of ‘authin’ was here
qmail-smtpd.c:759: error: redefinition of ‘user’
qmail-smtpd.c:112: note: previous definition of ‘user’ was here
qmail-smtpd.c:760: error: redefinition of ‘pass’
qmail-smtpd.c:113: note: previous definition of ‘pass’ was here
qmail-smtpd.c:761: error: redefinition of ‘resp’
qmail-smtpd.c:114: note: previous definition of ‘resp’ was here
qmail-smtpd.c:762: error: redefinition of ‘slop’
qmail-smtpd.c:116: note: previous definition of ‘slop’ was here
qmail-smtpd.c: In function ‘smtp_auth’:
qmail-smtpd.c:943: error: ‘seenmail’ undeclared (first use in this function)
make: *** [qmail-smtpd.o] Error 1

any idea?

thanks for the help

Reply | Permalink

Patch netqmail1.06

Roberto Puzzanghera Charles January 25, 2019 15:03

It seems like the patching process went wrong... 

Reply | Permalink

TLS 1.3

Wouter de Geus December 19, 2018 09:23

Hi Robert!

Thanks a lot for your continued effort to patch up QMail!

In the past I've been very happy with John Simpson's combined patch (https://qmail.jms1.net/patches/combined-details.shtml), but that hasn't been updated for years now.

Right now I'm trying to upgrade my legacy qmail server to a new incarnation based on Docker, going with your patch this time :)

That said, I tried to compile against the latest OpenSSL and quickly ran into trouble, so I was wondering if you (or anyone else that you know of) have plans to support the new OpenSSL and with that the TLS 1.3 protocol.

I figure it's a matter of time before this becomes a necessity, alreaady I see older TLS versions being dropped on various mailservers.

Anyway, keep up the good work!

Reply | Permalink

TLS 1.3

Roberto Puzzanghera Wouter de Geus December 19, 2018 10:39

Honestly, accomplishing this task would be far over my skills but I'm confident that an upgrade to the qmail-tls patch by f.vermulen will come at a certain point 

Reply | Permalink

error after update with the new patch

Bernardo Correia September 20, 2018 17:27

Hi Roberto!

I have a centos 7 working with your qmail how to. But when i try to update to the latest patch i start getting this errors on smtp log

qlogreceived: result=rejected code=451 reason=queuedelay detail=qq_temporary_problem_(#4.3.0)

Do you have any idea what can be?

Thanks,

Bernardo Correia 

Reply | Permalink

error after update with the new patch

miz Bernardo Correia July 24, 2019 11:47

Hi everybody,

same old story here :-)

- brand new centos 7 64bit server

- installation and compilation went perfectly fine

- everything seems to be working, exept for:

Jul 24 12:31:27 2019 qmail-smtpd: message delayed (unable to exec qq (#4.3.0)):xxx@domain.it from x.x.x.x to Jul 24 12:31:59

I'm still unable to solve the problem, already tried to increased soft limit with no luck, double checked all perms on queues and qmail directory, checked all the run files, nothing.

- there is no antivirus (no clamd, simscan, anything) installed, no qmail-scanner and no spamassassin.

- local delivery is working fine:

/var/qmail/bin/qmail-inject xxx@domain.it < /tmp/test.txt

Any hint about ways to debug this ?

Thank you ! 

Reply | Permalink

error after update with the new patch

Roberto Puzzanghera miz July 24, 2019 12:36

are you using my combined patch? if yes, can you post your run file and your tcp.smtp?

Reply | Permalink

error after update with the new patch

Roberto Puzzanghera Bernardo Correia September 20, 2018 18:05

check also your clamav and spamassassin logs, because something is breaking your delivery

Reply | Permalink

error after update with the new patch

Roberto Puzzanghera Bernardo Correia September 20, 2018 18:01

Did you try to increase your softlimit already?

Reply | Permalink

Bug in logit and logit2 functions

Mirko Buffoni August 20, 2018 16:44

I found a bug in logit and logit2 functions which comes from https://notes.sagredo.eu/files/qmail/patches/logging-4.patch

It was hard to track. But I was lucky to isolate the problem with a mail client who was issuing a RSET command and closed the connection brutally after this.

To replicate the problem I did:

$ telnet localhost 25

Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 Welcome to BLABLABLA
mail from: <sender@domain.tld>
250 ok
rcpt to: <recipient@domain.tld>
250 ok
data
354 go ahead
Date: Mon, 20 Aug 2018 15:24:01 +0200
From: sender@domain.tld
To: recipient@domain.tld
Subject: test

test
.
250 ok 1534778879 qp 11906
rset
250 flushed
^]
telnet> quit
Connection closed.

At this point a segfault at 9220000 ip 0805d309 sp bfc5e4ac error 6 in qmail-smtpd[8048000+34000] is generated

After a RSET command, the mailfrom.len is set to 0, but mailfrom.s is still allocated.
In logit/logit2 functions, a check is done on mailfrom.s and then a

stralloc_catb(&log_buf, mailfrom.s, mailfrom.len-1)) die_nomem();

is done, but mailform.len is zero and this will cause a memory allocation fault when using softlimit.

The following is a patch to cure this issue.

--- qmail-smtpd.c.orig 2018-08-20 16:34:55.000000000 +0200
+++ qmail-smtpd.c 2018-08-20 17:23:49.000000000 +0200
@@ -1096,19 +1096,19 @@
 if (!stralloc_copys(&log_buf, "qmail-smtpd: ")) die_nomem();
 if (!stralloc_cats(&log_buf, message)) die_nomem();
 if (!stralloc_catb(&log_buf, ": ", 2)) die_nomem();
- if (mailfrom.s) {
+ if (mailfrom.s && mailfrom.len) {
 if (!stralloc_catb(&log_buf, mailfrom.s, mailfrom.len-1)) die_nomem();
 } else
 if (!stralloc_catb(&log_buf, "(null)", 6)) die_nomem();
 if (!stralloc_catb(&log_buf, " from ", 6)) die_nomem();
 if (!stralloc_cats(&log_buf, remoteip)) die_nomem();
 if (!stralloc_catb(&log_buf, " to ", 4)) die_nomem();
- if (addr.s) {
+ if (addr.s && addr.len) {
 if (!stralloc_catb(&log_buf, addr.s, addr.len-1)) die_nomem();
 } else
 if (!stralloc_catb(&log_buf, "(null)", 6)) die_nomem();
 if (!stralloc_catb(&log_buf, " helo ", 6)) die_nomem();
- if (helohost.s) {
+ if (helohost.s && helohost.len) {
 if (!stralloc_catb(&log_buf, helohost.s, helohost.len-1)) die_nomem();
 } else
 if (!stralloc_catb(&log_buf, "(null)", 6)) die_nomem();
@@ -1125,19 +1125,19 @@
 if (!stralloc_cats(&log_buf, " (")) die_nomem();
 if (!stralloc_cats(&log_buf, reason)) die_nomem();
 if (!stralloc_cats(&log_buf, "): ")) die_nomem();
- if (mailfrom.s) {
+ if (mailfrom.s && mailfrom.len) {
 if (!stralloc_catb(&log_buf, mailfrom.s, mailfrom.len-1)) die_nomem();
 } else
 if (!stralloc_catb(&log_buf, "(null)", 6)) die_nomem();
 if (!stralloc_cats(&log_buf," from ")) die_nomem();
 if (!stralloc_cats(&log_buf, remoteip)) die_nomem();
 if (!stralloc_cats(&log_buf, " to ")) die_nomem();
- if (addr.s) {
+ if (addr.s && addr.len) {
 if (!stralloc_catb(&log_buf, addr.s, addr.len-1)) die_nomem();
 } else
 if (!stralloc_catb(&log_buf, "(null)", 6)) die_nomem();
 if (!stralloc_cats(&log_buf, " helo ")) die_nomem();
- if (helohost.s) {
+ if (helohost.s && helohost.len) {
 if (!stralloc_catb(&log_buf, helohost.s, helohost.len-1)) die_nomem();
 } else
 if (!stralloc_catb(&log_buf, "(null)", 6)) die_nomem();

Reply | Permalink

Bug in logit and logit2 functions

Roberto Puzzanghera Mirko Buffoni August 23, 2018 11:21

Thanks to Mirko this bug was fixed in the v.5 of the logging patch, which I have just included in my package

Reply | Permalink

Mess822 bug

Mirko Buffoni August 17, 2018 15:36

I found a bug in mess822-0.58 package.

You do not have a section for it, so I'm posting a patch under qmail.

You can use a tool like 822field to extract a field from headers in a mail.

However, it compares the header with string without considering that the string may be longer, after the match. So a

cat email | 822field Subjectttttt

will give back the Subject field in any case, which is wrong.

The proposed patch will fix this, allowing, as an extreme case, to specify a colon as last character in searched header string. So a | 822field Subject: will work too giving back the searched Subject, while | 822field Subjectt won't.

--- mess822_line.c.old 2018-08-17 16:03:24.000000000 +0200
+++ mess822_line.c 2018-08-17 16:02:26.000000000 +0200
@@ -41,7 +41,7 @@
 }

for (a = h->action;a->name;++a)
- if (!case_diffb(h->inprogress.s,pos,a->name))
+ if (!case_diffb(h->inprogress.s,pos,a->name) && (a->name[pos] == 0 || a->name[pos] == ':'))
 break;

for (;pos < h->inprogress.len;++pos) {

Reply | Permalink

Mess822 bug

Roberto Puzzanghera Mirko Buffoni August 17, 2018 15:58

Thank you, I'll check it out when I'll be back home

Reply | Permalink

combined patches

Vahid Baboli July 5, 2018 23:08

Hi,

Great job collecting and putting together this site.

We have 50+ qmail servers mainly to send out e-mail and not receiving any.

I am wondering, what patches do i really need to have a stable sending qmail servers.

I currently have DNS and TLS patch only.

Thanks very much if you reply.

Vahid.

Reply | Permalink

combined patches

Roberto Puzzanghera Vahid Baboli July 6, 2018 10:28

Provided that you can choose to install the complete combined patch and then use just what you need of it, this could be a subset of patches that you need to build a send server. The most important (in my opinion) are in bold text

qmail-authentication
qmail-tls
force-tls
oversize DNS
reread concurrency
big concurrency
big concurrency fix
Better qmail-smtpd logging
SMTP HELO/EHLO Greeting delay
DKIM and SURBL
EXT-TODO
BIG-TODO
qmail-inject-null-sender
qmail-taps-extended
qmail-remote CRLF
outgoingip
qmail-smtpd pid, qp log patch
any-to-cname
qmail-rfc2821
smtpd-502-to-500
qmail-moreipme
qmail-hide-ip-headers
qmail-date-localtime
qmail-smtpd liberal-lf
qmail-empf
reject-relay-test
qlog
dnscname
rcptcheck

Reply | Permalink

combined patches

Vahid Baboli Roberto Puzzanghera January 2, 2019 22:24

why am I keep getting this error while compiling qmail with a few patches (please see my other question):

more undefined references to `logit' follow collect2: error: ld returned 1 exit status

Reply | Permalink

combined patches

Roberto Puzzanghera Vahid Baboli January 3, 2019 14:12

as you know, logit is a function which belongs to the logging patch... did you get any error while patching?

Reply | Permalink

combined patches

Vahid Baboli Roberto Puzzanghera January 3, 2019 19:02

started fresh and noticed that if I apply patches in this order:

logging-5.patch compiles OK
qmail-remote-CRLF.diff - OK
qmail-inject-null-sender.patch - OK

roberto-netqmail-1.06_auth_tls_force-tls.patch-latest - fails with this error:

qmail-smtpd.o: In function `err_nogateway':
qmail-smtpd.c:(.text+0x1b8): undefined reference to `tls_nogateway'
qmail-smtpd.o: In function `setup':
qmail-smtpd.c:(.text+0x1030): undefined reference to `tls_init'

If I only apply roberto-netqmail-1.06.patch-latest patch, then I get

chkuser.c:38:22: fatal error: vpopmail.h: No such file or directory

These servers are only sending mail out so I only need any-to-cname and TLS patch.
which one do you recommend?
thanks again.

Reply | Permalink

combined patches

Roberto Puzzanghera Vahid Baboli January 3, 2019 19:25

First of all, I would recommend to apply the auth/tls/forcetls patch, which is the biggest one and the most difficult to fix if the patching went wrong, and then the others.

If your server is just sending, the logging patch is of little use, because it logs qmail-smtpd. 

"any to cname" is not so important for me, while qmail-remote-CRLF and qmail-inject-null-sender are both a good choice because they fix bugs.

You can always decide to use my big patch (roberto-netqmail-1.06.patch-latest) but you have to install vpopmail, libdomainkeys and libsrs2 libraries, but it's very easy to do, otherwise you'll get compilation breaks like the one you showed above (it's complaining about the lack of vpopmail)

And I would like to return the wishes for a happy 2019 :-)

Reply | Permalink

combined patches

Vahid Baboli Roberto Puzzanghera January 3, 2019 19:43

Sorry, didnt see this post.

so, trying fresh tarball, applying the following patches in this order:

roberto-netqmail-1.06_auth_tls_force-tls.patch-latest - OK
any-to-cname.patch - OK (I need this patch since we get so much large DNS realted issues)
qmail-remote-CRLF.diff - OK
qmail-inject-null-sender.patch - OK

so i should be good for prod i guess?
We are getting lots of complains and rejections due to use of TLS 1.0 and no also no TLS so I have to upgrade.
in the current built, I used netqmail-1.05-tls-20060104.patch.

Reply | Permalink

combined patches

Roberto Puzzanghera Vahid Baboli January 3, 2019 19:46

I would suggest to do all tests before switching to production...

Reply | Permalink

combined patches

Vahid Baboli Roberto Puzzanghera January 3, 2019 20:28

ah yeah, lots of tests...

daemontools needs to be recompiled and giving me hard time but i will figure out. thanks for your help.

Reply | Permalink

combined patches

Vahid Baboli Roberto Puzzanghera January 2, 2019 20:21

Happy New Year Roberto,

I have many qmail server to install/upgrade to include the new TLS 1.2 patch (other domains started denying TLS 1.0).

I am wondering is there is a way to make qmail-remote (we are only sending) binary static so I just package the binaries and deploy to servers rather that compile on each server. I am not sure all servers have the latest libraries.

i am installing the following patches to netqmail-1.06:

roberto-netqmail-1.06_auth_tls_force-tls.patch-latest
logging-5.patch
qmail-inject-null-sender.patch
any-to-cname.patch
qmail-remote-CRLF.diff

Thanks,

Reply | Permalink

combined patches

Roberto Puzzanghera Vahid Baboli January 3, 2019 19:29

I would also consider building a qmail package for your linux distribution, just to save the compilation time, but you must be sure that all the libraries are the same in all your servers, of course

Reply | Permalink

combined patches

Roberto Puzzanghera Vahid Baboli January 3, 2019 14:06

Perhaps this could be possible, but I think it would be more time expensive **and not secure** than compiling the entire qmail in each server, especially if they don't share the same libraries...

Reply | Permalink

FreeBSD

Kris von Mach November 14, 2017 10:38

When compiling this patch on FreeBSD I get the following error:

qmail-smtpd.c:2398:41: error: function definition is not allowed here
 void outqlog(char *s, unsigned int n) {
 ^
qmail-smtpd.c:2405:17: error: a parameter list without types is only allowed in a function definition
 void outsqlog(s) char *s; { outqlog(s,str_len(s)); }
 ^
qmail-smtpd.c:2405:19: error: expected ';' at end of declaration
 void outsqlog(s) char *s; { outqlog(s,str_len(s)); }
 ^

Any idea on how to fix that?

Reply | Permalink

Libdomainkeys compilation error

Tocy November 8, 2017 14:42

Hello,

Libdomainkeys gives a compilation error on debian 9 as follows:

make
gcc -DBIND_8_COMPAT -O2 -o makeheader makeheader.c
./makeheader domainkeys.h
gcc -DBIND_8_COMPAT -O2 -c dktest.c -I.
gcc -DBIND_8_COMPAT -O2 -c domainkeys.c -I.
domainkeys.c:123:14: error: field ‘mdctx’ has incomplete type
 EVP_MD_CTX mdctx; /* the hash */
 ^~~~~
domainkeys.c: In function ‘dkheaders’:
domainkeys.c:1285:5: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
 (void *)dk_headers(dk, dk->headers);
 ^
domainkeys.c: In function ‘dk_free’:
domainkeys.c:2155:3: warning: implicit declaration of function ‘EVP_MD_CTX_cleanup’ [-Wimplicit-function-declaration]
 EVP_MD_CTX_cleanup(&dk->mdctx);
 ^~~~~~~~~~~~~~~~~~
domainkeys.c:2162:6: warning: ‘ERR_remove_state’ is deprecated [-Wdeprecated-declarations]
 ERR_remove_state(0);
 ^~~~~~~~~~~~~~~~
In file included from /usr/include/openssl/x509_vfy.h:20:0,
 from /usr/include/openssl/x509.h:309,
 from /usr/include/openssl/pem.h:17,
 from domainkeys.c:28:
/usr/include/openssl/err.h:248:1: note: declared here
 DEPRECATEDIN_1_0_0(void ERR_remove_state(unsigned long pid))
 ^
Makefile:23: recipe for target 'domainkeys.o' failed
make: *** [domainkeys.o] Error 1

Reply | Permalink

Libdomainkeys compilation error

Roberto Puzzanghera Tocy November 8, 2017 14:52

which version of gcc?

Reply | Permalink

Libdomainkeys compilation error

Tocy Roberto Puzzanghera November 9, 2017 05:04

Here are the gcc versions installed: 

ii gcc 4:6.3.0-4 amd64 GNU C compiler
ii gcc-6 6.3.0-18 amd64 GNU C compiler
ii gcc-6-base:amd64 6.3.0-18 amd64 GCC, the GNU Compiler Collection (base package)
ii libgcc-6-dev:amd64 6.3.0-18 amd64 GCC support library (development files)
ii libgcc1:amd64 1:6.3.0-18 amd64 GCC support library

Reply | Permalink

Libdomainkeys compilation error

Roberto Puzzanghera Tocy November 9, 2017 10:44

I haven't tested with gcc-6.

tests would be much appreciated

Reply | Permalink

Libdomainkeys compilation error

Tocy Roberto Puzzanghera November 9, 2017 13:22

I will gladly test but I don't know how to fix the code for this library and the qmail-remote.c and all other files that may need fixing. Sorry but I am more of a system guy than a developer:)

Cheers,

Reply | Permalink

Libdomainkeys compilation error

Tocy Tocy November 10, 2017 02:42

The issue is linked to libssl-dev 1.1 with 1.0 all works.

Cheers,

Reply | Permalink

Libdomainkeys compilation error

sa1phx Tocy November 6, 2018 10:21

Hello, i also have this issue,

Fix it by changing this lines:

domainkeys.c:123 ->

From: EVP_MD_CTX mdctx; /* the hash */

To: EVP_MD_CTX *mdctx; /* the hash */

domainkeys.c:2156 ->

From: EVP_MD_CTX_cleanup(&dk->mdctx);

To: EVP_MD_CTX_free(&dk->mdctx);

After editing source file, compilation is successfull

Reply | Permalink

Libdomainkeys compilation error

Roberto Puzzanghera sa1phx November 6, 2018 13:16

and are you using libssl-dev 1.1?

Reply | Permalink

Libdomainkeys compilation error

Jim McNamara Roberto Puzzanghera January 25, 2019 14:36

I can confirm the changes sa1phx  posted for the "domainkeys.c:123:14: error: field ‘mdctx’ has incomplete type" problem on Debian 9 with openssl-1.1. Here are my details -

ii gcc 4:6.3.0-4 amd64 GNU C compiler
ii gcc-6 6.3.0-18+deb9u1 amd64 GNU C compiler
ii gcc-6-base:amd64 6.3.0-18+deb9u1 amd64 GCC, the GNU Compiler Collection (base package)
ii libgcc-6-dev:amd64 6.3.0-18+deb9u1 amd64 GCC support library (development files)
ii libgcc1:amd64 1:6.3.0-18+deb9u1 amd64 GCC support library

ii libssl-dev:amd64 1.1.0j-1~deb9u1 amd64 Secure Sockets Layer toolkit - development files
ii libssl-doc 1.1.0j-1~deb9u1 all Secure Sockets Layer toolkit - development documentation
ii libssl1.0.2:amd64 1.0.2q-1~deb9u1 amd64 Secure Sockets Layer toolkit - shared libraries
ii libssl1.1:amd64 1.1.0j-1~deb9u1 amd64 Secure Sockets Layer toolkit - shared libraries

Here is the resulting diff between the source with the libdomainkeys-0.69.diff applied and then the changes suggested by sa1phx. I confirm that after applying their changes, make succeeds and libdomainkeys.a is produced. I cannot yet confirm that the libdomainkeys.a file functions.

diff -u for-diff/domainkeys.c libdomainkeys/domainkeys.c
--- for-diff/domainkeys.c 2008-03-31 18:50:39.000000000 -0400
+++ libdomainkeys/domainkeys.c 2019-01-25 09:12:11.184191244 -0500
@@ -120,7 +120,7 @@
{
/* STARTPRIV */ 
  int dkmarker; /* in case somebody casts in */
- EVP_MD_CTX mdctx; /* the hash */
+ EVP_MD_CTX *mdctx; /* the hash */
  int signing; /* our current signing/verifying state */ 
  int in_headers; /* true if we're still processing headers */ 
  char *header; /* points to a malloc'ed block for header. */

@@ -2152,7 +2152,7 @@
#ifdef DK_HASH_BUFF
  DK_MFREE(dk->hash_buff);
#endif
- EVP_MD_CTX_cleanup(&dk->mdctx);
+ EVP_MD_CTX_free(&dk->mdctx);
  DK_MFREE(dk->header); /* alloc'ing dk->header is not optional. */
  dk->dkmarker = ~DKMARK;
  DK_MFREE(dk);

Reply | Permalink

Libdomainkeys compilation error

Roberto Puzzanghera Jim McNamara January 25, 2019 15:40

Thank you. And how are you patching qmail-remote.c?

I'm still unable to compile with openssl-1.1 and gcc-8.2, as I get this error

./compile qmail-remote.c
qmail-remote.c: In function ‘tls_init’:
qmail-remote.c:522:60: error: dereferencing pointer to incomplete type ‘X509_NAME_ENTRY’ {aka ‘struct X509_name_entry_st’}
 const ASN1_STRING *s = X509_NAME_get_entry(subj, i)->value;

I'm using this patch to solve other compilation breaks

--- qmail-remote.c.orig 2017-05-14 13:50:09 UTC
+++ qmail-remote.c
@@ -266,7 +266,7 @@ char *append;
 {
#ifdef TLS
 /* shouldn't talk to the client unless in an appropriate state */
- int state = ssl ? ssl->state : SSL_ST_BEFORE;
- if (state & SSL_ST_OK || (!smtps && state & SSL_ST_BEFORE))
+ int state = SSL_get_state(ssl);
+ if (state & TLS_ST_OK || (!smtps && state & TLS_ST_BEFORE))
 #endif
 substdio_putsflush(&smtpto,"QUIT\r\n");
--- ssl_timeoutio.c.orig 2017-05-14 13:50:09 UTC
+++ ssl_timeoutio.c
@@ -74,10 +74,10 @@ int ssl_timeoutrehandshake(int t, int rf

SSL_renegotiate(ssl);
 r = ssl_timeoutio(SSL_do_handshake, t, rfd, wfd, ssl, NULL, 0);
- if (r <= 0 || ssl->type == SSL_ST_CONNECT) return r;
+ if (r <= 0 || SSL_get_state(ssl) == SSL_ST_CONNECT) return r;

/* this is for the server only */
- ssl->state = SSL_ST_ACCEPT;
+ SSL_set_connect_state(ssl);
 return ssl_timeoutio(SSL_do_handshake, t, rfd, wfd, ssl, NULL, 0);
 }

As my C skills are close to zero, some help would be really appreciated in order to make my patch openssl-1.1 compliant.

Reply | Permalink

Libdomainkeys compilation error

Jim McNamara Roberto Puzzanghera January 28, 2019 15:32

Unfortunately, qmail-remote.c won 't compile for me in any way, even when I install and use the current openssl-1.0.2.q from source. I applied the patch you showed for qmail-remote.c and ssl_timeoutio.c, that moved things along but still make ultimately ends with error 1. 

When I try to make with the openssl-1.1.0 package from Debian I use this conf-cc file, the .h files are in /usr/include/openssl:

cc -O2 -g -DEXTERNAL_TODO -DTLS=20160918 -I/usr/include/openssl -I/home/vpopmail/include

This will be used to compile .c files.

./compile qmail-remote.c
In file included from qmail-remote.c:7:0:
substdio.h:12:64: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types]
 #define SUBSTDIO_FDBUF(op,fd,buf,len) { (buf), 0, (len), (fd), (op) }
 ^
qmail-remote.c:172:17: note: in expansion of macro ‘SUBSTDIO_FDBUF’
 substdio ssin = SUBSTDIO_FDBUF(read,0,inbuf,sizeof inbuf);
 ^~~~~~~~~~~~~~
substdio.h:12:64: note: (near initialization for ‘ssin.op’)
 #define SUBSTDIO_FDBUF(op,fd,buf,len) { (buf), 0, (len), (fd), (op) }
 ^
qmail-remote.c:172:17: note: in expansion of macro ‘SUBSTDIO_FDBUF’
 substdio ssin = SUBSTDIO_FDBUF(read,0,inbuf,sizeof inbuf);
 ^~~~~~~~~~~~~~
qmail-remote.c: In function ‘tls_init’:
qmail-remote.c:535:60: error: dereferencing pointer to incomplete type ‘X509_NAME_ENTRY {aka struct X509_name_entry_st}’
 const ASN1_STRING *s = X509_NAME_get_entry(subj, i)->value;
 ^~
qmail-remote.c: In function ‘mailfrom_cram’:
qmail-remote.c:670:3: warning: implicit declaration of function ‘hmac_md5’ [-Wimplicit-function-declaration]
 hmac_md5(chal.s,chal.len,pass.s,pass.len,digest);
 ^~~~~~~~
Makefile:1675: recipe for target 'qmail-remote.o' failed
make: *** [qmail-remote.o] Error 1

I didn't want to use openssl 1.0.2, but I saw that officially version 1.0.2 would be supported through December of 2019. I created /usr/local/special and passed, "./config --prefix=/usr/local/special --openssldir=/usr/local/special/openssl" to config, that way it would not end up in any $PATH down the road. I edit netqmail's conf-cc to read:

cc -O2 -g -DEXTERNAL_TODO -DTLS=20160918 -I/usr/local/special/include/openssl -I/home/vpopmail/include

This will be used to compile .c files.

Then I make clean, and try to make again now using the older openssl-1.0.2 and it still errors out in the end again on qmail-remote.c:

./compile qmail-remote.c
In file included from qmail-remote.c:7:0:
substdio.h:12:64: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types]
 #define SUBSTDIO_FDBUF(op,fd,buf,len) { (buf), 0, (len), (fd), (op) }
 ^
qmail-remote.c:172:17: note: in expansion of macro ‘SUBSTDIO_FDBUF’
 substdio ssin = SUBSTDIO_FDBUF(read,0,inbuf,sizeof inbuf);
 ^~~~~~~~~~~~~~
substdio.h:12:64: note: (near initialization for ‘ssin.op’)
 #define SUBSTDIO_FDBUF(op,fd,buf,len) { (buf), 0, (len), (fd), (op) }
 ^
qmail-remote.c:172:17: note: in expansion of macro ‘SUBSTDIO_FDBUF’
 substdio ssin = SUBSTDIO_FDBUF(read,0,inbuf,sizeof inbuf);
 ^~~~~~~~~~~~~~
qmail-remote.c: In function ‘tls_init’:
qmail-remote.c:535:60: error: dereferencing pointer to incomplete type ‘X509_NAME_ENTRY {aka struct X509_name_entry_st}’
 const ASN1_STRING *s = X509_NAME_get_entry(subj, i)->value;
 ^~
qmail-remote.c: In function ‘mailfrom_cram’:
qmail-remote.c:670:3: warning: implicit declaration of function ‘hmac_md5’ [-Wimplicit-function-declaration]
 hmac_md5(chal.s,chal.len,pass.s,pass.len,digest);
 ^~~~~~~~
Makefile:1675: recipe for target 'qmail-remote.o' failed
make: *** [qmail-remote.o] Error 1

I have even less C than you do, but am more than willing to continue testing & troubleshooting. There's apparently some deep issue with const ASN1_STRING *s = X509_NAME_get_entry(subj, i)->value; as we're both getting the same error on make, yours presumably on Slackware and mine on Debian, mine with both openssl-1.0.2 and openssl-1.1.0. 

Reply | Permalink

Libdomainkeys compilation error

Eric Jim McNamara February 13, 2019 21:18

const ASN1_STRING *s = X509_NAME_ENTRY_get_data(X509_NAME_get_entry(subj, i));

instead of

const ASN1_STRING *s = X509_NAME_get_entry(subj, i)->value;

Reply | Permalink

Libdomainkeys compilation error

Roberto Puzzanghera Eric February 13, 2019 21:30

Thank you, Eric. It compiles now. qmail-smtpd.c must be modified as well

Reply | Permalink

Libdomainkeys compilation error

Roberto Puzzanghera Roberto Puzzanghera February 13, 2019 22:48

New testing patch released. Look at the top of this page. There's a patch for libdomainkeys as well. They can be used both on v. 1.0 and 1.1 of openssl

Please give me some feedback, so that I can release it as stable soon..

Reply | Permalink

Libdomainkeys compilation error

Anonymous Roberto Puzzanghera March 28, 2019 12:42

Debian 9 openssl and libssl 1.1.0j

dktest not work 
log send

delivery 154: deferral: /var/qmail/bin/dk-filter:_(spawn-filter)_exit_code:_139:_/var/qmail/bin/dk-filter:_line_271:_62249_Segmentation_fault______/var/qmail/bin/dktest_-s_/var/qmail/control/domainkeys/hidden_domain/default/._(#4.3.0)spawn-filter_said:_Message_deferred

syslog

... dktest[62249]: segfault at 1 ip 00007fd82e3b7b36 sp 00007ffce29d2bc0 error 4 in libcrypto.so.1.1

Reply | Permalink

Libdomainkeys compilation error

Roberto Puzzanghera Anonymous March 31, 2019 20:47

Please try the following libdomainkeys patched by Manvendra Banghui. If this will not solve feel free to write me in private so that I can provide a direct contact with him.

Reply | Permalink

Libdomainkeys compilation error

Hamersky Roberto Puzzanghera April 1, 2019 08:53

Thanks Roberto and Manvendra with libdomainkeys patched by Manvendra Banghui working :)

Reply | Permalink

Libdomainkeys compilation error

Manvendra Bhangui Anonymous March 28, 2019 16:34

Just got notified of dktest segmentation fault. I will take a look at it. It might take me some time to replicate the same openssl version on my laptop and test it out. If it helps, you can temporarily disable domainkeys and just have DKIM.

Reply | Permalink

FORCEAUTHMAILFROM not check

MARCIO RUBENS November 6, 2017 20:17

Hello.

I performed the patch installation but the mailfrom check function is not being performed.
I ran tests by thunderbird by changing from: and sending successfully.

In the smtp run I configured with export FORCEAUTHMAILFROM = 1

Any tip?

thanks

Reply | Permalink

FORCEAUTHMAILFROM not check

Roberto Puzzanghera MARCIO RUBENS November 6, 2017 20:36

Hi, I have no idea.. my tests are ok... please double check everything

Reply | Permalink

FORCEAUTHMAILFROM not check

Marcio R Roberto Puzzanghera November 7, 2017 10:28

I did the installation again and I did not succeed.
Does this patch block the email with the from field changed?

Log of test performed:

2017-11-07 07: 50: 25.679940500 policy_check: local marciorubens@dialhost.com.br -> remote marciorubenscardoso@gmail.com (AUTHENTICATED SENDER)
2017-11-07 07: 50: 25.830499500 simscan: [8424]: CLEAN (-1.00 / 15.00 / 15.00): 0.1197s: dddd: 177.69.128.1: marciorubens@dialhost.com.br: marciorubenscardoso@gmail.com
2017-11-07 07: 50: 25.976899500 mail recv: pid 8424 from <marciorubens@dialhost.com.br> qp 8429
2017-11-07 07: 50: 25.976901500 qmail-smtpd: message accepted: marciorubens@dialhost.com.br from 177.69.128.1 to marciorubenscardoso@gmail.com helo [10.1.1.53]

Log Gmail:

Delivered-To: marciorubenscardoso@gmail.com
Received: by 10.176.87.18 with SMTP id s18csp4018920uaa;
        Tue, 7 Nov 2017 01:50:27 -0800 (PST)
X-Google-Smtp-Source: ABhQp + SMg7Vnmj4Ss9PNWvQpdkXHZ + Jd0MlFbzJrQVTHP + PtCDNom2DrakgBTAxwjkl7DwSkCaCR
X-Received: by 10.159.59.71 with SMTP id j7mr14577994uah.135.1510048227462;
        Tue, 07 Nov 2017 01:50:27 -0800 (PST)
ARC-Seal: i = 1; a = rsa-sha256; t = 1510048227; cv = none;
        d = google.com; s = arc-20160816;
        b = rcWVEW8 / w0hpFVZlQogAAqwV66o5rIH0yOkHWjjqw6lh6YjAaMF5gNlH0x0o61Ow0Y
         vddzV + 6l1NVvl6M4yd9eug1aPIhF7ndfX6ZitkE + Gl3xq2iPQ5AtcX + CHZFEpV2F + MVX
         a ++ FFpoGP5qmjlmyL974c6aLNZTP + dzkKE93IUF5XQtab9C4iney2OHVV2kkjfVIHfA7
         10
         nz
         giLw ==
ARC-Message-Signature: i = 1; a = rsa-sha256; c = relaxed / relaxed; d = google.com; s = arc-20160816;
        h = content-language: content-transfer-encoding: mime-version: user-agent
         : date: message-id: subject: from: to: / m: arc-authentication-results;
        bh = SzVMU + mFZiUdyQvZrHmIh1w9KIokwNhHQSVvk1pnTOU =;
        b = guPdLgygMuZNwQyJG3bapZzOPerg / R4pxt / aGWh9rG / JHidRBl / Rqrl6J8K8H1U47j
         IGkOaPRDZkCVwX57fh5Cgfdb3Uwkht3X2WZt + 0Oot1vurYcj9iPnKX5NYuwr0DoKVJw7
         WGFI9LuEoBhF3CI9ca3rHZgBwRU / Da9grff3NEWHRLYDFV0xvwxIw7qx9CupL3r2ScFV
         uhjxPVoVM5uE9i0XLSG2AkWgCcsgssEl8CLw6 / twyoLjqzKG6M9D8G1C4WYNZolPrd5D
         aHpOfTBxvX6M6RXQbabP4Ts1nXa6FBmhFysCJPPled15cMx9wsE689 + UaKShPSlYkfHr
         e9iw ==
ARC-Authentication-Results: i = 1; mx.google.com;
       spf = pass (google.com: domain of marciorubens@dialhost.com.br designates 138.118.172.67 as permitted sender) smtp.mailfrom=marciorubens@dialhost.com.br;
       dmarc = pass (p = NONE sp = NONE dis = NONE) header.from = dialhost.com.br
Return-Path: <marciorubens@dialhost.com.br>
Received: from mailf67-br118.dialhost.com.br (mailf67-br118.dialhost.com.br. [138.118.172.67])
        by mx.google.com with ESMTPS id s6si210550vka.356.2017.11.07.01.50.27
        for <marciorubenscardoso@gmail.com>
        (version = TLS1_2 cipher = AES128-SHA bits = 128/128);
        Tue, 07 Nov 2017 01:50:27 -0800 (PST)
Received-SPF: pass (google.com: domain of marciorubens@dialhost.com.br designates 138.118.172.67 as permitted sender) client-ip = 138.118.172.67;
Authentication-Results: mx.google.com;
       spf = pass (google.com: domain of marciorubens@dialhost.com.br designates 138.118.172.67 as permitted sender) smtp.mailfrom=marciorubens@dialhost.com.br;
       dmarc = pass (p = NONE sp = NONE dis = NONE) header.from = dialhost.com.br
Received: (qmail 8433 invoked by uid 89); 7 Nov 2017 07:50:25 -0200
Received: (simscan 1.4.0 ppid 8424 pid 8429 t 0.1287s) (scanners:
  attach: 1.4.0 clamav: 0.99.2
/ m: 58 / d: 23753); 07 Nov 0117 09:50:25 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on br118.dialhost.com
X-Spam-Level:
X-Spam-Status: No, score = -1.0 required = 15.0 tests = ALL_TRUSTED, HK_RANDOM_FROM autolearn = ham autolearn_force = no version = 3.4.1
Received: from unknown (HELO? 10.1.1.53?) (Marciorubens@dialhost.com.br)
  by 0 with ESMTPA; 7 Nov 2017 07:50:25 -0200
To: marciorubenscardoso@gmail.com
From: marciorubenswwww@dialhost.com.br
Subject: dddd
Message-ID: <241fe7b7-db09-f65c-f77d-58405c9b6553@dialhost.com.br>
Date: Tue, 7 Nov 2017 07:50:25 -0200
User-Agent: Mozilla / 5.0 (Windows NT 10.0; WOW64; rv: 52.0) Gecko / 20100101 Thunderbird / 52.4.0
MIME-Version: 1.0
Content-Type: text / plain; charset = utf-8; format = flowed
Content-Transfer-Encoding: 7bit
Content-Language: en

Reply | Permalink

FORCEAUTHMAILFROM not check

Roberto Puzzanghera Marcio R November 7, 2017 13:45

yes, it should block emails with a from field different from the auth-user. 

can you please post a telnet session and the run file of your qmail-submission service (I suppose you use this service to authenticate)?

Reply | Permalink

FORCEAUTHMAILFROM not check

Marcio R Roberto Puzzanghera November 7, 2017 16:00

telnet br118.dialhost.com.br 587
Trying 138.118.172.244...
Connected to br118.dialhost.com.br.
Escape character is '^]'.
220 mailf72-br118.dialhost.com.br ESMTP
EHLO dial.teste@dialhost.com.br
250-mailf72-br118.dialhost.com.br
250-STARTTLS
250-PIPELINING
250-8BITMIME
250-AUTH LOGIN PLAIN
250 SIZE 52428800
AUTH LOGIN
334 VXNlcm5hbWU6
ZGlhbC50ZXN0ZUBkaWFsaG9zdC5jb20uYnI=
334 UGFzc3dvcmQ6
NzBRVVFSSE1ldVZ5UU9taVFyOXM=
235 ok, go ahead (#2.0.0)
MAIL FROM:dial.teste2222@dialhost.com.br
250 ok
RCPT TO:marciorubenscardoso@gmail.com
250 ok
DATA
354 go ahead
tESTE
.
250 ok 1510067699 qp 22428
quit
221 mailf72-br118.dialhost.com.br 

#!/bin/sh
QMAILDUID=`id -u vpopmail`
NOFILESGID=`id -g vpopmail`
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
SOFTLIMIT=`cat /var/qmail/control/softlimit`

# You MUST export this, otherwise you'd get a 30 sec timeout
# "!" if you want the submission feature (auth required)
export QMAILQUEUE=/var/qmail/bin/qmail-dkim
export DKIMQUEUE=/var/qmail/bin/simscan
export DKIMVERIFY="FGHKLMNOQRTVWjpu"
export DKIMKEY=/var/qmail/control/domainkeys/%/default
export SMTPAUTH="!"
export FORCETLS=0
export FORCEAUTHMAILFROM=1
export RELAYCLIENT_NODKIMVERIFY=1
# This enables greetdelay for qmail-smtpd.
# comment out if using fail2ban on port 587
#export SMTPD_GREETDELAY=5
#export DROP_PRE_GREET=1

# This enables chkuser
export CHKUSER_START=ALWAYS

# This enables simscan debug
#export SIMSCAN_DEBUG=2

exec /usr/local/bin/softlimit -m "$SOFTLIMIT" \
 /usr/local/bin/tcpserver -v -H -R -l 0 \
 -x /home/vpopmail/etc/tcp.submission.cdb -c "$MAXSMTPD" \
 -u "$QMAILDUID" -g "$NOFILESGID" 0 587 \
 /var/qmail/bin/qmail-smtpd \
 /home/vpopmail/bin/vchkpw /bin/true 2>&1

Reply | Permalink

FORCEAUTHMAILFROM not check

miz Marcio R November 7, 2017 17:22

Hi,

I might me completely wrong, but did you try adding this:

AUTH=1
REQUIRE_AUTH=1
ALLOW_INSECURE_AUTH=0
FORCE_TLS=1

(i have these settings in my submission service file on smtp 587)

Reply | Permalink

FORCEAUTHMAILFROM not check

Roberto Puzzanghera miz November 7, 2017 17:26

but these variables have nothing to do with my patch...

Reply | Permalink

FORCEAUTHMAILFROM not check

miz Roberto Puzzanghera November 8, 2017 09:51

Yes Roberto, of course you are right, but I found a strange behaviour when I installed the run service and I had to set those variable in order to have the submission service  (TLS on 587 with AUTH and CHKUSER) work correctly.

I was just wondering if using AUTH only on TLS (disabling the PLAIN AUTH) would show the same behaviour / error.

Reply | Permalink

FORCEAUTHMAILFROM not check

Roberto Puzzanghera miz November 8, 2017 12:47

if you "grep -r" those variables in the netqmail source code patched with my combined patch you will not find any match, so this can't be an explaination...

Reply | Permalink

FORCEAUTHMAILFROM not check

Roberto Puzzanghera Marcio R November 7, 2017 16:42

Your config seems to be correct and I have almost the same run file in my 2 servers... I've no idea at the moment, if you find a solution let me know please

Reply | Permalink

compile error qmail-remote.c

Ed Vrijmoet October 24, 2017 23:33

I am trying to setup qmail on a fresh install of Debian 9 (stretch) with openssl-1.1.0f

I followed your installation and ran in to trouble at compiling netqmail-1.06 including the roberto patches

see my error list:

./compile qmail-remote.c
In file included from qmail-remote.c:7:0:
substdio.h:12:64: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types]
 #define SUBSTDIO_FDBUF(op,fd,buf,len) { (buf), 0, (len), (fd), (op) }
 ^
qmail-remote.c:173:17: note: in expansion of macro ‘SUBSTDIO_FDBUF’
 substdio ssin = SUBSTDIO_FDBUF(read,0,inbuf,sizeof inbuf);
 ^~~~~~~~~~~~~~
substdio.h:12:64: note: (near initialization for ‘ssin.op’)
 #define SUBSTDIO_FDBUF(op,fd,buf,len) { (buf), 0, (len), (fd), (op) }
 ^
qmail-remote.c:173:17: note: in expansion of macro ‘SUBSTDIO_FDBUF’
 substdio ssin = SUBSTDIO_FDBUF(read,0,inbuf,sizeof inbuf);
 ^~~~~~~~~~~~~~
qmail-remote.c: In function ‘quit’:
qmail-remote.c:290:24: error: dereferencing pointer to incomplete type ‘SSL {aka struct ssl_st}’
 int state = ssl ? ssl->state : SSL_ST_BEFORE;
 ^~
qmail-remote.c:290:34: error: ‘SSL_ST_BEFORE’ undeclared (first use in this function)
 int state = ssl ? ssl->state : SSL_ST_BEFORE;
 ^~~~~~~~~~~~~
qmail-remote.c:290:34: note: each undeclared identifier is reported only once for each function it appears in
qmail-remote.c:291:15: error: ‘SSL_ST_OK’ undeclared (first use in this function)
 if (state & SSL_ST_OK || (!smtps && state & SSL_ST_BEFORE))
 ^~~~~~~~~
qmail-remote.c: In function ‘tls_init’:
qmail-remote.c:536:60: error: dereferencing pointer to incomplete type ‘X509_NAME_ENTRY {aka struct X509_name_entry_st}’
 const ASN1_STRING *s = X509_NAME_get_entry(subj, i)->value;
 ^~
qmail-remote.c: In function ‘mailfrom_cram’:
qmail-remote.c:671:3: warning: implicit declaration of function ‘hmac_md5’ [-Wimplicit-function-declaration]
 hmac_md5(chal.s,chal.len,pass.s,pass.len,digest);
 ^~~~~~~~
Makefile:1675: recept voor doel 'qmail-remote.o' is mislukt
make: *** [qmail-remote.o] Fout 1

Can you help me with this

greetings Ed

Reply | Permalink

look here

Roberto Puzzanghera Ed Vrijmoet October 25, 2017 09:22

try to look here https://github.com/DinoTools/dionaea/issues/90

Reply | Permalink

compile error qmail-remote.c

Ed Vrijmoet Roberto Puzzanghera October 25, 2017 10:41

I am sorry but because I am not a programmer I don't understand what is written so I think that something has changed in openssl-1.1.0 

witch means that something has to change in the file qmail-remote.c the problem is that I don't know what

please help me understand what I have to change

Reply | Permalink

Re:

Roberto Puzzanghera Ed Vrijmoet October 25, 2017 13:21

Provided that I can't do the tests myself because I don't use Debian and I just have openssl-1.0.2k installed, if what reported in that is correct you miss some dependencies. 

So try to install them looking below "STEPS TO REPRODUCE" and compile again

Reply | Permalink

compile error netqmail

Ed Vrijmoet Roberto Puzzanghera October 26, 2017 23:11

Finally i found out how to compile

I had to use libssl1.0.2 as in this link https://github.com/duosecurity/duo_unix/issues/90

thanks very much for your help

Reply | Permalink

compile error netqmail

Ed Vrijmoet Roberto Puzzanghera October 25, 2017 23:28

I have been trying to find out what the problem is with compiling netqmail and what i found is this, all packages related to openssl cannot be compiled with openssl-1.1.0 the syntax off most of the ssl calls is wrong because openssl has changed sinds version 0.9. 

if you want to compile with openssl-1.1.0 then you have to rewrite all the .c and .h files with openssl calls in them.

qmail-remote.c ssl-timeoutio.c qmail-smtpd.c dkimsign.h dkimverify.h dkimfunc.cpp to name a few.

on debian 9 there is no old version of openssl and it is discouraged to use old versions.

so the only way to use qmail is to compile it on an old depracated linux system because all new versions will be with openssl-1.1 and higher.

thank you very much for your anwser.

Reply | Permalink

Subdomains emails errors

Marcio August 9, 2017 18:53

When sent an email to yyy@xx.domain.com the sending is performed as yyy@domain.com, returning error.
Any tips for correction?

Reply | Permalink

Never seen this error

roberto puzzanghera Marcio August 9, 2017 20:14

I've never seen this error. Are you using my combined patch?

Reply | Permalink

test erro

Marcio roberto puzzanghera August 10, 2017 13:00

Yes. I'm using it.
How do you make a submission test and see if it is occurring in your installation account?
Please send a test to gustavo.ribes@br.cobogroup.net

Reply | Permalink

It appears that your server

roberto puzzanghera Marcio August 10, 2017 13:16

It appears that your server is an exim MTA. I can't be of any help, sorry

Reply | Permalink

not Exim

Marcio roberto puzzanghera August 10, 2017 13:26

My server is a qmail and installed with your indicated patches

When I send emails to the email gustavo.ribes@br.cobogroup.net it removes br and returns errors informing that user gustavo.ribes@cobogroup.net does not exist.

Can you send a test email?

Reply | Permalink

Sending a test mail

roberto puzzanghera Marcio August 10, 2017 14:55

Sending a test mail returns an error message from mx1.cobospa.it which says that xxx@cobogroup.net does not exist.

What about that mx1.cobospa.it server? It appears to be a Sophos platform... maybe you have to check that all the MTAs that are routing your mails are configured to forward br.cobogroup.net to you

Reply | Permalink

Patched and working

John Trolinger July 19, 2017 22:44

We have the Latest stable combined patch for netqmail-1.06 v. 2017.05.14  and everything is looking good. 

To compile I did have to manually kill some VPOPMAIL processes that were tying up qmail-smtp.  The error was

install: fatal: unable to write .../bin/qmail-smtpd: text busy

Thank you Roberto!

Reply | Permalink

Bug in TLS patch

Eugene September 17, 2016 08:30

qmail-tls patch is buggy. qmail-remote server cert checking logic if configured through tlshosts/ is broken  - it'll consider *any* valid cert even if none of the alt/common names matches.

Somthing like this should fix this:

diff --git a/qmail-remote.c b/qmail-remote.c

index 40dbd31..f6b13b2 100644
--- a/qmail-remote.c
+++ b/qmail-remote.c
@@ -494,6 +494,7 @@ int tls_init()
     X509 *peercert;
     STACK_OF(GENERAL_NAME) *gens;
     int found_gen_dns = 0;
+    int matched = 0;

     int r = SSL_get_verify_result(ssl);
     if (r != X509_V_OK) {
@@ -517,7 +518,10 @@ int tls_init()
         const GENERAL_NAME *gn = sk_GENERAL_NAME_value(gens, i);
         if (gn->type == GEN_DNS){
           found_gen_dns = 1;
-          if (match_partner(gn->d.ia5->data, gn->d.ia5->length)) break;
+          if (match_partner(gn->d.ia5->data, gn->d.ia5->length)) {
+            matched = 1;
+            break;
+          }
         }
       }
       sk_GENERAL_NAME_pop_free(gens, GENERAL_NAME_free);
@@ -540,6 +544,9 @@ int tls_init()
         out("ZTLS unable to verify server "); out(partner_fqdn);
         out(": received certificate for "); outsafe(&peer); TLS_QUIT;
       }
+    } else if (!matched) {
+      out("ZTLS unable to verify server ");
+      tls_quit(partner_fqdn, "certificate contains no matching names");
     }

     X509_free(peercert);

Reply | Permalink

Missing features.h on FreeBSD 10.2

bzero November 5, 2015 14:57

Hi,

I applied latest patch for netqmail, then #make and receive error missing features.h, how could i solve this?

Also tried with older patch, and got the same error :(

i am using FreeBSD 10.2 64bit

Thank you.

Reply | Permalink

still no luck with many

bzero bzero November 5, 2015 17:58

still no luck with many attempts, google didn't return positive result on this matter :(

Reply | Permalink

Someone in the past already

roberto puzzanghera bzero November 5, 2015 19:03

Someone in the past already mentioned that my patch is not freebsd compliant. Unfortunately I don't have any freebsd machine to do tests. 

Reply | Permalink

i could prepare a server for

bzero roberto puzzanghera November 6, 2015 05:27

i could prepare a server for you to test it.
I will send you an email include account shortly.

Thanks a lot.

Reply | Permalink

Hi bzero

roberto puzzanghera bzero November 6, 2015 10:36

Hi bzero, thank you but this is not that kind of thing that I can do for free..

Reply | Permalink

Ciao Roberto and hi to all

miz November 3, 2015 14:09

Ciao Roberto and hi to all the qmail users,

here I'm again with a STRANGE problem occurring. I recently upgrade to the latest patch here, and I think that this is causing a problem:

2014-11-15
-modified the QUEUE_EXTRA variable in extra.h to record the Message-ID in the qmail-send's log. Thanks to Simone for the hint.

I have an account on my domain named log@[domain].[net]. Every single mail get copied to this account since the upgrade !

I'm basically running into this configuration (http://cr.yp.to/qmail/faq/admin.html#copies)

----------------------------

How do I keep a copy of all incoming and outgoing mail messages?

Answer: Set QUEUE_EXTRA to "Tlog\0" and QUEUE_EXTRALEN to 5 in extra.h. Recompile qmail. Put ./msg-log into ~alias/.qmail-log.

You can also use QUEUE_EXTRA to, e.g., record the Message-ID of every message: run

     | awk '/^$/ { exit } /^[mM][eE][sS][sS][aA][gG][eE]-/ { print }'

from ~alias/.qmail-log.

----------------------------

I tried to remove the /var/qmail/alias/.qmail-log but nothing happens.

Is there a way to disable/reconfigure this feature without recompiling ? If not, how can I remove that extra.h declaration in order to recopile without that feature ?

Thank you !

Reply | Permalink

you have to reverse that patch

roberto puzzanghera miz November 4, 2015 21:42

you have to reverse that patch. simply replace extra.h with the original file and recompile. also remove .qmail-log

Reply | Permalink

Thank you Roberto. I was

miz roberto puzzanghera November 5, 2015 10:09

Thank you Roberto. I was looking into a solution to keep the feature and disable it run-time; I will try with:

Set QUEUE_EXTRA to "Tlogother\0" and QUEUE_EXTRALEN to 8 in extra.h

to have the logging feature ready into the "logother@domain" alias. Otherwise I will just reverse the patch as you suggest and remove the feature.

Thank you !

Reply | Permalink

extra.h

John miz July 7, 2016 00:19

It is okay to enter the entire email address.  Just change the length number to the number of characters minus 1.

#ifndef EXTRA_H

#define EXTRA_H

#define QUEUE_EXTRA "Tlog@co.ker.tx.us\0"
#define QUEUE_EXTRALEN 18

#endif

Reply | Permalink

Woops! Not idiot proof.

George Cooke October 1, 2015 20:51

Thanks Roberto for your hard work and excellent guide on qmail.

I am installing qmail for the first time on Debian and I got to the 'finally install and start qmail' (make setup check, qmailctl start) part on this page, but qmailctl did run as it did not exist.

So I just spent an hour stressing out trying to work out why qmailctl and supervise scripts didn't exist, and got it working on my own from LWQ, then came back here to continue and realised that you provide exact instructions for qmailctl and the supervise stuff to get it running in the next page, the configuration section!! OMG!! I am such an idiot, I know I should have read the whole guide first perhaps but I think maybe you should could indicate something around the finally install & start part to stop idiots from me wasting hours thinking their installation is messed up.

Thanks so much!

Reply | Permalink

Woops! Not idiot proof.

GoofY George Cooke April 10, 2019 02:43

THNX was fighting the same thing, because the cmd qmailctl was mentioned in the guide...

Reply | Permalink

Woops! Not idiot proof.

Roberto Puzzanghera GoofY April 10, 2019 07:48

OK, I added a warning :-)

Reply | Permalink

:-)))

roberto puzzanghera George Cooke October 1, 2015 20:52

:-)))

George, you had to be very tired, not idiot, and I think that in  a normal situation this should not happen to you.

BTW I think it's not a good idea to add such obvious instructions, someone would be offended.. In addition the "install page" is just in the 4th page of the guide and the readers should consider all the following pages, as you already pointed out.

Reply | Permalink

smtproutes - smtp-auth

nic August 16, 2015 12:52

Dear  Roberto,

I have a box A which was sending spams as one of the email accounts was compromised because of a weak password.

The IP was blacklisted and to prevent more undelivered emails, i had decided to use box B to relay emails.

In box B, I had created an email account relay@boxb.com with password secret.

In box A, I had created the file smtproutes in /var/qmail/control/ and added an entry like this:-

domain1.com:smtp.boxb.com relay@boxb.com secret

Emails from domain1.com are now relaying fine. In box A, i have about 60 domains and being lazy i decided to change the extry of smtproutes (box A) from domain1.com:smtp.boxb.com relay@boxb.com secret to :smtp.boxb.com relay@boxb.com secret

But now i started to get the below error

<email@remotedomain.com>:
Sorry, I couldn't find any host named smtp.boxb.com?relay@boxb.com?secret. (#5.1.2)

What is wrong with my smtproutes? And is this the best way workaround until i had removed box A's IP from the blacklists?

regards

nic

Reply | Permalink

Nic, the man page says that

roberto puzzanghera nic August 16, 2015 18:04

Nic, the man page says that the correct syntax should be

:smtp.boxb.com|relay@boxb.com|secret

Reply | Permalink

smtproutes

nic roberto puzzanghera January 27, 2023 16:04

Hi Roberto,

Is the below syntax still working?

domain1.com:smtp.boxa.com|relay@boxa.com|secret
domain2.com:smtp.boxb.com|relay@boxb.com|secret

Thanks

Reply | Permalink

smtproutes

Roberto Puzzanghera nic January 27, 2023 19:25

Hi, I think yes. I don't think it has been modified. I'm using it just without pwd. Is it not working?

Reply | Permalink

smtproutes

nic Roberto Puzzanghera January 31, 2023 16:39

Not sure why it is not working for me. No bounce message.

Is there a command whereby certain domains uses local delivery whereas others use mulitple relays? Maybe i can troubleshoot from here.

Eg.

domain1.com:local
domain2.com:smtp.boxa.com|relay@boxa.com|secret
domain3.com:smtp.boxb.com|relay@boxb.com|secret

Thanks

Reply | Permalink

smtproutes

Roberto Puzzanghera nic February 1, 2023 10:11

Nic, 

domain1.com:

will route it to its own mx

Do you have Auth enabled on qmail-smtpd?

Reply | Permalink

smtproutes

Roberto Puzzanghera nic January 31, 2023 16:45

I don't know... I have to test it but I haven't got the time these days... sorry. Let me know if you solve

Reply | Permalink

Thanks Roberto!It is

nic roberto puzzanghera August 16, 2015 18:33

Thanks Roberto!

It is working good. Is this the best method for my case until i can get the IP delisted?

thanks again

nic

Reply | Permalink

I think is good enough. But

roberto puzzanghera nic August 16, 2015 18:42

I think is good enough. But in my opinion the most important thing is to recognize why that pwd was stolen.. was a simple multiple trial via imap or submission port? In that case use fail2ban. Or it was an sql exploit by means of a security hole in one of your hosted websites?

Reply | Permalink

The user was using 1234 as

nic roberto puzzanghera August 16, 2015 18:45

The user was using 1234 as the password. Sigh!

Many thanks again, Roberto!

Reply | Permalink

I recently published a pwd

roberto puzzanghera nic August 16, 2015 18:51

I recently published a pwd patch for qmailadmin, I think it can enforce the pwd complexity even though it is very rudimental. Are you using fail2ban as suggested?

Reply | Permalink

I saw the patch. Applying it

nic roberto puzzanghera August 16, 2015 19:20

I saw the patch. Applying it now.

Thanks

nic

Reply | Permalink

Is the patch in this

nic roberto puzzanghera August 16, 2015 18:54

Is the patch in this tutorial? Let me read through again and let me add this into my present build. And yes i am using fail2ban.

regards

nic

Reply | Permalink

can not start up qmail-send

xia0sheng March 14, 2015 14:43

dear roberto

I use centos7.0 to install the qmail,if i do not install the qmail patching netqmail-1.06, the qmail stat run properly,, but I can only sent mail to my own server and receive email from other mail server, can not sent mail to other mail server(i think it is the qmail auth problem).

But, when I installed the netqmail patch roberto-netqmail-1.06.patch-latest.gz(for qmail auth?), when i enter the commond qmailctl start , qmail-send can not up,and qmail-send PID are change(after each enter commond qmailctl stat), and if i enter the commond "top" ,i find a lot of qmail-todo process, the server becomes very slow, how can i do? Thank you.

A little summary

1, if i do not install roberto-netqmail-1.06.patch-latest.gz, i can send mail to my mail server and receive mail from other mail server(some@somemail.com to my@mymail.com),i can not send mail to other mail.

2, after the installation of roberto-netqmail-1.06.patch-latest.gz, qmail-send cannot open normally, have been varied number between 0 second and 1 second, the server CPU is very high.

Can you give me any suggestion on this matter? Thanks very much?

Reply | Permalink

Hi xia0sheng, as mentioned

roberto puzzanghera xia0sheng March 14, 2015 14:57

Hi xia0sheng,

as mentioned above, the TODO patch included in my package may require that the queue has to be rebuilt. So, if you are sure that there are no messages in your queue, because it's just a testing server, stop qmail and try to kill all your qmail-todo processes like this

qmailctl kill

if those processes are still alive kill them manually.

Then erase your queue

rm -rf /var/qmail/queue

Now you can recompile qmail and restart

Let me know if this solved your issue

Reply | Permalink

a lot qmail-todo process problem is also resolve

xia0sheng roberto puzzanghera March 19, 2015 05:26

ldconfig -p|grep libsrs2

the server is centos7.0, if  I patching "roberto-netqmail-1.06.patch-latest.gz"  the qmail-send can not up

the problem is  libsrs2, after install libsrs2

enter the command:

ldconfig -p|grep libsrs2

there is no result

the resove is

1. vim /etc/ld.so.conf

2. add  /usr/local/lib

3. save

4. ldconfig

5.  ldconfig -p|grep libsrs2

the result will be correct.

Reply | Permalink

I had built a new toaster on

nic xia0sheng July 20, 2015 05:34

I had built a new toaster on a VPS and also got flooded by qmail-todo which Roberto had mentioned.

"Be sure that libsrs2 is actually linked, otherwise you are going to have a qmail-send infinite crash and finally an auto-DoS"

I tried xia0sheng method and it did not work, maybe this is a CentOS 6.

So i added a custom file in /etc/ld.so.conf.d/

vim /etc/ld.so.conf.d/custom.conf

add the location of the libsrs2 library and mine is in /usr/local/lib

save

ldconfig
ldconfig -p|grep libsrs2

And the result

libsrs2.so.0 (libc6,x86-64) => /usr/local/lib/libsrs2.so.0
libsrs2.so (libc6,x86-64) => /usr/local/lib/libsrs2.so

My floodings stopped.

This might be a better because my library for libev is also in the folder /usr/local/lib

ldconfig -p|grep libev

libev.so.4 (libc6,x86-64) => /usr/local/lib/libev.so.4
libev.so.4 (libc6,x86-64) => /usr/lib64/libev.so.4
libev.so (libc6,x86-64) => /usr/local/lib/libev.so

Just my $0.02

Reply | Permalink

Thanks a lot. I found the same problem

Ruben Garcia nic December 8, 2018 13:10

Thanks a lot.

Your solution worked for me.

Ruben

Reply | Permalink

Many thanx, had the same

fasu xia0sheng March 26, 2015 14:57

Many thanx, had the same qmail-todo problem

Reply | Permalink

still not work

xia0sheng roberto puzzanghera March 15, 2015 05:28

dear  roberto

Thanks very much for your reply. I did as what you say, but the problem is still.

In fact , i remove the /var/qmail/queue of my installtion in my before install path.

I did as you say but when i enter the commond qmailctl stat , the qmail-send still can no up normal. and the log in /var/log/qmail/send/current  has no any error log.  where can i find the error log of qmail-send of the qmailctl stat?

i have another question, if i install the qmail before, but i want to delete it and rebuilt it . Is it ok  just delete the /var/qmail and /usr/local/src/netqmal-1.06 folder? and then make and path /usr/local/src/netqmail-1.06? Is there anything file or folder i should delete if i want rebuilt qmail?   or  should  i reinstall my linux server?

i think maybe it is the problem of my centos7.0 system .

i just learn qmail very little time, a lot of configure i do'not known .

can you give me some advice about what can i do?

wish you have a nice weekend!

Reply | Permalink

dear xia0sheng, I suppose

roberto puzzanghera xia0sheng March 15, 2015 09:01

dear xia0sheng, I suppose that you recompiled qmail after erasing your queue. This is very strange. If I understand well

1. you stopped qmail, erased the queue and you have no more qmail-todo processes alive
2. recompiled qmail
3. started qmail
4. you have /var/log/qmail/send/current is empty

is it right?

When you want to recompile just follow this steps. I suppose that you have a folder with a patched qmail

1. qmailctl stop
2. erease the queue if it is the first time you install my patch
3. cd to the source dir
4. make clean
5. make setup check (this will overwrite everything and rebuild the queue)
6. qmailctl start

Reply | Permalink

use auth_tls_force-tls.patch-latest pathing is ok

xia0sheng roberto puzzanghera March 15, 2015 12:48

Dear roberto:

I did as what you say, but the problem is still. So I change use the "roberto-netqmail-1.06_auth_tls_force-tls.patch-latest" and everything is ok.

But i still cannot send mail to other email accounts?i can send email to my server and recevie mail form other email account?

the error is "Please check the email , server reply: 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)" If I write 163.com to the file /var/qmail/control/tcpthosts, I can sent email to my mail.163.com account.

I known it is maybe the qmail-auth problem? but i do'not konwn how to solve it.

can you give me some addvice?

Thuanks very much!

Reply | Permalink

I can't be of much help if

roberto puzzanghera xia0sheng March 15, 2015 12:59

I can't be of much help if you don't try to provide details of what is happening to your server. You forgot to reply to my previous questions...

Concerning your new problem, your localhost must have the RELAYCLIENT flag in your tcp.smtp and tcp.submission. You should read the "tcprules" page. I suggest you to read carefully everything once again and perform all tests in the "Testing" page; I can assure that it works :)

Reply | Permalink

i'm sorry for previous question

xia0sheng roberto puzzanghera March 15, 2015 14:37

1. you stopped qmail, erased the queue and you have no more qmail-todo processes alive 

    I stop qmail, erased the queue, but because of i don't known i to kill the many qmail-todo process?before you tell me use             qmailctl kill?, i use reboot my server to kill the qmail-todo process. I don't known why every of my reboot , I should first enter commond svscanboot & (it's can not auto startup)and then the qmail can start.(of course i enter svscanboot & after the pathing the qmail ) 
2. recompiled qmail

yes

3. started qmail

yes

4. you have /var/log/qmail/send/current is empty

yes

is it right?(all of right except 1)

When you want to recompile just follow this steps. I suppose that you have a folder with a patched qmail

1. qmailctl stop
2. erease the queue if it is the first time you install my patch
3. cd to the source dir
4. make clean
5 .make setup check (this will overwrite everything and rebuild the queue)
6 .qmailctl start

then i did all of you said above, but it is still have the qmail-send problem(can not up)

after pathing your full pathing"roberto-netqmail-1.06.patch-latest.gz" 

the later i do is :

7. svscanboot &

8. qmailctl start

9.qmailctl stat  

    the status is 

/service/qmail-send: up (pid 11702) 1 seconds
/service/qmail-send/log: up (pid 11592) 8 seconds
/service/qmail-smtpd: up (pid 11584) 8 seconds
/service/qmail-smtpd/log: up (pid 11587) 8 seconds
/service/qmail-submission: up (pid 11586) 8 seconds
/service/qmail-submission/log: up (pid 11591) 8 seconds
/service/vpopmaild: up (pid 11583) 8 seconds
/service/vpopmaild/log: up (pid 11585) 8 seconds

messages in queue: 0

messages in queue but not yet preprocessed: 0

10. qmailctl stat again

/service/qmail-send: up (pid 11742) 1 seconds
/service/qmail-send/log: up (pid 11592) 10 seconds
/service/qmail-smtpd: up (pid 11584) 10 seconds
/service/qmail-smtpd/log: up (pid 11587) 10 seconds
/service/qmail-submission: up (pid 11586) 10 seconds
/service/qmail-submission/log: up (pid 11591) 10 seconds
/service/vpopmaild: up (pid 11583) 10 seconds
/service/vpopmaild/log: up (pid 11585) 10 seconds
messages in queue: 0
messages in queue but not yet preprocessed: 0

so it can not work.

and i use your "roberto-netqmail-1.06_auth_tls_force-tls.patch-latest"   every is ok except send mail to other mail server.

the /home/vpopmail/etc/tcp.smtp is

10.0.0.:allow,RELAYCLIENT=""
127.:allow,RELAYCLIENT=""

the /home/vpopmail/etc/tcp.smtp is

:allow,CHKUSER_WRONGRCPTLIMIT="3"

if i send mail to other mail acount, the error is

Please check the email <wangyouyu6@163.com>, server reply: 553 sorry, that domain isn't in my list of allowed rcpthosts; no valid cert for gatewaying (#5.7.1)

i reread your testing carefully tomorrow to find if solve my problem.

Thanks very much.

and if you will i can give you my mail server test acount, you enter my mail server and see what happen(i have no problem about this, because the mail server is just a test server )

if you want this, i can send you the test acount and password about my mail server.(can you receive mail about your mail acountroberto.puzzanghera@sagredo.eu?) and my email acount is wangyouyu6@163.com

Reply | Permalink

i'm sorry for previous question

carlos h xia0sheng September 3, 2021 13:56

hi roberto,

I m exactly in the same point as xia0sheng in 2015, how did you resolve it?

many thanks and kind regards

Reply | Permalink

i'm sorry for previous question

Carlos carlos h September 3, 2021 15:11

 I explain me better my problem. All seems fine, less when I try to send an email, it remains in the queue and lots of qmail-todo appears when I execute "top". Seems that is entered in an infinite loop.

I checked the log:

cat /var/log/qmail/smtpd/current

@400000006131272939ba7eec qlogreceived: result=accepted code=250 reason=queueaccept detail= helo=localhost mailfrom=carlos@autoexaming.com rcptto=chernandez@webfutura.online relay=yes rcpthosts= size=91 authuser= authtype= encrypted= sslverified=no localip=127.0.0.1 localport=25 remoteip=127.0.0.1 remoteport=35356 remotehost=localhost qp=1999 pid=1998

I believe the problem is in the part "remoteip=127.0.0.1" and "remotehost=localhost" but I dont how can I fix it.

I cleaned the queue, and patched, and recompiled qmail

Reply | Permalink

srs check

Roberto Puzzanghera Carlos September 3, 2021 16:35

can you do this and post the response please?

ldconfig -p|grep libsrs2

then check the srs.c in your source dir and check that the same dir is reported there, For example

#include </usr/local/include/srs2.h>

Reply | Permalink

srs check

carlos h Roberto Puzzanghera September 4, 2021 09:04

In srs.c

#include </usr/local/include/srs2.h>

Reply | Permalink

srs check

carlos h Roberto Puzzanghera September 4, 2021 08:51

I think this is fine, and for some reason is ignoring rcpthosts, because in the log shows "rcpthosts=" not "rcpthosts=yes"

# ldconfig -p|grep libsrs2
libsrs2.so.0 (libc6,x86-64) => /usr/local/lib/libsrs2.so.0
libsrs2.so (libc6,x86-64) => /usr/local/lib/libsrs2.so

Reply | Permalink

srs check

Roberto Puzzanghera carlos h September 4, 2021 10:20

rcpthost= is normal, but I agree that it should advertise that it considered the domain as rcpthost. This is eventually an issue of the log line verbosity.

Reply | Permalink

i'm sorry for previous question

Roberto Puzzanghera carlos h September 3, 2021 14:14

Hi Carlos,  can you please describe what is the issue in your server, please? I read the above from xiao and it is not clear to me...

Reply | Permalink

i'm sorry for previous question

carlos h Roberto Puzzanghera September 3, 2021 15:57

I m not absolutely secure, but I think there is a bug in the patch: roberto-netqmail-1.06.patch-2021.08.22 on chkuser part (I dont know if is a part of my previous problem)

On line 456 says:

+ hostname the value of "TCPREMOTEHOST"

and I believe it must be:

+ remotehostname the value of "TCPREMOTEHOST"

I dont know if after in some point the variable name is toggled or not, and if it causes the mistake to loop with my qmail-todo process

Reply | Permalink

i'm sorry for previous question

Roberto Puzzanghera carlos h September 3, 2021 16:32

but CHKUSER.log_format is just an info file, which is not part of the program...

Reply | Permalink

i'm sorry for previous question

carlos Roberto Puzzanghera September 3, 2021 17:31

Yes, you are right.

Sorry I wrote above as anonymous. When I send an email from my server (autoexaming.com) to an external domain (webfutura.online) In my /var/log/qmail/smtpd/current appears a connection from 127.0.0.1 to 127.0.0.1

@4000000061322839241167f4 qlogreceived: result=accepted code=250 reason=queueaccept detail= helo=localhost mailfrom=carlos@autoexaming.com rcptto=chernandez@webfutura.online relay=yes rcpthosts= size=88 authuser= authtype= encrypted= sslverified=no localip=127.0.0.1 localport=25 remoteip=127.0.0.1 remoteport=33472 remotehost=localhost qp=1287 pid=1279
@400000006132283b0c98c504 tcpserver: end 1279 status 0
@400000006132283b0c98d4a4 tcpserver: status: 0/200
@4000000061324c30147e1224 tcpserver: status: 0/200
@4000000061324c873434d094 tcpserver: status: 1/200
@4000000061324c8734399f0c tcpserver: pid 8425 from 127.0.0.1
@4000000061324c873446b2b4 tcpserver: ok 8425 autoexaming.com:127.0.0.1:25 localhost:127.0.0.1::33550
@4000000061324cc330c129bc tcpserver: end 8425 status 0
@4000000061324cc330c1395c tcpserver: status: 0/200

Reply | Permalink

i'm sorry for previous question

Roberto Puzzanghera carlos September 3, 2021 23:19

What do you have in your control/rcpthosts?

Please reply also to the other comment of mine here https://notes.sagredo.eu/en/qmail-notes-185/patching-qmail-82.html#comment2223

Reply | Permalink

i'm sorry for previous question

carlos h Roberto Puzzanghera September 4, 2021 08:42

thank you so much in advance for your great job :)

(In my case I preferred domain without smtp. prefix in all vars, and when generated cert i wrote the same)

$ cat /var/qmail/control/rcpthosts
autoexaming.com

Reply | Permalink

i'm sorry for previous question

Roberto Puzzanghera carlos h September 4, 2021 10:33

remoteip=127.0.0.1 remotehost=localhost is normal as you are connecting to localhost from localhost. If you connect to your server from another server, because you want to send an email after the auth, then you will see the remote ip in remoteip, but this is mainly for the submission service.

Concerning your rcpthosts issue... sorry if I ask... are you sure not to have changed rcpthosts and forgot to restart qmail?

Concerning the todo loop (it seems to be a separate problem) what do you have in your queue? How many msg?

Reply | Permalink

i'm sorry for previous question

carlos Roberto Puzzanghera September 4, 2021 13:09

First of all, thanks a lot for your affords :)

1) I m trying to send from my localhost to an external server (a hosting, that is working fine, not mine)

2) Concerning your rcpthosts issue... sorry if I ask... are you sure not to have changed rcpthosts and forgot to restart qmail?

Yes, indead i recompiled all, many times in the last days

3) Concerning the todo loop (it seems to be a separate problem) what do you have in your queue? How many msg?

It is half-solved for me, just enter in the loop when i do qmailctl restart. When I want restart qmail, reboot the computer.

I tried to do this test: https://notes.sagredo.eu/en/qmail-notes-185/testing-qmail-smtp-and-auth-22.html#vpopmail

In the test: "No valid MX test, mailbox syntax test" I get some strange:

# telnet 127.0.0.1 25
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
220 autoexaming.com ESMTP
mail from: unexistent@fakedomain.xxx
553 5.1.7 sorry, mailbox syntax not allowed (chkuser)
mail from: unexistent@fake_domain.xxx
553 5.1.7 sorry, mailbox syntax not allowed (chkuser)
quit

in the first case according with the test example, it should be:

mail from: unexistent@fakedomain.xxx
550 5.1.8 sorry, can't find a valid MX for sender domain (chkuser)

Reply | Permalink

i'm sorry for previous question

Roberto Puzzanghera carlos September 4, 2021 16:24

your server looks very bad as many different (apparently unrelated) issues appear

I think it's better if you write me in private and continue there the investigation. Once solved we'll post here the solution

Reply | Permalink

ok, let me know once you have

roberto puzzanghera xia0sheng March 15, 2015 15:01

ok, let me know once you have finished to double check everything

Reply | Permalink

Everything is ok, Thanks very much.

xia0sheng roberto puzzanghera March 19, 2015 04:15

dear  roberto:

      Thanks very much, now everything is ok.  i can use roundcube to send and receive mail.

      the problem is the configure of  roundcube   configure.inc.php file

      i  chose "Use the current IMAP username and password for SMTP authentication"  and then i can send mail to other mail account.

     thanks very much for the helps these days.

     Thanks very much....

     from:xia0sheng

Reply | Permalink

still have problems

xia0sheng roberto puzzanghera March 17, 2015 13:15

dear roberto:

i check everything carefully, but still have some problems.

I can use foxmail  to send and receive mail to or from other  mail acounts.

the setting is:

send server:smtp.wangyouyu.cn,

ssl(not select)

port is 587

and i should select use STARTTLS. If the setting is this, every is ok.

but if I don't select use STASTTLS, if i send mail the error is "538 auth not available without TLS (#5.3.3)"

and in the roundcube webmail the config.inc.php is 

<?php

/* Local configuration for Roundcube Webmail */

// ----------------------------------
// SQL DATABASE
// ----------------------------------
// Database connection string (DSN) for read+write operations
// Format (compatible with PEAR MDB2): db_provider://user:password@host/database
// Currently supported db_providers: mysql, pgsql, sqlite, mssql or sqlsrv
// For examples see http://pear.php.net/manual/en/package.database.mdb2.intro-dsn.php
// NOTE: for SQLite use absolute path: 'sqlite:////full/path/to/sqlite.db?mode=0646'
$config['db_dsnw'] = 'mysql://temp:XXXXXXX@localhost/roundcubemail';

// ----------------------------------
// IMAP
// ----------------------------------
// The mail host chosen to perform the log-in.
// Leave blank to show a textbox at login, give a list of hosts
// to display a pulldown menu or set one host as string.
// To use SSL/TLS connection, enter hostname with prefix ssl:// or tls://
// Supported replacement variables:
// %n - hostname ($_SERVER['SERVER_NAME'])
// %t - hostname without the first part
// %d - domain (http hostname $_SERVER['HTTP_HOST'] without the first part)
// %s - domain name after the '@' from e-mail address provided at login screen
// For example %n = mail.domain.tld, %t = domain.tld
// WARNING: After hostname change update of mail_host column in users table is
//          required to match old user data records with the new host.
$config['default_host'] = 'smtp.wangyouyu.cn';

// ----------------------------------
// SMTP
// ----------------------------------
// SMTP server host (for sending mails).
// To use SSL/TLS connection, enter hostname with prefix ssl:// or tls://
// If left blank, the PHP mail() function is used
// Supported replacement variables:
// %h - user's IMAP hostname
// %n - hostname ($_SERVER['SERVER_NAME'])
// %t - hostname without the first part
// %d - domain (http hostname $_SERVER['HTTP_HOST'] without the first part)
// %z - IMAP domain (IMAP hostname without the first part)
// For example %n = mail.domain.tld, %t = domain.tld
$config['smtp_server'] = 'smtp.wangyouyu.cn';

// SMTP port (default is 25; use 587 for STARTTLS or 465 for the
// deprecated SSL over SMTP (aka SMTPS))
$config['smtp_port'] = 587;

// provide an URL where a user can get support for this Roundcube installation
// PLEASE DO NOT LINK TO THE ROUNDCUBE.NET WEBSITE HERE!
$config['support_url'] = '';

// this key is used to encrypt the users imap password which is stored
// in the session record (and the client cookie if remember password is enabled).
// please provide a string of exactly 24 chars.
$config['des_key'] = 'al=t9fl&8A&Y+0D4rhipphsN';

// Automatically add this domain to user names for login
// Only for IMAP servers that require full e-mail addresses for login
// Specify an array with 'host' => 'domain' values to support multiple hosts
// Supported replacement variables:
// %h - user's IMAP hostname
// %n - hostname ($_SERVER['SERVER_NAME'])
// %t - hostname without the first part
// %d - domain (http hostname $_SERVER['HTTP_HOST'] without the first part)
// %z - IMAP domain (IMAP hostname without the first part)
// For example %n = mail.domain.tld, %t = domain.tld
$config['username_domain'] = 'wangyouyu.cn';

// Name your service. This is displayed on the login screen and in the window title
$config['product_name'] = 'xxxxxxx????';

// ----------------------------------
// PLUGINS
// ----------------------------------
// List of active plugins (in plugins/ directory)
$config['plugins'] = array('acl', 'additional_message_headers', 'archive', 'attachment_reminder', 'autologon', 'database_attachments', 'debug_logger', 'emoticons', 'enigma', 'example_addressbook', 'filesystem_attachments', 'help', 'hide_blockquote', 'http_authentication', 'identity_select', 'jqueryui', 'legacy_browser', 'managesieve', 'markasjunk', 'new_user_dialog', 'new_user_identity', 'newmail_notifier', 'password', 'redundant_attachments', 'show_additional_headers', 'squirrelmail_usercopy', 'subscriptions_option', 'userinfo', 'vcard_attachments', 'virtuser_file', 'virtuser_query', 'zipdownload');

// the default locale setting (leave empty for auto-detection)
// RFC1766 formatted language name like en_US, de_DE, de_CH, fr_FR, pt_BR
$config['language'] = 'zh_CN';

in the webmail if i send mail to other mail acounts

the error is "SMTP error: [553] sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)"

How can I set the roundcube use STARTTLS as foxmail setting?

thank very much.

I really don't konwn what to do now. 

Reply | Permalink

qmail-smtpd: read failed: (null) only with one sender

Marc January 2, 2015 12:29

Hello Roberto,

i have a problem with mails coming from amazon. Every Mail send from amazon is not delivered because it shows the error qmail-smtpd: read failed. This error only happen with mails from the amazon mail servers, i do not have this eror with other mails. I have no clue whats wrong -  do you have an idea? Output from Log File:

tcpserver: pid 18422 from 54.240.0.89
tcpserver: ok 18422 0:::ffff:5.9.211.13:25 :54.240.0.89::32891
CHKUSER accepted sender: from <20141222011816fe8d1176403e4a1da936071f1208d53f-C24F0W6MS7QTYP@bounces.amazon.com|remoteinfo/auth:|chkuser-identify:> remote <helo:a0-89.smtp-out.eu-west-1.amazonses.com|remotehostname:unknown|remotehostip:54.240.0.89> rcpt <> : sender accepted
tcpserver: status: 1/20
qmail-smtpd: read failed: (null) from 54.240.0.89 to 20141222011816fe8d1176403e4a1da936071f1208d53f-C24F0W6MS7QTYP@bounces.amazon.com helo a0-89.smtp-out.eu-west-1.amazonses.com
tcpserver: end 18422 status 256

Regards,

Marc

Reply | Permalink

I think you should record the

roberto puzzanghera Marc January 3, 2015 11:06

I think you should record the smtp conversation enabling recordio in your run file. Let me know if you solve

Reply | Permalink

qmail-smtpd read failed - SPF Check was the problem

Marc roberto puzzanghera January 3, 2015 16:55

Hello Roberto,

thanks for the hint with recordio. I figured out that the SPF check was the problem:

@4000000054a81075289ded24 9091 > 451 SPF lookup failure (#4.3.0)
@4000000054a8107529ddac9c 9091 < RSET
@4000000054a8107529de0674 9091 > 250 flushed

When i changed the /var/qmail/control/spfbehavior entry to 1 mail from amazon get thru and i noticed, that it take some time to process the mail.

I tried a manual spfquery for the amazon mail and the check take about 70 sec. So i think that the check takes to long and the qmail-smtp process take this as an timeout and reject the mail because of that. Other spf checks to other domains are working fast. Maybe i should try to change the dns server entry? But it is strange that this happens only to amazon servers.

Thanks for helping.

Reply | Permalink

  I would try a test

roberto puzzanghera Marc January 3, 2015 22:58

I would try a test like

dig amazon.com txt

and see if you get a timeout error or not

Reply | Permalink

qmail-send fail

huyenha December 6, 2014 17:15

Dear Roberto

I completely followed your notes, my email server can send email to another domain but cannot deliver to local account.

I've try to send from huyenha to nxhuy (2 accounts already created and loged in sucsessful) but it said: 

failure: Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/

qmail-send log:

@4000000054832f6635627354 new msg 2754774
@4000000054832f6635627b24 info msg 2754774: bytes 1228 from <huyenha@4trust.vn> qp 2158 uid 89
@4000000054832f6635627f0c starting delivery 1: msg 2754774 to local log@4trust.vn
@4000000054832f6635627f0c status: local 1/10 remote 0/20
@4000000054832f66356282f4 starting delivery 2: msg 2754774 to local nxhuy@4trust.vn
@4000000054832f66356282f4 status: local 2/10 remote 0/20
@4000000054832f66358539ac delivery 2: failure: Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/
@4000000054832f6635e71474 status: local 1/10 remote 0/20
@4000000054832f6635f5b2a4 delivery 1: success: Received:_(qmail_2158_invoked_by_uid_89);_6_Dec_2014_11:31:24_-0500/Received:_(qmail_2158_invoked_by_uid_89);_6_Dec_2014_11:31:24_-0500/Received:_by_simscan_1.4.0_ppid:_2149,_pid:_2151,_t:_0.0077s/Received:_by_simscan_1.4.0_ppid:_2149,_pid:_2151,_t:_0.0077s/Received:_from_unknown_(HELO_mail.4trust.vn)_()/Received:_from_unknown_(HELO_mail.4trust.vn)_()/__by_0_with_SMTP;_6_Dec_2014_11:31:24_-0500/Date:_Sat,_06_Dec_2014_23:31:24_+0700/From:_huyenha@4trust.vn/To:_nxhuy@4trust.vn/Subject:_Re:_Fwd:_ssdfadf/In-Reply-To:_<e8dd61a49b9a353705819b4d656a3cbc@4trust.vn>/References:_<01988b8baeb0552fb9b3e52dbf482e6a@4trust.vn>/_<e8dd61a49b9a353705819b4d656a3cbc@4trust.vn>/Message-ID:_<8e9696acc4134d69e84119c5567ac871@4trust.vn>/Message-ID:_<8e9696acc4134d69e84119c5567ac871@4trust.vn>/---/did_0+0+2/
@4000000054832f6635f62bbc status: local 0/10 remote 0/20
@4000000054832f670250cbdc bounce msg 2754774 qp 2167
@4000000054832f670250d3ac end msg 2754774

Please help me!

Reply | Permalink

Duplicate emails

Arturo huyenha January 2, 2015 23:03

Hi, 

I made the installation of a new server, I have the same problems as mentioned, for every email that incoming or outgoing a copy this email is sent to the account log@domain.com.

I revert the path and all work fine.

Any ideas???

Thanks

Reply | Permalink

This is normal, as the

roberto puzzanghera Arturo January 3, 2015 11:09

This is normal, as the log@yourdomain.xy account is used to improve the qmail-send log. What do you have in your ~alias/.qmail-log file?

Reply | Permalink

The .qmail-log contains:|

Arturo roberto puzzanghera January 3, 2015 11:40

The .qmail-log contains:

| awk '/^$/ { exit } /^[mM][eE][sS][sS][aA][gG][eE]/ { print } /^[rR][eE][cC][eE][iI][vV][eE][dD]:/ { print; } /^[fF][rR][oO][mM]:/ { print } /^[tT][oO]:/ { print } /^[sS][uU][bB][jJ][eE][cC][tT]:/ { print } /^[xX]-[mM][aA][iI][lL][eE][rR]/ { print } /[hH][eE][lL][oO]/{ print } /^[rR][eE][pP][lL][yY]-[tT][oO]/{ print } /^[rR][eE][tT][uU][rR][nN]-[pP][aA][tT][hH]/{ print } /^[cC][cC]:/{ print } /^[dD][eE][lL][iI][vV][eE][rR][eE][dD]-[tT][oO]/{ print } /^[dD][aA][tT][eE]:/{ print } / by /{ print } / id /{ print } /<.*>/{ print }'
| echo "---"

But the error is:

<log@domain.com>: Sorry, no mailbox here by that name. (#5.1.1)

And log:

@4000000054a7d4ad3592ce3c new msg 1322152
@4000000054a7d4ad3592d224 info msg 1322152: bytes 2377 from <> qp 4710 uid 1008
@4000000054a7d4ad359310a4 starting delivery 3: msg 1322152 to local domain.com-log@domain.com
@4000000054a7d4ad359310a4 status: local 1/10 remote 0/20
@4000000054a7d4ad35933f84 starting delivery 4: msg 1322152 to remote me@mail.es
@4000000054a7d4ad3593436c status: local 1/10 remote 1/20
@4000000054a7d4ad35c68c54 delivery 3: failure: Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/
@4000000054a7d4ad35c75774 status: local 0/10 remote 1/20

Thanks!

Reply | Permalink

can you confirm that

roberto puzzanghera Arturo January 3, 2015 12:25

can you confirm that domain.com (the domain inside control/me) really exists and has a valid MX record?

Reply | Permalink

Yes is correct!

Arturo roberto puzzanghera January 3, 2015 18:25

Hi,

The MX is correct and set fine in control/me file.

Reply | Permalink

and you created the

roberto puzzanghera Arturo January 3, 2015 22:51

and you created the domain with vpopmail?

Reply | Permalink

Yes

Arturo roberto puzzanghera January 3, 2015 22:55

Yes, the domain was created with vpopmail, and i delete and recreate the domain.

The domain is on another files control\files.

Reply | Permalink

  what control\files is

roberto puzzanghera Arturo January 3, 2015 23:13

what control\files is needed for?

Reply | Permalink

I mean that the domain is

Arturo roberto puzzanghera January 3, 2015 23:45

I mean that the domain is automatically added to other files in the folder Control (virtualdomains, rcpthosts, etc).

Reply | Permalink

No ideas at the moment, but 

roberto puzzanghera Arturo January 4, 2015 11:01

No ideas at the moment, but  you can be sure that the domain was actually created trying to connect to the postmaster account, for example

telnet 0 89
login postmaster@domain.com PASSWORD

Reply | Permalink

Good news, I think I've found

Arturo roberto puzzanghera January 4, 2015 12:52

Good news, I think I've found a possible motive, apparently aliases found in /var/qmail/alias not working, I created a symbolic link to /home/vpopmail/domains/domain.com/.qmail-log and this if is working now.

@4000000054a9350306110ffc delivery 19: success: Received:_(qmail_30229_invoked_by_uid_33);_4_Jan_2015_12:41:28_+0000/Received:_(qmail_30229_invoked_by_uid_33);_4_Jan_2015_12:41:28_+0000/To:_Arturo_Blanco_/To:_Arturo_Blanco_/Subject:_Re:_test_03/Date:_Sun,_04_Jan_2015_13:41:28_+0100/From:_user@domain.com/In-Reply-To:_/References:_/Message-ID:_/Message-ID:_/---/did_0+0+2/

Any idea why I do not work the /var/qmail/alias??

Reply | Permalink

mmh... do you have your

roberto puzzanghera Arturo January 4, 2015 14:36

mmh... do you have your aliases stored in mysql db (vpopmail compiled with --enable-valias)?

Reply | Permalink

This configurator with the

Arturo roberto puzzanghera January 4, 2015 14:50

This configurator with the --disable-valias option (I followed every step of your tutorial)

Reply | Permalink

root@mail:~# telnet 0

Arturo roberto puzzanghera January 4, 2015 12:35

root@mail:~# telnet 0 89 Trying 0.0.0.0... Connected to 0. Escape character is '^]'. +OK login postmaster@domain.com pass +OK+ vpopmail_dir /home/vpopmail domain_dir /home/vpopmail/domains/domain.com uid 89 gid 89 name postmaster comment Postmaster quota NOQUOTA user_dir /home/vpopmail/domains/domain.com/postmaster encrypted_password pass_encrypt clear_text_password pass no_password_change 0 no_pop 0 no_webmail 0 no_imap 0 bounce_mail 0 no_relay 0 no_dialup 0 user_flag_0 0 user_flag_1 0 user_flag_2 0 user_flag_3 0 no_smtp 0 domain_admin_privileges 1 override_domain_limits 0 no_spamassassin 0 delete_spam 0 no_maildrop 0 system_admin_privileges 0 .

Reply | Permalink

I realise that in qmail-send

huyenha huyenha December 7, 2014 04:50

I realise that in qmail-send log:

@4000000054832f66356282f4 starting delivery 2: msg 2754774 to local nxhuy@4trust.vn

must be:

@4000000054832f66356282f4 starting delivery 2: msg 2754774 to local 4trust.vn-nxhuy@4trust.vn

So I delete the domain and re-add, now it can deliver to local account.

But that generate another error that can't deliver to "log alias" for qmail-tap function

@400000005483d6841bf4da4c new msg 2754788
@400000005483d6841bf4de34 info msg 2754788: bytes 628 from <huyenha@4trust.vn> qp 11658 uid 89
@400000005483d6841bf4e21c starting delivery 1: msg 2754788 to local 4trust.vn-log@4trust.vn
@400000005483d6841bf4e604 status: local 1/10 remote 0/20
@400000005483d6841bf4e9ec starting delivery 2: msg 2754788 to local 4trust.vn-nxhuy@4trust.vn
@400000005483d6841bf4e9ec status: local 2/10 remote 0/20
@400000005483d6841ccb8f24 delivery 1: failure: Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/
@400000005483d6841ccb96f4 status: local 1/10 remote 0/20
@400000005483d6841cced314 delivery 2: success: did_0+0+1/
@400000005483d6841cced6fc status: local 0/10 remote 0/20
@400000005483d6842401182c bounce msg 2754788 qp 11669
@400000005483d6842401c40c end msg 2754788

Reply | Permalink

I think this is because my

roberto puzzanghera huyenha December 7, 2014 08:25

I think this is because my patch creates an alias /var/qmail/alias/.qmail-log which uses the same address of your tap address (http://notes.sagredo.eu/node/82#queue-extra). This alias is needed to improve the log of qmail send. You can solve by changing the tap address

Reply | Permalink

qmail-log alias

Shailendra Shukla roberto puzzanghera December 12, 2014 12:29

Hi Roberto ,

I have followed your excellent guide and installed my server. The issues is for every mail that is sent or received it is trying to send a copy to some log alias. How can I disable that . Below is the message transcript.

Hi. This is the qmail-send program at akhurathacpl.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <log@akhurathacpl.com>: Sorry, no mailbox here by that name. (#5.1.1) --- Below this line is a copy of the message. Return-Path: <support@akhurathacpl.com> Received: (qmail 11804 invoked by uid 89); 12 Dec 2014 13:46:33 +0530 Received: by simscan 1.4.0 ppid: 11796, pid: 11799, t: 0.0938s scanners: attach: 1.4.0 clamav: 0.98.5/m:55/d:19764 spam: 3.4.0 Received: from unknown (HELO mail.akhurathacpl.com) (::1) by 0 with SMTP; 12 Dec 2014 13:46:33 +0530 Received-SPF: unknown (0: No IP address in conversation) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_354b252cc407d8efce244ea9bc720ecc" Date: Fri, 12 Dec 2014 13:46:20 +0530 From: support@akhurathacpl.com To: support@akhurathacpl.com Subject: test mail Message-ID: <0703b9b216a5918c3639dcf4dad7d264@akhurathacpl.com> X-Sender: support@akhurathacpl.com User-Agent: Roundcube Webmail/1.0.3 --=_354b252cc407d8efce244ea9bc720ecc Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII test --=_354b252cc407d8efce244ea9bc720ecc Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"> <html><body style=3D'font-size: 10pt; font-family: Verdana,Geneva,sans-seri= f'> <p>test</p> <div>&nbsp;</div> </body></html> --=_354b252cc407d8efce244ea9bc720ecc--

Request your help in this regards

Thanks

Reply | Permalink

you can revert this patch

roberto puzzanghera Shailendra Shukla December 12, 2014 13:01

you can revert this patch http://notes.sagredo.eu/node/82#queue-extra

anyway I think you have deleted the ~alias/.qmail-log alias or you don't have a valid mx for your control/me domain. Actually this is not a real mailbox but an alias created in order to improve the qmail-send log, so you may want to continue to use it

Reply | Permalink

qmail-log alias

Shailendra Shukla roberto puzzanghera December 12, 2014 13:10

ahhh now I get you , actually this is a newly created server and I have still not pointed the mx to the new servers ip . Let me check by doing point the valid MX to the server .

Thanks a lot for your precious guidance as always you are a real life saver

Reply | Permalink

I think you have a valid mx

roberto puzzanghera Shailendra Shukla December 12, 2014 13:15

I think you have a valid mx for for your domain

$ dig akhurathacpl.com mx

; <<>> DiG 9.9.6-P1 <<>> akhurathacpl.com mx                                                                                                                                                  
;; global options: +cmd                                                                                                                                                                       
;; Got answer:                                                                                                                                                                                
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36916                                                                                                                                     
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL:  0                                                                                                                          
                                                                                                                                                                                              
;; QUESTION SECTION:                                                                                                                                                                          
;akhurathacpl.com.              IN      MX                                                                                                                                                    
                                                                                                                                                                                              
;; ANSWER SECTION:                                                                                                                                                                            
akhurathacpl.com.       3600    IN      MX      10 mail.net4india.com.

;; Query time: 288 msec
;; SERVER: 213.205.32.70#53(213.205.32.70)
;; WHEN: Fri Dec 12 14:03:12 CET 2014
;; MSG SIZE  rcvd: 65

Reply | Permalink

and are you sure you are

roberto puzzanghera huyenha December 6, 2014 17:30

and are you sure you are using my patch? I can't see chkuser in action... is it enabled?

Reply | Permalink

Yes, chkuser in action, this

huyenha roberto puzzanghera December 6, 2014 17:52

Yes, chkuser in action, this is qmail-smtpd log:

@4000000054832fc82cfe8ff4 tcpserver: status: 1/20
@4000000054832fc82cffbcbc tcpserver: pid 2222 from ::1
@4000000054832fc82d009f4c tcpserver: ok 2222 0:::1:25 :::1::40420
@4000000054832fc82d3d331c CHKUSER accepted sender: from <huyenha@4trust.vn|remoteinfo/auth:|chkuser-identify:> remote <helo:mail.4trust.vn|remotehostname:unknown|remotehostip:::1> rcpt <> : accepted any sender always
@4000000054832fc82d66a47c CHKUSER accepted rcpt: from <huyenha@4trust.vn|remoteinfo/auth:|chkuser-identify:> remote <helo:mail.4trust.vn|remotehostname:unknown|remotehostip:::1> rcpt <nxhuy@4trust.vn> : found existing recipient
@4000000054832fc8304afbd4 simscan:[2222]:RELAYCLIENT:0.0045s:-:::1:huyenha@4trust.vn:nxhuy@4trust.vn
@4000000054832fc83547c734 mail recv: pid 2222 from <huyenha@4trust.vn> qp 2224
@4000000054832fc83547cb1c qmail-smtpd: message accepted: huyenha@4trust.vn from ::1 to nxhuy@4trust.vn helo mail.4trust.vn
@4000000054832fc907f41454 tcpserver: end 2222 status 0
@4000000054832fc907f41c24 tcpserver: status: 0/20

Reply | Permalink

can you show your

roberto puzzanghera huyenha December 6, 2014 17:59

can you show your control/defaultdelivery?

Reply | Permalink

 Now it

huyenha roberto puzzanghera December 6, 2014 18:09

 Now it is:
|/var/qmail/bin/preline -f /usr/local/dovecot/libexec/dovecot/deliver -d $EXT@$USER

I also tried "| /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox"

But the result is the same error

Reply | Permalink

the content of the

roberto puzzanghera huyenha December 6, 2014 18:20

the content of the defaultdelivery is

| /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox

without quotes, right?

Reply | Permalink

dovecot issue?

roberto puzzanghera huyenha December 6, 2014 18:15

It can be a dovecot issue (you should also look for dovecot-lda errors, expecially in the sql driver).

But it's strange that you can't have it working when using vpopmail as deliver. Are there any .qmail overriding the defaultdelivery?

Let's fix vpopmail first of all.

Reply | Permalink

I've change the

huyenha roberto puzzanghera December 6, 2014 18:28

I've change the control/defaultdelivery and ~vpopmail/domains/4trust.vn/.qmail_default to | /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox"

But the error is still the same :(

Reply | Permalink

do you have double quotes?

roberto puzzanghera huyenha December 6, 2014 18:34

do you have double quotes at the end of that line?

Reply | Permalink

Sorry, It's my mistake, i've

huyenha roberto puzzanghera December 6, 2014 18:43

Sorry, It's my mistake, i've remove the double quote and re-test. The error is still there.

Could it be a qmail's error?

Reply | Permalink

can you send me in a private

roberto puzzanghera huyenha December 6, 2014 18:53

can you send me in a private msg an strace of smtp session?

Reply | Permalink

Hi, have you passed the

roberto puzzanghera huyenha December 6, 2014 17:27

Hi, have you passed the vpopmail login test from the command line?

Reply | Permalink

I've follow your vpopmail

huyenha roberto puzzanghera December 6, 2014 18:02

I've follow your vpopmail auth test at http://notes.sagredo.eu/node/22#vpopmail

the result is ok

telnet localhost 89
Trying ::1...
Connected to localhost.
Escape character is '^]'.
+OK
login nxhuy@4trust.vn 123456
+OK+
vpopmail_dir /home/vpopmail
domain_dir /home/vpopmail/domains/4trust.vn
uid 89
gid 89
name nxhuy
comment nxhuy
quota 524288000S
user_dir /home/vpopmail/domains/4trust.vn/nxhuy
encrypted_password $1$uk0Fi8aE$USOXMa6g9i0Rjgd9vgLx2/
clear_text_password 123456
no_password_change 0
no_pop 0
no_webmail 0
no_imap 0
bounce_mail 0
no_relay 0
no_dialup 0
user_flag_0 0
user_flag_1 0
user_flag_2 0
user_flag_3 0
no_smtp 0
domain_admin_privileges 0
override_domain_limits 0
no_spamassassin 0
delete_spam 0
no_maildrop 0
system_admin_privileges 0
.

Reply | Permalink

forcetls patch

Andrei August 21, 2014 21:43

Can you pls let me know how to remove the ForceTls patch from the big patch? I need the auth to work without tls.

Thank you!

Reply | Permalink

read above! :)

roberto puzzanghera Andrei August 21, 2014 22:42

read above! :)

Reply | Permalink

DKIM and SRS = fail :-(

S July 6, 2014 02:21

Hi,

if you use SRS, DKIM filter fails, as it sets original SENDER domain instead of that specified in SRS. Any suggestions how to fix it?

cheers and thanks for your patches!

S.

Reply | Permalink

Can you post how the headers

roberto puzzanghera S July 7, 2014 12:50

Can you post how the headers look like when we you use SRS?

I contacted M.Banghui, the author of the DKIM patch, and he told me that he can fix it.

Reply | Permalink

Sure :)

S roberto puzzanghera July 7, 2014 17:25

The DKIM is getting _SENDER  - and SRS is providing to qmail an original Sender domain, instead of the one taken from /var/qmail/control/srs_domain

BTW, why don't you move your awesome patchset to github? It would make things much easier :)

I would declare I can work on IPv6 part, as it is the only (but big) missing thing from your patches.

cheers,

S

Reply | Permalink

Hi, can you do a cut&paste of

roberto puzzanghera S July 7, 2014 21:11

Hi, can you do a cut&paste of the headers?

Actually an help on the IPv6 patch would be appreciated, as I have not much time these days, and I'm not an IPv6 expert. As you probably know M.Banghui has merged an IPv6 patch in his DKIM/SURBL and my plan is to add it to my package soon or later :)

Reply | Permalink

qmail-todo problem

Kamal June 15, 2014 21:33

Firslty, thanks Roberto for ur efforts of creating the patch, But i'm facing a critical problem after i patched qmail 1.6  with ur patch that i have found my server load reached to 250, and when i check the process found that qmail-todo consuming cpu terribly. But i don't know why this happened and what should i do, although i have applied the steps and installed qmail successfully.

Reply | Permalink

Re: qmail-todo problem

roberto puzzanghera Kamal June 15, 2014 22:00

Hi Kamal,

I assume that you erased your queue in this way before installing the todo-patched qmail for the first time:

qmailctl stop
rm -rf /var/qmail/queue
make setup check

If yes please post a

ps axfuww | grep qmail 

The best way to investigate what qmail-todo is doing is using strace:

strace -Ff -o /tmp/qmail-strace.log -p <pid_of_qmail-todo>

Reply | Permalink

Re: qmail-todo problem

Kamal roberto puzzanghera June 16, 2014 11:46

Hi Roberto,

Yes, I already erased the queue as you mentioned, I want to clear something i'm using the combined patch "roberto-netqmail1.06.patch-latest"  NOT todo-patch. but the problem with qmail-todo process that was consuming cpu.

Kindly find output details below,

strace.log
http://www.mediafire.com/view/9ptwzxri9xpptgr/qmail-strace.log

ps-axfuww.log
http://www.mediafire.com/view/1277h6de1g80xsn/ps-axfuww

Reply | Permalink

Maybe a lbsrs problem did you

Enetcs Kamal June 16, 2014 17:57

Maybe a lbsrs problem did you successfully installed it? did you ldconfig it?

Reply | Permalink

I think it's not a libsrs

roberto puzzanghera Enetcs June 16, 2014 19:22

I think it's not a libsrs issue, as in that case the compilation itself will break

Reply | Permalink

Re: qmail-todo problem