similar to: Proxy to gmail not working

Hello, I understand the matter of using Dovecot as a forward proxy to Gmail is very popular (and even trivial), but my lack of Dovecot experience took me to at point where I truly need your help... I'm starting my task by trying to have something simple, where I can test connectivity to Gmail by sending a telnet to our Dovecot server. The Dovecot server accepts the telnet request, but for

We have frequent timeout problems after upgrading our imap servers from dovecot 1.1.16 to dovecot 1.2.11. One server acts as proxy only, and the other one is the "real" imap server". The credentials for the proxy service are stored in a remote MYSQL database. There were no trouble with dovecot 1.1.16. But now, with the most recent version, we get frequent login failures. It

Hello, I just upgraded my servers from Dovecot 2.1.2 to Dovecot 2.1.3-0~auto+5 by using Debian binaries from "http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.1 main". The config was not touched but now IMAP connections are not possible anymore (LMTP works fine). When I try to connect to a mailbox, the connect fails. Some log entries:

On 9/17/19 5:35 PM, Richard W.M. Jones wrote: > Test both the TLS enabled and fallback paths. > > nbd-server doesn't appear to support TLS at all, and qemu-nbd is known > not to allow fallback to unencrypted, and therefore it only makes > sense to test nbdkit at the moment. > --- > .gitignore | 4 ++++ > +interop_nbdkit_tls_certs_allow_enabled_SOURCES =

I don't really need logging of successful local deliveries since the MTA provides enough data. I can't get rid of LDA delivery logs by setting deliver_log_format = All this does is produce an empty log message e.g. Apr 16 01:22:05 dserver dovecot: lda(user): Timo, would you consider inclusion of this patch which will skip logging deliveries if deliver_log_format is empty: ---

I was a little surprised to find that LIBNBD_TLS_ALLOW worked out of the box, so I had to examine the logs whereupon I saw the magic message ... libnbd: debug: nbd1: nbd_connect_command: server refused TLS (policy), continuing with unencrypted connection I don't believe this path has ever been tested before. It's possible the tests could be improved if they actually checked for this

Hi everyone, I'm new to this ML. I have some issue with GMail import settings... I run a dovecot server (2.3.4.1) on Debian10 and I try to connect to my accounts from GMail. It's work fine from thunderbird in pop3,pop3s, imap, imaps... Submission work too... But it won't work on GMail except if I set ssl=yes and disable_plaintext_auth = no... Then GMail connect without SSL or

Hi list, I am configuring a samba server as a PDC (called DSERVER). I have follow some good docs to build my smb.conf file (see below). However, my server does not works correctly: when I execute smbclient, I don't find my workgroup (SOCINFO) alghouth I activated the wins support. [adel@grid007 ~]$ smbclient -L localhost -U root Password: Domain=[DSERVER] OS=[Unix] Server=[Samba

Test both the TLS enabled and fallback paths. nbd-server doesn't appear to support TLS at all, and qemu-nbd is known not to allow fallback to unencrypted, and therefore it only makes sense to test nbdkit at the moment. --- .gitignore | 4 ++++ TODO | 3 --- interop/Makefile.am | 54 +++++++++++++++++++++++++++++++++++++++++++++ interop/interop.c | 30

I'm using Dovecot 2.2.5. I'm setting up and new IMAPS server for personal use (i.e. only me). I have success with self-signed certificates but not with others (e.g. StartSSL.com) With StartSSL certs: I've been able to connect and test commands via: openssl s_client -connect imaps.unixathome.org:993 Can you configure your iPhone or Macbook to access the above? Authentication

This neutral refactoring adds -DTLS_MODE. We can in future change the requested TLS mode, but not in this commit. It also checks that nbd_get_tls_negotiated returns true after connecting, when the requested mode was set to LIBNBD_TLS_REQUIRE. --- interop/Makefile.am | 4 ++++ interop/interop.c | 26 ++++++++++++++++++++------ 2 files changed, 24 insertions(+), 6 deletions(-) diff --git

Now that we have implemented systemd socket activation, we can use this to run qemu-nbd in tests. The first patch leaves some dead code around (the -DSERVE_OVER_TCP=1 path). It's possible we might want to use this to test against a putative future NBD server that only supports TCP, but on the other hand maybe we should just remove it. Tests & valgrind still pass for me. Rich.

Hi all, i have some troubles in the implementation of my proxyconfiguration. i have two kind of users, the first will be proxied to a dovecot backend with masteruser-login, the other one will be proxied to another non-dovecot imapserver with nopassword. Everything looks to work if i use passwd-file like this: user1:{PLAIN}pass1:::::::proxy=y host=192.168.1.1 destuser=user1*masteruser

Hi, I just noticed a crash in Dovecot (2.2.27) on Debian with the Debian version 1:2.2.27-2~bpo8+1: Jan 28 07:50:42 srv1 dovecot: imap(yyy at xxx.de): Panic: file mail-storage.c: line 2170 (mailbox_save_context_reset): assertion failed: (ctx->copying_via_save) Jan 28 07:50:42 srv1 dovecot: imap(yyy at xxx.de): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x97d8e) [0x7f3e7fab8d8e]

This borrows from a trick in libvirt - by defining $(NULL) to expand to an empty string, we can more consistently write multi-line macros where all useful lines terminate with \, making it easier to add/remove lines without worrying about whether \ needs to be touched up on neighboring lines. --- Looks big, but is fairly mechanical. I'm also doing a similar patch for nbdkit, where it would

what about something like: http://www.idtnetwork.com/show.aspx?mi=161 http://taolinux.org/?q=node/view/2 http://whiteboxlinux.org/ brigth, blinking... in the very first page...lets try do to as all others are doing... its a pratical approach... not what we think about Red Hat trademark guidelines. Luis. ______________________________ EMPREL, http://www.recife.pe.gov.br

Hello list, Still need your help configuring proxy infrastructure. Today, I really struggle configuring master passwords forwarding. What I want: master user can connect to any other account, on proxy. Could please somebody help me, I read both articles about this on wiki, but still can't connect :( What I did: on proxy: auth_master_user_separator=* passdb sql { args =

doveconf -n output: # 2.3.2.1 (0719df592): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.2 () # OS: Linux 4.18.0-12-generic x86_64 Ubuntu 18.10 # Hostname: mail.example.org auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes director_mail_servers = XX.XX.XX.XX hostname = mail.example.org log_path = /var/log/dovecot.log login_trusted_networks =

The PJSIP endpoint is configured for ulaw only. Not sure how or why we are seeing the g729 on calls for this endpoint. Would this be a case that asterisk detects the rtp stream is g729 even though it's negotiated as ulaw? Why would asterisk change the format to g729 when disallow = all and allow = ulaw are the endpoint settings? [121] type = endpoint context = IS transport = transport1 aors

Hi, Has anybody come across a situation where they were unable to register with Asterisk through a SIP stateless proxy server? I'm getting an error: "403 Authentication user name does not match account name" As far as I can tell the requests reaching Asterisk with and without the proxy are identical excepting the IP address the REGISTER request is coming from and the Via header