Yep, yep, yep, consider this solved. I believe I understand the issues
involved, now.
Many thanks for your help!
John Clements
On Tue, Nov 3, 2015 at 12:44 PM, Larry Rosenman wrote:
> Nov 3 12:23:05 desmond dovecot: lda(granitemon): Debug: Effective
> uid=1003, gid=1003, home
em can
mess up any other's mbox.
So, it looks like even if this bug is fixed, I'm left with two obvious
choices:
- make /var/mail writeable by all users that receive mail, or
- use LMTP instead.
Many thanks for your help,
John Clements
On Tue, Nov 3, 2015 at 12:13 PM, Larry Rosenm
clements@desmond:/var/log$ ls -lda /var/mail
drwxrwsr-x 2 root mail 4096 Nov 2 22:07 /var/mail
Best,
John Clements
On Tue, Nov 3, 2015 at 11:52 AM, Larry Rosenman wrote:
> what is the full permissions of /var/mail?
>
>
> ls -lda /var/mail
>
> On Tue, Nov 3, 2015 at 1:49
't appear to be confined to debian jessie: I took a
look at my existing installation, and I see that in fact I just went ahead
and made /var/mail world-writeable, which seems... sub-optimal. I'm sure I
could do that here, too, but I'd certainly rather not.
Thanks in advance, and let me know if I've left out relevant crucial
information.
Best,
John Clements
On Aug 26, 2011, at 10:30 PM, mail...@securitylabs.it wrote:
> Il 26/08/2011 20:38, John Clements ha scritto:
>> Dovecot is crashing occasionally for me. Today it crashed six times in
>> quick succession, as I fired up a computer (Mac) I hadn't used in a while,
>&g
No symbol table info available.
(gdb) q
Does anyone have any suggestions, here?
Many thanks in advance; let me know if I can provide more information!
All the best,
John Clements
smime.p7s
Description: S/MIME cryptographic signature
ch.groups.yahoo.com/group/postfix-users/message/274981
>
>
> OK. I tried all. It just doesn't works. virtual_transport = dovecot
> (or maildrop) return relay=none. Now I want work out how I can add a
> relay into chain, I think that is the base of this issue.
I'm certain that others on the list are better at reading between the lines
than I am, but you really need to be more explicit about what's happening;
provide a sequence of operations, the resulting behavior, and the behavior you
expect.
Apologies in advance if this message comes across as rude, or if I've missed
something obvious.
All the best,
John Clements
smime.p7s
Description: S/MIME cryptographic signature
