Mail being delivered multiple times ?

[kechols]

I have 1 user that is having every email she gets delivered to her zimbra inbox every minute, even if it's already been received. I've logged into her mailbox, deleted all her mail, and watched the same one I just deleted come back in one minute later. I've deleted the account and re-added it with no change in the problem. I'm running 3.0.1Ga (I know it's old, I've had bad luck with upgrading so far). Has anyone seen anything like this? Know of a way to fix it?

Thanks,
Kyle

[kechols]

Seems the problem has cleared itself for the moment....

[Guest6400]

I have had this happen to one user where they got all emails twice. Then around 2 hours later(possibly a reboot in there too) they were getting 3 of all emails.

Looking in the web client side the user only had 1 copy of each email.

Recreated the user's profile and everything worked fine.

I have no idea what caused this and it hasn't come back again.

[kechols]

Ok, so it's not cleared up, I've managed to get it stopped for about 10 minutes and it started right back... I'm thinking it may be getting hung in the antivirus or antispam queue. Anyone know of any other reason this would happen? I've deleted and recreated the profile, verified it's not an outlook problem, re-indexed the mailbox (with and without the duplicate emails in it). Anyone heard of the antispam process causing a problem like this?

Thanks,
Kyle

[raj]

I have seen this behavior in other email systems than Zimbra if the EMAIL CLIENT (i.e outlook) is set to POP the server with small interval (i.e: 1-3 min).

If this error is on EMAIL CLIENT please make sure your interval to check POP3 server is > 5 min.

Email client keeps index of emails downloaded, many times if its checking email again before it finished downloading email and these process overlapping you will keep getting the same email again. Actually there is only ONE copy on server.

Hope this helps..

Raj

[Guest6400]

If you're using Outlook check that in the WebUI there isn't duplicates. If there isn't it's a client problem, if there is then it's probably server related.

You haven't said what client you're using or how the user is getting the mail.

[kechols]

I see it showing up in the web client (zimbra) and her outlook inbox. I even see it when running postque -p |grep email repeatedly showing up (in ~1 minute intervals).

[kechols]

ok, so I thought the problem was in the AV engine but after disabling it I still see messages looping through the queue and redelivering, here is a sample from one of the few users (i recently found out this is affecting at least 3 -5 users) I know are having this issue.

Jun 11 08:53:08 mailserv6 amavis[15940]: (15940-03) ESMTP::10024 /opt/zimbra/ama
visd/tmp/amavis-20070611T085244-15940: <ltarrant@first-american.com> -> <lpattil
lo@access-bank.com> Received: SIZE=11186 from mailserv6.access-bank.com ([127.0.
0.1]) by localhost (mailserv6.access-bank.com [127.0.0.1]) (amavisd-new, port 10
024) with ESMTP id 15940-03 for <lpattillo@access-bank.com>; Mon, 11 Jun 2007 08
:53:08 -0500 (CDT)
Jun 11 08:53:08 mailserv6 amavis[15940]: (15940-03) Checking: ee2MsVVZ1x0Y [192.
168.4.2] <ltarrant@first-american.com> -> <lpattillo@access-bank.com>
Jun 11 08:53:09 mailserv6 amavis[15940]: (15940-03) FWD via SMTP: <ltarrant@firs
t-american.com> -> <lpattillo@access-bank.com>, 250 2.6.0 Ok, id=15940-03, from
MTA([127.0.0.1]:10025): 250 Ok: queued as AF2E43355CA
Jun 11 08:53:09 mailserv6 amavis[15940]: (15940-03) Passed CLEAN, LOCAL [192.168
.4.2] [192.168.4.2] <ltarrant@first-american.com> -> <lpattillo@access-bank.com>
, Message-ID: <013c01c7ac30$0bf96590$1bad000a@PELLCITY26>, mail_id: ee2MsVVZ1x0Y
, Hits: -, 703 ms
Jun 11 08:57:58 mailserv6 amavis[17076]: (17076-09) ESMTP::10024 /opt/zimbra/ama
visd/tmp/amavis-20070611T085657-17076: <lpattillo@access-bank.com> -> <ltarrant@
access-bank.com> Received: SIZE=13050 from mailserv6.access-bank.com ([127.0.0.1
]) by localhost (mailserv6.access-bank.com [127.0.0.1]) (amavisd-new, port 10024
) with ESMTP id 17076-09 for <ltarrant@access-bank.com>; Mon, 11 Jun 2007 08:57:
58 -0500 (CDT)
Jun 11 08:57:58 mailserv6 amavis[17076]: (17076-09) Checking: nXtfVVOjAi7f [192.
168.4.2] <lpattillo@access-bank.com> -> <ltarrant@access-bank.com>
Jun 11 08:57:58 mailserv6 amavis[17076]: (17076-09) FWD via SMTP: <lpattillo@acc
ess-bank.com> -> <ltarrant@access-bank.com>, 250 2.6.0 Ok, id=17076-09, from MTA
([127.0.0.1]:10025): 250 Ok: queued as C5CB93355C4
Jun 11 08:57:58 mailserv6 amavis[17076]: (17076-09) Passed CLEAN, LOCAL [192.168
.4.2] [192.168.4.2] <lpattillo@access-bank.com> -> <ltarrant@access-bank.com>, M
essage-ID: <001801c7ac30$6bdcab20$8004000a@AccessBank.com>, mail_id: nXtfVVOjAi7
f, Hits: -, 228 ms
Jun 11 09:02:42 mailserv6 amavis[20478]: (20478-07-2) ESMTP::10024 /opt/zimbra/a
mavisd/tmp/amavis-20070611T090138-20478: <ltarrant@first-american.com> -> <lpatt
illo@access-bank.com> Received: SIZE=14825 from mailserv6.access-bank.com ([127.
0.0.1]) by localhost (mailserv6.access-bank.com [127.0.0.1]) (amavisd-new, port
10024) with ESMTP id 20478-07-2 for <lpattillo@access-bank.com>; Mon, 11 Jun 200
7 09:02:42 -0500 (CDT)
Jun 11 09:02:42 mailserv6 amavis[20478]: (20478-07-2) Checking: zGZXuLJNulny [19
2.168.4.2] <ltarrant@first-american.com> -> <lpattillo@access-bank.com>
Jun 11 09:02:42 mailserv6 amavis[20478]: (20478-07-2) FWD via SMTP: <ltarrant@fi
rst-american.com> -> <lpattillo@access-bank.com>, 250 2.6.0 Ok, id=20478-07-2, f
rom MTA([127.0.0.1]:10025): 250 Ok: queued as 529FA3355DE
Jun 11 09:02:42 mailserv6 amavis[20478]: (20478-07-2) Passed CLEAN, LOCAL [192.1
68.4.2] [192.168.4.2] <ltarrant@first-american.com> -> <lpattillo@access-bank.co
m>, Message-ID: <015001c7ac31$3b530520$1bad000a@PELLCITY26>, mail_id: zGZXuLJNul
ny, Hits: -, 596 ms
Jun 11 09:09:19 mailserv6 amavis[28212]: (28212-01) ESMTP::10024 /opt/zimbra/ama
visd/tmp/amavis-20070611T090919-28212: <lpattillo@access-bank.com> -> <ltarrant@
access-bank.com> Received: SIZE=16799 from mailserv6.access-bank.com ([127.0.0.1
]) by localhost (mailserv6.access-bank.com [127.0.0.1]) (amavisd-new, port 10024
) with ESMTP id 28212-01 for <ltarrant@access-bank.com>; Mon, 11 Jun 2007 09:09:
19 -0500 (CDT)
Jun 11 09:09:19 mailserv6 amavis[28212]: (28212-01) Checking: AvEOBkGbqcIw [192.
168.4.2] <lpattillo@access-bank.com> -> <ltarrant@access-bank.com>
Jun 11 09:09:19 mailserv6 amavis[28212]: (28212-01) FWD via SMTP: <lpattillo@acc
ess-bank.com> -> <ltarrant@access-bank.com>, 250 2.6.0 Ok, id=28212-01, from MTA
([127.0.0.1]:10025): 250 Ok: queued as 7CD733355D3
Jun 11 09:09:19 mailserv6 amavis[28212]: (28212-01) Passed CLEAN, LOCAL [192.168
.4.2] [192.168.4.2] <lpattillo@access-bank.com> -> <ltarrant@access-bank.com>, M
essage-ID: <002601c7ac31$f7840d70$8004000a@AccessBank.com>, mail_id: AvEOBkGbqcI
w, Hits: -, 482 ms

Keep in mind this user is receiving the same 3 or 4 emails over 100 times in less than an hour...
Thanks,
Kyle

[kechols]

If you're using Outlook check that in the WebUI there isn't duplicates. If there isn't it's a client problem, if there is then it's probably server related.

You haven't said what client you're using or how the user is getting the mail.

My users use Outlook, I've checked through the webmail interface and see the multiple emails showing up there as well. This isn't a client problem, as I see the emails being delivered repeatedly in the logs and the webmail interface. Does anyone know any reason this would happen?

Thanks,
Kyle

[kechols]

I was digging around and found about 400 directories in /opt/zimbra/amavis/tmp
is this where amavis stores (or gets) it's que? If so, would it be safe to delete the sub-directores ?

I did some more googling on amavis and found this link
freespamfilter.org :: View topic - problem with redhat 9 setup
which seems to be a similar problem, but before i delete 400 directories I want to be sure I'm not doing more harm than good...


Thanks,