* Jeremy T. Bouse :
> I'm going ahead and asking here as I've been searching and haven't
> found any information...
>
> I've been using PostgreSQL, and MySQL in the past, to hold virtual user
> information for my Postfix server. The only thing that has bothered me
> is every *sql_*.cf file I h
I'm going ahead and asking here as I've been searching and haven't
found any information...
I've been using PostgreSQL, and MySQL in the past, to hold virtual user
information for my Postfix server. The only thing that has bothered me
is every *sql_*.cf file I had to setup had to have the user
On 01/25/2017 04:44 PM, Fazzina, Angelo wrote:
Hi,
I am trying to grep out all the log lines for a particular connection.
I added logging to see the cipher being used when connecting, now i want
to see if anyone is actually getting connected and sending emails.
Obviously with many threads, l
> On Jan 25, 2017, at 4:26 PM, Wietse Venema wrote:
>
>> Even fancier would be dynamically adjusting the database encoding to
>> UTF-8 when the client includes the "SMTPUTF8" ESMTP parameter in its
>> "MAIL" command. Since, presumably, in that case all non-ASCII data
>> in the SMTP dialogue are
Hi,
I am trying to grep out all the log lines for a particular connection.
I added logging to see the cipher being used when connecting, now i want to see
if
anyone is actually getting connected and sending emails.
Obviously with many threads, logs are not written chronologically, so need to
fin
Viktor Dukhovni:
>
> > On Jan 25, 2017, at 3:19 PM, Andrew Sullivan
> > wrote:
> >
> > I am aware that the Postgres driver is currently hard-coded to LATIN1.
> > This, of course, causes problems with SMTPUTF8, since the email
> > addresses and so on could be in UTF8.
> >
> > I have a reason to
On Wed, Jan 25, 2017 at 03:31:36PM -0500, Viktor Dukhovni wrote:
>
> The reason for LATIN1 is that all raw octet strings are valid LATIN1,
> so whatever non-ASCII garbage comes down the wire, database lookups
> won't tempfail with query encoding errors. Absent mechanisms like
> SMTPUTF8 non-ASCII
> On Jan 25, 2017, at 3:19 PM, Andrew Sullivan wrote:
>
> I am aware that the Postgres driver is currently hard-coded to LATIN1.
> This, of course, causes problems with SMTPUTF8, since the email
> addresses and so on could be in UTF8.
>
> I have a reason to need the combination, and I'm wonderi
Hi,
I am aware that the Postgres driver is currently hard-coded to LATIN1.
This, of course, causes problems with SMTPUTF8, since the email
addresses and so on could be in UTF8.
I have a reason to need the combination, and I'm wondering whether
there is anything standing in the way of just changin
On 25/01/2017 7:31 pm, Dominic Raferd wrote:
> The key text must be 'Server configuration problem'. I think you
> should look at earlier lines in your log which might tell you what
> your configuration problem is. See
> http://www.postfix.org/DEBUG_README.html. I note that the incoming
> mail was v
On 25 January 2017 at 19:17, Danny Horne wrote:
> Hi all,
>
> Can anyone decipher this? If by 'recipient address' they mean mine, I
> receive email from many different sources on that address all the time,
> so don't know what this entry is telling me.
>
> Jan 25 19:06:59 turing postfix/smtpd[777
Hi all,
Can anyone decipher this? If by 'recipient address' they mean mine, I
receive email from many different sources on that address all the time,
so don't know what this entry is telling me.
Jan 25 19:06:59 turing postfix/smtpd[7772]: NOQUEUE: reject: RCPT from
mx-out-04c.sjc1.discourse.org[
All options, assuming your imap/pop/lmtp are compatable and friendly using it.
I know dovecot you should only access a mailstore from one host at a
time, don't just randomly balance things, or it can corrupt the index
files.
Quoting Eero Volotinen :
how about mounting ceph or glusterfs di
Tim Smith skrev den 2017-01-25 16:40:
P.S. Yes I know OpenDKIM has a “TrustedHosts” config file. But that
would not be much good for me as my SMTP client machines can connect
from anywhere. And putting 0.0.0.0 in OpenDKIM trusted hosts wouldn’t
work either as I have a second postfix instance th
Hi,
I am trying to get OpenDKIM 2.11.0 running with Postfix 3.1.4.
When a SASL authenticated client sends an email via Postfix, the
following is logged :
Jan 25 15:15:59 bob opendkim[1016]: DDD1F400A1B2: [192.0.2.43]
[192.0.2.43] not internal
Jan 25 15:15:59 bob opendkim[1016]: DDD1F400A1B2: not
Hello Wietse,
Thank you for replying.
I understood what the problem is.
--
Hiroyuki Sato.
2017-01-25 1:28 GMT+09:00 Wietse Venema :
> Hiroyuki Sato:
>> I set up NSS(nslcd) and PAM config for LDAP on CentOS6.
>> And I got the following error when the postfix server can't connect to
>> LDAP serve
16 matches
Mail list logo
