On Wed, 14 Nov 2007, Matt wrote:
[...]
For what it's worth, I'd look at the newest message in the ./cur folder,
rather than the oldest in the ./new. (You want the last time the user
But most of my user POP3 and do not leave messages on server. I just
check if there is a message over 6 mont
On Wed, 14 Nov 2007, Matt wrote:
Another annoying thing about Exim is it checks if a user is over
quotta after it has accepted a message. It then trys to write the
message to the users ./new directory and at that point generates a
bounce. Meaning over quotta accounts generate alot of bounces t
> > >> I guess the issues I still think are important:
> > >>
> > >> 1. You shouldn't use dovecot.index as your marker file.
> > >
> > > I gave up trying to use dovecot.index. Instead I look at each users
> > > ./new directory. If there are any messages over 6 months old I put
> > > there email a
> >> I guess the issues I still think are important:
> >>
> >> 1. You shouldn't use dovecot.index as your marker file.
> >
> > I gave up trying to use dovecot.index. Instead I look at each users
> > ./new directory. If there are any messages over 6 months old I put
> > there email address in file
On Wed, 14 Nov 2007, Matt wrote:
[...]
I guess the issues I still think are important:
1. You shouldn't use dovecot.index as your marker file.
I gave up trying to use dovecot.index. Instead I look at each users
./new directory. If there are any messages over 6 months old I put
there email
> On Sun, 11 Nov 2007, Matt wrote:
>
>
> >> I think I'd avoid actually disabling the account through the MTA,
> >> especially if it's for security considerations and your accounts have
> >> shell access. But it wouldn't be that hard:
> >
> > My actual goal is to reduce load on the server. These ar
[Oops. Sorry for the delay.]
On Sun, 11 Nov 2007, Matt wrote:
I think I'd avoid actually disabling the account through the MTA,
especially if it's for security considerations and your accounts have
shell access. But it wouldn't be that hard:
My actual goal is to reduce load on the server. Th
> "M" == Matt <[EMAIL PROTECTED]> writes:
M> What if the script only touched the dovecot.index if it exists?
M> That would likely not be too difficult to test for with shell
M> script.
Might be tricky to do in shell without a race. On the other hand maybe a
race in this case is
> "BH" == Benjamin R Haskell <[EMAIL PROTECTED]> writes:
BH> Since you're not doing anything protocol-specific (like echo "* OK
BH> [ALERT] Blah"), you could use the symlink trick to only require
BH> one script:
BH> ln -s /path/script /path/imap
BH> ln -s /path/script /pat
>>> Can I just touch the dovecot.index instead?
>
>BH> Maybe. Not sure what environment variable holds its location,
>BH> though. And I'm not 100% sure it always exists or whether you'd
>BH> have to special-case the first-time login. (Will 'touch' creating
>BH> a zero-length in
On Mon, 12 Nov 2007, pod wrote:
"BH" == Benjamin R Haskell <[EMAIL PROTECTED]> writes:
>> Can I just touch the dovecot.index instead?
BH> Maybe. Not sure what environment variable holds its location,
BH> though. And I'm not 100% sure it always exists or whether you'd
BH> have to
> "BH" == Benjamin R Haskell <[EMAIL PROTECTED]> writes:
>> Can I just touch the dovecot.index instead?
BH> Maybe. Not sure what environment variable holds its location,
BH> though. And I'm not 100% sure it always exists or whether you'd
BH> have to special-case the first-tim
On Sun, 11 Nov 2007, Matt wrote:
Is there anyway I can get Dovecot to update mtime on dovecot.index
everytime a user successfully checks there email?
Postlogin scripting would work like Benjamin said. Another possibility
would be to check atime if you haven't disabled atime updates.
atime is
> > Is there anyway I can get Dovecot to update mtime on dovecot.index
> > everytime a user successfully checks there email?
>
> Postlogin scripting would work like Benjamin said. Another possibility
> would be to check atime if you haven't disabled atime updates.
atime is updated everytime I do a
On Sat, 2007-11-10 at 18:12 -0600, Matt wrote:
> Is there anyway I can get Dovecot to update mtime on dovecot.index
> everytime a user successfully checks there email?
Postlogin scripting would work like Benjamin said. Another possibility
would be to check atime if you haven't disabled atime updat
> I think I'd avoid actually disabling the account through the MTA,
> especially if it's for security considerations and your accounts have
> shell access. But it wouldn't be that hard:
My actual goal is to reduce load on the server. These are simply
email users and have no shell or any other acc
On Sat, 10 Nov 2007, Matt wrote:
Is there anyway I can get Dovecot to update mtime on dovecot.index
everytime a user successfully checks there email? Or perhaps there is
a better way to do what I want here.
I am working on a script that I want to check when the last time a
user checked there e
Is there anyway I can get Dovecot to update mtime on dovecot.index
everytime a user successfully checks there email? Or perhaps there is
a better way to do what I want here.
I am working on a script that I want to check when the last time a
user checked there email account. If a user has not che
18 matches
Mail list logo
