similar to: problem with disable_plaintext_auth

Hi I have installed the package dovecot-postfix on Ubuntu 12.04 LTS: dovecot --version: 2.0.19 postconf -d | grep version: 2.9.6 and receiving email works very fine, but relaying email does not work. I think the problem is that after STARTTLS the authentication is not being executed 250-AUTH PLAIN 250-AUTH=PLAIN which means using telnet returns telnet mx2.wyona.com 587 Trying

On 09/20/2018 12:56 PM, Robert Schetterer wrote: > Am 20.09.2018 um 11:04 schrieb Michael Goth: >> Hello, >> >> I'm setting up Dovecot 2.3.2.1 as a submission proxy to a Postfix >> backend server. Dovecot announces CHUNKING, but the Postfix backend >> does not support (or announce) it. >> >> HELO from Postfix: >> >> ?? 220

This should be an easy one. I'm trying to get postfix going. I've never done this before. I followed the directions at http://wiki.centos.org/HowTos/postfix. I opened port 25: iptables -I INPUT -p tcp -m tcp --dport 25 -j ACCEPT Here's an attempt to send mail: [motor at localhost motor]# mail -v larry.martell at gmail.com Subject: test test . EOT larry.martell at gmail.com...

Dear All, I've installed Postfix 2.7.0 and Dovecot 1.2.9 on Ubuntu 10.04. I want to use Dovecot SASL with Postfix and did the following configuration. main.cf smtpd_sasl_auth_enable = yes smtpd_sasl_type = dovecot smtpd_sasl_path = private/dovecot-auth smtpd_sasl_authenticated_header = yes smtpd_sasl_security_options = noanonymous smtpd_sasl_local_domain = $myhostname

Hi. I'm trying to get Dovecot - Postfix - SASL to work. But I need some help. Dovecot v1.0.rc14 Postfix 2.3.4 dovecot.conf ---------------- auth default { mechanisms = plain login passdb pam { } passdb passwd { } socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } postfix/main.cf

Hello, I'm trying to configure postfix + Dovecot SASL for user authenticated mail relay. I set following configuration on postfix queue_directory = /var/spool/postfix smtpd_sasl_auth_enable = yes smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_authenticated_header = yes smtpd_sasl_security_options = noanonymous smtpd_sasl_local_domain = $myhostname

Dear All, I have two machines, a Centos 3.4 machine and a Centos 4.1 machine. I have used the same sendmail.mc file on each, and 3.4 machine does plain SMTP auth with no problems, compiling the same mc file on the 4.1 machine gives this error: xxxxx [x.x.x.x] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA in the logs, it doesn't even try to authenticate, the cyrus sasl rpm

Hi List, I have a postfix server based on CentOS 5 in which I have been trying to add TLS encryption support for SMTP. From the localhost when I do an EHLO, following is the output [root at xxxxxxx ~]# nc localhost 25 220 xxxxxxx.xxxx.xxx.xx ESMTP Postfix EHLO localhost 250-xxxxxxx.xxxx.xxx.xx 250-PIPELINING 250-SIZE 41943040 250-VRFY 250-ETRN 250-STARTTLS 250-AUTH PLAIN LOGIN 250-AUTH=PLAIN

> Le 27 juil. 2019 ? 14:30, Stephan Bosch <stephan at rename-it.nl> a ?crit : > > On 23/07/2019 17:13, Jean-Daniel Dupas via dovecot wrote: >> Hello, >> >> I'm having trouble configuring the submission proxy. >> >> I have configured the submission service as follow: >> >> submission_host = smtp.example.com >>

Hello, I'm having trouble configuring the submission proxy. I have configured the submission service as follow: submission_host = smtp.example.com submission_relay_host = localhost submission_relay_port = 8587 submission_relay_rawlog_dir = /var/log/dovecot/ submission_relay_trusted = yes My main issue is that until I login, dovecot-submission won't connect to the backend and query the

Hello, I'm setting up Dovecot 2.3.2.1 as a submission proxy to a Postfix backend server. Dovecot announces CHUNKING, but the Postfix backend does not support (or announce) it. HELO from Postfix: 220 backend.mydomain.com ESMTP Postfix (Ubuntu) ehlo test 250-backend.mydomain.com 250-PIPELINING 250-SIZE 104857600 250-VRFY 250-ETRN 250-STARTTLS

Hi, tried to use postfix with virtual users and dovecot imaps/imap pop3/pop3s workin fine lokal smtp too, but a remote host is not able to send mail Debian Etch uname -a Linux mail 2.6.18-6-xen-amd64 #virtual user vmail:x:5000:8::/home/vmail:/bin/sh #master.cf added dovecot unix - n n - - pipe flags=DRhu user=vmail:mail argv=/usr/lib/dovecot/deliver -d

Hello all, I am struggeling to get my Dovecot SASL to work within postfix. I have used the configuration example listed on the main-site of dovecot and it basically isn't giving me any success at all. I am probably missing something easy, but after spending a few days testing and walking through everything I could think about I thought figured it was better to ask :) Hope someone can point me

I would like to instrument certain function calls with a function call of my own that takes some of the same arguments. For example, I would like to instrument calls to free with some function foo, so the C code would look like: foo(myarg1, myarg2, ptr); free(ptr); The problem occurs when I grab the arg from the free function and try to pass it to foo... if (isCallToFree(&I)) { Value*

On 09/20/2018 10:24 PM, Stephan Bosch wrote: > > > Op 20/09/2018 om 13:39 schreef Michael Goth: >> On 09/20/2018 12:56 PM, Robert Schetterer wrote: >>> Am 20.09.2018 um 11:04 schrieb Michael Goth: >>>> Hello, >>>> >>>> I'm setting up Dovecot 2.3.2.1 as a submission proxy to a Postfix >>>> backend server. Dovecot

Scott Ricketts wrote: > I would like to instrument certain function calls with a function call > of my own that takes some of the same arguments. For example, I would > like to instrument calls to free with some function foo, so the C code > would look like: > > foo(myarg1, myarg2, ptr); > free(ptr); > > The problem occurs when I grab the arg from the free function and

We recently began seeing server crashes in our cluster related to "pop3-login", which is causing "oom-killer" to be invoked. The server only recovers after a reboot. From dovecot.conf: login_process_per_connection = yes login_processes_count = 16 login_max_processes_count = 256 (Should we try switching processes_per_connection to no?) From dovecot.log: dovecot: Apr 17

I asked a user today to make sure his incoming and outgoing email was using TLS. He told me it wasn't possible because my Dovecot / Postfix daemons were only listening on TCP 25 & 143 according to a port scan he did. He told me the only way I could enable encrypted secure sessions between the client & server is to enable port 993 (IMAPs). I told him that TLS is supported on my mail

I have pretty much everything working fine. I have run into one issue with the filters that I am unsure where this a filter is being set. Dovecot 2.2.32 (dfbe293d4) I have setup dovecot-ldap.conf.ext to control my LDAP query's My current layout used filters based on looking at the posixAccount attributes ?user_filter = (&(objectClass=posixAccount)(uid=%u)) If I connect to a a ldap

Hi, With latest 2.3 -git (and 2.3.0 release), I'm running into this error with Thunderbird: "An error occurred while sending mail. The mail server responded: 5.5.4 Unsupported mail BODY type. Please verify that your email address is correct in your account settings and try again." This is fatal and means Thunderbird cannot use the submission service - fortunately I can revert