Re: user_deny.db and lmtpd
On Tue, July 8, 2014 17:16, Ken Murchison wrote: > On 07/04/2014 11:05 AM, Deniss wrote: >> Hello, >> >> is it possible to force lmtp to bounce messages with temporary reject >> code like 421 for certain user(s) ? >> >> Looks like lmtp does not respect user_deny.db file. > > You could try setting their quota to something small, e.g. 1 (one) Or, activate a sieve script, rejecting incomming ?? >> >> But mailbox may be flagged with MBTYPE_MOVING which is considered by >> lmtpd. >> >> Is there any tool to manually set / clear MBTYPE_MOVING flag on a given >> mailbox ? >> >> Best, >> Deniss >> > > -- > Kenneth Murchison > Principal Systems Software Engineer > Carnegie Mellon University > -- Mogens Melander +66 8701 33224 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Mailbox last access - most reliable source
Apropos, is there any way to block access to a mailbox on Cyrus, even if the user logins successfully? Perhaps there is a way on Cyrus to block new deliveries to a mailbox or I should handle this on my MTA? -- My best regards, Fabio Soares Schmidt Linux Professional Institute - LPIC-3 Microsoft Certified Technology Specialist: Active Directory On 8 July 2014 12:46, Fabio S. Schmidt wrote: > Thanks everyone for the answers ! > > I will scan the login entries in the syslog and use them. I thought about > redirecting all the users logins entries to a specific file and then > develop a script to delete mailboxes that have not been accessed in the > last 90 days. > > > -- > > My best regards, > Fabio Soares Schmidt > > > Linux Professional Institute - LPIC-3 > Microsoft Certified Technology Specialist: Active Directory > > > > > On 8 July 2014 01:21, Bron Gondwana wrote: > >> On Tue, Jul 8, 2014, at 06:51 AM, Nic Bernstein wrote: >> > On 07/07/2014 03:12 PM, Joseph Brennan wrote: >> > > "Fabio S. Schmidt" wrote: >> > > >> > >> I actually need to consider only the last access via IMAP or POP >> > > protocols. >> > > >> > > That can be very misleading, because a device may keep checking for >> new >> > > mail for a very long time after the user abandons the account. >> > > >> > > A recent timestamp on the user.seen file should be good, but that >> seems to >> > > update mysteriously sometimes. >> > >> > The "lastupdated:" field of cyradm's "info mailbox" command will show >> > the last time the mailbox was updated in any way, so that includes >> > deliveries. The timestamp of the user.seen file will only reflect the >> > last time that the seen state of anything in the mailbox changed, but >> > does not tell you when the mailbox was last accessed. >> > >> > I think you'd need to derive this information some other way, such as >> > from authentication logs. Of course the reliability and accessibility >> > of that will depend on your authentication mechanisms. >> >> I would go by entries in the syslog. We run a custom saslauthd, which >> does >> logging, so we get it from there - but this is what shows up in syslog: >> >> imap[20174]: login: HOST [IP] user@domain plaintext User logged in >> >> You can scan those and use them. >> -- >> Bron Gondwana >> br...@fastmail.fm >> >> Cyrus Home Page: http://www.cyrusimap.org/ >> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ >> To Unsubscribe: >> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus >> > Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Mailbox last access - most reliable source
Thanks everyone for the answers ! I will scan the login entries in the syslog and use them. I thought about redirecting all the users logins entries to a specific file and then develop a script to delete mailboxes that have not been accessed in the last 90 days. -- My best regards, Fabio Soares Schmidt Linux Professional Institute - LPIC-3 Microsoft Certified Technology Specialist: Active Directory On 8 July 2014 01:21, Bron Gondwana wrote: > On Tue, Jul 8, 2014, at 06:51 AM, Nic Bernstein wrote: > > On 07/07/2014 03:12 PM, Joseph Brennan wrote: > > > "Fabio S. Schmidt" wrote: > > > > > >> I actually need to consider only the last access via IMAP or POP > > > protocols. > > > > > > That can be very misleading, because a device may keep checking for new > > > mail for a very long time after the user abandons the account. > > > > > > A recent timestamp on the user.seen file should be good, but that > seems to > > > update mysteriously sometimes. > > > > The "lastupdated:" field of cyradm's "info mailbox" command will show > > the last time the mailbox was updated in any way, so that includes > > deliveries. The timestamp of the user.seen file will only reflect the > > last time that the seen state of anything in the mailbox changed, but > > does not tell you when the mailbox was last accessed. > > > > I think you'd need to derive this information some other way, such as > > from authentication logs. Of course the reliability and accessibility > > of that will depend on your authentication mechanisms. > > I would go by entries in the syslog. We run a custom saslauthd, which does > logging, so we get it from there - but this is what shows up in syslog: > > imap[20174]: login: HOST [IP] user@domain plaintext User logged in > > You can scan those and use them. > -- > Bron Gondwana > br...@fastmail.fm > > Cyrus Home Page: http://www.cyrusimap.org/ > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > To Unsubscribe: > https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus > Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: user_deny.db and lmtpd
On 07/04/2014 11:05 AM, Deniss wrote: > Hello, > > is it possible to force lmtp to bounce messages with temporary reject > code like 421 for certain user(s) ? > > Looks like lmtp does not respect user_deny.db file. You could try setting their quota to something small, e.g. 1 (one) > > But mailbox may be flagged with MBTYPE_MOVING which is considered by lmtpd. > > Is there any tool to manually set / clear MBTYPE_MOVING flag on a given > mailbox ? > > Best, > Deniss > > Cyrus Home Page: http://www.cyrusimap.org/ > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > To Unsubscribe: > https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus -- Kenneth Murchison Principal Systems Software Engineer Carnegie Mellon University Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
