similar to: problem with lda

thanks for your input. Bill: deliver is just a symlink to dovecot-lda Stephan: I don't know, and and it even does not work when I use deliver -f "postmaster at ourdomain.internal" - I get the same error message. A part of the mail I got when using 2.2.23: Return-Path: <MAILER-DAEMON> Delivered-To: user1 at ourdomain.internal Received: from localhost (localhost [127.0.0.1])

No reason to tell me about security, I just need chmod for my tests. Where to change it ? On Thu, Jan 25, 2018 at 12:00 PM, <dovecot-request at dovecot.org> wrote: > Send dovecot mailing list submissions to > dovecot at dovecot.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://dovecot.org/mailman/listinfo/dovecot > or, via email,

Op 1/24/2018 om 5:30 PM schreef Infoomatic: > Hello, > > I am currently testing the upgrade from our dovecot v2.2.23 to 2.3.0. I have a strange problem with lda. > We use bounce mails for internal users if they try to send virus/spammails. The exact same config works with 2.2.23, but not with 2.3.0. > > The relevant postfix/master.cf part: > dovecot unix - n n

I use postfix + dovecot LDA + mysql virtual users and up til friday, everything was working just fine. Dovecot is 2.0.beta6 (3156315704ef) Like I said, up til friday, when I added a vacation entry into postfix (which I have now removed to see if it was the reason) mails to the alias virusalert (which is aliased to me) went through just fine. Now I get these sort of errors from the LDA: Feb

Hi, While testing our migration to dovecot 2.3.0, we encountered 2 panics, 1 segmentation fault while we wanted to rebuild the solr indizes. Problem [1] was encountered while rebuilding the indizes, and now I don't know how many mails/documents are indexed or where it got stuck. [2] and [3] encountered while just playing around, since I did not know of "tokenize" and did not find a

It's fixed in head. Sorry. ---Aki TuomiDovecot oy -------- Alkuper?inen viesti --------L?hett?j?: Eric <ebroch at whitehorsetc.com> P?iv?m??r?: 31.3.2016 18.05 (GMT+02:00) Saaja: dovecot at dovecot.org Aihe: Re: v2.2.23 released Yes. I concur. On 3/31/2016 7:44 AM, Leon Kyneur wrote: > 2.2.23 seems to have broken doveadm backup, was previously working > fine on 2.2.22 >

http://dovecot.org/releases/2.2/dovecot-2.2.24.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.24.tar.gz.sig This should be a good release. :) * doveconf now warns if it sees a global setting being changed when the same setting was already set inside some filters. (A common mistake has been adding more plugins to a global mail_plugins setting after it was already set inside protocol

http://dovecot.org/releases/2.2/dovecot-2.2.24.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.24.tar.gz.sig This should be a good release. :) * doveconf now warns if it sees a global setting being changed when the same setting was already set inside some filters. (A common mistake has been adding more plugins to a global mail_plugins setting after it was already set inside protocol

I saw another thread about this topic, but I did not understand the solution. . . I recently discovered my bounced messages were not getting delivered. Obviously since I was not getting any messages, I thought everything was fine. Anyway, my maillog has entries similar to below for bounced messages: Mar 29 10:48:09 firewall postfix/pipe[9089]: 19565807: to=<myuser at my.domain>,

Hi there, I changed postfix to pass email to spamassassin, and then deliver to dovecot LDA. It fails to deliver. The current entry in master.cf now reads: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -d ${recipient} smtp inet n - - - - smtpd -o content_filter=spamassassin

Hello, Sometime when we receive a spam or virus that is detected as it, mailer daemon send a reply to the sender to inform that the message is a spam or content viruses. The problem is that the sender of the spam as something like voicemail at ourdomain.fr ( the user voicemail doesn't exist in our database ) And sometimes dovecot create the directory and store the reply 's mail...

Hi Louis, answers are inline ... On 03/24/2015 03:48 PM, L.P.H. van Belle wrote: > Realm is advices to use UPPERCASE.. not obligated. ( but very advices yes ) I changed the config to uppercase and rebooted, no change in the logfiles. > > check the following outputs and post them back in the list ( if needed anonymized ) > > hostname -i 192.168.1.235 > hostname -s the-ad-hostname

Hello, I've been trying to figure this out for some time and can't quite nail it down, despite searching the internet, and a couple of samba books. Here goes: I'm running "Version 3.4.3-3.3.1-2341-SUSE-SL11.2" of Samba on OpenSUSE 11.2. Here are some relevant excerpts from my smb.conf file: [global] ... security = ADS ... winbind separator = + ... log level = 2 ...

On 28.3.2019 22.34, Robert Kudyba via dovecot wrote: >>>>> Set >>>>> >>>>> ssl_client_ca_file=/path/to/cacert.pem to validate the certificate? >>>> >>>> Can this be the Lets Encrypt cert that we already have? In other >>>> words we have: >>>> ssl_cert = </etc/pki/dovecot/certs/dovecot.pem

I tried to synchronize the sysvol folders, on two dcs. Something went wrong since yesterday we have replication problems: One machine shows this, while the other one is happy. samba-tool drs showrepl ==== INBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=ourdomain,DC=com Default-First-Site-Name\DC03 via RPC DSA object GUID: af610e1a-9e3b-4cdd-a36b-c296d77a9479 Last attempt @

This is still happening after a reboot, Fedora 28. Restarting dovecot fixes the problem. Does anyone know if it could be related to this bug report? *https://bugzilla.redhat.com/show_bug.cgi?id=103401#c130 <https://bugzilla.redhat.com/show_bug.cgi?id=103401#c130> * and suggested work around to add ports to /proc/sys/net/ipv4/ip_local_reserved_ports? Nov 8 12:21:41 ourdomain dovecot[1386]:

I am trying to configure NIS, PAM, & LDAP on a CentOS 6.2 host. I've previously installed a similar configuration on RHEL4, but CentOS now uses nss-pam-ldapd and nslcd instead of nss_ldap, so the configurations are a little different. Currently, local users and groups are showing up but not LDAP users. When I do a /getent passwd/ and/getent group/ I don't get LDAP users. When I do

Hi all, Ok, been wanting to do this for a while, and I after the Heartbleed fiasco, the boss finally agreed to let me buy some real certs... Until now, we've been using self-signed certs with the following dovecot config: ssl = required ssl_cert = </etc/ssl/ourCerts/imap.pem ssl_key = </etc/ssl/ourCerts/imap_key.pem Now, I've created new keys/certs and the CSR, got the new

We're using quite successfully a samba 4.1 AD setup authenticating user. We have on an unregular basis mails that can't be delivered because dovecot-pam fails to verify the credentials. I'm trying to debug this and set the loglevel up to 3. I can see an error message being spammed in the log files and can't figure out what causes this. I expect a configuration error somewhere

Hi, I just upgraded from dovecot 2.2.19 to 2.3.2. "doveadm backup" worked fine in v 2.2.19, but now panics (user with shared folder): /opt/dovecot/bin/doveadm backup -u testuser -1 sdbox:/tmp/testuser dsync(standl2): Panic: file mailbox-attribute.c: line 360 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL) dsync(standl2):