search for: ldas

Hi I use rsync as a client to copy a directory structure from a remote server, once every month. Until a few weeks ago, we had direct access to the internet - and the way it would work is that the guy maintaining the rsync server would add my machine's IP to an access list and I would run the rsync command from my machine. Recently however, our network was 'upgraded' to a NAT

...help(); i_fatal_status(EX_USAGE, While this fixed my SEGFAULT, it still leaves the "From_" line with the default "dovecot.deliver" as the return path, something I don't want. It should be "MAILER-DAEMON" or some-such just like all the other LDAs in the case of a NULL return path. Perhaps there needs to be a new parameter so one can specify what a NULL return path should be converted to when it is encountered... Also, note that the "Usage" message in deliver.c does not include the relatively new -f option either, so that should...

...nd either learns as spam and deletes or learns as ham and moves back to the user's inbox. My questions now are these: 1.) Is there any danger regarding maildir consistency in directly moving mail items about? 2.) Could I somehow use deliver to move the mails? I think I can recall that other LDAs (maildrop?) allow for that? This would of course be preferred as the maildir cache would also still be optimized after the operation. If anyone has any suggestions, I'd really appreciate this. Thanks a lot for your help and this great tool! Martin -- "The nice thing about being a celeb...

...email. It should complain about an invalid envelope sender if (and only if) it needs to send a bounce (and thus will send that to MAILER-DAEMON instead). But it must in no case refuse to deliver the email to a perfectly valid local recipient. Yes, the envelope sender is flawed. But that is not the LDAs concern. If the SMTPD was happy enough, the email has been accepted and must not lead to a late bounce. In the case we're currently seeing this leads to backscatter spam. I think the right logic would be to not smtp_address_parse_path the enveloper sender unless it is needed for legitimate bou...

Hi, Our legacy data store retains a single copy of a message regardless of the number of mailboxes in which that message resides. It does this by creating hard links to that message in the mailboxes containing that message. Thus, when we perform data migration to the server target (Dovecot), the copies of the same message are copied over with the migration process (imapsync). We use the storage

Hi.. after upating from 2.0.1 to 2.0.4 postfix often reports errors when deliveing mails to dovecot: "Undelivered Mail Returned to Sender" -> Command died with signal 11: "/usr/libexec/dovecot/dovecot-lda" anyone seens this before ?

...mailboxes. But in the production phase with Dovecot v2 you will face some culprit: with LMTP all messages are different now, because of the user-related Delivered-To and final Recieved header. With deliver this does not happen, but your MTA possibly adds different headers then, because usually LDAs are called per recipient. Dovecot deliver has the "-p" option to optionally hard link to file message file to the argument of -p. But then you must use some scripting to have your MTA call that script for all final recipients. You should also check, if Sieve is compatible with -p, be...

http://dovecot.org/test/ One more for today :) Again mostly mbox fixes and optimizations. Don't try it with maildir because it crashes with COPY and APPEND commands. This release supports now UIDPLUS extension. It was mostly a side effect of making saving mails store the X-UID header immediately to mbox and adding the mail to index. So, a Dovecot LDA would finally make sense now. Besides

Here is sample filename from Maildir: 1243423383.M745917P32169.termserv1,W=1295:2,Sa 1) why there is no S=<size> field? It definetely differs from 1295.I've not quota plugin, could it be the reason of this? 2) what does "a" flag mean? I not found any description of this neither in Maildir spec nor on the Dovecot wiki.

I am using postfix + dovecot 2.0.6 + mailman And others 2 serves with only postfix and dovecot writing at same storage with OCFS2. We are having problens with IOwait, and still trying to figure out why that is happen! But, problem becomes much worse when some emails are used in mailman, when it happens all 3 serves became really slow. iowait goes to 80. Does anyone have an idea how to slow

...hing about the error above, except a bug in v2.2.2 and a google groups thread where users are just blaming each others for nothing .. I want to use a dovecot lda/lmtp because the quota settings for trash-folders are very nice and reducing my support times but im stuck at getting one of the dovecot-LDAs to work. Let me know if you need any additional information. Any help is greatly appreciated! -- Viele Gr??e / Best regards Patrick

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 Unicode U+FEFF ZERO WIDTH NO-BREAK SPACE character (AKA byte order mark) between "First" and "Last" :) Since that is passed as the -f parameter to

"Jorge Bastos" <mysql.jorge at decimal.pt> writes: > I?d like to achieve something that i don?t know if it?s possible. It's almost always possible; it really depends on how much work you want to do. > I have account info at domain.tld and when an email is received, I want to > forward it to several accounts, always in this order: > > ? Email1 at domain.tlf

Hello all! Some month ago I upgraded our dovecot installation from version 1.0.5 to version 2.1.7 without having any trouble. Postfix is delivering email directly per virtual transport to the maildirs and mailboxes of the users in /var/spool/vhosts/domains/.... Now I want to use dovecot-lda and created a new entry in the master.cf of postfix. dovecot unix - n n - -

Hi Centos Team, It seems this is partially resolved. The issue now is that rh-git29-runtime cannot be found by yum but the package itself is in the repo directory: http://mirrors.usc.edu/pub/linux/distributions/centos/7/sclo/x86_64/rh/rh-git29/rh-git29-runtime-2.3-4.el7.x86_64.rpm [root at ldas-pcdev4 ~]# yum install rh-git29-git Loaded plugins: auto-update-debuginfo, langpacks, priorities 555 packages excluded due to repository priority protections Resolving Dependencies --> Running transaction check ---> Package rh-git29-git.x86_64 0:2.9.3-2.el7 will be installed --> Processing...

Hi I noticed in a post that Timo might start work on a LDA Great! If so, here is something I would really like included. Support for PAM There is quite a lengthy reason behind this. In my organisation, user accounts are created on ldap. It is up to the services to create home directories whenever the user first uses them. For instance, Samba will do this the first time they connect to their

Hi Here is my environment: Red Hat Enterprise Linux Server release 5.7 (Tikanga) postfix-2.9.1-1.rhel5 dovecot 1.0.7 I want to config a complete postfix-dovecot mail server. First I configured postfix to use procmail, its default LDA and dovecot for pop3 and imap. I didn't changed main.cf a lot, just myhostname and a few other properties. I didn't set home_mailbox. About dovecot.conf

My Dovecot 2.2.16 server is interacting poorly with a variety of mail clients. The symptoms include disappearing messages, mismatched summaries, duplicated messages, and excessive full re-downloads. Dovecot 2.2.16 on FreeBSD 10.1-release r280247M ZFS is interacting suboptimally with various email clients. Output of "dovecot -n" further down. *Client Artifacts* Thunderbird 31.6