hmm if message cannot be written to disk surely it remains on mda queue as not delviered and does not just disappear ? or am i reading this wrong ?!> Dag Nygren <mailto:dag at newtech.fi> > 16 August 2017 at 7:14 am > Thanks for all the advice on how to configure systemd > not to loose my emails after every update. Much appreciated. > > But there could be other reasons for the mailboxes not being > writable and what I am really asking for is for > dovecot-lda not to loose the incoming emails into thin air > in these cases. > > Could we have some kind of collective place/places where they would > be saved in this case and then reintroduced into the system > after the problem is fixed? One file for example? > > Best > Dag > Dag Nygren <mailto:dag at newtech.fi> > 14 August 2017 at 4:24 pm > Hi! > > Have been using Fedora as my dovecot server for > some time and am struggling with systemd > at every update. > Fedora insists on setting > ProtectSystem=full in both dovecot.service and postfix.service > at every update of the packages. > > This makes my mailstore which is in /usr/local/var/mail > Read-only. > > And this makes the incoming emails delivered through > dovecot-lda disappear into /dev/null until I notice > the problem and we lose incoming emails. > > My question is: > Is there any way to set up a failback mailstore > for these occasions? > > PS! I really hate systemd - Destroys the UNIX way of > doing things with a heavy axe.... > > > Best > Dag
On Wednesday 16 August 2017 07:56:13 Matt Bryant wrote:> hmm if message cannot be written to disk surely it remains on mda queue > as not delviered and does not just disappear ? or am i reading this > wrong ?!That would be nice. ... I have the delivery chain postfix -> lda-dovecot and when postfix has passed the message to lda it will delete it from the queue. Then when kda-fails it is nowhere to be found any more. Could well be my dovecot or positfix config that is wrong... Best Dag
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 16 Aug 2017, Matt Bryant wrote:> hmm if message cannot be written to disk surely it remains on mda queue > as not delviered and does not just disappear ? or am i reading this > wrong ?!as Matt writes your MDA (aka dovecot-lda) returns with an exit code != 0 and your MTA should queue the message for later re-delivery. IMHO, you should look there, if you call dovecot-lda correctly.>> Dag Nygren <mailto:dag at newtech.fi> >> 16 August 2017 at 7:14 am >> Thanks for all the advice on how to configure systemd >> not to loose my emails after every update. Much appreciated. >> >> But there could be other reasons for the mailboxes not being >> writable and what I am really asking for is for >> dovecot-lda not to loose the incoming emails into thin air >> in these cases. >> >> Could we have some kind of collective place/places where they would >> be saved in this case and then reintroduced into the system >> after the problem is fixed? One file for example? >> >> Best >> Dag >> Dag Nygren <mailto:dag at newtech.fi> >> 14 August 2017 at 4:24 pm >> Hi! >> >> Have been using Fedora as my dovecot server for >> some time and am struggling with systemd >> at every update. >> Fedora insists on setting >> ProtectSystem=full in both dovecot.service and postfix.service >> at every update of the packages. >> >> This makes my mailstore which is in /usr/local/var/mail >> Read-only. >> >> And this makes the incoming emails delivered through >> dovecot-lda disappear into /dev/null until I notice >> the problem and we lose incoming emails. >> >> My question is: >> Is there any way to set up a failback mailstore >> for these occasions? >> >> PS! I really hate systemd - Destroys the UNIX way of >> doing things with a heavy axe.... >> >> >> Best >> Dag >- -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBWZPZYXz1H7kL/d9rAQK/Fwf/TH+njNQhkcnL/Yf8hldhurycZDAmhHH9 VuGrSGpjPFHydEXvYisviWoePyW7SeAYuOo3a5AqAN3ixi+zUhWcL8SUfSEc8P7b QknOwGKyv8zhhi79FJCvE2Ko9j3WqXYZbzTfuz3xWupthl7nEwJWjppZh3Ldz9Xx AkeWp+8qN2I4iBt+rkWZV1mAt9Ae7MGzsy3B/wyeQquJroThzgCGsD3dJEGuo9xB Wk9o8O8VOQhkcpGPFwSPQ39RgbfjRB4RUd19ReeEO4v5iwLQ0EF1eGrz2NAyExN1 dRwx7RYxmnRRGjiBLyP0jYVNY+kWwvuU+/fc/IxPrSW3z/IlhieJ6w==nfFm -----END PGP SIGNATURE-----
On Wednesday 16 August 2017 07:34:25 Steffen Kaiser wrote:> On Wed, 16 Aug 2017, Matt Bryant wrote: > > > hmm if message cannot be written to disk surely it remains on mda queue > > as not delviered and does not just disappear ? or am i reading this > > wrong ?! > > as Matt writes your MDA (aka dovecot-lda) returns with an exit code != 0 > and your MTA should queue the message for later re-delivery. > > IMHO, you should look there, if you call dovecot-lda correctly.You might be perfectly right here and to make it more complicated I forgot to tell you that procmail is also involved. I did debug a bit though and lda-deliver will return the proper return code 75 my .maildelivery files contains the recommended (?) "|IFS=' ' && exec /usr/bin/procmail -f- || exit 75" And the procamail recipe has: | deliver -d $ LOGNAME -m inbox As the action (just one example). But still my postfix thinks the message is properly delivered at a read/write error in the mailstore ??? But this seems to be a postfix configuration problem instead of a dovecot one so sorry for choosing the wrong group. Best Dag