Re: [xmail] CtrlClnt local/remote diff in return value on w2k
-Message d'origine- De : xmail-boun...@xmailserver.org [mailto:xmail-boun...@xmailserver.org]de la part de Davide Libenzi Envoyé : mardi 29 septembre 2009 19:32 À : XMail Users Mailing List Objet : Re: [xmail] CtrlClnt local/remote diff in return value on w2k On Tue, 29 Sep 2009, CLEMENT Francis wrote: Here is WinDBG result (some change in cmd line to mask sensitive data) : CommandLine: C:\XMail\Bin\CtrlClnt.exe -s www.xxx.yyy.zzz -n 6017 -u myusername -p mypassword userlist somehandleddomainname Starting directory: C:\XMail\Bin Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols Executable search path is: ModLoad: 0040 0047e000 CtrlClnt.exe ModLoad: 7846 784e2000 ntdll.dll ModLoad: 1000 100fd000 C:\XMail\Bin\LIBEAY32.dll ModLoad: 74fd 74fd9000 C:\WINNT\system32\WSOCK32.dll ModLoad: 77e7 77f2f000 C:\WINNT\system32\KERNEL32.DLL ModLoad: 74fb 74fc4000 C:\WINNT\system32\WS2_32.DLL ModLoad: 7800 78045000 C:\WINNT\system32\MSVCRT.DLL ModLoad: 78ed 78f35000 C:\WINNT\system32\ADVAPI32.DLL ModLoad: 770c 7712f000 C:\WINNT\system32\RPCRT4.dll ModLoad: 74fa 74fa8000 C:\WINNT\system32\WS2HELP.DLL ModLoad: 77f4 77f7d000 C:\WINNT\system32\GDI32.dll ModLoad: 77e0 77e5f000 C:\WINNT\system32\USER32.dll ModLoad: 7813 781cb000 C:\WINNT\system32\MSVCR80.dll ModLoad: 0023 00261000 C:\XMail\Bin\SSLEAY32.dll (ad8.aac): Break instruction exception - code 8003 (first chance) eax= ebx=00131f04 ecx= edx=00132c48 esi=7ffdf000 edi=00131f78 eip=7847193c esp=0012f984 ebp=0012fc98 iopl=0 nv up ei pl nz na po nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs= efl=0202 ntdll!DbgBreakPoint: 7847193c cc int 3 0:000 g ModLoad: 74f5 74f6d000 C:\WINNT\system32\msafd.dll ModLoad: 74f9 74f97000 C:\WINNT\System32\wshtcpip.dll (ad8.888): Access violation - code c005 (first chance) First chance exceptions are reported before any exception handling. This exception may be expected and handled. eax= ebx= ecx=0047a410 edx=0ae4 esi=0047a400 edi= eip=7846f281 esp=00b2fba0 ebp=00b2fc00 iopl=0 nv up ei pl zr na pe nc cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs= efl=00010246 ntdll!RtlpWaitForCriticalSection+0x8a: 7846f281 ff4010 inc dword ptr [eax+10h] ds:0023:0010= I'm not a windbg specialist ;) What do you mean with enable just in time debugging ? Should I do somethink more with Windbg at this point ? Thank you Francis. Do you have a debug version of CtrlClnt to run (like the ones included in the recent -pre releases)? If you run the CtrlClnt and you have the corresponding PDB file in the same directory, WinDBG should resolve the symbols. Also, can you show a Call Stack (in the View menu) from the point of fault? - Davide Here is it : Debug with ctrlclnt v 1.26pre05, Call Stack (with source and source args options activated) : ntdll!RtlpWaitForCriticalSection+0x8a ntdll!RtlEnterCriticalSection+0x46 CtrlClnt!SysCreateTlsKey(int * TlsKey = 0x0047a3cc, function * pFreeProc = 0x00404c60)+0xf [c:\temp\xmail-1.26-pre05\sysdepwin.cpp @ 1216] CtrlClnt!ErrOnceSetup(void)+0x15 [c:\temp\xmail-1.26-pre05\errors.cpp @ 333] CtrlClnt!SysThreadOnce(struct SYS_THREAD_ONCE * pThrOnce = 0x0047a3d0, function * pOnceProc = 0x00404bf0)+0x16 [c:\temp\xmail-1.26-pre05\sysdepwin.cpp @ 1287] CtrlClnt!ErrSetupEnv(void)+0x15 [c:\temp\xmail-1.26-pre05\errors.cpp @ 343] CtrlClnt!ErrSetErrorCode(int iError = -5, char * pszInfo = 0x , int iSize = -1)+0x9 [c:\temp\xmail-1.26-pre05\errors.cpp @ 380] CtrlClnt!SysLockMutex(void * hMutex = 0xfeeefeee, int iTimeout = 4194304)+0x26 [c:\temp\xmail-1.26-pre05\sysdepwin.cpp @ 937] CtrlClnt!BSslLockingCB(int iMode = 9, int iType = 1, char * pszFile = 0x100b2a44 .\crypto\err\err.c, int iLine = 419)+0x22 [c:\temp\xmail-1.26-pre05\sslbind.cpp @ 82] WARNING: Stack unwind information not available. Following frames may be wrong. LIBEAY32!CRYPTO_lock+0x81 LIBEAY32!ENGINE_load_ubsec+0x7bb ntdll!LdrShutdownThread+0xa3 KERNEL32!ExitThread+0x53 KERNEL32!FreeLibraryAndExitThread+0x24 msafd!SockAsyncThread+0xe7 KERNEL32!BaseThreadStart+0x52 Francis ___ xmail mailing list xmail@xmailserver.org http://xmailserver.org/mailman/listinfo/xmail
[xmail] SBS 2008 pop3connector
Is someone else having problem with this odd thing called SBS 2008 pop3connector? Many clients that use this connector are telling us that, for some reason, it is considering XMail´s headers as invalid. Some information from Microsoft´s site: Email Rejected Due to Protocol Errors (Invalid Headers) Note: A long-term solution to this issue is being investigated [New Content courtesy of Dan Thompson] Exchange will close an SMTP connection after a certain number of protocol errors (5 by default). (see the MaxProtocolErrors property of the ReceiveConnector object at: http://technet.microsoft.com/en-us/library/aa998618.aspx) When the SBS 2008 pop3connector downloads a message from a POP3 mailbox, it needs to figure out what the return path for the mail should be, which it does by reading the email's headers. The pop3connector does not do validation of the header value--it lets Exchange take care of that. If the header value that the pop3connector chooses is malformed, when it is sent to the Exchange server (as part of the MAIL FROM command), Exchange will reject it with a 501 error. That counts as a protocol error, and therefore is counted against the MaxProtocolErrors limit. Since the pop3connector was not able to deliver the mail, and does not know if the mail is safe to delete, it leaves the mail on the POP3 server. If there are 5 of these messages in your POP3 mailbox, then there will be 5 protocol errors in the pop3connector's SMTP session, which hits the limit, and Exchange will end the session with a transient error (4xx). When this happens, the pop3connector recognizes that the error is transient, and will retry again at the next scheduled download period. But since those 5 malformed messages are still in the POP3 mailbox, the same thing will continue to happen, with no forward progress being made. The workaround is to increase the MaxProtocolErrors property of the Windows SBS Fax Sharepoint Receive connector, and then restart the Exchange Transport service for the change to take effect (and you'll have to restart the pop3connector service, too, since it depends on the Exchange Transport service). Unfortunately, you can't set that property from the Exchange management GUI, so you have to do it from an (elevated) Exchange Powershell prompt. Here are the instructions: From an elevated Exchange Management Shell (Exchange Powershell window) (right click on Start--Microsoft Exchange Server 2007--Exchange Management Shell and then choose Run as administrator) run the following Powershell commands: Set-ReceiveConnector -Identity ($Env:computername + \Windows SBS Fax Sharepoint Receive + $Env:computername) -MaxProtocolErrors 500 Stop-Service pop3connector Restart-Service -force MSExchangeTransportStart-Service pop3connector That will increase the MaxProtocol errors (of the internal receive connector only) to match the pop3connector's max emails downloaded per session. Once you get 500 messages with malformed headers stacked up in the POP3 mailbox, though, you'll still have to delete them manually. Regards Edinilson :- ATINET-Professional Web Hosting Tel Voz: (0xx11) 4412-0876 http://www.atinet.com.br ___ xmail mailing list xmail@xmailserver.org http://xmailserver.org/mailman/listinfo/xmail
Re: [xmail] SBS 2008 pop3connector
On Wed, 30 Sep 2009, Edinilson - ATINET wrote: Is someone else having problem with this odd thing called SBS 2008 pop3connector? Many clients that use this connector are telling us that, for some reason, it is considering XMail´s headers as invalid. No idea. It'd be great to know what are those errors (or better, that MS considers so). - Davide ___ xmail mailing list xmail@xmailserver.org http://xmailserver.org/mailman/listinfo/xmail
Re: [xmail] CtrlClnt local/remote diff in return value on w2k
On Wed, 30 Sep 2009, CLEMENT Francis wrote: Here is it : Debug with ctrlclnt v 1.26pre05, Call Stack (with source and source args options activated) : ntdll!RtlpWaitForCriticalSection+0x8a ntdll!RtlEnterCriticalSection+0x46 CtrlClnt!SysCreateTlsKey(int * TlsKey = 0x0047a3cc, function * pFreeProc = 0x00404c60)+0xf [c:\temp\xmail-1.26-pre05\sysdepwin.cpp @ 1216] CtrlClnt!ErrOnceSetup(void)+0x15 [c:\temp\xmail-1.26-pre05\errors.cpp @ 333] CtrlClnt!SysThreadOnce(struct SYS_THREAD_ONCE * pThrOnce = 0x0047a3d0, function * pOnceProc = 0x00404bf0)+0x16 [c:\temp\xmail-1.26-pre05\sysdepwin.cpp @ 1287] CtrlClnt!ErrSetupEnv(void)+0x15 [c:\temp\xmail-1.26-pre05\errors.cpp @ 343] CtrlClnt!ErrSetErrorCode(int iError = -5, char * pszInfo = 0x , int iSize = -1)+0x9 [c:\temp\xmail-1.26-pre05\errors.cpp @ 380] CtrlClnt!SysLockMutex(void * hMutex = 0xfeeefeee, int iTimeout = 4194304)+0x26 [c:\temp\xmail-1.26-pre05\sysdepwin.cpp @ 937] CtrlClnt!BSslLockingCB(int iMode = 9, int iType = 1, char * pszFile = 0x100b2a44 .\crypto\err\err.c, int iLine = 419)+0x22 [c:\temp\xmail-1.26-pre05\sslbind.cpp @ 82] WARNING: Stack unwind information not available. Following frames may be wrong. LIBEAY32!CRYPTO_lock+0x81 LIBEAY32!ENGINE_load_ubsec+0x7bb ntdll!LdrShutdownThread+0xa3 KERNEL32!ExitThread+0x53 KERNEL32!FreeLibraryAndExitThread+0x24 msafd!SockAsyncThread+0xe7 KERNEL32!BaseThreadStart+0x52 Great trace. Need to investigate ... - Davide ___ xmail mailing list xmail@xmailserver.org http://xmailserver.org/mailman/listinfo/xmail
[xmail] Mail loop detected error
I've been using XMail 1.22 on Windows 2003 Server for several years. But recent days, after I updated it to 1.25 on RedHat Enterprise Linux 5.3, many mail loops sent from outside have been detected. Just as the following: [00] XMail bounce: rcpt=[...@test.com];Error=[Mail loop detected] [01] Error sending message [1254297205413.1088923968.205.beta] from [test.com]. ID:SCC31A Mail From: md...@dnv.com Rcpt To: c...@test.com [02] The reason of the delivery failure was: Mail loop detected [04] Here is listed the message log file: [PeekTime] 1254297205 : Wed, 30 Sep 2009 15:53:25 +0800 ErrCode = -163 ErrString = Mail loop detected Message SCC31A blocked by mail loop check ! SMTP-Error = 554 Message blocked by mail loop check [05] Here is listed the initial part of the message: Received: from VA3EHSOBE004.bigfish.com ([216.32.180.14]:21911) by test.com ([192.168.1.250]:25) with [XMail 1.25 ESMTP Server] id SCC31A for c...@test.com from ; Wed, 30 Sep 2009 15:53:23 +0800 Received: from mail12-va3-R.bigfish.com (10.7.14.248) by VA3EHSOBE004.bigfish.com (10.7.40.24) with Microsoft SMTP Server id 8.1.340.0; Wed, 30 Sep 2009 07:53:37 + Received: from mail12-va3 (localhost.localdomain [127.0.0.1]) by mail12-va3-R.bigfish.com (Postfix) with ESMTP id 600CC18C00E5 for c...@test.com; Wed, 30 Sep 2009 07:53:37 + (UTC) X-SpamScore: -63 X-BigFish: VPS-63(zz542N2e57K1432R9370K98dNf01M936eM62a3Le6dJ2174M9371Pf4eM103dK873fi9eb3izz1202hzzz2fh6bh61h) X-Spam-TCS-SCL: 0:0 X-FB-SS: 5, Received: by mail12-va3 (MessageSwitch) id 125429720377767_25372; Wed, 30 Sep 2009 07:53:23 + (UCT) Received: from VA3EHSMHS002.bigfish.com (unknown [10.7.14.254]) by mail12-va3.bigfish.com (Postfix) with ESMTP id 2D28410A8068for c...@test.com; Wed, 30 Sep 2009 07:53:22 + (UTC) Received: from dnv.com (193.212.132.158) by VA3EHSMHS002.bigfish.com (10.7.99.12) with Microsoft SMTP Server id 14.0.482.32; Wed, 30 Sep 2009 07:53:19 + Received: from osl092.verit.dnv.com ([172.16.34.92]) by dnv.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 30 Sep 2009 09:54:41 +0200 Received: from osl218.verit.dnv.com ([172.16.34.218]) by osl092.verit.dnv.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 30 Sep 2009 09:53:18 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: RE: Preliminary comments on material submitted with regards to the saturated diving equipment on Trico Sabre no.2 Date: Wed, 30 Sep 2009 09:53:18 +0200 Message-ID: b741324838eab042ba7d922ba46b105e0303d...@osl218.verit.dnv.com In-Reply-To: 20090930152230.b628.a2c49...@test.com X-MS-Has-Attach: X-MS-TNEF-Correlator: thread-topic: Preliminary comments on material submitted with regards to the saturated diving equipment on Trico Sabre no.2 thread-index: AcpBns+WG0kCl2ACQxOUOU5P/SBhdgAA7Hzg References: c4f28fab0b487f43b1da77a4bcda4a9f12b...@sha009.verit.dnv.com 20090930152230.b628.a2c49...@test.com From: md...@dnv.com To: c...@test.com X-OriginalArrivalTime: 30 Sep 2009 07:53:18.0782 (UTC) FILETIME=[13017DE0:01CA41A3] X-Reverse-DNS: dmz158.dnv.com Return-Path: md...@dnv.com Good Afternoon Mr. Chen, Regards, Chen Shihai ___ xmail mailing list xmail@xmailserver.org http://xmailserver.org/mailman/listinfo/xmail
Re: [xmail] Mail loop detected error
On Wed, 30 Sep 2009, Chen Shihai wrote: I've been using XMail 1.22 on Windows 2003 Server for several years. But recent days, after I updated it to 1.25 on RedHat Enterprise Linux 5.3, many mail loops sent from outside have been detected. Just as the following: Did you change the MaxMTAOps variable inside your server.tab file? That message has only 8 Received: headers, while the default for MaxMTAOps is 16. Received: from VA3EHSOBE004.bigfish.com ([216.32.180.14]:21911) by test.com ([192.168.1.250]:25) with [XMail 1.25 ESMTP Server] id SCC31A for c...@test.com from ; Wed, 30 Sep 2009 15:53:23 +0800 Received: from mail12-va3-R.bigfish.com (10.7.14.248) by VA3EHSOBE004.bigfish.com (10.7.40.24) with Microsoft SMTP Server id 8.1.340.0; Wed, 30 Sep 2009 07:53:37 + Received: from mail12-va3 (localhost.localdomain [127.0.0.1]) by mail12-va3-R.bigfish.com (Postfix) with ESMTP id 600CC18C00E5for c...@test.com; Wed, 30 Sep 2009 07:53:37 + (UTC) X-SpamScore: -63 X-BigFish: VPS-63(zz542N2e57K1432R9370K98dNf01M936eM62a3Le6dJ2174M9371Pf4eM103dK873fi9eb3izz1202hzzz2fh6bh61h) X-Spam-TCS-SCL: 0:0 X-FB-SS: 5, Received: by mail12-va3 (MessageSwitch) id 125429720377767_25372; Wed, 30 Sep 2009 07:53:23 + (UCT) Received: from VA3EHSMHS002.bigfish.com (unknown [10.7.14.254]) by mail12-va3.bigfish.com (Postfix) with ESMTP id 2D28410A8068 for c...@test.com; Wed, 30 Sep 2009 07:53:22 + (UTC) Received: from dnv.com (193.212.132.158) by VA3EHSMHS002.bigfish.com (10.7.99.12) with Microsoft SMTP Server id 14.0.482.32; Wed, 30 Sep 2009 07:53:19 + Received: from osl092.verit.dnv.com ([172.16.34.92]) by dnv.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 30 Sep 2009 09:54:41 +0200 Received: from osl218.verit.dnv.com ([172.16.34.218]) by osl092.verit.dnv.com with Microsoft SMTPSVC(6.0.3790.3959);Wed, 30 Sep 2009 09:53:18 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: RE: Preliminary comments on material submitted with regards to the saturated diving equipment on Trico Sabre no.2 Date: Wed, 30 Sep 2009 09:53:18 +0200 Message-ID: b741324838eab042ba7d922ba46b105e0303d...@osl218.verit.dnv.com In-Reply-To: 20090930152230.b628.a2c49...@test.com X-MS-Has-Attach: X-MS-TNEF-Correlator: thread-topic: Preliminary comments on material submitted with regards to the saturated diving equipment on Trico Sabre no.2 thread-index: AcpBns+WG0kCl2ACQxOUOU5P/SBhdgAA7Hzg References: c4f28fab0b487f43b1da77a4bcda4a9f12b...@sha009.verit.dnv.com 20090930152230.b628.a2c49...@test.com From: md...@dnv.com To: c...@test.com X-OriginalArrivalTime: 30 Sep 2009 07:53:18.0782 (UTC) FILETIME=[13017DE0:01CA41A3] X-Reverse-DNS: dmz158.dnv.com Return-Path: md...@dnv.com - Davide ___ xmail mailing list xmail@xmailserver.org http://xmailserver.org/mailman/listinfo/xmail
Re: [xmail] CtrlClnt local/remote diff in return value on w2k
On Wed, 30 Sep 2009, CLEMENT Francis wrote: Here is it : Debug with ctrlclnt v 1.26pre05, Call Stack (with source and source args options activated) : ntdll!RtlpWaitForCriticalSection+0x8a ntdll!RtlEnterCriticalSection+0x46 CtrlClnt!SysCreateTlsKey(int * TlsKey = 0x0047a3cc, function * pFreeProc = 0x00404c60)+0xf [c:\temp\xmail-1.26-pre05\sysdepwin.cpp @ 1216] CtrlClnt!ErrOnceSetup(void)+0x15 [c:\temp\xmail-1.26-pre05\errors.cpp @ 333] CtrlClnt!SysThreadOnce(struct SYS_THREAD_ONCE * pThrOnce = 0x0047a3d0, function * pOnceProc = 0x00404bf0)+0x16 [c:\temp\xmail-1.26-pre05\sysdepwin.cpp @ 1287] CtrlClnt!ErrSetupEnv(void)+0x15 [c:\temp\xmail-1.26-pre05\errors.cpp @ 343] CtrlClnt!ErrSetErrorCode(int iError = -5, char * pszInfo = 0x , int iSize = -1)+0x9 [c:\temp\xmail-1.26-pre05\errors.cpp @ 380] CtrlClnt!SysLockMutex(void * hMutex = 0xfeeefeee, int iTimeout = 4194304)+0x26 [c:\temp\xmail-1.26-pre05\sysdepwin.cpp @ 937] CtrlClnt!BSslLockingCB(int iMode = 9, int iType = 1, char * pszFile = 0x100b2a44 .\crypto\err\err.c, int iLine = 419)+0x22 [c:\temp\xmail-1.26-pre05\sslbind.cpp @ 82] WARNING: Stack unwind information not available. Following frames may be wrong. LIBEAY32!CRYPTO_lock+0x81 LIBEAY32!ENGINE_load_ubsec+0x7bb ntdll!LdrShutdownThread+0xa3 KERNEL32!ExitThread+0x53 KERNEL32!FreeLibraryAndExitThread+0x24 msafd!SockAsyncThread+0xe7 KERNEL32!BaseThreadStart+0x52 Really wierd. Seems like an MS async thread exit, triggers a call (via DllMain - ThreadDetach almost certainly) to the SSL code, which at that point, has already been freed. This happens after main() returns, so it's pretty hairy to fix. Lemme think ... - Davide ___ xmail mailing list xmail@xmailserver.org http://xmailserver.org/mailman/listinfo/xmail
Re: [xmail] CtrlClnt local/remote diff in return value on w2k
On Wed, 30 Sep 2009, Davide Libenzi wrote: On Wed, 30 Sep 2009, CLEMENT Francis wrote: Here is it : Debug with ctrlclnt v 1.26pre05, Call Stack (with source and source args options activated) : ntdll!RtlpWaitForCriticalSection+0x8a ntdll!RtlEnterCriticalSection+0x46 CtrlClnt!SysCreateTlsKey(int * TlsKey = 0x0047a3cc, function * pFreeProc = 0x00404c60)+0xf [c:\temp\xmail-1.26-pre05\sysdepwin.cpp @ 1216] CtrlClnt!ErrOnceSetup(void)+0x15 [c:\temp\xmail-1.26-pre05\errors.cpp @ 333] CtrlClnt!SysThreadOnce(struct SYS_THREAD_ONCE * pThrOnce = 0x0047a3d0, function * pOnceProc = 0x00404bf0)+0x16 [c:\temp\xmail-1.26-pre05\sysdepwin.cpp @ 1287] CtrlClnt!ErrSetupEnv(void)+0x15 [c:\temp\xmail-1.26-pre05\errors.cpp @ 343] CtrlClnt!ErrSetErrorCode(int iError = -5, char * pszInfo = 0x , int iSize = -1)+0x9 [c:\temp\xmail-1.26-pre05\errors.cpp @ 380] CtrlClnt!SysLockMutex(void * hMutex = 0xfeeefeee, int iTimeout = 4194304)+0x26 [c:\temp\xmail-1.26-pre05\sysdepwin.cpp @ 937] CtrlClnt!BSslLockingCB(int iMode = 9, int iType = 1, char * pszFile = 0x100b2a44 .\crypto\err\err.c, int iLine = 419)+0x22 [c:\temp\xmail-1.26-pre05\sslbind.cpp @ 82] WARNING: Stack unwind information not available. Following frames may be wrong. LIBEAY32!CRYPTO_lock+0x81 LIBEAY32!ENGINE_load_ubsec+0x7bb ntdll!LdrShutdownThread+0xa3 KERNEL32!ExitThread+0x53 KERNEL32!FreeLibraryAndExitThread+0x24 msafd!SockAsyncThread+0xe7 KERNEL32!BaseThreadStart+0x52 Really wierd. Seems like an MS async thread exit, triggers a call (via DllMain - ThreadDetach almost certainly) to the SSL code, which at that point, has already been freed. This happens after main() returns, so it's pretty hairy to fix. Lemme think ... Can you try to get this and try on a 1.26 setup (needs the 1.26 SSL libs)? http://www.sendspace.com/file/k0ic6w - Davide ___ xmail mailing list xmail@xmailserver.org http://xmailserver.org/mailman/listinfo/xmail
