Thread View: comp.mail.pegasus-mail.misc
3 messages
3 total messages
Started by Cameron Mckenzie
Mon, 22 Feb 1999 00:00
Mercury/32 crashes just just after fetching mail, when it tries to distribute
Author: Cameron Mckenzie
Date: Mon, 22 Feb 1999 00:00
Date: Mon, 22 Feb 1999 00:00
292 lines
12119 bytes
12119 bytes
My Mercury/32 (v 2.10 and/or V2.16) which I run 2 versions of (on a
WIN 95C platform (Ihave tried win95Zero, win95a,b and c) , one for
local delivery, the other for collecting and sending mail via dial-up
which is launched via NETLAUNCH.
It was running successfully for some 6 months. Then all of a sudden
it starts crashing with a page fault in KERNEL32.DLL just after
collecting the POP3 mail and as it tries to distribute the mail via
the DOMAIN mailbox. Surprising thing is that the SMTP server keeps on
running (i.e. sending mail) after the (pop3 collector) crashes, but
closes(crashes with the core module) just as soon as you accept the
crash output window. Sometimes one or 2 mails get distributed, but
then the Mercury 32 crashes. See crash output below.
***********************************************************************************
MERCURY caused an invalid page fault in
module KERNEL32.DLL at 0137:bff857e8.
Registers:
EAX=c0019ca0 CS=0137 EIP=bff857e8 EFLGS=00010202
EBX=0242ff8c SS=013f ESP=02330000 EBP=02330074
ECX=815a180c DS=013f ESI=02330270 FS=45cf
EDX=bff7678c ES=013f EDI=02330254 GS=0000
Bytes at CS:EIP:
56 89 4d f8 57 8b 41 40 8b 75 08 89 45 ec 83 7d
Stack dump:
0242ff8c 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000
************************************************************************************
I now have a domain mailbox with some 500 messages in it, waiting to
be distributed.
I have tried everyting, I have removed the Virus software, run mercury
from a local hard drive, I have tried file permissions, you name it
!!! Re-installed the Novell/32 client as well. (Version 1.5 of
Novell/32 client, about the only thing that has not been changed, I
have even installed new hardware.)
Netcard is running NE2000 compatible 32 bit driver on an old network
card.
I have even done a bindfix, and created a new domain mailbox.
One thing that has changed is that there is now much more mail being
fetched.
Does not exceed 10 minutes though. (Netlaunch on-line time)
***************************************************************
(Have not been able to get the new scheduling module Mercury X to
work,
any tips here will be most appreciated, I don't understand what to
fill in the empty blocks,
i would gather mercurys.dll or what ??, how do you link it to the new
dialing software
under win95/98)
**************************************************************************
Thanks
Cameron Mckenzie
Network Manager
Andersen Consulting
mckenzie@iafrica.com
Here are the 2 ini files:-
Mercore INI File (RUNS all the time)
# MERCURY.INI generated by Mercury Setup
#
#
# Sample Bindery Mode MERCURY.INI file (in fact, the one I use on my
# production server). This one implements most of the possible
# switches for each module, but you can edit it to do less if you
# wish. All the fields shown below are described in the file
# MGUIDE.HLP which is supplied in the Mercury archive.
#
# Anything after a '#' to the end of the line is a comment and
# is stripped out before parsing. Trailing and leading whitespace is
# also stripped before parsing. Many sample commands have been left
# in this file commented out for reference purposes.
#
[General]
myname: sacbc.org.za # Canonical name for this server
timezone: -0200 # Time Zone to add to date fields
file_api: 1 # Use the file api instead of queues
mailqueue: F:\MERCORE\QUEUE # Where mail should be put for
delivery smtpqueue: F:\MERCORE\QUEUE # Where the SMTP client
should look for mail newmail_path: \~8 # Where to find the users'
WinPMail mailboxes.
[Protocols]
;F:\mercore\mercuryc.dll
;F:\mercore\mercuryd.dll
;F:\mercore\mercuryx.dll
[Mercury]
failfile: F:\mercore\Mercury\FAILURE.MER # Delivery failure
notification template confirmfile: F:\mercore\Mercury\CONFIRM.MER
# Delivery confirmation template aliasfile:
F:\mercore\Mercury\ALIAS.MER # System-wide alias file synfile:
F:\mercore\Mercury\SYNONYM.MER # User synonym database listfile:
F:\mercore\Mercury\LISTS.MER # List of lists logwidth: 30 #
Width of address fields in logfile retpath: 1 # Do/Don't use
'return-path' for errors maxhops: 30 # Used to detect mailing
loops gullible: 0 # If NZ, don't validate 'From' fields
bitnethost: cunyvm.cuny.edu # Relay host for '.bitnet' rewrites
poll: 10 # Seconds between queue polling cycles scratch:
F:\mercore\Scratch # Where we can write temp files returnlines:
15 # How many lines of failed messages to return postmaster:
jmkhabel # NetWare UIC of postmaster broadcast: 1 # Yes, we
want broadcast notifications, but receipts: 0 # ... no
broadcasts for receipt confirmations PM_notify: 1 # Do/Don't
send errors to the postmaster change_owner: 1 # Change message
ownership to recipient auto_tzone: 1 # If NZ, obtain timezone
information from OS
[MercuryC]
# Session_logging: G:\ # Directory to write session
# transcripts
host: pta.lia.net # mail mail host which relays for us
scratch: F:\mercore\Mercury # Where we can write temp files
poll: 30 # Seconds between queue polling
cycles returnlines: 15 # How many lines of failed
messages to return failfile: F:\mercore\Mercury\FAILURE.MER #
Delivery failure template esmtp: 1 # Yes, we
want to use ESMTP extensions
[MercuryD]
Scratch : F:\mercore\Mercury
Timeout : 30
Poll : 30
[MercuryS]
# Session_logging: G:\ # Directory to write session
# transcripts
debug: 1 # Whether or not to show session
progress # allow: 192.156.225.2 # A machine we WILL
permit to connect # refuse: 192.156.225.0 # A group of
machines we WON'T permit. logfile: F:\mercore\Logs\MERCURYS.LOG #
size: 1500000
[MercuryP]
scratch : F:\mercore\Mercury
Timeout : 60
[MercuryX]
Cmd_Wait: 0
IE4_Dialling: 3
Use_ETRN: 0
Clients_only: 0
Drain_queues: 1
Sunday: 0000,0000,0,0,0,0
Monday: 0600,1600,120,600,0,0
Tuesday: 0600,1600,5,120,0,0
Wednesday: 0600,1600,120,600,0,0
Thursday: 0600,1600,120,600,0,0
Friday: 0600,1600,120,600,0,0
Saturday: 0000,0000,0,0,0,0
[Domains]
fs1: fs1
fs1: sacbc.org.za
DM=dmailbox: sacbc.org.za
[Maiser]
Maiser: Maiser # 'Username' of mail server account
Helpfile: F:\mercore\Mercury\MAISER.HLP # Help sent on failed
maiser requests Lookupfile: F:\mercore\Mercury\MAISER.LKP #
Format file for the 'lookup' command Send_dir:
F:\mercore\Mercury\SENDABLE # Directory for the 'send' command
Logfile: F:\mercore\Logs\MAISER.LOG # Mail server log file
Notify: F:\mercore\Mercury\TMP # Dir. for pending 'notify'
commands NoList: N # If 'Y', disable the 'list' command
Local_only: Y # If 'Y', local 'notify' commands only
[MercuryH]
Logfile : F:\mercore\Logs\MERCURYH.LOG
# Addressbook : \\CLIO\SYS\SYSTEM\MERCURY\PH.PMR
# MOTD : \\CLIO\SYS\SYSTEM\MERCURY\PH-MOTD.TXT
# Administrator : postmaster@clio.pmail.gen.nz
Timeout : 30
[Groups]
[Rewrite]
***************************************************************
This is the INI for the Version that is brought up ocasionally via
NETLAUNCH)
# MERCURY.INI generated by Mercury Setup
#
#
# Sample Bindery Mode MERCURY.INI file (in fact, the one I use on my
# production server). This one implements most of the possible
# switches for each module, but you can edit it to do less if you
# wish. All the fields shown below are described in the file
# MGUIDE.EXE which is supplied in the Mercury archive.
#
# Anything after a '#' to the end of the line is a comment and
# is stripped out before parsing. Trailing and leading whitespace is
# also stripped before parsing.
#
[General]
myname: sacbc.org.za # Canonical name for this server
timezone: +0200 # Time Zone to add to date fields
file_api: 1 # Use the file api instead of queues
mailqueue: F:\MERCORE\QUEUE # Where mail should be put for
delivery smtpqueue: F:\MERCORE\QUEUE # Where the SMTP client
should look for mail newmail_path: \~8 # Where to find the users'
WinPMail mailboxes.
[Protocols]
F:\imail\mercuryc.dll
F:\imail\mercuryd.dll
[Mercury]
failfile: F:\imail\Mercury\FAILURE.MER # Delivery failure
notification template confirmfile: F:\imail\Mercury\CONFIRM.MER #
Delivery confirmation template aliasfile:
F:\imail\Mercury\ALIAS.MER # System-wide alias file synfile:
F:\imail\Mercury\SYNONYM.MER # User synonym database listfile:
F:\imail\Mercury\LISTS.MER # List of lists logwidth: 30 #
Width of address fields in logfile retpath: 1 # Do/Don't use
'return-path' for errors maxhops: 30 # Used to detect mailing
loops gullible: 0 # If NZ, don't validate 'From' fields
bitnethost: cunyvm.cuny.edu # Relay host for '.bitnet' rewrites
poll: 1000 # Seconds between queue polling cycles scratch:
F:\imail\Scratch # Where we can write temp files switch: 2
# number of ms to yield per op on heavy I/O returnlines: 15 #
How many lines of failed messages to return postmaster: jmkhabel
# NetWare UIC of postmaster broadcast: 1 # Yes, we want
broadcast notifications, but receipts: 0 # ... no broadcasts
for receipt confirmations PM_notify: 1 # Do/Don't send errors to
the postmaster change_owner: 1 # Change message ownership to
recipient auto_tzone: 1 # If NZ, obtain timezone information from
OS
[MercuryC]
Host : pta.lia.net
Failfile : F:\MERCORE\Mercury\FAILURE.MER
HELO : sacbcmail
Poll : 46
Scratch : F:\imail\Mercury
ReturnLines : 15
Switch : 2
Timeout : 360
ESMTP : 1
[MercuryD]
Scratch : F:\MERCORE\Mercury
Timeout : 360
Poll : 25
[MercuryS]
# Session_logging: G:\ # Directory to write session
# transcripts
switch: 2
debug: 1 # Whether or not to show session
progress # allow: 192.156.225.2 # A machine we WILL
permit to connect # refuse: 192.156.225.0 # A group of
machines we WON'T permit. logfile: F:\imail\Logs\MERCURYS.LOG #
size: 1500000
[MercuryP]
scratch : F:\imail\Mercury
switch : 2
Timeout : 60
# [Groups]
# testgroup : TESTGRP
[Domains]
fs1: fs1
fs1: sacbc.org.za
DM=dmailbox: sacbc.org.za
[Maiser]
Maiser: Maiser # 'Username' of mail server account
Helpfile: F:\imail\Mercury\MAISER.HLP # Help sent on failed
maiser requests Lookupfile: F:\imail\Mercury\MAISER.LKP # Format
file for the 'lookup' command Send_dir: F:\imail\Mercury\SENDABLE
# Directory for the 'send' command Logfile:
F:\imail\Logs\MAISER.LOG # Mail server log file Notify:
F:\imail\Mercury\TMP # Dir. for pending 'notify' commands NoList:
Y # If 'Y', disable the 'list' command Local_only: Y # If
'Y', local 'notify' commands only
[Groups]
[Rewrite]
Re: Mercury/32 crashes just just after fetching mail, when it tries to distribute
Author: Michael Salem
Date: Mon, 22 Feb 1999 00:00
Date: Mon, 22 Feb 1999 00:00
26 lines
2298 bytes
2298 bytes
I was unable to read this message, as I automatically kill all messages longer than 200 lines. However, from the Subject line this appears exactly like a problem I had, reported here some weeks ago, but with no response. Essentially, in a dial-up system, Mercury/32 would dial and then crash with 4 successive messages. Sometimes a few messages would be delivered. Once this happened, it would recur every time. It was associated with particular messages. I think the common factor was large numbers of Cc: addresses. When it firts happened, I moved all the .MDD files to a separate directory where Mercury/32 couldn't find them; next session worked fine. I then moved half of them back, and moved them around in a binary chop way until I identified the message causing the problem (if you have 1024 potential suspects, you can identify the culprit in just 10 tries this way). In my case, all messages from this particular sender caused trouble, and no others; so when the problem recurred I knew what message to seek and destroy. I sent David Harris a copy of the culprit messages, so the problem may be solved in the latest Mercury/32 (2.16); having worked round the problem, I haven't yet tested whether it is actually solved. Best wishes, -- Michael Salem
Re: Mercury/32 crashes just just after fetching mail, when it tries to distribute
Author: Andrew Steele
Date: Wed, 24 Feb 1999 00:00
Date: Wed, 24 Feb 1999 00:00
19 lines
1621 bytes
1621 bytes
mckenzie@iafrica.com (Cameron Mckenzie) wrote:
>It was running successfully for some 6 months. Then all of a sudden
>it starts crashing with a page fault in KERNEL32.DLL just after
>collecting the POP3 mail and as it tries to distribute the mail via
>the DOMAIN mailbox.
I've had something similar happen in two independent installations. I
never tracked down the cause but removing and reinstalling Mercury/32
seemed to solve the problem which has not subsequently recurred.
Andrew Steele
================ Andrew Steele ====================
NetWorks - Media Consultants Ltd
Simple Solutions for the Information Age
P.O. Box 154, Keighley | phone & fax: +44 1535 217101
West Yorkshire, BD20 6UU | mobile: +44 973 224346
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads