similar to: dovecot & OCFS2 Cluster

Hi Timo, Are there any plans to support the SIZE option in the lmtp server? Paul

Hello, recently I inspected the sourcecode of the lmtp server. I searched for changes that would add return-path header. ( http://www.dovecot.org/list/dovecot/2010-February/046401.html ) But I found, that all mails are spooled via files in /tmp. ( dovecot2/srv/lmtp/commands.c ~line 695 ) has somebody experiences while delivering huge ammount of mail via dovecot2 lmtp service? - is it

There is a bug in ocfs2 1.4 if you are using it you should be looking for upgrading to ocfs2 1.6 I have several performance problens with ocfs2 but now i guess the problem is the webmail client that we are using. I have several post here about it. I will write a new one as soon as i found the solution. Anyway, why use lmtp over lda ? My setup have about 5000 active acounts all in maildir.

On Jan 13, 2015, at 8:30 PM, Reindl Harald <h.reindl at thelounge.net> wrote: > > so what you want in your OP is just DISCARD in a sieve script and there is no point in "Using Dovecot LMTP it would be more optimal to kick a 5xx back" when the desired result is DISCARD > > why do you want the burden of keep the SMTP session with the client open until the mail is

St?phane Cottin writes: > dspam already send errors to syslog, the point here is to never loose > email contents. This was a wrong design, i'm now use a wrapper instead > ( see my previous post for details ). You're stilling going to lose contents. If dspam fails, the mail is dumped, the LDA returns exit code 75, and the MTA will probably issue a bounce Email to the sender.

Dave McGuire writes: >> http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/AllowNets >> >> then setup fail2ban to manage extrafields > > Now that's a very interesting idea, thank you! I will investigate this. If you don't expect yor firewall to handle 45K+ IPs, I'm not how you expect dovecot will handle a comma separated string with 45K+ entries any

Hi Folks, I have a couple of questions which I hope that you will be able to assist with, first some background. I run a few sendmail servers that run MailScanner/Spamassassin/sendmail (current versions) on Centos 5.4 and Centos 4.8 These boxes accept mail for a large number of domains (6000+) scan the mail removing spam and then forward the ham to another server for delivery. I am attempting to

A summary of answers I got to the questiosn I posed. > Is there a reason I should prefer LMTP over LDA for local delivery? Thanks for the responses I received. The benefits reported were more/better information logging, and service isolation. Also, one significant advantage not mentioned for LMTP was that one delivery failure to multiple recipients can be disambiguated; LDA can only return

Am 12.06.2020 um 02:03 schrieb Ralph Seichter: > * Andreas Born: > >> There exists one problem: at this stage of mail reception you have no >> body content nor header information on which a milter may perform >> deeper analysis, only envelope data. > > I am not sure what you mean by "this stage of mail reception", or what I meant the different stages when

I'm trying to setup per user '+spam' delivery from amavis tags, so that each user gets any mails tagged as spam to 'spam' Maildir via +spam Dovecot lmtp delivery. after say 7 days I want to delete all spams older than 7 days, if I simply delete mail files from the file system, is that a 'bad thing' ? what is a proper way to do that, and scripts ? for

"Scott W. Sander" writes: > I have noticed that the name of my private server running dovecot appears > in email headers rather than the public-friendly name of my server. Which headers are you taking about? If you're talking about Received: headers, that's usually inserted by your MTA, not dovecot. Joseph Tam <jtam.home at gmail.com>

Am 26.01.2015 um 08:52 schrieb Steffen Kaiser: > On Sun, 25 Jan 2015, Joseph Tam wrote: >> St?phane Cottin writes: > >>> dspam already send errors to syslog, the point here is to never loose >>> email contents. This was a wrong design, i'm now use a wrapper instead >>> ( see my previous post for details ). > >> You're stilling going to lose

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: ---

Hi, I'm running dovecot 1.2.11 on Centos and have the expire plugin enabled. I've had this in place for some time but until now never actually ran the expire-tool. I'm now trying to put this to use. The expire plugin as such is working fine and also the tool is working fine - up to a point. When I run it with --test it goes through a bunch of boxes and lists the messages it

Hi, like I have written in the subject line I want to limit the pop login per user and per minute. Currently I am having several customers which are fetching their email with popcon (MS Exchange). This has never been a problem. But... They all have got the same "technician" which take care of their systems. The problem is, that he misconfigured the servers of these customers. In

Hi there, I'm using Dovecot together with Postfix; as I understand it, there are two ways to transfer the mail from Postfix to Dovecot. 1.) by using LDA with mailbox_command = /usr/libexec/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT" 2.) by using LMTP with mailbox_transport = lmtp:unix:private/dovecot-lmtp (currently using number 1) I'm interessted in the

On Thu, 10 Aug 2017, Larry Rosenman wrote: > Which mail client on iOS? Sorry, maybe not iOS, but definitely MacOSX Mail app. Joseph Tam <jtam.home at gmail.com>

We uograded our dovecot from version 2.1.10 -> 2.10.12, but within the first hour of use, dovecot-lda would segfault during delivery. This left a lock file lying around causing the user's mail readers to hang; much hilarity ensues. All further deliveries to the same user will result in a crash. The only thing that fixes this condition is to blow away the user's INBOX cache index.

I'm using Dovecot LDA with Exim. I'm also using Dictionary Quotas in a MySQL database. I want to avoid backscatter completely, so I set "quota_full_tempfail = yes" and handle quota checking in the Exim RCPT ACL during the SMTP session. The problem lies in the case where a user's account is nearly full. Smaller messages will continue to come through, but a larger message

Hi Aki, Am 21.02.19 um 12:55 schrieb Aki Tuomi: > > On 21.2.2019 13.47, Lionel Elie Mamane via dovecot wrote: >> I noticed a mail stuck in my mail queue. dovecot-lda was returning >> error 64 Invalid parameter given. (EX_USAGE). >> >> Weird, weird, weird. After some sleuthing, I found the sender address >> was FirstLast at domain.tld, with a UTF8-encoded