Hi, I managed to do some test but with no luck.
As suggested I specified two parameters in main.cf that where not
present before:
disable_dns_lookups = no
smtp_host_lookup = dns
Sure mastervoice.it has an A record that point to 2.229.104.67 (web
server) while the mail server is at
d.davo...@mastertraining.it skrev den 04-12-2012 14:03:
Hi everybody,
I'm running a postfix 2.5.5-1 on a old debian server, managing
different mail domains. I'm migrating now to a different mail
provider, one domain at time (es. example.com).
I removed example.com from virtual_alias_domains
d.davo...@mastertraining.it skrev den 04-12-2012 15:52:
Now it MX records are:
# dig example.com MX +noall +answer
dig @8.8.8.8 example.com MX +noall +answer
is ok ?
example.com.12889 IN MX 10
ASPMX.L.GOOGLE.COM.
example.com.12889 IN MX 20
Muzaffer Tolga Özses skrev den 04-12-2012 09:10:
mydestination = localhost
try using it as default, comment it in main.cf
if it still loops then recipient domain is missing in mysql
virtual_mailbox_domains
virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf
On Wed, Dec 05, 2012 at 12:45:37PM +0100, d.davo...@mastertraining.it wrote:
mydestination = mail2.mastercom, localhost.mastercom, localhost,
mastertraining.it, registroelettronico.com, masterscuola.it,
mastercom
myhostname = mail.mastertraining.it
relay_domains = $mydestination
On Tue, Dec 4, 2012 at 5:48 AM, Wietse Venema wie...@porcupine.org wrote:
Taking a quick look at the source, it looks like 2.8 does not use the
thread-safe getpwnam_r. It does not appear that postfix is threaded,
so it should be safe to not use getpwnam_r.
It has NOTHING TO TO WITH THREADS.
Dan Lists:
It has NOTHING TO TO WITH THREADS.
In particular, getpwnam() on top of *SQL etc. return null (i.e.
user not found) when the database is unavailable. There is no
official API for getpwnam() to indicate I don't know because
getpwnam() is not supposed to return in such cases.
As
Chris skrev den 03-12-2012 19:40:
I've been asked to skip RBL checks for certain users on the domain.
How can I
do that without disabling the for everybody else?
make one restriction class pr recipient
and make a recipient check with result of the restriction class
We're using virtual
Chris skrev den 03-12-2012 23:52:
I'm already using a hash db to map users that opted out of
greylisting in
smtpd_recipient_restrictions. Map's in the form of
u...@example.com OK
Can I re-use the same list in the position Neil suggested?
nope, OK is accept all recipient, so it just accept
Hello.
I'm getting `warning:xsasl_cyrus_server_get_mechanism_list: no
applicable SASL mechanisms' (/var/log/mail.log) and `fatal: no SASL
authentication mechanisms' (/var/log/mail.err) in Debian Squeeze.
Installed:
postfix: 2.7.1-1+squeeze1
libsasl2-2: 2.1.23.dfsg1-7
libsasl2-modules:
jug...@lavabit.com:
Hello.
I'm getting `warning:xsasl_cyrus_server_get_mechanism_list: no
applicable SASL mechanisms' (/var/log/mail.log) and `fatal: no SASL
authentication mechanisms' (/var/log/mail.err) in Debian Squeeze.
Installed:
postfix: 2.7.1-1+squeeze1
libsasl2-2:
On Wed, Dec 5, 2012 at 11:55 AM, Wietse Venema wie...@porcupine.org wrote:
I will not base Postfix development on UNDOCUMENTED return values.
That is unmaintainable.
I've brought it up on the FreeBSD lists. I suggested that it is a bug
for getpwnam_r to act the way it is. I'll probably end
Am 05.12.2012 22:02, schrieb jug...@lavabit.com:
Consider reading Postfix documentation.
The error message is described there.
I haven't found it. Could you paste it?
While the Postfix documentation Dr. Venema referred to has the necessary
clues, you can find Debian-specific ones in the
On Dec 5, 2012, at 2:02 PM, jug...@lavabit.com wrote:
Will it solve the problem if I switch to Dovecot SASL?
I've been using the Dovecot SASL option for several years on Debian Lenny and
Squeeze, largely because figuring out Cyrus looked like too much work, and it
was simple and quick to set
Dan Lists:
On Wed, Dec 5, 2012 at 11:55 AM, Wietse Venema wie...@porcupine.org wrote:
I will not base Postfix development on UNDOCUMENTED return values.
That is unmaintainable.
I've brought it up on the FreeBSD lists. I suggested that it is a bug
for getpwnam_r to act the way it is.
jug...@lavabit.com:
Consider reading Postfix documentation.
The error message is described there.
I haven't found it. Could you paste it?
Well there is at least one section that covers not found or
missing authentication mechanisms.
The problem is a mis-match between
The problem is a mis-match between smtpd_sasl_security_options
(e.g., noplaintext) and the available server mechanisms (e.g.,
plaintext only).
I've configured UNIX-domain socket communication, enabled SASL
authentication and authorization(0), but I'm still getting `fatal: no
SASL
On 12/5/2012 7:23 PM, jug...@lavabit.com wrote:
The problem is a mis-match between smtpd_sasl_security_options
(e.g., noplaintext) and the available server mechanisms (e.g.,
plaintext only).
I've configured UNIX-domain socket communication, enabled SASL
authentication and authorization(0),
Hi Everyone,
On 01/12/12 18:19, Noel Jones wrote:
On 12/1/2012 11:11 AM, PGR wrote:
Hi Everyone,
I would like to know how to stop/forbid this server to send us their emails
The content of received email is
Received: from web-groupsolweb1.aquaray.com (unknown [95.128.42.80])
by
19 matches
Mail list logo
