On Sat, May 18, 2019 at 11:39 PM mick crane wrote:
> https://wiki.dovecot.org/TestInstallation
TestInstallation is lovely document. I got Dovecot to answer
everything pretty well, considering that TLS and such don't apply here
(the server is on my LAN, and it's just 10 or 20 feet of Cat5e away).
On Sun, May 19, 2019 at 6:06 AM mick crane wrote:
>
> which file are you editing ?
> I think how it works is that apt puts its files in /usr/share/dovecot
> and update overwrites those, whereas "your" files are in /etc/dovecot.
Didn't know about the configs in share, but I was working on
/etc/dov
On Sat, 18 May 2019 23:13:26 +
Glenn English wrote:
> I installed mutt on the mail server, and it found mail that's been
> coming in and was stored properly by Postfix.
>
> It's gotta be something with Dovecot.
>
Any possibility that a certificate might have expired?
--
Joe
Hi.
On Sat, May 18, 2019 at 11:13:26PM +, Glenn English wrote:
> I installed mutt on the mail server, and it found mail that's been
> coming in and was stored properly by Postfix.
>
> It's gotta be something with Dovecot.
/etc/dovecot/conf.d/10-auth.conf says to this:
Note that if t
On 2019-05-19 00:58, Glenn English wrote:
On Sat, May 18, 2019 at 11:39 PM mick crane
wrote:
https://wiki.dovecot.org/TestInstallation
That looks great -- first thing in the morning :-)
which file are you editing ?
I think how it works is that apt puts its files in /usr/share/dovecot
and
On Sat, May 18, 2019 at 11:39 PM mick crane wrote:
> https://wiki.dovecot.org/TestInstallation
That looks great -- first thing in the morning :-)
--
Glenn English
On Sat, May 18, 2019 at 11:29 PM Kushal Kumaran wrote:
> The documentation for the disable_plaintext_auth parameter seems like it
> is exactly what you need to tweak. I cannot tell why you didn't run
> into this earlier.
I did. But what I did to try to get it to work, didn't.
--
Glenn English
On Sat, May 18, 2019 at 11:39 PM mick crane wrote:
> Dunno why it suddenly stopped working.
I don't either.
> The commented out lines in the config file normally show the default.
Oh, yeah. I knew that once :-)
Copying the line, uncommenting it, and change it to 'no' made the fail
take longer
On 2019-05-18 23:58, Glenn English wrote:
I couldn't find anything in the Dovecot config files that addressed
that, except a commented out line: "#disable_plaintext_auth = yes."
But Dovecot seems to be tossing PLAINTEXT anyway. I didn't try
deleting the line.
Dunno why it suddenly stopped wor
I installed mutt on the mail server, and it found mail that's been
coming in and was stored properly by Postfix.
It's gotta be something with Dovecot.
--
Glenn English
Glenn English writes:
> Buster, Stretch, Wheezy
>
> I know this is probably the wrong place to ask, but DU is full of
> knowledgeable folks...
>
> This morning I quit receiving IMAP email (Dovecot, Thunderbird). I
> installed and tried several other clients (iMail, Geary, Sylpheed) and
> none wor
Buster, Stretch, Wheezy
I know this is probably the wrong place to ask, but DU is full of
knowledgeable folks...
This morning I quit receiving IMAP email (Dovecot, Thunderbird). I
installed and tried several other clients (iMail, Geary, Sylpheed) and
none worked. They said things like my Authenti
please ignore & excuse the noise
0x17F9F9B7.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
Hello,
Im figuring out. If my domain doesn't have any reverse ip equivalent over
the internet. Will some of my mails have problems, I mean will I get
reveicing problems. My friends uses qmail and some are not. I can receive
from other users but from other qmail mta I can't.
Is this problem an MTA
derrick and all:
Tried suggestions re: authentication; still got "relay prohibited; you
should authenticate first."
Finally uncommented all the methods in the client-side authentication
lines in exim.conf. got something slightly different when sending, this
time to [EMAIL PROTECTED]
result included
Starting with the first error message (from your other message) :
[EMAIL PROTECTED]
SMTP error from remote mailer after RCPT TO:<[EMAIL PROTECTED]>:
host smtp.mailtag.com [66.84.135.12]: 554 Undeliverable TO address:
<[EMAIL PROTECTED]>
Ok, so exim on your system tried talking
]]
Sent: Sunday, December 15, 2002 6:39 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: continuing email problems (fwd)
Re-sending. It appears that my Shellword character set was wrong. sorry!
-- Forwarded message --
Date: Sun, 15 Dec 2002 08:26:36 -0600 (CST)
From: Cheryl
Re-sending. It appears that my Shellword character set was wrong. sorry!
-- Forwarded message --
Date: Sun, 15 Dec 2002 08:26:36 -0600 (CST)
From: Cheryl Homiak <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: continuing email problems
Having checked my exim logs on b
Having checked my exim logs on both my desktop (cable connection charter)
and laptop (ppp mailtag) computers, I find two different errors.
On the cable machine, I find in the logs when the receiving host tries to
take the email from charter: "relay prohibitted. You must authenticate
first." The ema
I am using the qmail mail server and only some users cannot send e-mail to
me. I can send mail to these users without any problems. One of them got
the following message:
The message could not be sent because one of the recipients was rejected by
>the
>server. The rejected email address was "
20 matches
Mail list logo
