similar to: Strange error message

Ok, I've ALMOST got this working ... I can run deliver as a user, but when I try using it as the default delivery agent from sendmail, I get deliver(userid): net_connect(/var/run/dovecot/auth-master) failed: Permission denied Does deliver run as root, as the recipient's ID, sendmail's ID or sendmail's GID? (I'm running freebsd) Or am I totally clueless ?? Here is dovecot

Dovecot 1.0.3 Deliver is saying this on two specific emails. Other emails to these 2 users are going through fine. Looking at the mail headers the only thing questionable I see is: From: "AMS Publication Division"@ams.org Is this the problem? # 1.0.3: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap pop3 listen(default): *:143 listen(imap): *:143 listen(pop3):

There are three applications that have their mitts on files on my mail server, which is running AIXV5.3 and UWIMAP and mbox format. The mail folders and INBOXES are native to that machine, but also are NFS exported to a login server and a mailing list server. All three machines are running the lockd daemon. Everybody wants to lock differently 1) procmail (delivering for sendmail), which

I have Dovecot 1.0 in trial use by the IT staff, and have some locking questions Background, the mail server runs procmail, sendmail and NFS exports the user homedir and mailbox to a) a login shell host and b) a mailing list services host. It runs UWIMAP on the usual ports and dovecot on a arbitrary port number. Because of concern with NFS and file access contention. I have the following

Sorry, couldn't find this in the archives. Under freebsd 4.x, the native mail.local that sendmail uses by default writes From_ lines that include the origin address. This is very readily parsable and handy for quick greps in mboxes. But deliver defaults it to MAILER-DAEMON. I see you can specify the envelope From_ with "-f", but I'm not sure how that's useful. Also

While experimenting a bit, I found that for some reason, locking indexes with flock is problematic, but only if user is taken from passwd-file. The host system is openbsd 3.9, dovecot's configuration is added at the bottom. Authentication is from two places - first from mentioned passwd-file, then from passwd file using bsdauth (in this case, there're no problems with flock). So, if

How does IMAP lock the /var/spool/mail/user file? Here's my problem: I'm writing a script to expire old or oversize mail through a series of archive folders. I don't want to take the whole server down to do this, nor does it seem like I would have to lock the user out entirely if I can manage to emulate the locks correctly. I am able to lock /var/spool/mail/user (and ~user/mail/*)

Hi, I have just built a copy of dovecot on my sparc based solaris box. I now have dovecot running but when I try to log in using thunderbird or the solaris default package I get bombed out and the following error is generated.... dovecot: Nov 09 21:42:57 Error: child 20780 (imap) returned error 89 dovecot: Nov 09 21:42:57 Error: imap(ppchurch): flock() locks not supported I have set the

Hi List, last time i did a lot of packaging and installing different versions of dovecot 1.0.x (rc not included ;) )and all was fine. Now a have a little problem. In this case it was an update from 1.0.13 to 1.1.1 Sometime it happens that 1 user out of x (more than 100) got this standardmessage for ~1 or ~2 thousend times in his mailbox (mbox) for example: >From MAILER_DAEMON Mon Sep 18

On Tue, 9 Oct 2018 12:08:00 +0200 Sami Ketola <sami.ketola at dovecot.fi> wrote: > How do you deliver then mails to the server? > > also mbox is very unoptimised mailbox format for this. Each time mail is deleted from mbox mailbox the whole mbox while needs to be rewritten to remove the mail. OpenSMTPD and Dovecot run on the same machine. OpenSMTPD receives incoming mails and

Can anyone help with some pointers to debug a problem with Samba and CTDB with smbstatus traversing the connections tdb? I've got a new two node cluster with Samba and CTDB on AIX. If I run smbstatus when the server has much user activity it hangs and the node it was run on gets banned. I see the following in the ctdb log: 2014/10/29 11:12:45.374580 [3932342]:

Hi, Since the 23rd of March, we encounter mailbox corruption for some users (15 out of 5000) using POP mainly via Thunderbird. Symptoms are : -users can login but fail to receive new mails and fail to read their inbox -Dovecot.log : ar 29 11:00:06 Error: POP3(user_login): Couldn't init INBOX: Mailbox isn't a valid mbox -The mailbox start with either 'FFrom or

With following configuration: userdb static { args = uid=10000 gid=10000 home=/home/vmail/domain.tld/%u/./ mail=maildir:~/maildirs } and accompanying passdb passwd-file consisting of only user and password, for example test:{PLAIN}test: dovecot will access home=/home/vmail/domain.tld/test/home/vmail/domain.tld/test/maildirs instead of home=/home/vmail/domain.tld/test/maildirs dovecot

Hi - I'm trying to verify if OpenSSH/SFTP will in fact lock files with advisory file locking in Linux. I can test locking with the linux "flock" command to verify that file locking does work - but when I upload or download a file with SFTP it will not detect a lock. I'm asking about Linux specifically because about a year ago I was doing a similar process in Solaris 9 and

What syntax is needed to make this work? The 2.0 wiki recomendations don't work - I can see the inboxes or the folders but not both at once and there are lots of error messages about prefix clashes if I simply use the existing 2.0.20 conf file on 2.1.6 The layout I have is: Inboxes in mbox format - /var/spool/mail/%u Folders in maildir format - /var/spool/imap/%u/Maildir/ Control and

part of extensions.conf: exten => 11,1,Answer() exten => 11,n,NoOp(CallerID : ${CALLERID(all)}) exten => 11,n,Playback(/tmp/welkom-tcs.alaw) exten => 11,n,GoToIfTime(09:00-17:59|mon-fri|*|*?open,s,1) ; wordt doorgerouteerd naar context open, maar indien gesloten : exten => 11,n,NoOp(Oproep tijdens winkel gesloten) exten => 11,n,Playback(/tmp/winkel-gesloten.alaw) exten =>

Dear Colleagues, I use exim's appendfile transport, procmail and a local mutt on my system, they all (to my knowledge) use lockfiles when working with mboxes. However, `doveconf | grep lock` says dotlock_use_excl = yes lock_method = fcntl mail_max_lock_timeout = 0 mbox_dotlock_change_timeout = 2 mins mbox_lock_timeout = 5 mins mbox_read_locks = fcntl mbox_write_locks = dotlock fcntl

Hi, I'm writing an application with C under Linux and I'm trying to use the flock system function to lock a file of an NT4 Server over Samba. The problem is that the lock works well within the same machine but if it is a process on another machine (the same program) the one that tries to access the locked file, the process is not blocked until the lock is released but given full access

/etc/postfix/main.cf.default: mailbox_delivery_lock = flock, dotlock Is flock equivalent to dovecot's fnctl locking? For mbox what type of locking settings should I be using? (No NFS, only local filesystem.) Warren Togami warren at togami.com

Running current CVS HEAD I get: dovecot: Dec 01 13:27:38 Info: Dovecot v1.0-test52 starting up dovecot: Dec 01 13:33:34 Info: imap-login: Login: jtl [69.162.177.245] dovecot: Dec 01 13:41:07 Error: IMAP(jtl): UIDVALIDITY changed (1100294646 -> 110192643 5) in mbox file /var/spool/mail/j/t/jtl dovecot: Dec 01 13:41:07 Error: IMAP(jtl): UIDVALIDITY changed (1100294646 -> 110192643 5) in