/2014 05:25 PM, Joseph Brennan wrote:
> Alvin Starr wrote:
>
>> I am guessing that since one copy of the message is created using the
>> imap interface and the other is created using the LMTP delivery that the
>> duplicate delivery is not catching them.
> To be precise, a c
Alvin Starr wrote:
> I am guessing that since one copy of the message is created using the
> imap interface and the other is created using the LMTP delivery that the
> duplicate delivery is not catching them.
To be precise, a client creates the sent mail copy by writing it to the
fo
I am using postfix with Cyrus and I have a number of people who are
using clients that will not place a copy of the sent mail into the Sent
folder.
I have configured postfix to place a BCC'd copy into the sent folder.
I was hoping the the duplicate delivery mechanism would work to insure
On Tue, Mar 08, 2011 at 04:30:45PM +0100, Eric Luyten wrote:
> On Tue, March 8, 2011 4:24 pm, Gary Mills wrote:
> > We are running cyrus-imapd-2.3.8 with this entry in /etc/cyrus.conf:
> >
> > delprune cmd="cyr_expire -E 3" at=0400
> >
> > I believe this is the default setting. Is there any r
On Tue, March 8, 2011 4:24 pm, Gary Mills wrote:
> We are running cyrus-imapd-2.3.8 with this entry in /etc/cyrus.conf:
>
>
> delprune cmd="cyr_expire -E 3" at=0400
>
> I believe this is the default setting. Is there any reason to keep
> message IDs around for three days? I'm wondering if re
We are running cyrus-imapd-2.3.8 with this entry in /etc/cyrus.conf:
delprune cmd="cyr_expire -E 3" at=0400
I believe this is the default setting. Is there any reason to keep
message IDs around for three days? I'm wondering if reducing it to
one day will improve performance for local d
Hi,
Am Mittwoch, den 21.04.2010, 00:37 +0200 schrieb Marcus:
[...]
> I did clean /var/lib/cyrus/db and deleted /var/lib/cyrus/deliver.db
> after stopping cyrus. But after three day I got the same error
[...]
I've checked the logs again tonight and the "IOERROR: lock_shared" only
comes up while du
Hi,
Am Dienstag, den 06.04.2010, 18:13 -0500 schrieb Dan White:
> On 07/04/10 00:45 +0200, Marcus wrote:
> >I've restarted cyrus and got a "recovery /var/lib/cyrus/deliver.db:
> >found partial txn, not replaying". Delivering is working fine and
> >dupelim check too. Could someone confirm, that Sim
On 07/04/10 00:45 +0200, Marcus wrote:
>I've restarted cyrus and got a "recovery /var/lib/cyrus/deliver.db:
>found partial txn, not replaying". Delivering is working fine and
>dupelim check too. Could someone confirm, that Simon's idea to clean
>up /var/lib/cyrus/db and remove deliver.db is _not_
On Wed, 7 Apr 2010, Marcus wrote:
>> Just guessing, maybe you have to stop cyrus, clean up the $configdir/db
>> directory, remove the existing deliver.db file and start up again.
>> Maybe you have some BDB stuff left over in ../db.
>
> I've restarted cyrus and got a "recovery /var/lib/cyrus/delive
red /var/lib/cyrus/deliver.db: Interrupted system call
> > Apr 5 04:12:48 server cyrus/lmtpunix[8473]: DBERROR:
> > opening /var/lib/cyrus/deliver.db: cyrusdb error
> > Apr 5 04:12:48 server cyrus/lmtpunix[8473]: FATAL: lmtpd: unable to
> > init duplicate delivery database
&
/deliver.db: Interrupted system call
> > Apr 5 04:12:48 server cyrus/lmtpunix[8473]: DBERROR:
> > opening /var/lib/cyrus/deliver.db: cyrusdb error
> > Apr 5 04:12:48 server cyrus/lmtpunix[8473]: FATAL: lmtpd: unable to
> > init duplicate delivery database
> > Apr
RROR:
> opening /var/lib/cyrus/deliver.db: cyrusdb error
> Apr 5 04:12:48 server cyrus/lmtpunix[8473]: FATAL: lmtpd: unable to
> init duplicate delivery database
> Apr 5 04:12:48 server cyrus/master[21374]: process 8473 exited, status
> 75
> Apr 5 04:12:48 server cyrus/master[21
/deliver.db: cyrusdb error
Apr 5 04:12:48 server cyrus/lmtpunix[8473]: FATAL: lmtpd: unable to
init duplicate delivery database
Apr 5 04:12:48 server cyrus/master[21374]: process 8473 exited, status
75
Apr 5 04:12:48 server cyrus/master[21374]: service lmtpunix pid 8473 in
READY state: terminated
ed Cyrus duplicate suppression by adding the
>> following line to my imapd.conf :
>>
>> duplicatesuppression: 0
>>
>>
>>
>> Somewhat naively I thought that Cyrus wouldn't be writing the duplicate
>> delivery database anymore, but this is no
:
duplicatesuppression: 0
Somewhat naively I thought that Cyrus wouldn't be writing the duplicate
delivery database anymore, but this is not the case.
Cyrus still needs to write to the delivery database, e.g. for vacation
messages. But it will deliver messages even if they have the same
message-id.
Is
thought that Cyrus wouldn't be writing the duplicate
delivery database anymore, but this is not the case.
Is there, other than by patching the C code, a way to disable writing
delivery.db ?
This is a Cyrus 2.2 system, upgrading to 2.3 this summer.
Regards,
Eric Luyten, Computing Centre VU
Test schrieb:
> I am running in a stupid thing and am probably overlooking something:
>
> I'm running web-cyradm, postfix, cyrus-imapd...
>
> I have multiple domains with an info@ adres ([EMAIL PROTECTED],
> [EMAIL PROTECTED])
>
> When i send an email to [EMAIL PROTECTED] it also gets delivered
All,
I am running in a stupid thing and am probably overlooking something:
I'm running web-cyradm, postfix, cyrus-imapd...
I have multiple domains with an info@ adres ([EMAIL PROTECTED],
[EMAIL PROTECTED])
When i send an email to [EMAIL PROTECTED] it also gets delivered to
[EMAIL PROTECTED] whi
I have duplicate delivery suppression turned off in my imapd.conf file
duplicate_suppression: 0
but I still a lot log messages about eliminating duplicate delivery
Jan 18 18:54:53 liverwurst lmtp[22929]: dupelim: eliminated duplicate
message to user.cp2195 id <[EMAIL PROTECTED]> (de
init duplicate delivery
database
unable to initialize inviromnent loc
All these errors keep going on and on. I remove the contents of the db
folder and deliver.db and restarted cyrus-imapd. I did not help. These
mistakes stopped occuring when I removed /var/lib/imap/socket folder but
I was
On Fri, 15 Apr 2005, Martine James (02 23 23 71 31) wrote:
I installed Cyrus one year ago and it used to work nicely with option
"duplicatesuppression" as set by default (YES)
Things went wrong four days ago with this message:
Apr 14 12:00:04 machine.etu.univ-rennes1.fr pop3[7118]: [ID 729713
loc
569]: [ID 157947
local6.error] FATAL: lmtpd: unable to init duplicate delivery database
this a sendmail log:
Apr 14 14:28:37 machine.etu.univ-rennes1.fr postfix/lmtp[10031]: [ID 197553
mail.info] 8D46E4D: to=<[EMAIL PROTECTED]>, orig_to=<[EMAIL PROTECTED]>,
relay=none, delay=0, status=d
On Tue, 01 Feb 2005, Kyle Silfer wrote:
> Andreas Hasenack <[EMAIL PROTECTED]> said:
> > > > Exactly what DB4 version? I'm using 4.2.52 + two patches and never had
> > > > this
> > > issue.
> > >
> > > This is 4.1.25 from the SuSE 9.0 install CDs.
> > >
> > > Are you saying this version may be b
Andreas Hasenack <[EMAIL PROTECTED]> said:
> > > Exactly what DB4 version? I'm using 4.2.52 + two patches and never had
> > > this
> > issue.
> >
> > This is 4.1.25 from the SuSE 9.0 install CDs.
> >
> > Are you saying this version may be buggy and I should have the latest?
>
> You should chec
On Thu, Jan 27, 2005 at 01:03:19AM -, Kyle Silfer wrote:
> Kyle Silfer <[EMAIL PROTECTED]> said:
>
> > Andreas Hasenack <[EMAIL PROTECTED]> said:
> >
> > > Exactly what DB4 version? I'm using 4.2.52 + two patches and never had
> > > this
> > issue.
> >
> > This is 4.1.25 from the SuSE 9.0 i
On Wed, Jan 26, 2005 at 07:53:10PM -, Kyle Silfer wrote:
> Andreas Hasenack <[EMAIL PROTECTED]> said:
>
> > On Wed, Jan 26, 2005 at 06:29:58PM -, Kyle Silfer wrote:
> > > I suspected a problem with deliver.db, so I shut cyrus down and renamed
> > > it.
> > > The problem remains with the f
Kyle Silfer wrote:
>> Are you saying this version may be buggy and I should have the
>> latest?
>
> Since no one has responded, let me expand my query:
>
> Are there any issues just compiling and installing the latest
> Berkeley DB sources to match the SuSE RPM file layout? Will my
> existing Cyrus
Kyle Silfer <[EMAIL PROTECTED]> said:
> Andreas Hasenack <[EMAIL PROTECTED]> said:
>
> > Exactly what DB4 version? I'm using 4.2.52 + two patches and never had this
> issue.
>
> This is 4.1.25 from the SuSE 9.0 install CDs.
>
> Are you saying this version may be buggy and I should have the late
Andreas Hasenack <[EMAIL PROTECTED]> said:
> On Wed, Jan 26, 2005 at 06:29:58PM -, Kyle Silfer wrote:
> > I suspected a problem with deliver.db, so I shut cyrus down and renamed it.
> > The problem remains with the freshly-created deliver.db.
> >
> > This is with Cyrus 2.1.15 on SuSE Linux 9.
On Wed, Jan 26, 2005 at 06:29:58PM -, Kyle Silfer wrote:
> I suspected a problem with deliver.db, so I shut cyrus down and renamed it.
> The problem remains with the freshly-created deliver.db.
>
> This is with Cyrus 2.1.15 on SuSE Linux 9.0. Postfix is the MTA. What should I
> be doing to fix
I am having major issues with the duplicate suppression in Cyrus. Essentially,
sometimes it works and sometimes it doesn't.
After lots of testing, results remain erratic: sometimes some of the dupes are
caught, sometimes none of the dupes are caught, and sometimes all of the dupes
are caught.
He
x[30172]: mystore: committing txn 2147500838
Aug 30 04:27:08 ns3 lmtpunix[30172]: duplicate_mark:
<[EMAIL PROTECTED]>.urkle+drip.ws.sieve.
1093858028 0
Does anyone have any clue why this has happened? Is this as a result of
duplicate delivery? if it is, I thought it was not su
committing txn 2147500838
Aug 30 04:27:08 ns3 lmtpunix[30172]: duplicate_mark:
<[EMAIL PROTECTED]>.urkle+drip.ws.sieve.
1093858028 0
Does anyone have any clue why this has happened? Is this as a result of
duplicate delivery? if it is, I thought it was not supposed to take
On Fri, 20 Aug 2004, Rob Carter wrote:
Gentlefolk,
Does anyone have experiences they'd be willing to share with combatting
deadlocks within a BDB 3.3 duplicate delivery database on a high-traffic
Cyrus v2.1.16 (or earlier 2.1.x) server? We're running a 60,000+ user/1.2
million m
,
>
> Does anyone have experiences they'd be willing to share with combatting
> deadlocks within a BDB 3.3 duplicate delivery database on a high-traffic Cyrus
> v2.1.16 (or earlier 2.1.x) server? We're running a 60,000+ user/1.2 million
> message/day Cyrus postoffice on a
Gentlefolk,
Does anyone have experiences they'd be willing to share with combatting
deadlocks within a BDB 3.3 duplicate delivery database on a high-traffic Cyrus
v2.1.16 (or earlier 2.1.x) server? We're running a 60,000+ user/1.2 million
message/day Cyrus postoffice on an 8-way Sola
On Wed, 18 Feb 2004, Joakim Ryden wrote:
> On Wednesday 18 February 2004 02:17 am, Per Steinar Iversen wrote:
> > Is it possible to avoid the use of duplicate delivery suppression?
> [...]
>
> 'man imapd.conf' - look for 'duplicatesuppression'.
Note that
On Wednesday 18 February 2004 02:17 am, Per Steinar Iversen wrote:
> Is it possible to avoid the use of duplicate delivery suppression?
[...]
'man imapd.conf' - look for 'duplicatesuppression'.
--Jo
---
Home Page: http://asg.web.cmu.edu/cyrus
Wiki/FAQ: http://cyrusw
Is it possible to avoid the use of duplicate delivery suppression?
Today our Cyrus imapd had its delivery database corrupted, after that we
had no new deliveries. Looking at the log it seems that duplicates are
actually detected rather infrequently... I would rather have an occasional
duplicate
On Wed, 03 Dec 2003, Rob Siemborski wrote:
> On Wed, 3 Dec 2003, Christian Schulte wrote:
> > Richard Gilbert schrieb:
> > > The reason why I am restarting the server is to deal with the odd
> > > "IOERROR: reading message: unexpected end of file" errors, which I am
> > > still getting, which first
On Wed, 3 Dec 2003, Christian Schulte wrote:
> Richard Gilbert schrieb:
> > The reason why I am restarting the server is to deal with the odd
> > "IOERROR: reading message: unexpected end of file" errors, which I am
> > still getting, which first led me to the lock_flock patch (archive message
> >
Richard Gilbert schrieb:
The reason why I am restarting the server is to deal with the odd
"IOERROR: reading message: unexpected end of file" errors, which I am
still getting, which first led me to the lock_flock patch (archive message
18705).
This is interesting. I am also seeing these entries fro
g the duplicate.db before restarting. ([EMAIL PROTECTED] said he ran
reconstruct -f after deleting the database but reconstruct doesn't seem to
be relevant to the duplicate delivery database so I won't bother.)
The duplicate delivery database (Berkeley DB3) seems to be at the root o
ap/deliver.db: Invalid argument
> Nov 18 13:49:09 tux lmtpd[19879]: DBERROR: opening
> /var/lib/imap/deliver.db: cyrusdb error
> Nov 18 13:49:09 tux lmtpd[19879]: FATAL: lmtpd: unable to init
> duplicate
> delivery database
> Nov 18 13:49:09 tux ctl_cyrusdb[19874]: done checkpointing
18 13:49:09 tux lmtpd[19879]: DBERROR: opening
/var/lib/imap/deliver.db: Invalid argument
Nov 18 13:49:09 tux lmtpd[19879]: DBERROR: opening
/var/lib/imap/deliver.db: cyrusdb error
Nov 18 13:49:09 tux lmtpd[19879]: FATAL: lmtpd: unable to init duplicate
delivery database
Nov 18 13:49:09 tux
18 13:49:09 tux lmtpd[19879]: DBERROR: opening
/var/lib/imap/deliver.db: Invalid argument
Nov 18 13:49:09 tux lmtpd[19879]: DBERROR: opening
/var/lib/imap/deliver.db: cyrusdb error
Nov 18 13:49:09 tux lmtpd[19879]: FATAL: lmtpd: unable to init duplicate
delivery database
Nov 18 13:49:09 tux
On Thu, 14 Aug 2003, Andrew Brink wrote:
> I looked in the docs, and wiki a few days ago and didn't find anything
> about this, perhaps a wiki post would be helpful.
http://asg.web.cmu.edu/twiki/bin/view/Cyrus/DuplicateDeliveryExplained
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
From: "Andrew Brink" <[EMAIL PROTECTED]>
To: "Cyrus Info list" <[EMAIL PROTECTED]>
Sent: Thursday, August 14, 2003 2:49 PM
Subject: Duplicate Delivery Suppression
> What exactly is duplicate delivery suppression? (Yes, I know it
> suppresses duplicate delive
What exactly is duplicate delivery suppression? (Yes, I know it
suppresses duplicate delivery of messages)
Rather, what I want to know is why messages would be duplicated, etc.
I looked in the docs, and wiki a few days ago and didn't find anything
about this, perhaps a wiki post would be he
On Fri, Jun 27, 2003 at 03:10:47PM +0200, Sebastian Hagedorn wrote:
> Every MTA along the way should add a message-id if there isn't one.
qmail don't add message-id for any messages that comes through
smtp (qmail-smtpd).
Regards,
P.Y. Adi Prasaja
On Fri, 2003-06-27 at 16:48, Rob Siemborski wrote:
> On Fri, 27 Jun 2003, Stephen Grier wrote:
>
> > We use Exim here. The messages do have a Message-Id: header, but with an
> > empty value. I assume Exim will not add or alter the msg-id in this
> > case.
>
> Any idea why this one user is getting
On Fri, 27 Jun 2003 16:52:02 +0100 (BST) David Carter <[EMAIL PROTECTED]> wrote:
> On Fri, 27 Jun 2003, Stephen Grier wrote:
>
> > We use Exim here. The messages do have a Message-Id: header, but with an
> > empty value.
>
> Eeep. That's no fun at all.
>
> > I assume Exim will not add or alter
On Fri, 27 Jun 2003, Stephen Grier wrote:
> Yes, the messages do have a Message-Id: header with an empty value. I've
> identified 2 domains which appear to be doing this.
>
> Would it be reasonable to have lmtpd not add an entry to the deliver db
> for zero-length message-ids?
It would be reasona
On Fri, 27 Jun 2003, Stephen Grier wrote:
> We use Exim here. The messages do have a Message-Id: header, but with an
> empty value. I assume Exim will not add or alter the msg-id in this
> case.
Any idea why this one user is getting a bunch of messages like this, or
what might be generating them?
On Fri, 27 Jun 2003, Stephen Grier wrote:
> We use Exim here. The messages do have a Message-Id: header, but with an
> empty value.
Eeep. That's no fun at all.
> I assume Exim will not add or alter the msg-id in this case.
I suspect this is the case, though arguably Exim should do something abo
the possibility that the server is suppressing
> > messages that are not duplicates, but merely have no message-id header.
> >
> > Has anyone else seen this happening?. If this continues to happen we may
> > have to disable duplicate delivery suppression.
>
> This seem
On Fri, 2003-06-27 at 14:10, Sebastian Hagedorn wrote:
> -- Stephen Grier <[EMAIL PROTECTED]> is rumored to have mumbled on
> Freitag, 27. Juni 2003 13:47 Uhr +0100 regarding non-existent msgids &
> duplicate delivery suppression:
>
> > I have noticed that this
t duplicates, but merely have no message-id header.
>
> Has anyone else seen this happening?. If this continues to happen we may
> have to disable duplicate delivery suppression.
This seems quite likely. If a message doesn't contain a Message-ID, your
mail system should really add one
-- Stephen Grier <[EMAIL PROTECTED]> is rumored to have mumbled on
Freitag, 27. Juni 2003 13:47 Uhr +0100 regarding non-existent msgids &
duplicate delivery suppression:
I have noticed that this has been happening on other occasions, where
lmtpd does a duplicate_check and then a dupl
Hi,
We are currently running cyrus-imapd-2.1.11 with duplicate delivery
suppression enabled.
One of our users complained that they were not receiving their mail.
Having looked at the logs I noticed a string of entries like the
following:
Jun 25 13:11:43 machine lmtpd[18521]:
duplicate_check
, so I don't know if the client which did this, MS Outlook,
> Build 10.0.3416, behaved sensibly or not. We may have to disable
> duplicate delivery suppression if this is likely to happen again.
Disable MS Outlook Build 10.0.3416 instead. Duplicating msgids is
EXTREMELY unacceptable. Or
Hi,
We're currently running cyrus-imapd-2.1.11 with duplicate delivery
suppression enabled.
We recently received a complaint from a user who reported not receiving
a message he was sent. On investigation, it seems that he initially sent
a message to a third party along with a request for a
[EMAIL PROTECTED] schrieb am Wed, Jan 16, 2002 at 04:00:16PM +0100:
> Ken Murchison schrieb am Wed, Jan 16, 2002 at 09:42:35AM -0500:
> >
> >
> > Chris Peck wrote:
> > >
> > > The file "install-perf" seems to indicate that it is possible to
>
Ken Murchison schrieb am Wed, Jan 16, 2002 at 09:42:35AM -0500:
>
>
> Chris Peck wrote:
> >
> > The file "install-perf" seems to indicate that it is possible to
> > "disable duplicate delivery suppression". Does anyone know how to do so?
>
&
Chris Peck wrote:
>
> The file "install-perf" seems to indicate that it is possible to
> "disable duplicate delivery suppression". Does anyone know how to do so?
Not without changing the source. Cyrus 2.1.x has an imapd.conf option
to do so.
Ken
--
Kenneth Mu
The file "install-perf" seems to indicate that it is possible to
"disable duplicate delivery suppression". Does anyone know how to do so?
thanks,
chris
Chris Peck
Manager of Unix Services
Information Technology
The College of William and Mary
Williamsburg, VA 23187
-dupelim.patch/imap/lmtpd.c
--- cyrus-imapd-2.0.16/imap/lmtpd.c Mon May 21 20:21:47 2001
+++ cyrus-imapd-2.0.16-dupelim.patch/imap/lmtpd.c Thu Nov 15 15:54:28 2001
@@ -277,12 +277,17 @@
return EC_SOFTWARE;
}
-/* initialize duplicate delivery database */
-dupelim
SIEVE! If dupe elimination is off, so is SIEVE, as the
comment says in the lmtpd.c: sieve_find_script(const char *user) function
/* duplicate delivery suppression is needed for sieve */
> If it does work, then the thing to do would be to add a config to
> imapd.conf to control wether or no
f you look at (2.0.16) imap/lmtpd.c line 281...
/* initialize duplicate delivery database */
dupelim = 1;
if (duplicate_init(0) != 0) {
syslog(LOG_ERR,
"deliver: unable to init duplicate delivery database\n");
dupelim = 0;
}
"dupelim" is
Hi,
within the Cyrus IMAP package (2.0.16) there is much talk about sieve only
working with duplicate delivery suppression and disabling that would also
disable sieve.
No more information is supplied, only the configure switch --disable-sieve.
My point is: I need *fast* delivery (you may
Hy!
On 04-Sep-2001 Scott Adkins wrote:
>> You definitely need to run recovery on your duplicate delivery
>> database. I might just delete the database entirely; since the
>> duplicate delivery database isn't transactional, it can't guarantee
>> consistency, a
Date: Tue, 04 Sep 2001 18:31:10 -0400
From: Scott Adkins <[EMAIL PROTECTED]>
We stopped the server and nuked the delivery files altogether. This only
worked for 2 days, however, and now we are back to where we were. We see
a constant stream of duplicate delivery database
nd so forth... hitting all the delivery databases ]
>[ there is a mixture of duplicate_check and duplicate-mark entries
> also ]
>
> You definitely need to run recovery on your duplicate delivery
> database. I might just delete the database entirely; since the
> duplicate
]
You definitely need to run recovery on your duplicate delivery
database. I might just delete the database entirely; since the
duplicate delivery database isn't transactional, it can't guarantee
consistency, and there's no critical database in it.
To run recover, you must kill at l
We are seeing problems in our log file with regards to our duplicate
delivery database. They are as follows:
lmtpd[19330]: duplicate_mark: error setting
/536836816: Invalid argument
lmtpd[19330]: duplicate_check: opening /var/imap/deliverdb/deliver-m.db:
Invalid argument
lmtpd[19330
76 matches
Mail list logo
