similar to: Writing to mail directory

Displaying 20 results from an estimated 2000 matches similar to: "Writing to mail directory"

2006 Aug 23
0
Unable to get LDA working
FreeBSD 6.1 STABLE Postfix version 2.4-20060806 Dovecot v1.0.rc2 I have the following in the postfix main.cf file: mailbox_command = /usr/local/libexec/dovecot/deliver This is from the dovecot.conf file: default_mail_env = mbox:/var/mail/%u However, mail is never delivered with this configuration. This is an excerpt from the 'dovecot.log' file: deliver(gerard): Error:
2006 Oct 02
3
Dovecot as LDA
FreeBSD 6.1-RELEASE-p8 postfix-current-2.4.20060903,3 dovecot-1.0.r7 I am experiencing a problem with dovecot as an LDA. It will not deliver mail unless the mail directory is chmod'd to 1777. Below is an example of the log file output. The dovecot.log file had over a hundred entries similar to this: deliver(gerard): Error: open(/var/mail/.temp.scorpio.seibercom.net.1123.cd38cd4d82e1368f)
2006 Aug 09
10
Dovecot as LDA with Postfix
I have been attempting to replace Procmail with Dovecot as the LDA for my Postfix mail server, but without success. Below is a truncated output from the /var/log/maillog. Aug 9 11:56:20 scorpio postfix/local[4338]: 88C3FC3D1: to=<gerard at localhost.seibercom.net>, orig_to=<gerard at localhost>, relay=local, delay=1119, delays=1118/0.71/0/0.11, dsn=4.3.0, status=deferred (temporary
2019 Jan 18
1
Samba, ZFS and FreeBSD 12
On Fri, 18 Jan 2019 12:14:47 +0000, Rowland Penny via samba stated: >On Fri, 18 Jan 2019 11:15:38 +0000 >Gerard Seibert via samba <samba at lists.samba.org> wrote: > >> FreeBSD 12.0-RELEASE-p2 GENERIC amd64 >> samba48-4.8.7 >> >> Ever since updating from FreeBSD 11 to FreeBSD 12, I have experienced >> a problem with samba. While still on FreeBSD 11,
2019 Jan 18
2
Samba, ZFS and FreeBSD 12
FreeBSD 12.0-RELEASE-p2 GENERIC amd64 samba48-4.8.7 Ever since updating from FreeBSD 11 to FreeBSD 12, I have experienced a problem with samba. While still on FreeBSD 11, I configured a Windows 10 machine to write backups of selected directories to my FreeBSD machine. That worked perfectly. No problems were detected and everything was backed up correctly. However, after updating to FreeBSD 12 a
2018 Dec 21
1
Problem with quota
On Thu, 20 Dec 2018 16:59:54 -0800, Jeremy Allison stated: >On Thu, Dec 20, 2018 at 12:08:02PM +0000, Gerard Seibert via samba wrote: >> Samba version 4.8.7, running on a FreeBSD 12.0-RELEASE amd64 system with a >> ZFS file system. >> >> I have a Windows 10 machine configured to do automatic backups to my >> FreeBSD machine on a daily basis. Since updating
2018 Dec 20
3
Problem with quota
Samba version 4.8.7, running on a FreeBSD 12.0-RELEASE amd64 system with a ZFS file system. I have a Windows 10 machine configured to do automatic backups to my FreeBSD machine on a daily basis. Since updating FreeBSD, the following errors are displayed when the backup begins. This is a truncated list. Dec 19 06:29:01 scorpio smbd[56795]: [2018/12/19 06:29:01.413635, 0]
2013 Mar 18
2
SASL + Postfix woes
Okay, I wasn't going to try and fix up the messed up mail server I was given; however, I decided that I might as well try. Situation: The system has a Postfix MTA and uses Dovecot for LDA and Cyrus-SASL for SASL. That works fine. I decided that I wanted to switch over to Dovecot for SASL. dovecot is presently using MySQL for its database. I make the (I thought) necessary changes in Postfix
2014 Jul 01
1
Error receiving mail from postfix
When mail is relayed to dovecot from postfix, I am getting this error message in the maillog: Jul 1 07:05:19 scorpio postfix/pipe[45488]: 3h2jQl3Xldz3FMPc: to=<user at domain.com>, relay=dovecot, delay=0.16, delays=0.12/0.01/0/0.03, dsn=4.3.0, status=deferred (temporary failure. Command output: lda: Error: user user at domain.com: Error reading configuration: Invalid settings:
2019 Mar 19
1
Samba warning message
On Tue, 19 Mar 2019 13:02:40 +0000, Rowland Penny via samba stated: >On Tue, 19 Mar 2019 12:37:08 +0000 >Gerard Seibert via samba <samba at lists.samba.org> wrote: > >> Samba 4.8.9 >> FreeBSD 12.0-RELEASE-p3 / amd64 >> >> Since updating both FreeBSD and Samba, I have been getting the >> following screen pop-ups incessantly. They are always the same
2010 Oct 05
2
how to upgrade (update) the dovecot
Dear All, Is there any easy way to upgrade Dovecot like yum command? Or I have to delete the current and install the new version then change the setting?> I will appreciate if you can tell me the steps please? Best Regards Arif --- On Fri, 1/10/10, dovecot-request at dovecot.org <dovecot-request at dovecot.org> wrote: From: dovecot-request at dovecot.org <dovecot-request at
2019 Mar 19
2
Samba warning message
Samba 4.8.9 FreeBSD 12.0-RELEASE-p3 / amd64 Since updating both FreeBSD and Samba, I have been getting the following screen pop-ups incessantly. They are always the same except for the time. IP 102.168.0.102 is a Win10 PRO / amd64 machine. I never received any warnings before updating. <quot> Mar 19 08:23:58 scorpio nmbd[11202]: [2019/03/19 08:23:58.049153, 0]
2018 Apr 10
1
doveconf error upon boot up
On Tue, 10 Apr 2018 11:08:20 -0400, David Mehler stated: >Can you send a complete doveconf -n and your dovecot startup lines in >/etc/rc.conf? /etc/rc.conf ## Dovecot dovecot_enable="YES" # 2.3.1 (8e2f634): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.1 (d9bc6dfe) # OS: FreeBSD 11.1-RELEASE-p9 amd64 zfs # Hostname: localhost auth_mechanisms = plain login
2019 Jan 18
0
Samba, ZFS and FreeBSD 12
On Fri, 18 Jan 2019 11:15:38 +0000 Gerard Seibert via samba <samba at lists.samba.org> wrote: > FreeBSD 12.0-RELEASE-p2 GENERIC amd64 > samba48-4.8.7 > > Ever since updating from FreeBSD 11 to FreeBSD 12, I have experienced > a problem with samba. While still on FreeBSD 11, I configured a > Windows 10 machine to write backups of selected directories to my > FreeBSD
2018 Dec 21
0
Problem with quota
On Thu, Dec 20, 2018 at 12:08:02PM +0000, Gerard Seibert via samba wrote: > Samba version 4.8.7, running on a FreeBSD 12.0-RELEASE amd64 system with a > ZFS file system. > > I have a Windows 10 machine configured to do automatic backups to my FreeBSD > machine on a daily basis. Since updating FreeBSD, the following errors are > displayed when the backup begins. This is a
2019 May 26
1
Unknown error message
dovecot 2.3.6 (7eab80676) FreeBSD 12.0-RELEASE-p5 amd64 I have recently been finding error messages similar to the following in my Dovecot log file: May 26 06:58:32 imap(gerard at seibercom.net)<87791><WvXT+LyJHBCubeH6>: Error: stat(/var/mail/vmail/seibercom.net/gerard/.dovecot.sieve/tmp) failed: Not a directory The message is correct as there is no such directory. The question is
2012 Apr 14
3
LMTP auth problem
hey all, im getting the following error: Apr 14 14:29:44 lmtpdirector1 dovecot: auth: Error: passdb(scorpio,127.0.0.1): Auth client doesn't have permissions to do a PASS lookup: /var/run/dovecot/auth-userdb mode=0666, but not owned by UID 112(dovecot) Apr 14 14:29:44 lmtpdirector1 dovecot: lmtp(18298): Error: user scorpio: Auth PASS lookup failed My config. Director servers running both
2010 Oct 01
0
dovecot Digest, Vol 90, Issue 3
Dear All, Thanks for all your replied but still I don't know how to install from 1.0.7 to 1.2.14. What should I consider to keep the same configuration during or after upgrade? It is the first time I am trying to upgrade my Dovecot. Thank a lot for your help --- On Fri, 1/10/10, dovecot-request at dovecot.org <dovecot-request at dovecot.org> wrote: From: dovecot-request at
2006 Jan 03
2
Error returning browse list: NT_STATUS_OK
I continue to receive this error message: Error returning browse list: NT_STATUS_OK This is how I am attempting to list the shares on my WinXP machine. smbclient -L GERARD -U gerard Password: Domain=[GERARD] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Sharename Type Comment --------- ---- ------- Error returning browse list: NT_STATUS_OK
2006 Feb 04
1
Usernames & Passwords
I thought I had posted this previously, but I cannot seem to find any record of it. I am using Samba in a mixed network (WinXP and FreeBSD 5.4). There is no domain involved. Using the following command, I can access a share on one of the WinXP machines: smbclient //SERVER/SHARE -u NAME%PASSWORD I now find that I can also access the share using an incorrect 'NAME' or 'PASSWORD'