On 2024/5/11 22:51, Jason Hirsh via Postfix-users wrote:
My nonrandom action for tho morning OK I bandaided my going back to an older
main.cf but updating the ssl/tls infoThat brought mail back on line
Sort of
Dovecot still not happy with me but this error seems more warning and best
su
Jason Hirsh via Postfix-users skrev den 2024-05-11 16:51:
status=sent (delivered via dovecot service
(lda(ja...@theoceanwindow.com): Error:
net_connect_unix(/var/run/dovecot/stats-writer) failed: Permis))
grep -r stats /etc/dovecot/
i get an helpfull url from it
/etc/dovecot/conf.d/10-metri
My nonrandom action for tho morning OK I bandaided my going back to an older
main.cf but updating the ssl/tls infoThat brought mail back on line
Sort of
Dovecot still not happy with me but this error seems more warning and best
suited to be addressed else where
status=sent (delivered via d
On Sat, May 11, 2024 at 11:11:30AM +0200, Benny Pedersen via Postfix-users
wrote:
> > I am running Postfix/Dovecot/MySQL mail server. It was doing ok
> > until I tried to improve it., I
>
> maybe just reboot ? :)
Unlikely to help. Just restarting dovecot would be about the most
that's needed
Jason Hirsh via Postfix-users skrev den 2024-05-11 02:47:
I am running Postfix/Dovecot/MySQL mail server. It was doing ok
until I tried to improve it., I
maybe just reboot ? :)
dsn=4.4.1, status=deferred (connect to triggerfish.theoceanwindow.com
[1][private/dovecot-lmtp]: Connection
0:11:27 triggerfish postfix/lmtp[47754]: 172816542AC3:
> to=, orig_to=, relay=none, delay=38307,
> delays=38307/0.01/0/0, dsn=4.4.1, status=deferred (connect to
> triggerfish.theoceanwindow.com[private/dovecot-lmtp]: Connection refused)
The Dovecot LMTP delivery agent is not listening on
I am running Postfix/Dovecot/MySQL mail server. It was doing ok until I tried
to improve it., I
dsn=4.4.1, status=deferred (connect to
triggerfish.theoceanwindow.com[private/dovecot-lmtp]: Connection refused)
May 10 20:11:27 triggerfish postfix/lmtp[47754]: 172816542AC3:
to=, orig_to=, relay
liver mail to dovecot
with LMTP.
Ah, i get it. Viktor wasn't saying don't use the method, it was about the
naming of lmtp vs dovecot-lmtp. Makes sense now, thanks.
> On 5 Jan 2023, at 18:23, post...@ptld.com wrote:
>
>>> unix_listener /var/spool/postfix/private/lmtp {
>>>mode = 0660
>>>user = postfix
>>>group = postfix
>>> }
>> DO NOT do this! That socket is for the listen side of t
unix_listener /var/spool/postfix/private/lmtp {
mode = 0660
user = postfix
group = postfix
}
DO NOT do this! That socket is for the listen side of the qmgr<->lmtp
communication. The Dovecot LMTP socket needs to be outside the
Postfix-private namespace.
Viktor,
C
reated, so I changed the config to use that one.
Now I only have to find out why dovecot doesn't create the
/var/spool/postfix/private/dovecot-lmtp socket
G
Gerben Wierda:
> Jan 05 16:16:59 snape postfix/lmtp[126]: C71B3D1262: to=,
> relay=snape.rna.nl[private/lmtp], delay=300, delays=0.02/0/300/0, dsn=4.4.2,
> status=deferred (conversation with snape.rna.nl[private/lmtp] timed out while
> receiving the initial server greeting)
Postfix creates the
he tcp:
>
> service lmtp {
> inet_listener lmtp {
> address = 127.0.0.1
> port = 24
> }
This is fine.
> unix_listener /var/spool/postfix/private/lmtp {
> mode = 0660
> user = postfix
> group = postfix
> }
DO NOT do this! That socket
I am setting up a new server combination (postfix + dovecot). dovecot's auth
service works for postfix. Just lmtp does not and I need to find out why. I
don't see anything in the dovecot logging, but I see this on the postfix side
(debug)
Jan 05 16:11:59 snape postfix/lmtp[127]: connection esta
Hi everybody,
I have a postfix server that is serving two domains, a main domain
(domainA.org) and a hosted domain (domainB.org), that is using dovecot
for authentication and lmtp. I have set up an openldap to be used as a
backend for the managed identities. Currently, all @domainB.org
addres
nodes on a primary-primary roles Dovecot says at my
> dovecot-lmtp:
>
> "No space left on device", I want to know why if I have 1 terabyte around
> and below 100% of use as I mentioned upstairs lines, when this occurs my
> email production server collapses at all, and all u
says at my
dovecot-lmtp:
"No space left on device", I want to know why if I have 1 terabyte around
and below 100% of use as I mentioned upstairs lines, when this occurs my
email production server collapses at all, and all users notifies that they
can not see their data, tells me that thei
Wietse Venema schrieb am 22.01.20 um 14:50:48 Uhr:
> ratatouille:
> > srw-rw-rw- 1 postfix postfix 0 22. Jan 20:24 lmtp
>
> that is not /var/spool/postfix/private/dovecot-lmtp
The problem was something, I assume webmin, modified
dovecot.conf from protocols = imap lmtp sie
Wietse Venema schrieb am 22.01.20 um 14:50:48 Uhr:
> ratatouille:
> > srw-rw-rw- 1 postfix postfix 0 22. Jan 20:24 lmtp
>
> that is not /var/spool/postfix/private/dovecot-lmtp
/var/spool/postfix/private/dovecot-lmtp is not created and I don't know
why. Just subscribed
ratatouille:
> srw-rw-rw- 1 postfix postfix 0 22. Jan 20:24 lmtp
that is not /var/spool/postfix/private/dovecot-lmtp
Wietse
Wietse Venema schrieb am 22.01.20 um 14:44:42 Uhr:
> > dovecot is running but it does not create doceot-lmtp. It creates lmtp
> > socket.
> >
> > service lmtp {
> > unix_listener /var/spool/postfix/private/dovecot-lmtp {
> > group = postfix
> &
ratatouille schrieb am 22.01.20 um 20:41:25 Uhr:
> dovecot is running but it does not create doceot-lmtp. It creates lmtp socket.
>
> service lmtp {
> unix_listener /var/spool/postfix/private/dovecot-lmtp {
> group = postfix
> mode = 0600
> user = postfix
>
The relevant setting (dovecot 10-master.conf) appears to be correct in
> > the snippet you provide.
>
> dovecot is running but it does not create doceot-lmtp. It creates lmtp socket.
>
> service lmtp {
> unix_listener /var/spool/postfix/private/dovecot-lmtp {
> gro
orrect in
> the snippet you provide.
dovecot is running but it does not create doceot-lmtp. It creates lmtp socket.
service lmtp {
unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0600
user = postfix
}
}
I searched nearly the whole system for lmtp
:
ratatouille:
Hello all!
Since some modifications on my testserver I have the following problem:
connect to smtp.amimanera.de[private/dovecot-lmtp]: No such file or directory
# fgrep -r dovecot-lmtp /etc
/etc/postfix/main.cf:mailbox_transport = lmtp:unix:private/dovecot-lmtp
Is there a
Wietse Venema:
> ratatouille:
> > Hello all!
> >
> > Since some modifications on my testserver I have the following problem:
> > connect to smtp.amimanera.de[private/dovecot-lmtp]: No such file or
> > directory
> >
> > # fgrep -r dovecot-lmtp /e
Wietse Venema schrieb am 22.01.20 um 12:45:07 Uhr:
> ratatouille:
> > Hello all!
> >
> > Since some modifications on my testserver I have the following problem:
> > connect to smtp.amimanera.de[private/dovecot-lmtp]: No such file or
> > directory
> >
&g
ratatouille:
> Hello all!
>
> Since some modifications on my testserver I have the following problem:
> connect to smtp.amimanera.de[private/dovecot-lmtp]: No such file or directory
>
> # fgrep -r dovecot-lmtp /etc
> /etc/postfix/main.cf:mailbox_transport = lmtp:unix:pri
Hello all!
Since some modifications on my testserver I have the following problem:
connect to smtp.amimanera.de[private/dovecot-lmtp]: No such file or directory
# fgrep -r dovecot-lmtp /etc
/etc/postfix/main.cf:mailbox_transport = lmtp:unix:private/dovecot-lmtp
/etc/dovecot/conf.d/10-master.conf
fully delivered to the mailbox as expected but if I send an email
> to the address testus...@example.com, which isn't listed in the map, it
> also gets delivered to the dovecot-lmtp process
Depends on *how* you send it. The unlisted address should
be rejected via SMTP, but would be acce
I have to, i'm authenticating users against samba's ldap using gssapi.
Isn't postfix supposed to stop the mail before handing it to lmtp if
it's own map doesn't include the recipient?
Thanks!
Best regards,
David Wells.
El 26/09/2019 a las 17:08, @lbutlr escribió:
> On Sep 26, 2019, at 1:29 PM,
On Sep 26, 2019, at 1:29 PM, David Wells - Alfavinil S.A.
wrote:
> and as dovecot has the option "allow_all_users=yes”
Simple, don’t do that.
Somewhere in your chain something has to validate the users, otherwise yes,
everything will be accepted because that is what you told the system to do.
Good afternoon.
Dovecot is relaying mails to users that do not exist in the
virtual_mailbox_maps to the dovecot lmtp. I'm using dovecot's lmtp to
deliver mails for a virtual domain. The relevant postfix conf is as follows
> virtual_alias_maps = hash:/etc/postfix/virtual
> virtual
On 2019-08-11 12:39, Coy Hile wrote:
For posterity's sake, this was a misconfiguration in postfix.
virtual_mailbox_domains =
pgsql:/opt/local/etc/postfix/postfix_virtual_domains.cf
Turns out this was an error in that query. I'd missed a term,
so that returned something (which implies "this do
gmail.com
pgsql:/opt/local/etc/postfix/postfix_virtual_domains.cf
> virtual_transport = lmtp:unix:private/dovecot-lmtp
> 2019-08-11T15:38:40+00:00 81716ec5-bca4-6d53-ed81-bd1a55d46b4f
> postfix/lmtp[56821]: [ID 197553 mail.info] 12327F13D: to=,
> relay=81716ec5-bca4-6d53-ed81-bd1a55d46b4f.lo
configured relay host (the IMAP server doesn’t have direct internet
accesss, only the relay box.):
I’ve got postfix setup to use dovecot-lmtp for (virtual) user delivery, and
things to users or aliases that Dovecot knows about now get delivered
correctly. However, I’ve done something wrong with postfix
> On Mar 6, 2019, at 8:40 AM, Marek Kozlowski
> wrote:
>
> I'm using dovecot for IMAP/POP. I've read that since dovecot 2.0 I may use
> dovecot
> as an LMTP and implement desired solution by adding sieve/pigeon classifier to
> dovecot LMTP. It perfectly(?
processing automagically
put it to some `Junk' folder in users' maildirs rather then to `new/'.
I'm using dovecot for IMAP/POP. I've read that since dovecot 2.0 I may
use dovecot as an LMTP and implement desired solution by adding
sieve/pigeon classifier to dovecot LMTP. It pe
Use local
> aliases(5) just for things that expand to "|pipes",
> "/files" and ":include:/paths".
'As much as possible' and when it isn't possible - is there some
solution?
> > - local users or virtual users?
> > (I think best will
> On Feb 6, 2018, at 9:05 AM, Franta Noska
> wrote:
>
> - mailserver will be the target for two domains (old surviving and current
> new)
>
> - users, their aliases and mail groups are in remote LDAP DB with schema
> /objects/values as:
>
> USERS:
> dn: cn=username, ou=rank, o=myorg
> cn: u
se (whether one from something as
local_transport = lmtp:unix:/var/run/dovecot/dovecot-lmtp
virtual_transport = lmtp:unix:/var/run/dovecot/dovecot-lmtp
mailbox_transport = lmtp:unix:/var/run/dovecot/dovecot-lmtp
or something else?
- which maps are needed and how to define them?
- eventually how to
On 4/8/2017 1:59 μμ, Alex JOST wrote:
Dovecot needs to know about the user. What does 'doveadm user -u
imaptes...@noa.gr' print?
Thank you Alex,
I just found the problem. After switching to LMTP, Dovecot receives from
Postfix a fully qualified username, whereas with LDA it was receiving a
'
l2.noa.gr[private/dovecot-lmtp],
delay=0.21, delays=0.17/0.015/0.01/0.015, dsn=5.1.1, status=bounced
(host vmail2.noa.gr[private/dovecot-lmtp] said: 550 5.1.1
User doesn't exist: imaptes...@noa.gr (in reply to
RCPT TO command))
Dovecot needs to know about the user. What does 'dovea
=1 (queue active)
Aug 4 12:19:42 vmail2 postfix/lmtp[3151]: 64EF58EE1BCBE:
to=, relay=vmail2.noa.gr[private/dovecot-lmtp],
delay=0.21, delays=0.17/0.015/0.01/0.015, dsn=5.1.1, status=bounced
(host vmail2.noa.gr[private/dovecot-lmtp] said: 550 5.1.1
User doesn't exist: imaptes...@noa.gr (in rep
an see the socket for lmtp in
/var/spool/postfix/private/.
So according to all the tutorials I've read my assumption is that my next step
is this in postfix' main.cf:
virtual_transport = lmtp:unix:private/dovecot-lmtp
which I did, and postfix restarts with no errors. But, it see
Hi,
this is not a postfix problem. Furthermore it is fully covered in the
dovecot docs.
You need to put the dovecot-lmtp socket into /var/spool/postfix/private.
This means the unix_listener must get the path to that. See here:
http://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP
Also note
Hello list,
I am trying to send a mail message from root to a system user on the same
box. While postfix functions without dovecot properly, once dovecot is
installed, I get the message from logs as set in the subject line - that
postfix/lmpt cannot connect to [private/dovecot-lmtp]: No such file
On Thu, Nov 28, 2013 at 11:52:26AM +1100, craig.post...@noboost.org wrote:
> Just after advice, I'm configuring Postfix to work with a Dovecot LMTP
> for (Sieve delivery). I want to be 100% certain that if Dovecot stuffs
> up in some way, or a user fails to write a correct sieve s
Hi,
Just after advice, I'm configuring Postfix to work with a Dovecot LMTP
for (Sieve delivery). I want to be 100% certain that if Dovecot stuffs
up in some way, or a user fails to write a correct sieve script, that we
won't loose any mail?
Current configuration (works fine)
Spec
> Original Message
>From: mouss
>To: postfix-users@postfix.org
>Sent: Sat, Jul 23, 2011, 5:55 AM
>Subject: Re: dovecot lmtp
>
>Le 20/07/2011 00:03, Kendall Shaw a écrit :
>> On 07/19/2011 01:32 PM, mouss wrote:
>>> Le 19/07/2011 22:00, Kendall Sha
Le 20/07/2011 00:03, Kendall Shaw a écrit :
> On 07/19/2011 01:32 PM, mouss wrote:
>> Le 19/07/2011 22:00, Kendall Shaw a écrit :
>>
>> Your setup is ok, but your test is not...
>>
>> you have defined virtual_transport to be dovecot, but this only applies
>> to virtual_mailbox_domains.
>>
>> you di
On Tue, Jul 19, 2011 at 03:03:38PM -0700, Kendall Shaw wrote:
> Okay, but I am not sending mail to @localhost. I send to
> ks...@kendallshaw.com. Fetchmail sends RCPT TO:. There
> is the header To: ks...@kendallshaw.com in the message. Does postfix decide
> on the destination based on the To he
On 07/19/2011 01:32 PM, mouss wrote:
Le 19/07/2011 22:00, Kendall Shaw a écrit :
Your setup is ok, but your test is not...
you have defined virtual_transport to be dovecot, but this only applies
to virtual_mailbox_domains.
you didn't explicitely specify mydestination, so the default applies:
$
On Tue, Jul 19, 2011 at 01:00:50PM -0700, Kendall Shaw wrote:
> RCPT TO:
>
> In the log, messages about delivery for that message look like:
>
> ... postfix/qmgr[9145]: 41B0F692043: from=,
> size=2763, nrcpt=1 (queue active)
>
> ... postfix/local[7649]: 41B0F692043:
> to=, orig_to=,
>
s/madeup-cert.pem
> smtpd_tls_key_file = /etc/openssl/private/madeup-key.pem
> smtpd_tls_received_header = yes
> smtpd_tls_security_level = may
> smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
> tls_random_source = dev:/dev/urandom
> unkno
= may
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
tls_random_source = dev:/dev/urandom
unknown_local_recipient_reject_code = 550
virtual_mailbox_domains = kendallshaw.com
virtual_transport = lmtp:unix:private/dovecot-lmtp
Socket:
srw-rw 1 postfix postfix 0 Jul 19 07
56 matches
Mail list logo
