similar to: Dovecot - PowerMTA

Displaying 20 results from an estimated 10000 matches similar to: "Dovecot - PowerMTA"

2013 Mar 18
4
Dovecot - Sieve script loaded but filtering doesn't works ?
Hello, I'm trying to install dovecot as LDA, IMAP server and Sieve functions, all of this with a Postfix, Spamassassin and a MySQL Auth. When I use a Sieve script, it 's loaded but actions are not respect with this logs : Mar 18 10:31:19 localhost dovecot: lda(info at info.xx.com): Debug: sieve: using sieve path for user's script: /vmail/sieve/info.xx.com/info.sieve Mar 18
2018 Mar 06
0
Mail addresses with quotes + Postfix
Op 6-3-2018 om 14:34 schreef Philipp Berger: > I upgraded to Dovecot 2.3.0.1 as advised, but it still seems broken. In > the Postfix log I now see: > > Mar? 6 13:49:03 myhost amavis[7165]: (07165-10) K00VtLRHdrYw FWD from > <admin at mydomain.tld> -> <"@"@mydomain.tld>, BODY=7BIT 250 2.0.0 from > MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as
2018 Mar 07
0
Mail addresses with quotes + Postfix
Op 7-3-2018 om 13:46 schreef Philipp Berger: > I wrapped the LDA command in a script. I can see that Postfix passes > "@@mydomain.tld" as the -d argument, without quotes. > I then adapted the script to specifically replace this address with > "@"@mydomain.tld, but this results in the following error message by > Dovecot: > > ??? auth: Info: userdb(?):
2018 Mar 06
2
Mail addresses with quotes + Postfix
I upgraded to Dovecot 2.3.0.1 as advised, but it still seems broken. In the Postfix log I now see: Mar? 6 13:49:03 myhost amavis[7165]: (07165-10) K00VtLRHdrYw FWD from <admin at mydomain.tld> -> <"@"@mydomain.tld>, BODY=7BIT 250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as B8CA22DA1B37 Mar? 6 13:49:03 myhost amavis[7165]: (07165-10) Passed CLEAN
2018 Mar 07
0
Mail addresses with quotes + Postfix
Interesting, the documentation and the build-in help of dovecot-lda do not mention -r exists :) case 'r': /* final recipient address */ if (smtp_address_parse_path(ctx.pool, optarg, SMTP_ADDRESS_PARSE_FLAG_ALLOW_LOCALPART | SMTP_ADDRESS_PARSE_FLAG_BRACKETS_OPTIONAL, &final_rcpt_to, &errstr) < 0) { i_fatal_status(EX_USAGE, "Invalid -a parameter: %s",
2018 Mar 07
3
Mail addresses with quotes + Postfix
I wrapped the LDA command in a script. I can see that Postfix passes "@@mydomain.tld" as the -d argument, without quotes. I then adapted the script to specifically replace this address with "@"@mydomain.tld, but this results in the following error message by Dovecot: ??? auth: Info: userdb(?): Username character disallowed by auth_username_chars: 0x22 (username:
2018 Mar 07
2
Mail addresses with quotes + Postfix
Op 7-3-2018 om 15:40 schreef Stephan Bosch: > > > Op 7-3-2018 om 13:46 schreef Philipp Berger: >> I wrapped the LDA command in a script. I can see that Postfix passes >> "@@mydomain.tld" as the -d argument, without quotes. >> I then adapted the script to specifically replace this address with >> "@"@mydomain.tld, but this results in the
2007 Jan 30
1
Need help with "mbox sync" problem
The following is occurring consistently on users in only one vhost domain. Other vhost domains are not having the problem. The email client in use is the same (in both the working and non-working domains). dovecot: Jan 29 21:19:18 Error: POP3(user1 at mydomain.tld): mbox sync: UID inserted in the middle of mailbox /var/mail/vhosts/mydomain.tld/user1 (5629 > 5423, seq=2, idx_msgs=5) dovecot:
2019 Mar 10
0
readonly archive folders using squashfs
For every user at domain.tld I created a user at backup.domain.tld where he could look up deleted messages (archive). I then made user at backup.domain.tld's cur directory a shared directory to user at domain.tld but only with read privileges. So, anytime the user wants to read his old messages, he only needs to read his .archive folder, which is user at backup.domain.tld's cur. No
2013 Aug 29
0
Issues with dovecot-antipsam plugin
Hello list, I have a postfix 2.11 with dovecot 2.2.5 instance. I have configured and installed anavisd-new to use Spamassassin. I want to train the filter. For that i choose dovecot's antispam plugin using mailtrain backend. I compiled and installed the latest version of the antispam plugin from http://hg.dovecot.org/dovecot-antispam-plugin/rev/5ebc6aae4d7c The configuration is below.
2016 Oct 19
0
sieve sending vacation message from vmail@ns1.domain.tld
/var/log/maillog showed this Oct 19 13:25:41 ns1 postfix/smtpd[1298]: 7599A2C19C6: client=unknown[127.0.0.1] Oct 19 13:25:41 ns1 postfix/cleanup[1085]: 7599A2C19C6: message-id=<edc55a9b-eb49-3945-dc60-0e1d51a78e97 at nbmlaw.co.uk> Oct 19 13:25:41 ns1 postfix/qmgr[1059]: 7599A2C19C6: from=<matthew.broadhead at nbmlaw.co.uk>, size=3190, nrcpt=1 (queue active) Oct 19 13:25:41 ns1
2014 Oct 03
1
X-sieve-redirected-from
Hi, I am chasing a problem with sieve vacation messages. the sieve file looks like this: ## Generated by Roundcube Webmail SieveRules Plugin ## require ["copy","vacation"]; # rule:[computerisms.ca] if anyof (address :contains "To" "bob.miller at ctfn.ca", address :contains "Cc" "bob.miller at ctfn.ca") { redirect :copy "bob at
2006 Jan 24
2
Dovecot don't recognise new messages in maildir /new
Hi, i'm google for it and i searched the archives, but i can't find the problem i have or a hint for a solution. I'm using Postfix as MTA, the new messages deliver by postfix to the maildir: /mail/domain.tld/userpart/new/ Dovecot sometimes show the new mails directly (it's very unusual) but mostly it needs for an hour that dovecot recognize the new messages. Reconnecting of the
2016 Oct 20
0
sieve sending vacation message from vmail@ns1.domain.tld
Op 10/20/2016 om 7:38 PM schreef Matthew Broadhead: > do i need to provide more information? > It still doesn't make sense to me. I do notice that the version you're using is ancient (dated 26-09-2013), which may well the problem. Do have the ability to upgrade? Regards, Stephan. > On 19/10/2016 14:49, Matthew Broadhead wrote: >> /var/log/maillog showed this >>
2009 Jan 21
2
Bug or other issue? Jan 22 00:02:09 argon postfix/pipe[21251]: E8126A3671: to=<mbj@seonic.net>, orig_to=<root>, relay=dovecot, delay=0.38, delays=0.03/0/0/0.35, dsn=5.3.0, status=bounced (Command died with signal 6: "/usr/libexec/dovecot/deliver")
Hi, I found the following in my logfiles: The failure is not reproducable at the moment. System is delivering mails to mailboxes with no problems at all. It is a production installation with medium load. dovecot --version: 1.1.7 OS: Linux (Gentoo/x86 stable) - grsec enabled kernel deliver.log: deliver(user at example.tld): Panic: file istream-tee.c: line 144 (i_stream_tee_read): assertion
2016 Oct 25
0
sieve sending vacation message from vmail@ns1.domain.tld
are there any instructions or tests i can make to check the sieve configuration? or does the magic all happen internally and there are no settings to change? On 21/10/2016 10:22, Matthew Broadhead wrote: > the server is using CentOS 7 and that is the package that comes > through yum. everything is up to date. i am hesitant to install a > new package manually as that could cause
2016 Nov 06
0
sieve sending vacation message from vmail@ns1.domain.tld
it seemed like a simple configuration issue. i was hoping someone could point me in the right direction. seems i was wrong. i may as well unsubscribe this list as there is not much help here On 02/11/2016 18:29, Matthew Broadhead wrote: > is there something more i need to be doing my end? > > On 25/10/2016 09:11, Matthew Broadhead wrote: >> are there any instructions or tests
2018 May 06
1
2.3.1 Replication is throwing scary errors
Hi all, New to the mailing lists but have joined up because of above */2.3.1 Replication is throwing scary errors /*Brief system configuration ??? MX1 - Main ??? ??? Freebsd 11.1-Release-p9 ??? ??? Hosted on a Vultr VM in Sydney AU ??? ??? MTA = Postfix 3.4-20180401 ??? ??? Dovecot = 2.3.1 ??? ??? File system = ufs ??? MX2 - Backup ??? ??? Freebsd 11.1-Release-p9 ??? ???? Running on
2016 Oct 20
2
sieve sending vacation message from vmail@ns1.domain.tld
do i need to provide more information? On 19/10/2016 14:49, Matthew Broadhead wrote: > /var/log/maillog showed this > Oct 19 13:25:41 ns1 postfix/smtpd[1298]: 7599A2C19C6: > client=unknown[127.0.0.1] > Oct 19 13:25:41 ns1 postfix/cleanup[1085]: 7599A2C19C6: > message-id=<edc55a9b-eb49-3945-dc60-0e1d51a78e97 at nbmlaw.co.uk> > Oct 19 13:25:41 ns1 postfix/qmgr[1059]:
2018 May 06
0
2.3.1 Replication is throwing scary errors
Seems you got the hash wrong... You probably mean 4a1e2e8e85ad5d4ab43496a5f3cd6b7ff6ac5955, which fixes a memory leak, but does not release sync lock. Interesting if this commit fixes the issue. Looking at the sync code, where the lock is made / released, there is only one commit recently, which is 8077d714e11388a294f1583e706152396972acce and that one creates home directory if missing. Would