Ahh - thanks. Problem is, without going through the entire help system, users will not know this, nor other details which appear in the Help, but not in the manual.
Hi folks
Once more into the fray:
I have suddenly begun seeing this message for mail addresssed to one of our staff:
Received: from spooler by apsarchaeology.co.uk (Mercury/32 v4.52); 25 May 2008 00:00:03 +0100
X-Envelope-To: Electronic Postmaster <Admin@apsarchaeology.co.uk>
To: Electronic Postmaster <Admin@apsarchaeology.co.uk>
From: Electronic Postmaster <postmaster@apsarchaeology.co.uk>
Date: Sat, 24 May 2008 23:59:50 +0100
Subject: Postmaster Notify: Delivery Failure.
MIME-Version: 1.0
Content-type: multipart/mixed; boundary=8109.-393682578
X-PMFLAGS: 570949760 0 1 Y6JMN9XF.CNM
This message is in MIME format. If you are seeing this text,
then your mailer does not understand this format properly.
--8109.-393682578
Content-type: Text/Plain; charset=US-ASCII
Content-Disposition: Inline
Content-Description: Reason for delivery failure.
The attached message has failed delivery and has been referred
to you as postmaster. The following error report or reports
were given to explain the problem:
*** <user@apsarchaeology.co.uk>
Error getting mailbox information for user.Error getting mailbox information for user.Error getting mailbox information for user.Error getting mailbox information for user.Error getting mailbox information for user.Error getting mailbox information for u
s
er.Error getting mailbox information for user.Error getting mailbox information for user.Error getting mailbox information for user.Error getting mailbox information for user.Error getting mailbox information for user.Error getting mailbox information fo
r
user.Error getting mailbox information for user.Error getting mailbox information for user.Error getting mailbox information for user.Error getting mailbox information for user.Error getting mailbox information for user.
--8109.-393682578
Content-type: Message/RFC822
X-SPAMWALL: Passed through antiSPAM test by SpamHalter 4.3.1 on apsarchaeology.co.uk (2668)
X-SPAMWALL: probability - 0.0%
X-SPAMWALL: Whitelisted
Return-path: <sender@domain.com>
Received: from mail178.messagelabs.com (85.158.139.19) by apsarchaeology.co.uk (Mercury/32 v4.52) ID MG000176;
24 May 2008 15:58:17 +0100
X-VirusChecked: Checked
X-Env-Sender: sender@domain.com
X-Msg-Ref: server-2.tower-178.messagelabs.com!1211641180!12344338!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,apsarchaeology.co.uk
X-Originating-IP: [217.146.188.9]
X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG,
HTML_10_20,HTML_MESSAGE,ML_MATCH_27,ML_MATCH_4
Received: (qmail 12385 invoked from network); 24 May 2008 14:59:41 -0000
Received: from web86010.mail.ird.yahoo.com (HELO web86010.mail.ird.yahoo.com) (217.146.188.9)
by server-2.tower-178.messagelabs.com with SMTP; 24 May 2008 14:59:41 -0000
Received: (qmail 24742 invoked by uid 60001); 24 May 2008 14:59:40 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=s1024; d=btinternet.com;
h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
b=w3sqPmPpzrxRDnCgtAvotXTe82NPOKTq+CgoDC3PqO1KC6zL9Vz1qwIEnYoNk7SXjS2U50oEDdHHfP9XNwD+k1eVdVpSzZgHRNVNIoI17PH2FLb6Y1BdGU6KJGnaxPaarfpEHQi4NRo+ngw57oEJ6hM3WX1MtVzJr5ugICHs9Xo=;
X-YMail-OSG: B7dobdsVM1kuBSRXeW1xxHT0k0pB2vFxsM7kT7_glV0cGykPG6WjBbcnejFzJRNeg.c1Ua.FrLZuyFNaryPtiIRMPD72GGS1weEH2Q--
Received: from [88.111.238.51] by web86010.mail.ird.yahoo.com via HTTP; Sat, 24 May 2008 15:59:40 BST
Date: Sat, 24 May 2008 15:59:40 +0100 (BST)
From: SENDER <sender@domain.com>
Subject: Re: Test Pit survey
To: user <user@apsarchaeology.co.uk>
In-Reply-To: <4836DB19.22087.17130E0@user.apsarchaeology.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1480858396-1211641180=:24237"
Content-Transfer-Encoding: 8bit
Message-ID: <785193.24237.qm@web86010.mail.ird.yahoo.com>
--0-1480858396-1211641180=:24237
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
The user's mail account was receiving mail without problems last week. Today I tried sending a mail to this person, and the Mercury Core process reports:
09:28:38: Job MG000443: from greenman@googlemail.com (non-local)
To: user (local) *Deferred
Mail is being successfully delivered to all other users on the system. I thought it might be a similar issue to what I had before when mail was being deferred, so I reset the security for the user's mailbox which did not work. Next I stripped out all users and re-applied the permissions. And the same problem persists.
Does anyone have any ideas what may be causing this, please?
Thanks
Never seen this myself, but (as you seem to be aware) this can occur when the user folder is inaccessible for one reason or another.
My first step would be what you have already done.
Maybe some (minor if only one user affected) corruption of pmail.usr?
My next steps would be:
Back up user folder.
Delete user (from Mercury 'Manage Users')
Verify folder is removed
Restart Mercury
Re-add user
Test mail delivery
(Assuming success [:)]) Copy back user data.
(Assuming failure [:'(]) Post to forum again. [:P]
[quote user="dilberts_left_nut"]
Never seen this myself, but (as you seem to be aware) this can occur when the user folder is inaccessible for one reason or another.
My first step would be what you have already done.
Maybe some (minor if only one user affected) corruption of pmail.usr?
My next steps would be:
Back up user folder.
Delete user (from Mercury 'Manage Users')
Verify folder is removed
Restart Mercury
Re-add user
Test mail delivery
(Assuming success [:)]) Copy back user data.
(Assuming failure [:'(]) Post to forum again. [:P]
[/quote]
Thanks a lot for replying.
As soon as I went into Manage Users from within Mercury I saw the problem. The user's account was not listed. This is odd as it was present in pmail.usr. Anyway, I did as you suggested and now everything is working again.
Cheers and grateful beers!
Thanks for the reply, Peter.
If this was the case and the file could only be partially read, wouldn't this have affected other pmail.usr entries too? All other names were present in the list that appeared when I used Mercury's 'Manage Local Users' dialog.
What is best practice regards this? With Mercury installed, is it advisable to use Mercury to manage the users or Pegasus Mail, or does it not matter?
Thanks.
What is best practice regards this? With Mercury installed, is it
advisable to use Mercury to manage the users or Pegasus Mail, or does
it not matter?
Mercury and using the CTRL+Configuration + Manage local user. The changes made by Pegasus Mail will not be picked up by the running copy of Mercury.
[quote user="Greenman"]Thanks, Thomas. That is an essential piece of information. Is it in the manual?[/quote]
I suspect is is but I've not read the whole manual. It is in the help:
Important note: Mercury reads the Pegasus Mail system file PMAIL.USR to obtain local user information, and caches it in memory while it runs. If you make changes to PMAIL.USR using Pegasus Mail or via any other process that manipulates the file directly, you will need open the Mercury user administration dialog while holding down the CTRL key, to force it to re-scan the list. Restarting Mercury will also work in this situation. Until Mercury refreshes its cached copy of the user list, it will not be able to deliver to users added via the alternative method. Mercury saves changes made by its own user dialog as soon as you click OK, so we recommend that you do all your user administration from within Mercury.
