public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Shields <laebshade@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: Re: [gentoo-user] Re: Messed up mail access rights
Date: Fri, 30 Sep 2005 16:26:59 -0400	[thread overview]
Message-ID: <642958cc0509301326p453a030bh53b10d277d460a8a@mail.gmail.com> (raw)
In-Reply-To: <F49BE7328A1DA246AFC5C2CDDB86D917DFB00F@BCV0X134EXC0005>

[-- Attachment #1: Type: text/plain, Size: 2392 bytes --]

Meh, you could always chmod -R 770 * from the top dir of the maildir and see
what happens (since the "Mail" dir is 770, it's quite possible all the other
dirs should have same permissions). If that screws it up even more or
doesn't work, you can always restore your backup again.

On 9/27/05, Michael Kintzios <michaelkintzios@lycos.co.uk> wrote:
>
>
>
> > -----Original Message-----
> > From: Michael Kintzios [mailto:michaelkintzios@lycos.co.uk]
> > Sent: 26 September 2005 21:50
> > To: gentoo-user@lists.gentoo.org
> > Subject: Re: Re: [gentoo-user] Re: Messed up mail access rights
> >
> >
> > > From:: Neil Bothwick <neil@digimed.co.uk>
> > > To: gentoo-user@lists.gentoo.org
> > > Subject: Re: [gentoo-user] Re: Messed up mail access rights
> > > Date: Mon, 26 Sep 2005 10:19:25 +0100
> >
> > > On Sat, 24 Sep 2005 10:04:13 +0000, Mick wrote:
> > > > > Providing some basic information such as what mail
> > servers are you
> > > > > using would be a big plus to get an answer from someone.
> > > > Unfortunately it's a sendmail setup on a hosted account
> > and no info is
> > > > forthcoming from the admin. It seems like an mbox style mail
> > > > implementation. That's all I know about it I'm afraid.
> > > You could telnet into the server to see what the software identifies
> > > itself as.
> >
> > Thanks, this is what I got:
> >
> > > "telnet servername 25" for the SMTP server
> >
> > 220-viv.XXXXXXXXXXX.com <http://220-viv.XXXXXXXXXXX.com> ESMTP Exim 4.50#1 Mon, 26 Sep 2005
> > 16:39:45 -0400
> > 220-We do not authorize the use of this system to transport
> > unsolicited,
> > 220 and/or bulk e-mail.
> >
> > > "telnet servername 110" for the POP server
> >
> > +OK POP3 viva [cppop 19.0] at [XX.XX.XXX.XXX]
> >
> > > "telnet servername 143" for the IMAP server
> >
> > * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS AUTH=LOGIN]
> > viv.XXXXXXXXXX.com <http://viv.XXXXXXXXXX.com> IMAP4rev1 2003.339-cpanelat Mon, 26 Sep
> > 2005 16:45:38 -0400 (EDT)
> >
> > Is this enough to ascertain what the access rights ought to be?
> >
> > PS. What the recommended Gentoo telnet client?
>
> The lot is also accessible via Horde's and squirrel mail web gui's - not
> sure if that's relevant but thought I better mention it.
> --
> Regards,
> Mick
>
> --
> gentoo-user@gentoo.org mailing list
>
>


--
- Mark Shields

[-- Attachment #2: Type: text/html, Size: 3260 bytes --]

      reply	other threads:[~2005-09-30 20:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-26 20:50 Re: [gentoo-user] Re: Messed up mail access rights Michael Kintzios
2005-09-27 11:17 ` Michael Kintzios
2005-09-30 20:26   ` Mark Shields [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=642958cc0509301326p453a030bh53b10d277d460a8a@mail.gmail.com \
    --to=laebshade@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox