Displaying 20 results from an estimated 1000 matches similar to: "submission_host problem"
2011 Nov 13
1
Chroot
Hello,
I have successfully setup dovecot with chroot but there are two things yet
1. submission_host problem (I posted message 2 days ago)
2. Problem with acl's and sharing:
all maildirs are located in: /var/mail/jdoe at example.com/Maildir
so:
mail_chroot=/var/mail
I setup acls with:
10-mail.conf
...
namespace {
type = private
separator = /
prefix =.
inbox = yes
hidden = no
2014 Jul 02
1
Shared folders not listed by IMAP
Hello
I just upgraded my system and there is a problem with shared mailboxes.
When I use the doveadm command I can see shared folders:
doveadm mailbox list -u 'test at mydomain.pl'
Drafts
Sent
Spam
Trash
Shared
Virtuals
Virtuals/all
Shared/test2 at mydomain.pl
Shared/test2 at mydomain.pl/Sent
INBOX
But I can't see them over IMAP protocol.
Some config opts:
valid_chroot_dirs =
2018 Nov 15
2
Sieve notify variables not working with body?
Hi,
I want to send notification like this:
if body :text :matches "*" {
notify :importance "3"
:message "[NOTIFY] ${1}"
"mailto:test at example,com";
}
The notification works but the variable ${1} seems to be empty.
But in this case:
if header :matches "Subject" "*" {
notify
2018 Nov 16
1
Sieve notify variables not working with body?
Thanks, now it works.
But it seems that :message string (of notify command) is limited to 255
chars.
Is there any chance to change limit to 512 ?
require ["body","enotify","variables","foreverypart","mime","extracttext"];
foreverypart
{
if header :mime :type :is "Content-Type" "text"
{
extracttext
2013 Oct 02
1
LDAP for passdb and SQL for userdb
Hello
Is it possible to setup double backend ? ldap for auth only and SQL for
userdb information(quota,maildir etc) ?
Now I'm using SQL backend and configuration looks like this:
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql.conf
}
userdb {
driver = prefetch
}
userdb {
driver = sql
args = /etc/dovecot/dovecot-sql.conf
}
Can I do something like:
passdb {
driver = sql
args
2010 Jun 18
2
New mailbox & autocreate
Hi,
First of all BIG THANKS for great piece of software.
I have a small problem with autocreate. My mails are stored in:
/var/mail
Ex.
/var/mail/test at test.pl/Maildir
Account information comes from DB. So when new account appears in DB
full path including home dir is created. But there is one small
problem:
Group always is "wheel". Autocreating ignores gid from DB and uses the
group
2023 Jan 17
1
submission_host auth
When using dovecot container with sieve plugin there is no sendmail to use for sending email for sieve redirect action for example. We can use submission_host instead https://doc.dovecot.org/settings/core/#core_setting-submission_host but there is no way to specify credentials for auth in remote MTA. Submission_relay_* settings e.g. submission_relay_master_user relate to dovecot submission
2023 Jan 17
1
submission_host auth
> When using dovecot container with sieve plugin there is no sendmail to use for sending email for sieve redirect action for example. We can use submission_host instead https://doc.dovecot.org/settings/core/#core_setting-submission_host but there is no way to specify credentials for auth in remote MTA. Submission_relay_* settings e.g. submission_relay_master_user relate to dovecot submission
2011 Mar 21
1
2.0.11 segfault while can't access submission_host
15-lda.conf:
submission_host = 192.168.m.n:587
2011-03-21T14:43:49+01:00 prac/p-prac dovecot: [ID 583609 mail.debug]
lmtp(12354, user at us.edu.pl): Debug: mcQ1NitVh01CMAAAuqlTtQ: sieve:
executing script from /mails/sieve/user at us.edu.pl.svbin
2011-03-21T14:43:49+01:00 prac/p-prac dovecot: [ID 583609 mail.error]
lmtp(12354, user at us.edu.pl): Error: smtp(192.168.m.n:587): RCPT TO
failed:
2023 Jan 17
1
submission_host auth
Thanks for the reply, postfix + dovecot sasl configured and working properly. My question is about "adding dovecot authentication when sending emails via submission_host".
Let's say we have dovecot + sieve plugin container.
Dovecot configured to use remote SMTP submission host to send messages:
submission_host = postfix.example.com:587
User foo at example.com has the following
2023 Jan 17
1
submission_host auth
> Let's say we have dovecot + sieve plugin container.
> Dovecot configured to use remote SMTP submission host to send messages:
> submission_host = postfix.example.com:587
I reviewed my config to see how i did it. I think you are right and SASL isn't used here. I have dovecot and postfix on the same machine and in dovecot i set
submission_host = localhost:25
Then in my
2012 Nov 09
1
Sieve puts incoming message into inbox on any problem with submission_host
Hello dovecot-users,
I have a question/suggestion regarding the submission_host feature of
the lda (either via dovecot-lda binary or lmtp) in combination with sieve.
When trying to deliver message to a mailbox and this message has a sieve
redirect action applied to it, dovecot is using the configured smtp
server to forward the message just fine. Unfortunately, if the server
configured for
2006 Apr 05
2
What causes deadlock?
Hi
What causes deadlock?
Apr 5 14:02:43 WARNING[2413] channel.c: Avoided initial deadlock for
'0x82acb10', 10 retries!
Apr 5 14:02:43 WARNING[2413] channel.c: Avoided initial deadlock for
'0x8298160', 10 retries!
Here is the portion of the log:
Apr 5 14:02:42 NOTICE[23363] chan_zap.c: Got event 18 (Ring Begin)...
Apr 5 14:02:42 VERBOSE[23363] logger.c: -- Executing
2015 Aug 15
4
[syslinux:master] efi/pxe: Reuse handle
On Fri, Aug 14, 2015 at 11:42 AM, Patrick Masotta via Syslinux
<syslinux at zytor.com> wrote:
>>>>>
> website (meaning, HP could test their firmware to be compatible with
> Syslinux and with non-Windows OSes). If the HP firmware could be made
> (more) compliant with UEFI specs, or if it could be improved and still
> be compliant with UEFI specs, wouldn't
2020 Oct 09
2
Providers running dovecot?
On Fri, Oct 09, 2020 at 10:15:10AM +0200, Olivier Cailloux wrote:
> The real, ?final? question I am interested in is, but which might be
> slightly off-topic on this list (the reason I asked the other
> question), is to find providers that satisfy these two conditions:
> a) offer free e-mail accounts
> b) implement correctly the IMAP SEARCH feature of RFC 3501.
IMO this is the
2004 Nov 22
1
Fedora Core 3 and Samba
Over the last week I've upgraded one of my samba servers to FC3. I ran into
some problems joining XP machines to the domain. Tracing back the problem
I've found that FC3 has changed the behavior of the useradd/adduser script.
It will no longer allow a UNIX account to be added to the system that has a
'$' in it. I've verified this behavior by trying it at the command line,
2018 Nov 16
0
Sieve notify variables not working with body?
Op 15-11-2018 om 23:54 schreef Bambero:
> Hi,
>
> I want to send notification like this:
>
> if body :text :matches "*" {
> ?????????? notify :importance "3"
> ?????????????? :message "[NOTIFY] ${1}"
> ?????????????? "mailto:test at example <mailto:test at example>,com";
> }
>
> The notification works but the variable
2018 Feb 12
2
User manipulation of tty mode opcodes / IUTF8 incompatibilities
Hey all,
The IUTF8 tty mode support added to the client in 7.3 unfortunately
appears to have broken interop with a handful of noncompliant server
implementations that immediately close the connection when they are
sent an opcode that they know nothing about, rather than ignore it.
Setting the value to 0 is not enough: its mere presence regardless of
value is enough to cause the server to bomb
2011 Feb 09
1
Dovecot + Solr does not index without break-imap-search?
Hi folks,
We are working with Dovecot 2.0.9 with Solr support and there is a
thing, a little strange for us. Let me explain.
We have this conf for Solr:
plugin {
...
fts = solr
fts_solr = url=http:// solr.domain:8983/solr/ break-imap-search
quota = maildir
...
}
With 'break-imap-search', Dovecot connects with solr, solr indexes all,
searchs are
2015 Aug 14
2
[syslinux:master] efi/pxe: Reuse handle
>
> Today there are certain PCs i.e Elitebook 2560p, Elitebook 8460p that with
> updated FW ""to the last known version"" cannot PXE boot syslinux for the
> above mentioned reasons.
>
> We have already talked about this with Gene an there's an strategy for making
> syslinux able to deal with these "weirdo" FWs.
> It's just a matter