Re: SASL AUTH with postfix

2019-11-14 Thread Benny Pedersen via dovecot

On 2019-11-14 22:57, Jorge Bastos via dovecot wrote:


It was in my front and didn't saw it.
Now i need to go further, have the SASL auth being read from a
diferrent table than the password_query for *sql.


https://doc.dovecot.org/configuration_manual/authentication/sql/


In the below conf, would it be possible and how, to check an specific
sql table for auth?


missguiding, the auth below is just the dovecot socket for dovecot-sasl 
auth in postfix


for sql baackends you need to read above link, are you have solved the 
realm problem or want to ditt it ?



service auth {
  # Postfix smtp-auth
unix_listener /var/spool/postfix/private/auth {
mode = 0660
# Assuming the default Postfix user and group
user = postfix
group = postfix
}
}


Re: SASL AUTH with postfix

2019-11-14 Thread Jorge Bastos via dovecot

On 2019-11-14 15:41, Benny Pedersen via dovecot wrote:


Jorge Bastos via dovecot skrev den 2019-11-14 16:25:


I've tried to search for the realm part in dovecot but didn't found it,
Could you guide me to it?


doveconf -d | grep realm

doveconf -n if more help is needed


Thanks Benny, 


It was in my front and didn't saw it.
Now i need to go further, have the SASL auth being read from a diferrent
table than the password_query for *sql. 


In the below conf, would it be possible and how, to check an specific
sql table for auth? 


service auth {
 # Postfix smtp-auth
   unix_listener /var/spool/postfix/private/auth {
   mode = 0660
   # Assuming the default Postfix user and group
   user = postfix
   group = postfix
   }
}

Re: http API for IMAP

2019-11-14 Thread Ralph Seichter via dovecot
* Thomas Güttler via dovecot:

> Stateless, http and URLs are the future.

A bold claim, and not worth anything without proof, which is impossible
to provide because you cannot predict the future.

> JavaScript running on in browser or mobile phone can't connect to
> IMAP/SMTP.

That's simply not true. There are JavaScript libraries like SmtpJS, a
low-level TCP/UDP socket API, and more.

Please do your research before stating obvious falsehoods.

-Ralph


Re: SASL AUTH with postfix

2019-11-14 Thread Benny Pedersen via dovecot

Jorge Bastos via dovecot skrev den 2019-11-14 16:25:


I've tried to search for the realm part in dovecot but didn't found it,
Could you guide me to it?


doveconf -d | grep realm

doveconf -n if more help is needed


RE: SASL AUTH with postfix

2019-11-14 Thread Jorge Bastos via dovecot
Hi Benny,

I've tried to search for the realm part in dovecot but didn't found it,
Could you guide me to it?

-Original Message-
From: dovecot  On Behalf Of Benny Pedersen via
dovecot
Sent: 13 de novembro de 2019 23:33
To: dovecot@dovecot.org
Subject: Re: SASL AUTH with postfix

Jorge Bastos via dovecot skrev den 2019-11-13 23:53:
> Jorge Bastos via dovecot skrev den 2019-11-13 22:00:

> plus:
> smtpd_sasl_local_domain = fastmail
> 
> but the user that i have in the table, that worked with Cyrus, in the
> format: "username@fastmail", it's not working with dovecot

if that fails dovecot have no password for that non fqdn mail

solution dont add this to postfix

in dovecot is realm setup ?



Re: http API for IMAP

2019-11-14 Thread Chris Kiakas via dovecot
You just described a more complex environment not a simplified environment. You 
can run code within code within code. Already we have all this abstraction and 
it’s leading to people not understanding and implementing solutions that make 
very little sense. Like what you describe. Why would you want to run an IMAP 
server in a browser? It’s so wrong I don’t even know where to start.

If you are not talking about an IMAP server and you are talking about an IMAP 
client you are in the wrong forum.


> On Nov 14, 2019, at 8:21 AM, Phillip Odam via dovecot  
> wrote:
> 
> A HTTP API for IMAP and for that matter, POP3 and SMTP is exactly what we 
> built where I work.
> 
> For anyone wonder why build such a thing? A simplified interface is an 
> exceptionally powerful tool. Many of our clients have encountered issues 
> constructing multipart http requests so if that’s an issue, good luck getting 
> IMAP to work. Since multipart turns out to be such an issue we’ve turned out 
> support for a variety of uploads including (completely non-standard) where 
> the request body is just the file content.
> 
> We’ve built our API in Java and as such have simply used the JavaMail API. 
> Admittedly though the plan is to get off this design since when there’s 10s 
> of thousands messages in an IMAP maildir folder the index can grow to an 
> unmanageable size.
> 
> On Thu, Nov 14, 2019 at 2:59 AM Thomas Güttler via dovecot 
>  wrote:
> 
> 
> Am 13.11.19 um 17:21 schrieb Ralph Seichter via dovecot:
> > * Thomas Güttler via dovecot:
> > 
> >> Is there a way to access mails in dovecot via https?
> > 
> > Why on earth would that be beneficial?
> > 
> >"The Internet Message Access Protocol, Version 4rev1 (IMAP4rev1)
> > allows a client to access and manipulate electronic mail messages
> > on a server." (RFC 3501)
> > 
> > Putting it bluntly: Learn to use the protocol specifically designed for
> > the task at hand, not a protocol with different design goals that you
> > happen to know better.
> 
> Stateless, http and URLs are the future. JavaScript running on in browser or
> mobile phone can't connect to IMAP/SMTP.
> 
> AFAIK you can't sent a link/URL to a mail on a shared folder to a friend.
> Like "Hi  bob, she loves me. See this message from here https:/./"
> 
> Regards,
>Thomas Güttler
> 
> 
> 
> 
> -- 
> Thomas Guettler http://www.thomas-guettler.de/
> I am looking for feedback: https://github.com/guettli/programming-guidelines



Re: JMAP: Re: http API for IMAP

2019-11-14 Thread Benny Pedersen via dovecot

Thomas Güttler via dovecot skrev den 2019-11-14 14:44:


https://proxy.jmap.io/

This way you can use JMAP even if you imap server does not
support it.


fair, i just try avoid proxy in all terms


Re: http API for IMAP

2019-11-14 Thread Thomas Güttler via dovecot




Am 14.11.19 um 14:21 schrieb Phillip Odam via dovecot:

A HTTP API for IMAP and for that matter, POP3 and SMTP is exactly what we built 
where I work.



Did you build upon JMAP? If not, why not?

Regards,
 Thomas Güttler

--
Thomas Guettler http://www.thomas-guettler.de/
I am looking for feedback: https://github.com/guettli/programming-guidelines


Re: JMAP: Re: http API for IMAP

2019-11-14 Thread Thomas Güttler via dovecot

Am 14.11.19 um 14:03 schrieb Benny Pedersen via dovecot:

Thomas Güttler via dovecot skrev den 2019-11-14 08:55:


Is there already an open source imap2jmap server?


why do you say imap here ?

https://www.cyrusimap.org/imap/developer/jmap.html

cyrus already have it, we just wait for dovecot :)



I used my favorite search engine (ecosia) and found

   https://proxy.jmap.io/

This way you can use JMAP even if you imap server does not
support it.


Regards,
  Thomas Güttler


--
Thomas Guettler http://www.thomas-guettler.de/
I am looking for feedback: https://github.com/guettli/programming-guidelines


Dovecot Master User: Access user's mailbox without owner's password

2019-11-14 Thread Dav Rdrz via dovecot
Hi, I hope you're all right. I describe below the scenario where the
problem occurs.
I'm trying to activate a master user [1] to be able to access all the
boxes of all users by imap.
I have configured the dovecot-master-users [2] file with the
appropriate permissions.
When I try to access, for example with roundcube, through
u...@mydomain.com*my_master_u...@not-exist.com
I see in the log, that it seems to ignore the master-user (*) and
tries to authenticate the Active Directory but with the master user's
password. Then it shows in the log the messages

auth: Info: ldap(u...@mydomain.com,127.0.0.1,<6sFGXE6XLwB/AAAB> )
invalid credentials
auth: Debug: client passdb out: FAIL 1 user=u...@mydomain.com

I have other test cases, but I need to validate the master user login that way.

I would appreciate any comments you can make and I am waiting to
answer any questions.

Regards,

[1] https://doc.dovecot.org/configuration_manual/authentication/master_users/
[2] https://docs.iredmail.org/dovecot.master.user.html

---

root@mail-01:/etc/dovecot# cat /etc/issue
Ubuntu 14.04.5 LTS \n \l

root@mail-01:/etc/dovecot# dpkg -l | grep dovecot | awk {'print $2" "$3'}
dovecot-core 1:2.2.9-1ubuntu2.6
dovecot-imapd 1:2.2.9-1ubuntu2.6
dovecot-ldap 1:2.2.9-1ubuntu2.6
dovecot-lmtpd 1:2.2.9-1ubuntu2.6
dovecot-managesieved 1:2.2.9-1ubuntu2.6
dovecot-mysql 1:2.2.9-1ubuntu2.6
dovecot-pop3d 1:2.2.9-1ubuntu2.6
dovecot-sieve 1:2.2.9-1ubuntu2.6

root@mail-01:/etc/dovecot# cat dovecot.conf | grep -v '#' | grep -v -e
'^$' | sed  "s/REALDOMAIN/mydomain/g"
listen = * [::]
mail_plugins = quota mailbox_alias acl
protocols = pop3 imap sieve lmtp
mail_uid = 2000
mail_gid = 2000
first_valid_uid = 2000
last_valid_uid = 2000
log_path = /var/log/dovecot.log
auth_verbose = yes
auth_debug = yes
ssl_protocols = !SSLv2 !SSLv3
ssl = required
verbose_ssl = no
ssl_ca = 

Re: http API for IMAP

2019-11-14 Thread Phillip Odam via dovecot
A HTTP API for IMAP and for that matter, POP3 and SMTP is exactly what we
built where I work.

For anyone wonder why build such a thing? A simplified interface is an
exceptionally powerful tool. Many of our clients have encountered issues
constructing multipart http requests so if that’s an issue, good luck
getting IMAP to work. Since multipart turns out to be such an issue we’ve
turned out support for a variety of uploads including (completely
non-standard) where the request body is just the file content.

We’ve built our API in Java and as such have simply used the JavaMail API.
Admittedly though the plan is to get off this design since when there’s 10s
of thousands messages in an IMAP maildir folder the index can grow to an
unmanageable size.

On Thu, Nov 14, 2019 at 2:59 AM Thomas Güttler via dovecot <
dovecot@dovecot.org> wrote:

>
>
> Am 13.11.19 um 17:21 schrieb Ralph Seichter via dovecot:
> > * Thomas Güttler via dovecot:
> >
> >> Is there a way to access mails in dovecot via https?
> >
> > Why on earth would that be beneficial?
> >
> >"The Internet Message Access Protocol, Version 4rev1 (IMAP4rev1)
> > allows a client to access and manipulate electronic mail messages
> > on a server." (RFC 3501)
> >
> > Putting it bluntly: Learn to use the protocol specifically designed for
> > the task at hand, not a protocol with different design goals that you
> > happen to know better.
>
> Stateless, http and URLs are the future. JavaScript running on in browser
> or
> mobile phone can't connect to IMAP/SMTP.
>
> AFAIK you can't sent a link/URL to a mail on a shared folder to a friend.
> Like "Hi  bob, she loves me. See this message from here https:/./"
>
> Regards,
>Thomas Güttler
>
>
>
>
> --
> Thomas Guettler http://www.thomas-guettler.de/
> I am looking for feedback:
> https://github.com/guettli/programming-guidelines
>


Re: JMAP: Re: http API for IMAP

2019-11-14 Thread Benny Pedersen via dovecot

Thomas Güttler via dovecot skrev den 2019-11-14 08:55:


Is there already an open source imap2jmap server?


why do you say imap here ?

https://www.cyrusimap.org/imap/developer/jmap.html

cyrus already have it, we just wait for dovecot :)

did you google ?


Crash when moving mail from Inbox to Trash

2019-11-14 Thread marvin alcantara via dovecot
Hi,

I am developing a dovecot plugin, and inside my plugin I am implementing my own 
expunge function. Inside my function, I am calling the following lines of code:
 if (storage->v.mail_open(mail, , >open_file) < 0) return -1;
The mail_open virtual function is an invalid address. The storage should be 
mdbox however, it seems that it didn't get the correct mdbox_mail_open of 
mdbox-storage.
Do you have any suggestions as to why this is happening?

dovecot version:2.3.7 (a3d493f)


Sincerely,Marvin