[Dovecot] Update Dovecot index files on maildrop delivery?

[Kārlis Repsons]

Hi all,
is there some easy way to inform Dovecot about a new delivery, which has 
happened after postfix invoked maildrop, so the index files would be updated?


signature.asc
Description: This is a digitally signed message part.

Re: [Dovecot] Update Dovecot index files on maildrop delivery?

[Eduardo M KALINOWSKI]

On Sex, 15 Jan 2010, Kārlis Repsons wrote:

is there some easy way to inform Dovecot about a new delivery, which has
happened after postfix invoked maildrop, so the index files would be updated?


That's exactly the task for which dovecot deliver was made.



--
Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: [Dovecot] 1.2.9 imap crash with backtrace

[Cor Bosman]

We're seeing this same coredump on a few dozen customers as well. Also
Netapp/NFS. 

cor

Re: [Dovecot] Update Dovecot index files on maildrop delivery?

[Kārlis Repsons]

On Friday 15 January 2010 12:20:05 Eduardo M KALINOWSKI wrote:
> On Sex, 15 Jan 2010, Kārlis Repsons wrote:
> > is there some easy way to inform Dovecot about a new delivery, which has
> > happened after postfix invoked maildrop, so the index files would be
> > updated?
> 
> That's exactly the task for which dovecot deliver was made.
But maybe you could also post a short info on how should deliver be called? 

I read that "The Dovecot LDA, called deliver, is a local delivery agent which 
takes mail from an MTA and delivers it to a user's mailbox, while keeping 
Dovecot index files up to date."
However in my case maildrop seems to be in the place of deliver. Would it work 
if maildrop had deliver called by xfilter with the options appended, then 
followed by "to /dev/null"?


signature.asc
Description: This is a digitally signed message part.

Re: [Dovecot] Update Dovecot index files on maildrop delivery?

[Eduardo M KALINOWSKI]

On Sex, 15 Jan 2010, Kārlis Repsons wrote:

On Friday 15 January 2010 12:20:05 Eduardo M KALINOWSKI wrote:

On Sex, 15 Jan 2010, Kārlis Repsons wrote:
> is there some easy way to inform Dovecot about a new delivery, which has
> happened after postfix invoked maildrop, so the index files would be
> updated?

That's exactly the task for which dovecot deliver was made.

But maybe you could also post a short info on how should deliver be called?

I read that "The Dovecot LDA, called deliver, is a local delivery agent which
takes mail from an MTA and delivers it to a user's mailbox, while keeping
Dovecot index files up to date."
However in my case maildrop seems to be in the place of deliver.  
Would it work

if maildrop had deliver called by xfilter with the options appended, then
followed by "to /dev/null"?


I don't know maildrop, so I can't tell if this would work. But the  
idea is to use deliver instead of maildrop, unless you need something  
that only maildrop can do.


In this case, I'd leave things as they are and not worry about  
indexes. When the mail folder is opened next time dovecot will notice  
the new messages and update the indexes.




--
 knghtbrd: Eww, find a better name, the movie sucked.. 
 Mercury: The engine is better than the movie

Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: [Dovecot] Update Dovecot index files on maildrop delivery?

[Kārlis Repsons]

On Friday 15 January 2010 14:44:07 Eduardo M KALINOWSKI wrote:
> On Sex, 15 Jan 2010, Kārlis Repsons wrote:
> > On Friday 15 January 2010 12:20:05 Eduardo M KALINOWSKI wrote:
> >> On Sex, 15 Jan 2010, Kārlis Repsons wrote:
> >> > is there some easy way to inform Dovecot about a new delivery, which
> >> > has happened after postfix invoked maildrop, so the index files would
> >> > be updated?
> >>
> >> That's exactly the task for which dovecot deliver was made.
> >
> > But maybe you could also post a short info on how should deliver be
> > called?
> >
> > I read that "The Dovecot LDA, called deliver, is a local delivery agent
> > which takes mail from an MTA and delivers it to a user's mailbox, while
> > keeping Dovecot index files up to date."
> > However in my case maildrop seems to be in the place of deliver.
> > Would it work
> > if maildrop had deliver called by xfilter with the options appended, then
> > followed by "to /dev/null"?
> 
> I don't know maildrop, so I can't tell if this would work. But the
> idea is to use deliver instead of maildrop, unless you need something
> that only maildrop can do.
> 
> In this case, I'd leave things as they are and not worry about
> indexes. When the mail folder is opened next time dovecot will notice
> the new messages and update the indexes.

But I think, client MUA will not be timely notified of the new mail, which 
might happen for one together with index updating (wouldn't it?)...


signature.asc
Description: This is a digitally signed message part.

Re: [Dovecot] Dovecot Proxy and environment variables

[BaQs]

Hi all!

I now use dovecot 1.2.9 on proxy, and 1.2.4 on destination server.
Then, it seems that login_trusted_networks doesn't work any more, and
I've got private proxy's ip opensmtp database.

---destination server
More details may help:
mail_executable = /usr/local/libexec/dovecot/opensmtp.sh
/usr/local/libexec/dovecot/courier2dovecot.sh

opensmtp.sh:
echo "replace into opensmtp(ip,domain) VALUES('$IP','$DOMAIN');" | mysql
---destination server

---proxy
password_query = SELECT NULL AS password, host, 'Y' AS nologin, 'Y' AS
nodelay, 'Y' AS nopassword, 'Y' AS proxy,'%u' as user FROM proxy WHERE
domain = '%d'
---proxy


On Mon, 30 Nov 2009 17:05:40 +0100, BaQs  wrote:
> Seems to work great! 
> 
> Thanks a lot, enormous! 
> 
> On Mon, 30 Nov 2009 10:37:02 -0500, Timo Sirainen  wrote:
>> If you have Dovecot v1.2 in both proxy and destination servers, you can
>> just set in dest server login_trusted_networks to include the proxy's
> IP.
>> 
>> On Nov 30, 2009, at 3:50 AM, BaQs wrote:
>> 
>>> 
>>> Hi List,
>>> 
>>> Sorry to bother you again but nobody would have any solution ?
>>> 
>>> I just want to get real IP on a dovecot behind a dovecot proxy.
>>> 
>>> I am using dovecot 1.2.4 but can change version if a solution exists.
>>> 
>>> 
>>> Thanks a lot in advance,
>>> Pierre
>>> 
>>> On Fri, 27 Nov 2009 16:25:53 +0100, BaQs  wrote:
 Dear list, 
 
 First of all, I am French so excuse my bad english. 
 
 I am
 currently using dovecot proxy feature, using sql backend. 
 
 I "proxy" the
 imap/pop requests to another server, let's say server2. 
 
 On server2, I use
 a script to keep up to date a "pop before smtp auth" database. 
 
 I used
 mail_executable = /path/to/this/script.sh ... 
 
 My problem is: the $IP
 environment variable on server2 is the proxy's IP. 
 
 How could I give a
 variable from proxy to server2, or simply get the real client public
> IP
>>> ?
 
 
 Thanks a lot in advance for your answers 
 
 Pierre. 
 
 PS: let me also
 thank very much dovecot developers and community !
>>>

Re: [Dovecot] Dovecot Proxy and environment variables

[Charles Marcus]

On 2010-01-15, BaQs (serar...@baqs.net) wrote:
> I now use dovecot 1.2.9 on proxy, and 1.2.4 on destination server.

Not that this will necessarily fix your problem (though it might) - if
you are using dovecot proxy with multiple dovecot servers, you really
should keep them all the same version...

Re: [Dovecot] Dovecot Proxy and environment variables

[BaQs]

Ok, found what happens


I only catch public IP when using imap, not pop3.

Any way to catch public IP using pop3 as well ?


On Fri, 15 Jan 2010 11:33:11 -0500, Charles Marcus
 wrote:
> On 2010-01-15, BaQs (serar...@baqs.net) wrote:
>> I now use dovecot 1.2.9 on proxy, and 1.2.4 on destination server.
> 
> Not that this will necessarily fix your problem (though it might) - if
> you are using dovecot proxy with multiple dovecot servers, you really
> should keep them all the same version...

[Dovecot] unlinking

[David Halik]

Quick question. How important are these? Are the errors recoverable and 
not a big deal, or are they actually a problem? I see a few of these 
randomly over the course of the day.


Jan 15 10:04:04 gehenna13.rutgers.edu dovecot: IMAP(user): 
unlink(/rci/nqu/rci/u8/user/dovecot/.such and such 
maildir/.nfs001e95102b8d) failed: Device or resource busy
Jan 15 10:04:04 gehenna13.rutgers.edu dovecot: IMAP(user): 
unlink(/rci/nqu/rci/u8/user/dovecot/.such and such 
maildir/.nfs001e95102b8d) failed: Device or resource busy
Jan 15 10:04:04 gehenna13.rutgers.edu dovecot: IMAP(user): 
unlink_directory(/rci/nqu/rci/u8/user/dovecot/.such and such maildir) 
failed: Device or resource busy
Jan 15 10:04:04 gehenna13.rutgers.edu dovecot: IMAP(user): 
unlink_directory(/rci/nqu/rci/u8/user/dovecot/.such and such maildir) 
failed: Device or resource busy


--

David Halik
System Administrator
OIT-CSS Rutgers University
dha...@jla.rutgers.edu

[Dovecot] sieve: failed to save binary

[wenjie zheng]

RHEL 5.3
Dovecot 2.0 beta1
dovecot-sieve (updated 1 week ago, changeset a3eb0b0b2ddf)

Jan 15 11:30:06 mail4a dovecot: lmtp(31015, testmail...@dev.p4nt5.com):
sieve: using sieve path for user's script: /data/mail/de/
dev.p4nt5.com/te/testmail4a2/.dovecot.sieve
Jan 15 11:30:06 mail4a dovecot: lmtp(31015, testmail...@dev.p4nt5.com):
sieve: executed before user's script(1):
/etc/dovecot/dovecot-global-sieve.sieve
Jan 15 11:30:06 mail4a dovecot: lmtp(31015, testmail...@dev.p4nt5.com):
afEDDB6mUEsneQAA0TR52A: sieve: failed to save binary:
open(/etc/dovecot/dovecot-global-sieve.svbinmail4a.31015.) failed:
Permission denied (euid=5000(virtual) egid=5000(virtual) missing +w perm:
/etc/dovecot)

It seems that Dovecot wants to save it as something specific with a
different name. Even running sievec manually does not make it work.

Thanks,
Wenjie

Re: [Dovecot] Moving

[Timo Sirainen]

On 10.1.2010, at 17.56, Timo Sirainen wrote:

> On 2.1.2010, at 23.18, Timo Sirainen wrote:
> 
>> I'm moving back to Finland tomorrow. It's probably going to take a week or 
>> so until things settle down and I'm again back to coding.
> 
> And now I'm without internet at home, hopefully my mobile 3g connection opens 
> in a few days..

No. And trying to call to their help desk says something about some union 
strike or whatever. So I guess that won't be happening anytime soon.

> And in any case I'll get cable modem by Saturday.

Except today I found out my sister actually had ADSL. I don't know why I 
thought she had cable.. So I wasted a whole week waiting for it. Anyway, bought 
cable internet today and have to wait until next week for it to actually work.. 
And they sold me a cable modem (that they said they haven't had for 2+ years) 
for double its price..

Re: [Dovecot] sieve: failed to save binary

[Stephan Bosch]

wenjie zheng wrote:

RHEL 5.3
Dovecot 2.0 beta1
dovecot-sieve (updated 1 week ago, changeset a3eb0b0b2ddf)

Jan 15 11:30:06 mail4a dovecot: lmtp(31015, testmail...@dev.p4nt5.com):
sieve: using sieve path for user's script: /data/mail/de/
dev.p4nt5.com/te/testmail4a2/.dovecot.sieve
Jan 15 11:30:06 mail4a dovecot: lmtp(31015, testmail...@dev.p4nt5.com):
sieve: executed before user's script(1):
/etc/dovecot/dovecot-global-sieve.sieve
Jan 15 11:30:06 mail4a dovecot: lmtp(31015, testmail...@dev.p4nt5.com):
afEDDB6mUEsneQAA0TR52A: sieve: failed to save binary:
open(/etc/dovecot/dovecot-global-sieve.svbinmail4a.31015.) failed:
Permission denied (euid=5000(virtual) egid=5000(virtual) missing +w perm:
/etc/dovecot)

It seems that Dovecot wants to save it as something specific with a
different name. Even running sievec manually does not make it work.

It tries to save the compiled binary in the same directory as the 
script. This requires write access. The error you see is the attempt to 
create the initial temporary file to which the compiled binary is 
written. Subsequently, this would be renamed to 
/etc/dovecot/dovecot-global-sieve.svbin, overwriting any previous 
binary. To prevent this error, you will need to execute sievec with 
admin privileges to compile these scripts:


http://wiki.dovecot.org/LDA/Sieve/Dovecot#Script_Compiling

Regards,

Stephan

[Dovecot] sieve: discarding vacation response

[wenjie zheng]

Configuration: RHEL 5.3, Dovecot 2.0 beta1, dovecot-2.0-sieve (1week old)

[wen...@build dovecot2-2.0.beta1]$ telnet mail4a 24
Trying 172.19.1.74...
Connected to mail4a.cloud.dev.mlsrvr.com (172.19.1.74).
Escape character is '^]'.
220 mail4a Dovecot LMTP ready
mail from:
250 2.1.0 OK
rcpt to:
250 2.1.5 OK
DATA
354 OK
From: 
To: foo
Subject: hello

Hello there

.
250 2.0.0  eMcYKg7gUEt8ewAA0TR52A Saved
quit
221 2.0.0 Client quit
Connection closed by foreign host.

testmail...@dev.p4nt5.com has a local .dovecot.sieve file, which
contains a vacation auto response.

#begin
require ["fileinto", "body", "vacation"];

vacation
:days 1
text:
I am away.
.
;


keep;
#end

In the log:
Jan 15 15:38:07 mail4a dovecot: lmtp(31612,
testmail...@dev.p4nt5.com): eMcYKg7gUEt8ewAA0TR52A: sieve:
msgid=unspecified: discarding vacation response for message implicitly
delivered to 
Jan 15 15:38:07 mail4a dovecot: lmtp(31612,
testmail...@dev.p4nt5.com): eMcYKg7gUEt8ewAA0TR52A: sieve:
msgid=unspecified: stored mail into mailbox 'INBOX'


Thanks,
Wenjie

Re: [Dovecot] sieve: discarding vacation response

[Stephan Bosch]

wenjie zheng wrote:
[...]


rcpt to:
250 2.1.5 OK
DATA
354 OK
From: 
To: foo
Subject: hello

Hello there

The vacation action requires that the mail explicitly lists the 
recipient in the To/Cc/etc headers of the message. Your test message 
does not contain the user's address in the To: header.


From RFC 5230:


4.5.  Address Parameter and Limiting Replies to Personal Messages

"Vacation" MUST NOT respond to a message unless the recipient user's
email address is in a "To", "Cc", "Bcc", "Resent-To", "Resent-Cc", or
"Resent-Bcc" line of the original message.  An email address is
considered to belong to the recipient if it is one of:

1.  an email address known by the implementation to be associated
with the recipient,

2.  the final envelope recipient address if it's available to the
implementation, or

3.  an address specified by the script writer via the ":addresses"
argument described in the next paragraph.

Users can supply additional mail addresses that are theirs with the
":addresses" argument, which takes a string-list listing additional
addresses that a user might have.  These addresses are considered to
belong to the recipient user in addition to the addresses known to
the implementation.



In the log:
Jan 15 15:38:07 mail4a dovecot: lmtp(31612,
testmail...@dev.p4nt5.com): eMcYKg7gUEt8ewAA0TR52A: sieve:
msgid=unspecified: discarding vacation response for message implicitly
delivered to 


Hence, you get the above log message, indicating no vacation response is 
sent.


Regards,

Stephan.

Re: [Dovecot] listen to imap*s* on multiple ports?

[Pascal Volk]

On 01/16/2010 03:36 AM Frank Cusack wrote:
> How can I listen to ssl-wrapped IMAP on multiple ports? …

http://dovecot.org/list/dovecot/2010-January/045874.html
Please don't forget to substitute listen with ssl_listen


Regards,
Pascal
-- 
The trapper recommends today: c01dcafe.1001...@localdomain.org

[Dovecot] listen to imap*s* on multiple ports?

[Frank Cusack]

is out of date.

How can I listen to ssl-wrapped IMAP on multiple ports?  I need to
listen on both 993 (for some stupid clients I have to support that
can't do START TLS) and 80 (to get past L3/L4 firewalls).  I'd like
to do it in dovecot rather than use nc, ipfilter or whatever.

-frank