- dovecot - dovecot.org

[Dovecot] NTLM Authentication with Dovecot and Postfix
by Matthew Larsen 25 Jun '13

25 Jun '13

I'm trying to get NTLM authentication working with Dovecot to authenticate Postfix SMTP clients. I can authenticate postfix smtp clients using the plain text login mechanism via Dovecot and winbind. However, using the NTLM mechanism gives me an error in my maillog that says: "dovecot: auth: winbind(?,10.20.2.0): user not authenticated: NT_STATUS_UNSUCCESSFUL". At this point, I'm rather stuck. It appears PAM and winbind work for authenticating with AD because it works with the plain text mechanism, but I'm missing something with the NTLM authentication method. Any suggestions as to what I've got wrong, or other logging I can turn up / examine that might shed some light on this? /// Logging and configuration information below /// -- When I use the LOGIN mechanism I see this in the mail logging and the message is relayed: Jun 21 13:12:58 SBSMTPNV05 postfix/smtpd[1501]: connect from nvit01b.mydomain.com[10.20.2.0] Jun 21 13:12:58 SBSMTPNV05 dovecot: auth: Debug: auth client connected (pid=1501) Jun 21 13:12:58 SBSMTPNV05 dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=smtp#011nologin#011lip=10.20.4.12#011rip=10.20.2.0#011resp=AG[...snip...]g== Jun 21 13:12:58 SBSMTPNV05 dovecot: auth: Debug: pam(myusername,10.20.2.0): lookup service=dovecot Jun 21 13:12:58 SBSMTPNV05 dovecot: auth: Debug: pam(myusername,10.20.2.0): #1/1 style=1 msg=Password: Jun 21 13:12:58 SBSMTPNV05 dovecot: auth: Debug: client out: OK#0111#011user=myusername Jun 21 13:12:58 SBSMTPNV05 postfix/smtpd[1501]: 54EAF8059B: client=nvit01b.mydomain.com[10.20.2.0], sasl_method=PLAIN, sasl_username=myusername Jun 21 13:12:58 SBSMTPNV05 postfix/cleanup[1504]: 54EAF8059B: message-id=<51C4B3C8.30008(a)domain1.com> Jun 21 13:12:58 SBSMTPNV05 postfix/qmgr[1499]: 54EAF8059B: from=<someone(a)domain1.com>, size=2700, nrcpt=1 (queue active) Jun 21 13:12:58 SBSMTPNV05 postfix/smtpd[1501]: disconnect from nvit01b.mydomain.com[10.20.2.0] Jun 21 13:12:59 SBSMTPNV05 postfix/smtp[1505]: 54EAF8059B: to=<someone(a)gmail.com>, relay=gmail-smtp-in.l.google.com[74.125.25.27]:25, delay=1.2, delays=0.23/0.04/0.16/0.72, dsn=2.0.0, status=sent (250 2.0.0 OK 1371845579 wf5si3786287pab.138 - gsmtp) Jun 21 13:12:59 SBSMTPNV05 postfix/qmgr[1499]: 54EAF8059B: removed -- I also see this in the secure log: Jun 21 13:12:58 SBSMTPNV05 auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=myusername rhost=10.20.2.0 user=myusername Jun 21 13:12:58 SBSMTPNV05 auth: pam_winbind(dovecot:auth): getting password (0x00000010) Jun 21 13:12:58 SBSMTPNV05 auth: pam_winbind(dovecot:auth): pam_get_item returned a password Jun 21 13:12:58 SBSMTPNV05 auth: pam_winbind(dovecot:auth): user 'myusername' granted access Jun 21 13:12:58 SBSMTPNV05 auth: pam_winbind(dovecot:account): user 'myusername' granted access -- However, when I switch the mechanism to NTLM in the Thurnderbird MUA I see this: Jun 21 13:15:46 SBSMTPNV05 postfix/smtpd[1506]: connect from nvit01b.mydomain.com[10.20.2.0] Jun 21 13:15:46 SBSMTPNV05 dovecot: auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth Jun 21 13:15:46 SBSMTPNV05 dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libauthdb_ldap.so Jun 21 13:15:46 SBSMTPNV05 dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_sqlite.so Jun 21 13:15:46 SBSMTPNV05 dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libmech_gssapi.so Jun 21 13:15:46 SBSMTPNV05 dovecot: auth: Debug: auth client connected (pid=1506) Jun 21 13:15:46 SBSMTPNV05 dovecot: auth: Debug: client in: AUTH#0111#011NTLM#011service=smtp#011nologin#011lip=10.20.4.12#011rip=10.20.2.0#011resp=TlRMT[...snip...]A= Jun 21 13:15:46 SBSMTPNV05 dovecot: auth: Debug: client out: CONT#0111#011TlRMT[[...snip...]A Jun 21 13:15:46 SBSMTPNV05 dovecot: auth: Debug: client in: CONT#0111#011TlRMT[...snip...]A= Jun 21 13:15:46 SBSMTPNV05 dovecot: auth: winbind(?,10.20.2.0): user not authenticated: NT_STATUS_UNSUCCESSFUL Jun 21 13:15:48 SBSMTPNV05 postfix/smtpd[1506]: warning: nvit01b.mydomain.com[10.20.2.0]: SASL NTLM authentication failed: TlRMT[...snip...]A Jun 21 13:15:48 SBSMTPNV05 dovecot: auth: Debug: client out: FAIL#0111 Jun 21 13:15:49 SBSMTPNV05 postfix/smtpd[1506]: disconnect from nvit01b.mydomain.com[10.20.2.0] -- with nothing in the secure log and I don't see anything show up in the winbind logs either. -- I've reviewed these pages as reference, and I'm not sure what I'm missing: http://wiki2.dovecot.org/HowTo/ActiveDirectoryNtlm http://wiki2.dovecot.org/Authentication/Mechanisms/NTLM http://www.dovecot.org/list/dovecot/2008-December/035630.html http://www.dovecot.org/list/dovecot/2010-February/046763.html http://blog.al-shami.net/2008/05/freebsd-postfix-dovecot-and-active-directo… http://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL -- Here's some of my relevant configuration as I understand it: -- I've joined the computer to the AD domain. The wbinfo tests work fine: # wbinfo -t checking the trust secret for domain MYDOMAIN via RPC calls succeeded # doveconf -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-358.11.1.el6.x86_64 x86_64 CentOS release 6.4 (Final) auth_debug_passwords = yes auth_mechanisms = plain ntlm login auth_use_winbind = yes auth_username_format = %Lu listen = * mbox_write_locks = fcntl passdb { driver = pam } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } //////////////////// # postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 7 html_directory = no inet_interfaces = all inet_protocols = ipv4 line_length_limit = 6144 mail_owner = postfix mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man mydestination = $myhostname, localhost.$mydomain, localhost myhostname = srvsbsmtp05.mydomain.com newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.6.6/README_FILES sample_directory = /usr/share/doc/postfix-2.6.6/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtpd_recipient_restrictions = permit_sasl_authenticated,reject_unauth_destination smtpd_sasl_auth_enable = yes smtpd_sasl_path = private/auth smtpd_sasl_type = dovecot unknown_local_recipient_reject_code = 550 ///////////////////// # cat /etc/krb5.conf [logging] default = FILE:/var/log/krb5libs.log kdc = FILE:/var/log/krb5kdc.log admin_server = FILE:/var/log/kadmind.log [libdefaults] default_realm = MYDOMAIN.COM dns_lookup_realm = true dns_lookup_kdc = true ticket_lifetime = 24h renew_lifetime = 7d forwardable = true [domain_realm] .mydomain.com = MYDOMAIN.COM mydomain.com = MYDOMAIN.COM //////////////////// system keytab: # klist -ke Keytab name: FILE:/etc/krb5.keytab KVNO Principal ---- -------------------------------------------------------------------------- 3 host/sbsmtpnv05.mydomain.com(a)MYDOMAIN.COM (des-cbc-crc) 3 host/sbsmtpnv05.mydomain.com(a)MYDOMAIN.COM (des-cbc-md5) 3 host/sbsmtpnv05.mydomain.com(a)MYDOMAIN.COM (arcfour-hmac) 3 host/sbsmtpnv05.mydomain.com(a)MYDOMAIN.COM (aes128-cts-hmac-sha1-96) 3 host/sbsmtpnv05.mydomain.com(a)MYDOMAIN.COM (aes256-cts-hmac-sha1-96) 3 host/sbsmtpnv05(a)MYDOMAIN.COM (des-cbc-crc) 3 host/sbsmtpnv05(a)MYDOMAIN.COM (des-cbc-md5) 3 host/sbsmtpnv05(a)MYDOMAIN.COM (arcfour-hmac) 3 host/sbsmtpnv05(a)MYDOMAIN.COM (aes128-cts-hmac-sha1-96) 3 host/sbsmtpnv05(a)MYDOMAIN.COM (aes256-cts-hmac-sha1-96) 3 SBSMTPNV05$(a)MYDOMAIN.COM (des-cbc-crc) 3 SBSMTPNV05$(a)MYDOMAIN.COM (des-cbc-md5) 3 SBSMTPNV05$(a)MYDOMAIN.COM (arcfour-hmac) 3 SBSMTPNV05$(a)MYDOMAIN.COM (aes128-cts-hmac-sha1-96) 3 SBSMTPNV05$(a)MYDOMAIN.COM (aes256-cts-hmac-sha1-96) 5 smtp/sbsmtpnv05.mydomain.com(a)MYDOMAIN.COM (des-cbc-crc) 5 smtp/sbsmtpnv05.mydomain.com(a)MYDOMAIN.COM (des-cbc-md5) 5 smtp/sbsmtpnv05.mydomain.com(a)MYDOMAIN.COM (arcfour-hmac) 5 smtp/sbsmtpnv05.mydomain.com(a)MYDOMAIN.COM (aes128-cts-hmac-sha1-96) 5 smtp/sbsmtpnv05.mydomain.com(a)MYDOMAIN.COM (aes256-cts-hmac-sha1-96) //////////////////// Samba config: [global] workgroup = MYDOMAIN realm = MYDOMAIN.COM server string = Samba Server Version %v security = ADS kerberos method = system keytab log file = /var/log/samba/log.%m max log size = 50 printcap name = /dev/null domain master = No template shell = /bin/bash winbind separator = + winbind use default domain = Yes idmap config * : range = 10000-50000 idmap config * : backend = tdb printing = bsd cups options = raw print command = lpr -r -P'%p' %s lpq command = lpq -P'%p' lprm command = lprm -P'%p' %j

1 0

[Dovecot] v2.2.4 released
by Timo Sirainen 25 Jun '13

25 Jun '13

http://dovecot.org/releases/2.2/dovecot-2.2.4.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.4.tar.gz.sig OK, this should be a pretty good and stable version. + doveadm: Added "flags" command to modify message flags. + doveadm: Added "deduplicate" command to expunge message duplicates. + dsync: Show the state in process title with verbose_proctitle=yes. - imap/pop3 proxy: Master user logins were broken in v2.2.3 - sdbox/mdbox: A corrupted index header with wrong size was never automatically fixed in v2.2.3. - mbox: Fixed assert-crashes related to locking.

4 6

[Dovecot] Configuring TLS 1.2
by Phillip Odam 25 Jun '13

25 Jun '13

Hi I'm running dovecot 2.1.6 and am trying to configure it to require TLS 1.2. So far I've only got as far as getting TLS 1.0 going. In the config file <dovecot root>/etc/dovecot/conf.d/10-ssl.conf, I've tried setting ssl_protocols to values like TLSv1.2:!TLSv1:!SSL3 but without any success. Attempts to google this matter turns up results for dovecot v1.2 as opposed to configuring TLS 1.2 in dovecot And having a look over the mailing list archive hasn't turned anything up thus far. Any pointers would be greatly appreciated. Thanks Phillip

2 2

[Dovecot] Sieve file permission problem
by Zoltan Lippai 25 Jun '13

25 Jun '13

Hi folks, I am using dovecot 2.1.7 with the ManageSieve plugin which works great. Recently I set up Afterlogic webmail on my server (the community version) and it has a nice UI to manage the sieve settings. It uses port 2000 to communicate with dovecot via the ManageSieve plugin. Also, dovecot uses Maildirs to store the messages. The problem is that the permissions on the files that store the sieve rules are to strict. I am talking about the "sieve" directory and the .dovecot.sieve file. The sieve folder has a chmod 700 and the .dovecot.sieve is chmod 600. Both are owned by vmail:mail If I delete these two items, then the rules can be saved via the web interface. Then these files are created but for some reason the ManageSieve plugin can't modify them. Here is the output of dovecot -n: http://pastebin.com/4eqyBKCA Can you help me out on this? Thanks a lot! Zoltan

5 7

[Dovecot] dsync assert failure in 2.2.2
by Tomas Olsson 25 Jun '13

25 Jun '13

Hi, with 2.2.2 and today's hg, dsync crashes with dsync(root): Panic: file ../../../../../src/lib-storage/index/mbox/mbox-lock.c: line 797 (mbox_lock): assertion failed: (lock_type == F_RDLCK || mbox->mbox_lock_type != F_RDLCK) when I run USER=root 2.2-hg/bin/dsync -c etc/dovecot.conf -f -o mail_location=mbox:/tmp/imap/fwadmin.tmp:INBOX=/tmp/imap/fwadmin.tmp/INBOX mirror mdbox:/tmp/imap/fwadmin It seems to happen for all mailboxes that are not empty. 2.2.1 completes the conversion without any complaints. config: # 2.2.2 (a3b5b762639a): etc/dovecot.conf # OS: Linux 3.2.0-32-generic i686 Ubuntu 12.04.2 LTS default_internal_user = nobody default_login_user = nobody Backtrace (hg version): #0 i_panic (format=0x252530 "file %s: line %d (%s): assertion failed: (%s)") at ../../../src/lib/failures.c:255 #1 0x001c643f in mbox_lock (mbox=0x80d9b40, lock_type=<optimized out>, lock_id_r=0x811352c) at ../../../../../src/lib-storage/index/mbox/mbox-lock.c:797 #2 0x001c695c in mbox_mail_seek (mail=0x81188e0) at ../../../../../src/lib-storage/index/mbox/mbox-mail.c:82 #3 0x001c6ee1 in mbox_mail_init_stream (mail=0x81188e0) at ../../../../../src/lib-storage/index/mbox/mbox-mail.c:335 #4 mbox_mail_get_stream (_mail=0x81188e0, get_body=false, hdr_size=0x0, body_size=0x0, stream_r=0xbffff77c) at ../../../../../src/lib-storage/index/mbox/mbox-mail.c:375 #5 0x001e65b0 in mail_get_hdr_stream (mail=0x81188e0, hdr_size=0x0, stream_r=0xbffff77c) at ../../../src/lib-storage/mail.c:226 #6 0x00215532 in index_mail_get_header_stream (_mail=0x81188e0, headers=0x8106fd0, stream_r=0xbffff7e0) at ../../../../src/lib-storage/index/index-mail-headers.c:837 #7 0x001e649d in mail_get_header_stream (mail=0x81188e0, headers=0x8106fd0, stream_r=0xbffff7e0) at ../../../src/lib-storage/mail.c:190 #8 0x08084bf2 in dsync_mail_get_hdr_hash (mail=0x81188e0, hdr_hash_r=0xbffff8ec) at ../../../../src/doveadm/dsync/dsync-mail.c:32 #9 0x080736a8 in importer_try_next_mail (wanted_uid=1, importer=0x81136e0) at ../../../../src/doveadm/dsync/dsync-mailbox-import.c:515 #10 importer_next_mail (importer=0x81136e0, wanted_uid=1) at ../../../../src/doveadm/dsync/dsync-mailbox-import.c:536 #11 0x0807729a in dsync_mailbox_import_changes_finish (importer=0x81136e0) at ../../../../src/doveadm/dsync/dsync-mailbox-import.c:1754 #12 0x08072e3b in dsync_brain_recv_mail_change (brain=0x80beaf8) at ../../../../src/doveadm/dsync/dsync-brain-mails.c:102 #13 dsync_brain_sync_mails (brain=0x80beaf8) at ../../../../src/doveadm/dsync/dsync-brain-mails.c:319 #14 0x0806f11b in dsync_brain_run_real (changed_r=0xbffffae6, brain=0x80beaf8) at ../../../../src/doveadm/dsync/dsync-brain.c:440 #15 dsync_brain_run (brain=0x80beaf8, changed_r=0xbffffae6) at ../../../../src/doveadm/dsync/dsync-brain.c:469 #16 0x0806d1ef in cmd_dsync_run_local (ibc2=0x80be8d8, brain=0x80beaf8, user=0x80ba8f0, ctx=0x80b2ca8) at ../../../../src/doveadm/dsync/doveadm-dsync.c:356 #17 cmd_dsync_run (_ctx=0x80b2ca8, user=0x80ba8f0) at ../../../../src/doveadm/dsync/doveadm-dsync.c:543 #18 0x08055424 in doveadm_mail_next_user (error_r=0xbffffbcc, ctx=0x80b2ca8, input=<optimized out>) at ../../../src/doveadm/doveadm-mail.c:308 #19 doveadm_mail_next_user (ctx=0x80b2ca8, input=<optimized out>, error_r=0xbffffbcc) at ../../../src/doveadm/doveadm-mail.c:267 #20 0x080560fc in doveadm_mail_cmd (argv=0x80af1ec, argc=<optimized out>, cmd=0x80b226c) at ../../../src/doveadm/doveadm-mail.c:517 #21 doveadm_mail_try_run (cmd_name=0x80af286 "sync", argc=3, argv=0x80af1e4) at ../../../src/doveadm/doveadm-mail.c:609 #22 0x08055046 in main (argc=3, argv=0x80af1e4) at ../../../src/doveadm/doveadm.c:398 I'm attaching the mbox file. /t

1 1

[Dovecot] Quota based on LDAP group
by Pavel Herrmann 24 Jun '13

24 Jun '13

Hi I have a setup where my dovecot (2.0, if that makes a difference) authenticates against an LDAP directory. In my scenario, I have two types of users, lets call them "normal" and "privileged". What I need is for the normal user to have a fixed quota, but for the priviledged to have none. (The users do not exist on the underlying system, so I cant do quota based on FS) The issue is that my LDAP is actually an AD, and there is a fair amount of new accounts over the time (in other words, I cannot use LDAP attribute for storing quota, because the AD tools don't understand it, and I would have to add it manually for each new account). The approach I had in mind is using quota based on user group (I do have groups representing both normal and priviledged users), but I cannot find a way to set it up in dovecot. Am I missing something or does dovecot not support LDAP groups as attribute source? thanks Pavel Herrmann

2 4

[Dovecot] chown
by Yann Shukor 24 Jun '13

24 Jun '13

Hi I currently have to execute the following command everytime I restart Dovecot : chown dovenull:vmail /var/run/dovecot/login What should I change in my config files to avoidhaving to do this ? thanks yann ========= Dovecot -n: ========= # 2.2.2 (45399357008a): /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-686-pae i686 Debian 7.0 ext4 auth_debug = yes auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-userdb auth_verbose = yes disable_plaintext_auth = no first_valid_gid = 5000 first_valid_uid = 5000 hostname = holimail.holinice.com last_valid_gid = 5000 last_valid_uid = 5000 listen = * mail_debug = yes mail_gid = vmail mail_location = maildir:/var/vmail/%d/%n/Maildir mail_privileged_group = mail mail_uid = vmail 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 ihave namespace inbox { inbox = yes location = maildir:/var/vmail/%d/%n/Maildir mailbox Brouillons { special_use = \Drafts } mailbox "Courrier indesirable" { special_use = \Junk } mailbox "Elements envoyes" { special_use = \Sent } mailbox "Elements supprimes" { special_use = \Trash } prefix = subscriptions = yes } passdb { args = scheme=CRAM-MD5 /etc/dovecot/users.conf driver = passwd-file } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = azurtem(a)holinice.com protocols = " imap sieve pop3" service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } } service imap-login { group = dovecot inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service imap { process_limit = 1024 } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service pop3 { process_limit = 1024 } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = uid=5000 gid=5000 home=/var/vmail/%d/%n allow_all_users=yes driver = static } userdb { driver = passwd } protocol lda { mail_plugins = " sieve" }

2 1

[Dovecot] auth probes without IP - "Initial status notification not received ..."
by LEVAI Daniel 24 Jun '13

24 Jun '13

Hi! I've been getting a bunch of these messages lately in my logs: dovecot: master: Error: service(auth): Initial status notification not received in 30 seconds, killing the process dovecot: auth: Fatal: master: service(auth): child 11016 killed with signal 9 dovecot: master: Error: service(auth): Initial status notification not received in 30 seconds, killing the process dovecot: auth: Fatal: master: service(auth): child 27660 killed with signal 9 # fgrep -c -e "master: Error: service(auth): Initial status" dovecot.log* [...] dovecot.log.1:501 dovecot.log.2:250 [...] But I can not link these auth probes to any IP addresses within the dovecot log files. This is dovecot-2.2.2 on OpenBSD-stable. What do you guys suggest? Thanks, Daniel -- LÉVAI Dániel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F

2 2

[Dovecot] Warning recipient when message delivery fails due to over-quota
by Ben Johnson 24 Jun '13

24 Jun '13

I'm working to configure automated quota notifications in Dovecot and am wondering if it is possible to send a warning message to a user when message delivery fails because the user is over-quota. I already have the following directives configured: quota_warning = storage=95%% quota-warning 95 %u %d quota_warning2 = storage=80%% quota-warning 80 %u %d quota_warning3 = -storage=100%% quota-below below %u %d These seem to function as expected, but the problem I'm facing is that when a message is large enough to take the user's quota from, say, 84% to over 100%, the message is rejected (as expected), but the user is never warned that a message failed to be delivered because it would have put him over 100% usage. I suppose that I'm looking for a trigger that is tripped when delivering the message *would* put the user over-quota (as opposed to *does in fact* put the user over). The sender receives an automated rejection message already. I'm wondering if the recipient can be warned at the same time. (I'm not concerned about further increasing the user's quota consumption with the warning message; I would set noenforcing to 1.) Is this possible? Any help is much appreciated. Thanks in advance. -Ben

3 4

[Dovecot] mail_max_userip_connections on a per user basis
by Antonio Leding 24 Jun '13

24 Jun '13

Hello, Can the above setting be applied on a per user account basis? I thought that maybe something like per account quotas might be a possible method but not sure. Thanks.

2 1