similar to: different userdb and/or passdb for lmtp and pop3/imap?

Displaying 20 results from an estimated 6000 matches similar to: "different userdb and/or passdb for lmtp and pop3/imap?"

2012 Sep 12
5
question on "doveadm user" and pass/userdb
Hi, I'm about getting to know dovecot in details, I am about the command "doveadm user". The man page shows this example: userdb: jane uid : 8001 gid : 8001 home : /home/jane mail : sdbox:~/sdbox plugins : sieve quota_rule: *:storage=150M It seems to be nice, however I never got this only: ~# doveadm
2014 Aug 06
0
maildir: could lda/lmtp log filenames?
hello, on a mailstorage server receiving messages per lda/lmtp I like to pimp my logfile. when starting to search for a specific message I have a queueid. I like to combine that id with the filename the message has after delivery to a maildir. I know, that will not work with other formats then maildir. Aug 6 11:37:30 mailserver postfix/lmtp[17884]: 3hSnmj208Zz259d: to=<rcpt at
2015 Mar 06
0
LMTP error: Too many concurrent deliveries for user (in reply to end of DATA command)
Am 06.03.2015 um 14:44 schrieb Ralf Hildebrandt: > I updated dovecot today and all over a sudden I'm getting: > > Mar 6 14:40:46 mail postfix/lmtp[3150]: 3kz95y3nX3zCtTS: to=<recipient at backup.invalid>, relay=127.0.0.1[private/dovecot-lmtp], > delay=88, delays=87/0.94/0.01/0.01, dsn=4.3.0, status=deferred (host 127.0.0.1[private/dovecot-lmtp] said: 451 4.3.0 >
2013 Jun 14
1
Multiple user sharing a single mailbox
I'm designing a system where some but not all groups of users want to share a single mailbox, i.e the user will not have there own inbox. I think this is possible by setting up a user database that returns the same mail location and possible the same home directory. This sharing would only occur in a single domain. Example User Database UserID | home | mail all at site1.example.com |
2005 Mar 02
1
Several issues with 1.0-stable
All, We have Dovecot 1.0-stable deployed in our 3000 users environment as of last weekend. Up untill now, I have 3 issues: - When stopping Dovecot with: kill -TERM `cat /var/run/dovecot/master.pid`, the 'dovecot' process itself dies, the 'imap-login' processes die, but the 'imap' processes (there are a lot of them) don't die, but become a zombie. I think the way
2019 Jan 25
1
Shared instance
I don't want such mailbox. I have inbox namespace mail_location = maildir:/mailStorage/%Ld/%Ln:LAYOUT=fs namespace inbox { ? type = private ? separator = / ? prefix = ? inbox = yes } and another private namespace used for archiving namespace archive { ?prefix = archived/ ?inbox = no ?type = private ?location = maildir:/mailStorageArchive/%Ld/%Ln:LAYOUT=fs ?mailbox Archive { ?
2005 Mar 04
2
Strange behaviour with moving mail
Hi All, Sorry to bother you again. I am not too familiar with IMAP yet, so maybe I am asking stupid questions. Here goes anyway: In our (Dovecot 1.0-stable) setup, we have two namespaces: the default namespace, which location is '/var/mailstore/1%u/%u' and the "Mailstorage" namespace, which location is '~/.Mailstorage/'. Now we create a folder called 'Test' in
2012 Jun 05
2
best practises for mail systems
hello! Can someone point me to some best practices in building high-available scalable mail system or! share your own success stories. I've read article in LJ "Building a Scalable High-Availability E-Mail System with Active Directory and More" but it seemed to be outdated and there's a single point of failure (Master node). What I want to achieve: high-available,
2012 Jun 05
1
[ Re: best practises for mail systems]
Hello, If disk space and bandwidth are affordable (and from your setup it seems that they are affordable as you have everything locally) I would split the mail storage completely and use replication in between n-master servers (n=2 for your case). The replication is not yet fully tested, but Timo is actively working on this feature. The fear of lossing the imap session does not make sense (at
2011 Sep 07
2
is it necessary lmtp and director to avoid index corruption in mail delivery?
Hello all, If I have several postfix/dovecot-lda boxes with shared nfs storage, how director helps in this scenario? is it necesary to use lmtp instead of dovecot-lda? With postfix/dovecot-lda boxes incoming mail happens at the smtp layer but director redirects are working in the lmtp/imap/pop3 layer.
2016 Aug 22
2
LMTP doing passdb queries ?
Hi, I can see dovecot is doing a passdb query when handling the LMTP RCPT command. That's kinda unexpected for me. I would have thought it only did a userdb lookup. I have disabled lmtp_proxy to be sure it didn't do a passdb lookup to check the proxy field. Is this expected? Doesn't the LDA only do userdb lookups? /Peter
2011 Oct 20
1
Port variable in LMTP userdb lookups?
Hi all, I'm currently changing some systems to use the redirector service, which means that to get local deliveries going I need to get lmtp set up so it can be redirected as well. This is working fine, however we have a number of different ports running on our servers depending on which brand a customer is using. When the time comes to do the user look up, we use (port, user, domain) to
2012 Oct 03
5
LMTP userdb lookup
Is it possible to have separate userdb lookups for LMTP and POP/IMAP?
2012 Feb 11
1
Passdb disconnected unexpectedly when trying to do Director with LMTP
Hi there, I'm running Dovecot 2.0.16 just set up the director with cut&paste from the wiki. It's working & running fine for pop/imap connections (as verified by doveadm director status user), however when I specify 'RCPT TO' for a (tcp) lmtp connection straight away I get: 451 4.3.0 <xxx at yyy.com> Temporary user lookup failure and in the logs:
2013 Jul 31
1
LMTP: userdb lookup - user-filter with variables
I tried to use dovcots lmtp instead of dovecot-lda. postfix has in master.cf ... dovecot-lda -f ... -d ${user} to separate the user part from user at hostname.domain. So lookup of "user" succeeds in userdb (LDAP) done by dovecot-lda. I have always local addresses like to=<user at hostname.domain> postfix/lmtp[6579]: [ID 197553 mail.info] B3CDA66A16: to=<h0094slk at
2011 Jan 20
4
LMTP & home, chroot, mail userdb fields.
Hello, Dovecot. I'm using postfix + dovecot with pure virtual users. postfix uses standard virtual transport, and dovecot fetches such fields from userdb: chroot: "/usr/home/hosted/v-mail/%d/%n" home: "/" mail: "maildir:." Everything works Ok -- dovecot founds users' mail. Now, after upgrade to dovecot2, I want to use it LMTP server as
2012 Jun 28
2
RAID1+md concat+XFS as mailstorage
Hello! somewhere in maillist I've seen RAID1+md concat+XFS being promoted as mailstorage. Does anybody in here actually use this setup? I've decided to give it a try, but ended up with not being able to recover any data off survived pairs from linear array when _the_first of raid1 pairs got down. thanks!
2014 May 30
1
Disabling plus sign extension delimiter in lmtp listener (or userdb)
Hello We have migrated our email services from a server, which did not support IMAP and folders, therefore threated the plus sign + as a normal character in a part of an email address. Our new server delivers the emails via lmtp to dovecot. the few users which got a + character in the username first could not log-in (fixed by adding + to auth_username_chars). Now the next problem turn out to
2018 Feb 06
2
LDAP userdb and dovecot LDA/LMTP - different requirements
Hi, I want to use Dovecot LDA (or rather LMTP) use as local deliver with Postfix MTA. Users are in LDAP DB with structure as: dn: cn=username, ou=rank, o=myorg cn: username objectClass: Person gidNumber: uNNN uidNumber: gNNN userPassword: (somehow hashed, can only bind verification) homeDirectory: /Home/$rank/$username mailActive: 0/1 mail: usera at OneDomain mail: userb at
2016 Aug 03
2
service-specific userdb affecting lmtp, quota-service
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 2 Aug 2016, Michael Fox wrote: > Update: > > I was able to eliminate the /var/log/mail.err error messages (shown below) > by creating a userdb.quota-status and userdb.lmtp passwd-file. However, > since userdb.pop3 and userdb.imap will have different extra-fields values > for namespace (different namespace/xxx/inbox=yes