Hi
After years of a smoothly running mail server, my logs are starting to
fill with this error message:
fatal: proxy:mysql:/etc/postfix/mailalias.cf(0,lock|fold_fix): table
lookup problem
I haven't updated anything or changed any configs (in either mysql or
postfix) so I'd appreciate some hints
Simon Brereton:
Hi
After years of a smoothly running mail server, my logs are starting to
fill with this error message:
fatal: proxy:mysql:/etc/postfix/mailalias.cf(0,lock|fold_fix): table
lookup problem
I would expcet to see some warning before an uninformative fatal message.
BTW the
On 5 March 2013 16:47, Wietse Venema wie...@porcupine.org wrote:
Simon Brereton:
Hi
After years of a smoothly running mail server, my logs are starting to
fill with this error message:
fatal: proxy:mysql:/etc/postfix/mailalias.cf(0,lock|fold_fix): table
lookup problem
I would expcet to
On Mon, Mar 04, 2013 at 01:35:42PM -0600, Noel Jones wrote:
There's several ways to do this. I think the easiest is:
# main.cf
header_checks = regexp:/etc/postfix/header_checks
in your header_checks file:
/./ REDIRECT some...@example.com
where someone is a valid local user, and
Simon Brereton:
Mar 5 08:45:14 mail postfix/proxymap[24831]: warning: mysql query
failed: MySQL server has gone away
The mysql server closed the connection (or crashed).
Mar 5 10:53:22 mail postfix/proxymap[26043]: warning: connect to
mysql server localhost: Can't connect to local MySQL
On 5 Mar 2013 19:07, Wietse Venema wie...@porcupine.org wrote:
Simon Brereton:
Mar 5 08:45:14 mail postfix/proxymap[24831]: warning: mysql query
failed: MySQL server has gone away
The mysql server closed the connection (or crashed).
Mar 5 10:53:22 mail postfix/proxymap[26043]:
Hi ,
I use virtual_alias_maps with a mysql server to manage aliases and
catch-all accounts.
For the past few years this approach worked like a charm, but after
upgrading to 2.10 I get two different behaviours.
When mailing from a domain to a domain both hosted on this server, the
Forgot to add the proper postfinger file.
postfinger - postfix configuration on Tue Mar 5 23:20:05 CET 2013
version: 1.30
--System Parameters--
mail_version = 2.10.0
hostname = black-mail.nl
uname = Linux black-mail.nl 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64
GNU/Linux
--Packaging
On Tue, Mar 05, 2013 at 11:19:22PM +0100, Michiel Hazelhof wrote:
which results in a reject, Mail.log: Mar 5 21:55:30 black-mail
postfix/smtpd[19444]: NOQUEUE: reject: RCPT from
domain.nl[2a00:d10:101::26:0]: 554 5.7.1 al...@hazelhof.nl:
Recipient address rejected: Unknown user;
On Fri, Mar 01, 2013 at 03:19:42PM +0100, Bastian Blank wrote:
I found that one MTA bounced several mails. The mails where sent to
test@example.com and accepted by Postfix. The backend LMTP then
rejected the mails.
This is what I found out:
- RCPT TO: test@example.com
- The ldap table
Viktor Dukhovni:
Arguably, all lookup keys in tables should be in external (RFC-5322)
form. The suggested doubling of internal spaces is far less important
in practice that avoiding the loss of leading spaces.
Which external form?
- RFC 5321 and 5322 have different rules.
- Worse, The
On Tue, Mar 05, 2013 at 11:16:18PM -0500, Wietse Venema wrote:
Viktor Dukhovni:
Arguably, all lookup keys in tables should be in external (RFC-5322)
form. The suggested doubling of internal spaces is far less important
in practice that avoiding the loss of leading spaces.
Which external
12 matches
Mail list logo