Great! This solved the problem, as far as I can see now....

I will review some 24 hours and post if I can see any other effects.

Thank you very much, should have asked long time ago!

Dieter

 All,

 after I really stuck trying to google and find help in the boards, I am writing as perhaps someone can help me to find the correct route:

I use since many years the mercury/32 mailserver connected to my old netware server and I am basically very happy with it.

What I am doing out of perhaps normal: I have an incoming account with local delivery and additionaly all emails to it are being forwarded to another external account, which I mainly use on my mobile phone.

This works as well with most emails. However all email where its sender is xxx@aol.com or xxx@hotmail.com or xxx@outlook.com or similar are bouncing:

    --- Problems not

related to specific addresses in the message:

   550

"envelope sender not allowed xxx@outlook.com"

   *** xxx@xxx.hostingkunde.de

 All these emails are coming to me then, because I am the postmaster and I receive the emails with above error message and attachment.

I tried to adjust mercury.ini after reading about the issue to this:

[Domains]
/[Root]: xxx.de
/[Root]: [10.1.0.164]

Yesterday I recognized that new mercury 4.80 was out in beta, so I was hoping that may do something. In difference, when the error happens then mercury closes with force close on the windows pc, but of course it is adjusted to restart automatically.

 This perhaps would be interesting for the developers, and so I decided to write this message.

 Is the 550 error message created from within the mercury modules, or is it coming from my ISP, which is rejecting the resending message?

I really stuck and my thinking.

Thanks for any hint or guidance.

Best regards,
Dieter

That doesn't look like an error message from Mercury.

If Mercury 4.80 repeatedly crashes when a message is refused by your ISP it would be great if you could check if  there are any .DMP files created in either the Mercury directory, or a subdirectory of it called "dumps". If there are, please let me know. If not please temporarily switch on session logging for MercuryC, try resending one of the failed messages, and if there is a crash post the relevant part of the log here.

Here is the last bounced message, which is from yesterday, out of MercuryCSession.log folder.

 17:12:38.890: --- 24 Mar 2015, 17:12:38.890 ---
17:12:38.890: Connect to 'smtprelaypool.ispgateway.de', timeout 240 seconds.
17:12:40.468: [*] SSL/TLS session established
17:12:40.468: [*] DHE-RSA-AES256-GCM-SHA384, TLSv1.2, Kx=DH, Au=RSA, Enc=AESGCM(256), Mac=AEAD<lf>
17:12:40.468: [*] Peer's certificate name is '/C=DE/OU=Domain Control Validated/CN=smtprelaypool.ispgateway.de'.
17:12:40.484: >> 220 smtprelay06.ispgateway.de ESMTP dfex<cr><lf>
17:12:40.484: << EHLO imtrex.de<cr><lf>
17:12:40.500: >> 250-smtprelay06.ispgateway.de Hello imtrex.de [46.237.202.3]<cr><lf>
17:12:40.500: >> 250-SIZE 104857600<cr><lf>
17:12:40.500: >> 250-8BITMIME<cr><lf>
17:12:40.500: >> 250-PIPELINING<cr><lf>
17:12:40.500: >> 250-AUTH PLAIN LOGIN<cr><lf>
17:12:40.500: >> 250 HELP<cr><lf>
17:12:40.500: << AUTH LOGIN<cr><lf>
17:12:40.531: >> 334 VXNlcm5hbWU6<cr><lf>
17:12:40.531: << [removed]<cr><lf>
17:12:40.546: >> 334 UGFzc3dvcmQ6<cr><lf>
17:12:40.546: << [removed]<cr><lf>
17:12:40.578: >> 235 Authentication succeeded<cr><lf>
17:12:40.578: << MAIL FROM:<googlealerts-noreply@google.com> SIZE=74060<cr><lf>
17:12:40.593: >> 550 "envelope sender not allowed googlealerts-noreply@google.com"<cr><lf>
17:12:40.609: << QUIT<cr><lf>
17:12:40.625: >> 221 smtprelay06.ispgateway.de closing connection<cr><lf>
17:12:40.625: [*] OpenSSL secure session normally terminated.
17:12:40.625: --- Connection closed normally at 24 Mar 2015, 17:12:40.625. ---
17:12:40.625:  

Today no other messages from googlemail or outlook or hotmail users, but some other 100 emails delvivered correctyl by the mechanism.

Thanks,

D.

As far as I can see this transaction didn't cause any error in Mercury. The message was refused by your ISP though as they didn't accept googlealerts-noreply@google.com as sender. Try specifying an address from your domain as "Forced SMTP sender" in MercuryC configuration.