Old mail-address still active, while distribution list with same name exists

[Alain Spineux]

On Mon, Nov 17, 2008 at 11:36 AM, Volker Stoppe <grenzlaeufer at gmx.net> wrote:
> Hallo!
>
> On Fri, 14 Nov 2008 17:51:10 +0100, Alain Spineux <aspineux at gmail.com>
> wrote:
>>> name1 (address) -> recepient1
>>> name1 gets deleted
>>> name1 (as distribution list) is created: with recepeint1, reciepient2
>>> and
>>> reciepient3
>>> mail to name1 -> mail is only sent to reciepient1
>
>> The forward is done by cyrus imap at delivery, by a sieve script. (
>> look in lmtpd.log )
>> The sieve scrip is attached to a mailbox and probably not deleted at
>> deletion of the mailbox.
>> Kolabd could maybe delete such script at creation and/or deletion time
>> to prevent this kind of problem
>> look into /kolab/var/imapd/sieve/ for the scripts and delete manualy
>> all files in the directory with the same name as mailbox.
>> You could also recreate the normal user, reset the forwarding, then
>> recreate the list ! This is longer
>
>
> Unfortunately nothing helped. I found the folder with the scripts, deleted
> it but it didn't help. Then I deleted the distribution list, recreated the
> user, created a forward for the user and deleted the forward and the
> user-account again. Nothing changed. Below are some logs.
>
> Maybe anyone else has an other idea?

Is-it an openpkg distrib ?

Take a look at,
http://wiki.kolab.org/index.php/What_is_happening_to_my_emails_where_are_their._Search_your_postfix_log_to_find_them
maybe this will help

did you look at /kolab/var/resmgr/resmgr.log

One again what about the postmap query for the distribution list ?

>
> Greetings
>
> Volker
>
>
>
>
>
> When I do a slapcat, the distribution list has the right members:
>
> mail:/kolab/var/imapd/log# slapcat | grep -A 25 mylist
> /kolab/etc/openldap/slapd.conf: line 66: new attribute <member>
> dn: cn=mylist at domain.com,dc=domain,dc=com
> objectClass: kolabGroupOfNames
> cn: mylist at domain.com
> mail: mylist at domain.com
> member: cn=User A,dc=domain,dc=com
> member: cn=User B,dc=domain,dc=com
> member: cn=User C,dc=domain,dc=com
> structuralObjectClass: kolabGroupOfNames
> entryUUID: 7e756234-48dc-102d-8ff0-37fef441d556
> creatorsName: cn=manager,cn=internal,dc=domain,dc=com
> createTimestamp: 20081117101607Z
> entryCSN: 20081117101607Z#000000#00#000000
> modifiersName: cn=manager,cn=internal,dc=domain,dc=com
> modifyTimestamp: 20081117101607Z
>
>
>
> lmtp.log
> Nov 17 11:21:46 mail <debug> lmtp[30196]: accepted connection
> Nov 17 11:21:46 mail <debug> lmtp[30196]: connection from localhost
> [127.0.0.1] preauth'd as postman
> Nov 17 11:21:46 mail <debug> lmtp[30196]: append_fromstage: message 2639
> added to domain.com!user.user^c
> Nov 17 11:21:46 mail <info> lmtp[30196]: Delivered:
> <op.ukrdq8aogaej35 at vst-tp.lichtplatz.net> to mailbox:
> domain.com!user.user^c
> Nov 17 11:21:46 mail <debug> lmtp[30196]: mystore: starting txn 2147487238
> Nov 17 11:21:46 mail <debug> lmtp[30196]: mystore: committing txn
> 2147487238
> Nov 17 11:21:46 mail <debug> lmtp[30196]: duplicate_mark:
> <op.ukrdq8aogaej35 at vst-tp.lichtplatz.net> .user^c+ at domain.com.sieve.
> 1226917306 0
>

You have no error like
Nov 13 09:30:30 eg01.emailgency.loc <debug> lmtpunix[2859]: IOERROR:
fstating sieve script
/kolab/var/imapd/sieve/domain/a/atesteg01.emailgency.loc/c/catcha
ll^atesteg01^emailgency^loc/defaultbc: (2) No such file or directory

meaning their is no default sieve script, then you should have one !

The good way to manage sieve script is to use sieveshell like in :

/kolab/bin/sieveshell -u admin at eg01.emailgency.loc -a
admin at eg01.emailgency.loc localhost
connecting to localhost
Please enter your password:
> help
Usage:
  sieveshell [-u username] [-a authname] [-r realm] <server>

help             - this screen
list             - list scripts on server
put <filename> [<target name>]
                 - upload script to server
get <name> [<filename>]
                 - get script. if no filename display to stdout
delete <name>    - delete script.
activate <name>  - set a script as the active script
deactivate       - deactivate all scripts
quit             - quit
> list
kolab-forward.siv  <- active script


Try to remove and deactive the script this way


>
> mail:/kolab/var/postfix/log# cat postfix.log | grep 34B1C128079:
> Nov 17 11:21:46 mail <info> postfix/smtpd[30054]: 34B1C128079:
> client=217-20-117-138.company.de[217.20.117.138]
> Nov 17 11:21:46 mail <info> postfix/cleanup[30020]: 34B1C128079:
> message-id=<op.ukrdq8aogaej35 at vst-tp.lichtplatz.net>
> Nov 17 11:21:46 mail <info> postfix/qmgr[25211]: 34B1C128079:
> from=<vst at company.de>, size=1732, nrcpt=1 (queue active)
> Nov 17 11:21:46 mail <info> postfix/pipe[29135]: 34B1C128079:
> to=<user.c at domain.com>, orig_to=<mylist at domain.com>, relay=kolabfilter,
> delay=0, status=sent (mail.domain.com)
> Nov 17 11:21:46 mail <info> postfix/qmgr[25211]: 34B1C128079: removed
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you