Cyrus vacation notice

Andrew Nash nashcom at btinternet.com
Mon Apr 19 09:41:32 EDT 2010


Thanks for that.  I edited the main.cf file at the end of last week when I noticed the error messages weren't available!
 
In main.cf I now have:
 
error_notice_recipient = root at server.domain
bounce_notice_recipient = $error_notice_recipient 
2bounce_notice_recipient = $error_notice_recipient
delay_notice_recipient = $error_notice_recipient

After making the above changes, I found the previously described notification in the root mailbox:
 
>From MAILER-DAEMON  Mon Apr 19 10:58:33 2010
Return-Path: <>
Delivered-To: root at server.domain
Received: by server.domain (Postfix, from userid 41)
            id 4C13E7E222; Mon, 19 Apr 2010 10:58:33 +0100 (BST)
Message-ID: <cmu-sieve-11863-1271671113-1 at server.domain>
Date: Mon, 19 Apr 2010 10:58:33 +0100
X-Sieve: CMU Sieve 2.2
From: <outofofficeuser at domain>
To: <root at server.domain>
Subject: Absence notification
In-Reply-To: <20100419-10541090-2044 at 264029-mta1-03.lon.intensive.int>
Auto-Submitted: auto-replied (vacation)
 
This is an automated reply.
This person is temporarily out of the office
and has left the following note:
 
I am out of the office at a training course until Wednesday 28 April. I will respond to your email on my return. If you wish to speak to someone, please call reception on 999999. 

 
I'm new to the inner workings of the mail server, so it's taking me a bit of time to trace messages through the system.  Is it possible to tell anything from the above - for example, if Cyrus is using the wrong field to deliver the out of office message?
 
Thanks again for your help.
 
David
 

--- On Mon, 19/4/10, Adam Tauno Williams <awilliam at whitemice.org> wrote:


From: Adam Tauno Williams <awilliam at whitemice.org>
Subject: Re: Cyrus vacation notice
To: info-cyrus at lists.andrew.cmu.edu
Date: Monday, 19 April, 2010, 14:01


On Mon, 2010-04-19 at 14:37 +0200, Marc Patermann wrote:
> > I couldn’t find any trace of a postmaster mailbox, so I changed the
> > error logging address to ‘root’.
> If postfix may not have been able to deliver to the postmaster mailbox
> there must be information in the log file about this.
> If error message go to an non existing mailbox this is an configuration
> problem. Fix this!

+1 +1 +1

Check out the Postfix configuration directives: "notify_classes",
"2bounce_notice_recipient", "bounce_notice_recipient",
"delay_notice_recipient", "double_bounce_sender", and
"error_notice_recipient".  Tuning these can make your life much simpler.

-- 
OpenGroupware developer: awilliam at whitemice.org
<http://whitemiceconsulting.blogspot.com/>
OpenGroupare & Cyrus IMAPd documenation @
<http://docs.opengroupware.org/Members/whitemice/wmogag/file_view>

----
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20100419/40493b76/attachment-0001.html 


More information about the Info-cyrus mailing list