- dovecot - dovecot.org

[SIEVE] pipe :copy to external program with arguments
by spamvoll＠googlemail.com 02 Aug '18

02 Aug '18

Hi all, quick questions about sieve pipe: I want to pipe spam messages to an external program with additional parameters my spamlearn.sieve script: require ["vnd.dovecot.pipe", "copy", "imapsieve"]; pipe :copy "mybin" ["-h 127.0.0.1:44444" , "markspam"]; I also tried: pipe :copy "mybin" ["-h 127.0.0.1:44444 markspam"]; pipe :copy "mybin" ["-h 127.0.0.1:44444"] ["markspam"]; pipe :copy :args ["-h 127.0.0.1:44444 markspam"] "mybin" ; It never executes correct, it always ends with: Error: sieve: Execution of script /my/path/to/spamlearn.sieve failed So whats the correct syntax ? What works is a single argument: pipe :copy "myscript" ["markspam"]; Dovecot Version 2.3.2.1

3 2

Problems with Sieve and vnd.dovecot.pipe
by Haiko Hertes 02 Aug '18

02 Aug '18

Hello all! I have changed my mailserver from spamassasin and procmail to rspamd and sieve. Rspamd is working, but with some sieve script I still have problems. I have created a script to learn spam: haiko@SERVERNAME:~$ sudo cat /var/vmail/sieve/global/learn-spam.sieve require ["vnd.dovecot.pipe", "copy", "imapsieve"]; pipe :copy "rspamd-learn-spam.sh"; If I run sieve to use this script I get this: haiko@SERVERNAME:~$ sudo sieve /var/vmail/sieve/global/learn-spam.sieve sieve: vnd.dovecot.pipe: file not found sieve: can't require vnd.dovecot.pipe Speicherzugriffsfehler I think, my configs are OK: haiko@SERVERNAME:~$ doveconf -n # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-7-amd64 x86_64 Debian 9.5 auth_debug_passwords = yes auth_mechanisms = plain login PLAIN LOGIN auth_username_format = %Ln debug_log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot.log listen = * log_path = /var/log/dovecot.log mail_gid = postfix mail_location = maildir:~/Maildir mail_privileged_group = postfix mail_uid = postfix managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacati on subaddress comparator-i;ascii-numeric relational regex imap4flags copy includ e variables body enotify environment mailbox date index ihave duplicate mime for everypart extracttext imapsieve namespace inbox { inbox = yes location = mailbox "Deleted Items" { special_use = \Trash } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = . } passdb { driver = pam } passdb { driver = pam } plugin { imapsieve_mailbox1_before = file:/var/vmail/sieve/global/learn-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/var/vmail/sieve/global/learn-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * quota = maildir:User quota quota_exceeded_message = Benutzer %u hat das Speichervolumen überschritten. / User %u has exhausted allowed storage space. sieve = ~/.dovecot.sieve sieve_before = /var/vmail/sieve/global/spam-global.sieve sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.filter sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.filter sieve_implicit_extensions = +vnd.dovecot.pipe +vnd.dovecot.filter sieve_pipe_bin_dir = /var/vmail/sieve/global sieve_plugins = sieve_imapsieve sieve_extprograms sieve_trace_level = tests sieve_user_log = ~/.dovecot.sieve.log } postmaster_address = postmaster(a)hertes.net protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imaps { address = * } process_min_avail = 1 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { process_limit = 1024 } service pop3-login { inet_listener pop3s { address = * } } ssl = required ssl_cert = </etc/letsencrypt/live/hertes.net/fullchain.pem ssl_cipher_list = EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA256:EECD H:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:! RC4: !SEED:!IDEA:!ECDSA:kEDH:CAMELLIA128-SHA:AES128-SHA ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = uid=vmail gid=vmail home=/var/vmail/%d/%n driver = passwd } userdb { driver = passwd } protocol lmtp { mail_plugins = " sieve" postmaster_address = postmaster(a)hertes.net } protocol imap { imap_idle_notify_interval = 29 mins mail_max_userip_connections = 20 mail_plugins = " imap_quota imap_sieve quota imap_quota imap_sieve" } Does anyone of you have a hint what could be wrong here?? Thanks! Best regards, Haiko

2 1

Basic question about file permissions for sieve error log
by J Doe 02 Aug '18

02 Aug '18

Hello, I have an admittedly very basic question, but I am not able to get it to work. I store my global sieve script in: /etc/dovecot. I recently made a mistake in my global sieve script which causes Dovecot to attempt to log the errors in: /etc/dovecot/sieve-global.log In /var/log/dovecot.log I see: Jul 24 15:33:32 lmtp(test(a)example.com): Error: ABVWGAx/V1uKLAAA1B5X9w: sieve: failed to open logfile (LOGGING TO STDERR): open(/etc/dovecot/sieve-global.log) failed: Permission denied (euid=5000(vmail) egid=5000(vmail) missing +w perm: /etc/dovecot, we're not in group 122(dovecot), dir owned by 0:122 mode=0775) …but the group membership shows: $ sudo -u vmail groups vmail dovecot …and I restarted Dovecot, but the same error happens. What am I doing wrong ? Thanks, - J

3 2

LMTP Log
by Thomas Kristensen 02 Aug '18

02 Aug '18

Hey I got a server setup where the Postfix and dovecot is on separated servers. In the postfis log is goes like this on mail in: Jul 26 10:23:13 edimailsl2 postfix/smtpd[12812]: 41blTs18Bzz40nl: client=unknown[172.0.0.12] Jul 26 10:23:21 edimailsl2 postfix/cleanup[12825]: 41blTs18Bzz40nl: message-id=<> Jul 26 10:23:21 edimailsl2 postfix/qmgr[10666]: 41blTs18Bzz40nl: from=<tk(a)multimed.dk>, size=225, nrcpt=1 (queue active) Jul 26 10:23:21 edimailsl2 postfix/lmtp[12827]: 41blTs18Bzz40nl: to=<test(a)domain.dk>, relay=172.26.248.178[172.26.248.178]:2003, delay=8.6, delays=8.5/0.06/0.01/0.08, dsn=2.0.0, status=sent (250 2.0.0 <test(a)domain.dk> oCuyJ/mEWVvFfwAAbOxY/Q Saved) Jul 26 10:23:21 edimailsl2 postfix/qmgr[10666]: 41blTs18Bzz40nl: removed And the LMTP on the Dovecot server is: Jul 26 10:23:21 vanslmtpsl1 dovecot: lmtp(32709): Connect from 172.0.0.1 Jul 26 10:23:21 vanslmtpsl1 dovecot: lmtp(test@ domain.dk): msgid=unspecified: saved mail to INBOX Jul 26 10:23:21 vanslmtpsl1 dovecot: lmtp(32709): Disconnect from 172.0.0.1: Successful quit How can I make LMTP log the ID it gives postfix (oCuyJ/mEWVvFfwAAbOxY/Q)? So I can relate the logs from the 2 servers. Med venlig hilsen Thomas Kristensen [MM_mail_logo_3_AS] Storhaven 12 - 7100 Vejle Tlf: 75 72 54 99 - Fax: 75 72 65 33 E-mail: tk(a)multimed.dk<mailto:tk@multimed.dk>

2 1

question about using procmail
by Joe Wong 01 Aug '18

01 Aug '18

Hello, I am new to Dovecot, testing the setup with Solr FTS plugin. Currently I am using procmail to delivery email into user's mailbox. I am using maildir on file system. I found that if email is delivered via procmail, the indexer-worker is not being called. But when I move the email between folders via IMAP, indexer is involved. Is this expected? - Joe

3 5

lmtp + tcpwrap
by A. Schulze 01 Aug '18

01 Aug '18

Hello, Using the TCP Wrapper Dovecot could control access to IMAP and POP3 servers. Is it also possible to controll access to an LMTP Server listening on Port 24? Andreas

1 0

Re: Get rid of the "dbox-Mails"-folder
by Hativ 31 Jul '18

31 Jul '18

Hey Aki, DIRNAME with empty value has no effect, just like with FULLDIRNAME. "~/sdbox" instead of "~/" doesn't change that.. Greetings, Hativ Am 07.07.2018 um 20:24 schrieb Aki Tuomi: > Does it work better if you use > > mail_location=sdbox:~/sdbox:DIRNAME= > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Hativ <hativ3(a)gmail.com> > Date: 07/07/2018 20:53 (GMT+02:00) > To: dovecot(a)dovecot.org > Subject: Re: Get rid of the "dbox-Mails"-folder > > Hey again, > > sorry, but I have to correct me: Even with dot it's not working > completely. The subscriptions file is not created and the dovecot-acl > file has the wrong path, too. > > :-( > > Greetings, > > Hativ > > Am 07.07.2018 um 02:26 schrieb Hativ: >> Hey again, >> >> I've found a working configuration: mail_location = >> sdbox:~/:FULLDIRNAME=. >> >> I use a dot instead of slash or empty value. >> >> Now my folder structure looks like I want and Dovecot is working fine. >> >> Can anyone (maybe even a Dovecot developer?) say if the configuration >> is okay? I've tried to check the source code, but I don't know C as >> good as it's needed for that. >> >> Greetings, >> >> Hativ >> >> Am 06.07.2018 um 16:10 schrieb Hativ: >>> Hey to all, >>> >>> is it possible to get rid of the "dbox-Mails"-folder when using sdbox? >>> >>> Currently my folder structure looks like this (I hope the output >>> from tree would be formatted well): >>> /srv/mail/ >>> └── example.com >>> └── user >>> ├── dovecot-acl-list >>> ├── dovecot-attributes >>> ├── dovecot.list.index.log >>> ├── dovecot.mailbox.log >>> ├── dovecot-uidvalidity >>> ├── dovecot-uidvalidity.5b3f746f >>> ├── mailboxes >>> │ ├── Drafts >>> │ │ └── dbox-Mails >>> │ │ └── dovecot.index.log >>> │ ├── INBOX >>> │ │ └── dbox-Mails >>> │ │ ├── dovecot.index.cache >>> │ │ ├── dovecot.index.log >>> │ │ └── u.1 >>> │ ├── Junk >>> │ │ └── dbox-Mails >>> │ │ └── dovecot.index.log >>> │ ├── Sent >>> │ │ └── dbox-Mails >>> │ │ └── dovecot.index.log >>> │ └── Trash >>> │ └── dbox-Mails >>> │ └── dovecot.index.log >>> └── subscriptions >>> >>> I would like to let it look like this: >>> /srv/mail/ >>> └── example.com >>> └── user >>> ├── dovecot-acl-list >>> ├── dovecot-attributes >>> ├── dovecot.list.index.log >>> ├── dovecot.mailbox.log >>> ├── dovecot-uidvalidity >>> ├── dovecot-uidvalidity.5b3f746f >>> ├── mailboxes >>> │ ├── Drafts >>> │ │ └── dovecot.index.log >>> │ ├── INBOX >>> │ │ └── dovecot.index.cache >>> │ │ └── dovecot.index.log >>> │ │ └── u.1 >>> │ ├── Junk >>> │ │ └──dovecot.index.log >>> │ ├── Sent >>> │ │ └── dovecot.index.log >>> │ └── Trash >>> │ └── dovecot.index.log >>> └── subscriptions >>> >>> My path configuration: >>> mail_attribute_dict = file:%h/dovecot-attributes >>> mail_home = /srv/mail/%d/%n/ >>> mail_location = sdbox:~/ >>> >>> I have tried >>> mail_location = sdbox:~/:FULLDIRNAME= >>> and >>> mail_location = sdbox:~/:FULLDIRNAME=/ >>> but it doesn't work. >>> >>> The first doesn't change anything. The second auto-creates the >>> folders after first login like I want, but after next login they are >>> greyed out and no longer accessible. >>> >>> Is it possible to get rid of the "dbox-Mails"-folder? I want this >>> because I don't like to have an unneeded deep folder structure. Or >>> is there a good reason to let the "dbox-Mails" folder in my setup? >>> >>> Greetings, >>> >>> Hativ >>> >> >

2 2

Re: uid problem
by Aki Tuomi 31 Jul '18

31 Jul '18

https://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP Aki On 31.07.2018 14:35, Andras Kemeny wrote: > > can you point me to an url regarding LTMP between postfix and dovecot? > it might be an area worth exploring for me. > > thanks, > a > > > 2018. 07. 31. 12:46 keltezéssel, Aki Tuomi írta: >> >> Well, I don't know about yuuuge security risk (not saying there isn't >> any...), but if this concerns you, you can also use LTMP instead, >> which is probably a better solution here. >> >> Aki >> >> >> On 31.07.2018 13:42, Andras Kemeny wrote: >>> >>> yeah, the only problem about that is it's a yuuuge security risk :), >>> and also, postfix simply won't let me: >>> >>> Jul 31 02:20:37 rhyno postfix/pipe[29532]: fatal: user= command-line >>> attribute specifies root privileges >>> >>> so it's entirely possible i'm knocking on the wrong door, and >>> instead i should be asking this in the postfix mailing list. >>> >>> however, i'm also worried about this: "to bypass this check, set: >>> service auth { unix_listener /var/run/dovecot/auth-userdb { >>> mode=0777 } }", as i have done what it says, and the check wasn't >>> bypassed so i'm wary about something bad coming up once i somehow >>> fix this initial UID problem. >>> >>> thanks, >>> a >>> >>> >>> 2018. 07. 31. 7:12 keltezéssel, Aki Tuomi írta: >>>> You could run dovecot-lda as root. It will setuid to correct account. >>>> >>>> >>>> >>>> --- >>>> Aki Tuomi >>>> Dovecot oy >>>> >>>> -------- Original message -------- >>>> From: Andras Kemeny <pdx(a)pdx.hu> >>>> Date: 31/07/2018 04:46 (GMT+02:00) >>>> To: dovecot(a)dovecot.org >>>> Subject: uid problem >>>> >>>> hi, >>>> >>>> contacting this mailing list is my last-ditch effort to somehow >>>> come to >>>> a working configuration where postfix "ends in" dovecot, IE for >>>> special >>>> LDAP-based users, featured in the virtual mailbox delivery, dovecot >>>> would act as LDA. >>>> >>>> here's the deal. >>>> >>>> i've set up dovecot's access to the LDAP server, and for the >>>> purposes of >>>> being an IMAP server and a SASL auth backend, dovecot works >>>> brilliantly >>>> and without a glitch. i can access my test mailbox (in maildir >>>> format), >>>> i can use the LDA as root and it delivers the message correctly >>>> (after a >>>> switch to the target user's UID), and even postfix's submission works >>>> with dovecot as its SASL backend. >>>> >>>> what does not work is dovecot as LDA from postfix. >>>> >>>> i'm getting these errors in the log: >>>> >>>> Jul 31 03:40:40 rhyno dovecot: lda(aik): Error: user aik: Auth USER >>>> lookup failed >>>> Jul 31 03:40:40 rhyno dovecot: auth: Error: userdb(aik): client >>>> doesn't >>>> have lookup permissions for this user: userdb uid (10001) doesn't >>>> match >>>> peer uid (5000) (to bypass this check, set: service auth { >>>> unix_listener >>>> /var/run/dovecot/auth-userdb { mode=0777 } }) >>>> Jul 31 03:40:40 rhyno dovecot: lda: Fatal: Internal error occurred. >>>> Refer to server log for more information. >>>> >>>> for the sake of clarity, i've tried the "to bypass this check" >>>> instructions, didn't help. >>>> >>>> also, for the sake of operational clarity, "aik" is the LDAP account >>>> with the following parameters: >>>> >>>> dn: uid=aik,ou=People,dc=rhyno,dc=tech >>>> objectClass: account >>>> objectClass: posixAccount >>>> objectClass: postfixUser >>>> cn: aik >>>> uid: aik >>>> uidNumber: 10001 >>>> gidNumber: 10001 >>>> homeDirectory: /home/aik >>>> loginShell: /bin/sh >>>> gecos: aik >>>> description: User account >>>> structuralObjectClass: account >>>> entryUUID: db947584-0369-1038-98b3-675e2f0cea17 >>>> creatorsName: cn=admin,dc=rhyno,dc=tech >>>> createTimestamp: 20180613152616Z >>>> email: *********** >>>> userPassword:: ************************* >>>> mailacceptinggeneralid: andras.kemeny >>>> mailacceptinggeneralid: kemeny.andras >>>> mailacceptinggeneralid: aik >>>> mailacceptinggeneralid: pdx >>>> mailacceptinggeneralid: @rhyno.tech >>>> mailacceptinggeneralid: @rhynotechnologies.com >>>> maildrop: aik >>>> >>>> and postfix's master.cf says: >>>> >>>> dovecot unix - n n - - pipe >>>> flags=ODRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -e -f >>>> ${sender} -d ${user} >>>> >>>> so i'm stuck at this point. obviously, if the LDA is spawned with >>>> vmail:vmail perms, it cannot become uid 10001 (btw, the LDAP and >>>> passwd >>>> accounts were once connected, but for security reasons, the connection >>>> has been severed -- still the /home/aik/mail dir is owned by uid >>>> 10001 etc). >>>> >>>> what am i doint wrong? >>>> >>>> thanks, >>>> a >>> >> >

1 0

Almost there with Sieve
by Danny Horne 31 Jul '18

31 Jul '18

Hi all, Dovecot - 2.2.35 Pigeonhole - 0.4.23 I've recently moved mail filtering from local filtering (using Thunderbird) to Sieve. I've got filtering into folders and flagging emails working fine, but for possibly one tiny glitch. When specifying folders to filter into I have to use the format 'INBOX/Folder name' instead of just 'Folder name'. Can this be corrected? No real biggie but would be nice if it could. [root@kepler ~]# dovecot -n # 2.2.35 (b1cb664): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.23 (b2e41927) # OS: Linux 4.17.3-200.fc28.x86_64 x86_64 Fedora release 28 (Twenty Eight) xfs # Hostname: kepler.trisect.uk auth_mechanisms = cram-md5 base_dir = /var/run/dovecot/ mail_access_groups = mail mail_home = /var/spool/vhosts/homedir/%d/%n mail_location = mbox:/var/spool/vhosts/%d/%n:INBOX=/var/spool/mail/%d/%n managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = scheme=cram-md5 /etc/cram-md5.pwd driver = passwd-file } passdb { driver = pam } plugin { sieve = file:/var/spool/vhosts/sieve-scripts;active=/var/spool/vhosts/sieve-scripts/%u.sieve sieve_user_email = postmaster(a)trisect.uk } protocols = imap lmtp sieve sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 0 } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 0 vsz_limit = 256 M } service managesieve { process_limit = 1024 } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = # hidden, use -P to show it userdb { args = uid=vmail gid=vmail driver = static } userdb { driver = passwd } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" } protocol imap { mail_max_userip_connections = 200 } protocol sieve { mail_max_userip_connections = 25 managesieve_implementation_string = Dovecot Pigeonhole managesieve_max_compile_errors = 5 managesieve_max_line_length = 65536 } Thanks for looking

2 2

Re: uid problem
by Aki Tuomi 31 Jul '18

31 Jul '18

Well, I don't know about yuuuge security risk (not saying there isn't any...), but if this concerns you, you can also use LTMP instead, which is probably a better solution here. Aki On 31.07.2018 13:42, Andras Kemeny wrote: > > yeah, the only problem about that is it's a yuuuge security risk :), > and also, postfix simply won't let me: > > Jul 31 02:20:37 rhyno postfix/pipe[29532]: fatal: user= command-line > attribute specifies root privileges > > so it's entirely possible i'm knocking on the wrong door, and instead > i should be asking this in the postfix mailing list. > > however, i'm also worried about this: "to bypass this check, set: > service auth { unix_listener /var/run/dovecot/auth-userdb { mode=0777 > } }", as i have done what it says, and the check wasn't bypassed so > i'm wary about something bad coming up once i somehow fix this initial > UID problem. > > thanks, > a > > > 2018. 07. 31. 7:12 keltezéssel, Aki Tuomi írta: >> You could run dovecot-lda as root. It will setuid to correct account. >> >> >> >> --- >> Aki Tuomi >> Dovecot oy >> >> -------- Original message -------- >> From: Andras Kemeny <pdx(a)pdx.hu> >> Date: 31/07/2018 04:46 (GMT+02:00) >> To: dovecot(a)dovecot.org >> Subject: uid problem >> >> hi, >> >> contacting this mailing list is my last-ditch effort to somehow come to >> a working configuration where postfix "ends in" dovecot, IE for special >> LDAP-based users, featured in the virtual mailbox delivery, dovecot >> would act as LDA. >> >> here's the deal. >> >> i've set up dovecot's access to the LDAP server, and for the purposes of >> being an IMAP server and a SASL auth backend, dovecot works brilliantly >> and without a glitch. i can access my test mailbox (in maildir format), >> i can use the LDA as root and it delivers the message correctly (after a >> switch to the target user's UID), and even postfix's submission works >> with dovecot as its SASL backend. >> >> what does not work is dovecot as LDA from postfix. >> >> i'm getting these errors in the log: >> >> Jul 31 03:40:40 rhyno dovecot: lda(aik): Error: user aik: Auth USER >> lookup failed >> Jul 31 03:40:40 rhyno dovecot: auth: Error: userdb(aik): client doesn't >> have lookup permissions for this user: userdb uid (10001) doesn't match >> peer uid (5000) (to bypass this check, set: service auth { unix_listener >> /var/run/dovecot/auth-userdb { mode=0777 } }) >> Jul 31 03:40:40 rhyno dovecot: lda: Fatal: Internal error occurred. >> Refer to server log for more information. >> >> for the sake of clarity, i've tried the "to bypass this check" >> instructions, didn't help. >> >> also, for the sake of operational clarity, "aik" is the LDAP account >> with the following parameters: >> >> dn: uid=aik,ou=People,dc=rhyno,dc=tech >> objectClass: account >> objectClass: posixAccount >> objectClass: postfixUser >> cn: aik >> uid: aik >> uidNumber: 10001 >> gidNumber: 10001 >> homeDirectory: /home/aik >> loginShell: /bin/sh >> gecos: aik >> description: User account >> structuralObjectClass: account >> entryUUID: db947584-0369-1038-98b3-675e2f0cea17 >> creatorsName: cn=admin,dc=rhyno,dc=tech >> createTimestamp: 20180613152616Z >> email: *********** >> userPassword:: ************************* >> mailacceptinggeneralid: andras.kemeny >> mailacceptinggeneralid: kemeny.andras >> mailacceptinggeneralid: aik >> mailacceptinggeneralid: pdx >> mailacceptinggeneralid: @rhyno.tech >> mailacceptinggeneralid: @rhynotechnologies.com >> maildrop: aik >> >> and postfix's master.cf says: >> >> dovecot unix - n n - - pipe >> flags=ODRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -e -f >> ${sender} -d ${user} >> >> so i'm stuck at this point. obviously, if the LDA is spawned with >> vmail:vmail perms, it cannot become uid 10001 (btw, the LDAP and passwd >> accounts were once connected, but for security reasons, the connection >> has been severed -- still the /home/aik/mail dir is owned by uid >> 10001 etc). >> >> what am i doint wrong? >> >> thanks, >> a >

1 0