On Wed, Mar 12, 2014 at 04:01:59AM +, Tom Furie wrote:
> On Tue, Mar 11, 2014 at 09:43:41PM -0400, Tony Baldwin wrote:
>
> > This is what we ended up doing, rolling back to an older version of
> > mariadb, libmysqlclient18, etc.
> >
> > I posted the relevant instructions (where to get the old
On Tue, Mar 11, 2014 at 09:43:41PM -0400, Tony Baldwin wrote:
> This is what we ended up doing, rolling back to an older version of
> mariadb, libmysqlclient18, etc.
>
> I posted the relevant instructions (where to get the older pkgs, etc.)
> earlier.
> Both Taz' server and the other are both sen
On Tue, Mar 11, 2014 at 10:11:23PM +, Tom Furie wrote:
> On Tue, Mar 11, 2014 at 07:36:55PM +0100, Tazman Deville wrote:
>
> > There are few users on either server, and all I've tested are unable to
> > send mail.
> > In both servers, there is 1 mail DB for both dovecot and postfix, yes.
>
>
On Tue, Mar 11, 2014 at 07:36:55PM +0100, Tazman Deville wrote:
> There are few users on either server, and all I've tested are unable to
> send mail.
> In both servers, there is 1 mail DB for both dovecot and postfix, yes.
If both dovecot and postfix are using the same authentication mechanism
i
On Tue, Mar 11, 2014 at 07:45:06PM +0100, Tazman Deville wrote:
> On Tue, Mar 11, 2014 at 07:36:55PM +0100, Tazman Deville wrote:
> > On Tue, Mar 11, 2014 at 04:35:51PM +, Tom Furie wrote:
> > > On Tue, Mar 11, 2014 at 04:22:45PM +0100, Tazman Deville wrote:
>
> Well, with this pam error, I fo
On Tue, Mar 11, 2014 at 07:36:55PM +0100, Tazman Deville wrote:
> On Tue, Mar 11, 2014 at 04:35:51PM +, Tom Furie wrote:
> > On Tue, Mar 11, 2014 at 04:22:45PM +0100, Tazman Deville wrote:
> >
> > > They both use mysql (well, mariadb) auth for both dovecot and
> > > postfix.
> > > I have confi
On Tue, Mar 11, 2014 at 04:35:51PM +, Tom Furie wrote:
> On Tue, Mar 11, 2014 at 04:22:45PM +0100, Tazman Deville wrote:
>
> > They both use mysql (well, mariadb) auth for both dovecot and
> > postfix.
> > I have confirmed that I can connect to the DB on either server with
> > the
> > mail adm
On Tue, Mar 11, 2014 at 03:13:25PM +, Tom Furie wrote:
> On Tue, Mar 11, 2014 at 02:49:34PM +0100, Tazman Deville wrote:
> > Perhaps this is relevant:
> > telnet localhost 25
(snip)
> That looks okay in as much as you are able to connect to the SMTP
> server, however you haven't tried to authen
On Tue, Mar 11, 2014 at 04:22:45PM +0100, Tazman Deville wrote:
> They both use mysql (well, mariadb) auth for both dovecot and postfix.
> I have confirmed that I can connect to the DB on either server with the
> mail admin account configured in postfix.
> Yet, I can not send mail.
Do they connec
On Tue, Mar 11, 2014 at 03:13:25PM +, Tom Furie wrote:
> On Tue, Mar 11, 2014 at 02:49:34PM +0100, Tazman Deville wrote:
> > On Tue, Mar 11, 2014 at 02:41:02PM +0100, Tazman Deville wrote:
>
> > > both servers show similar in mail.warn:
> > > Mar 11 13:52:16 myownsite postfix/smtpd[16685]: war
On Tue, Mar 11, 2014 at 02:49:34PM +0100, Tazman Deville wrote:
> On Tue, Mar 11, 2014 at 02:41:02PM +0100, Tazman Deville wrote:
> > both servers show similar in mail.warn:
> > Mar 11 13:52:16 myownsite postfix/smtpd[16685]: warning: SASL
> > authentication failure: Password verification failed
>
On Tue, Mar 11, 2014 at 03:12:22PM +0100, Jochen Spieker wrote:
> Tazman Deville:
> >
> > Now, that I look, I'm seeing this in the mail.err logs:
> > Mar 10 22:04:58 myownsite dovecot: auth-worker(13988): Error:
> > mysql(127.0.0.1): Connect failed to database (mail): Can't connect to
> > MySQL se
Tazman Deville:
>
> Now, that I look, I'm seeing this in the mail.err logs:
> Mar 10 22:04:58 myownsite dovecot: auth-worker(13988): Error:
> mysql(127.0.0.1): Connect failed to database (mail): Can't connect to
> MySQL server on '127.0.0.1' (111) - waiting for 125 seconds before
> retry
> on one
On Tue, Mar 11, 2014 at 02:41:02PM +0100, Tazman Deville wrote:
> On Tue, Mar 11, 2014 at 01:25:39PM +, Jonathan Dowland wrote:
> > If mail is not sending, you need to look at the postfix logs and see if
> > there's an explanation for a test mail. dovecot will not be relevant
> > unless you are
On Tue, Mar 11, 2014 at 02:41:02PM +0100, Tazman Deville wrote:
> On Tue, Mar 11, 2014 at 01:25:39PM +, Jonathan Dowland wrote:
> > If mail is not sending, you need to look at the postfix logs and see if
> > there's an explanation for a test mail. dovecot will not be relevant
> > unless you are
On Tue, Mar 11, 2014 at 01:25:39PM +, Jonathan Dowland wrote:
> If mail is not sending, you need to look at the postfix logs and see if
> there's an explanation for a test mail. dovecot will not be relevant
> unless you are using send-over-IMAP which is unlikely. Can you share
> some relevant l
If mail is not sending, you need to look at the postfix logs and see if
there's an explanation for a test mail. dovecot will not be relevant
unless you are using send-over-IMAP which is unlikely. Can you share
some relevant log lines?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.
On Tue, Mar 11, 2014 at 02:17:52PM +0100, Tazman Deville wrote:
> I have two servers, both running wheezy with dovecot/postfix for mail.
> They were both sending/receiving mail fine 24 hours ago.
> Now neither is.
> On one, I've done nothing to alter anything with either postfix or
> dovecot in the
I have two servers, both running wheezy with dovecot/postfix for mail.
They were both sending/receiving mail fine 24 hours ago.
Now neither is.
On one, I've done nothing to alter anything with either postfix or
dovecot in the last 24 hours.
On the other, I generated a new smtpd.key and smptd.crt fo
19 matches
Mail list logo
