Zitat von Grant emailgr...@gmail.com:
For the first time ever, 7 of my (very much legitimate) automated
messages sent to gmail users have bounced with this message:
Our system has detected that this message is likely unsolicited mail.
To reduce the amount of spam sent to Gmail this message
Zitat von Matteo Cazzador mat...@netlite.it:
Hi, i've a problem causing by blacklist.
I 've a virtual postfix mail server (with smtp server sasl auth),
when a user send a mail
using my smtp server to a specific domain i obtain:
hostname ... server refused to talk to me: 550 Denied by
Hi, thank's , but it's not so clear for me.
The mail client receive a notification of error but too late over 24
hours from first send.
If the email is important this time it's too large.
Is it possibile to reduce it?
Il 05/12/2013 10:19, lst_ho...@kwsoft.de ha scritto:
Zitat von Matteo
Hi, is it possible to act on it using
delay_warning_time and or
maximal_queue_lifetime
Il 05/12/2013 10:24, Matteo Cazzador ha scritto:
Hi, thank's , but it's not so clear for me.
The mail client receive a notification of error but too late over 24
hours from first send.
If the email is
Hi All!
On one of the servers I manage I have
smtpd_client_restrictions =
permit_mynetworks
permit_sasl_authenticated
reject_unknown_client
permit
Obviously this rejects any requests where the DNS (forward or reverse)
fails.
I am under increasing pressure to
On 2013-12-05 7:50 AM, Andreas Kasenides andr...@cymail.eu wrote:
smtpd_client_restrictions =
permit_mynetworks
permit_sasl_authenticated
reject_unknown_client
permit
Obviously this rejects any requests where the DNS (forward or reverse)
fails.
I am under increasing pressure
yes was clear for sure but what follows was not so much for me, I mean what I
say.
A last question: can a a delay be the result of I/O writing issues on the
incoming queue ?
I suppose yes reading the manual (a = time from message arrival to last
active
I am not sure I understand. I am sending out email from postfix.
Postfix looks up the target domain mx record. Are you saying the
domain the target domain's dns server varies response based on query
source ip address?
On Thu, Dec 5, 2013 at 1:34 AM, Robert Schetterer r...@sys4.de wrote:
Am
nobody said that anywhere
if they receive mails from other senders that senders
are *not* using DNS and ignore the MX
Am 05.12.2013 15:26, schrieb Roman Gelfand:
I am not sure I understand. I am sending out email from postfix.
Postfix looks up the target domain mx record. Are you saying the
Am 05.12.2013 15:26, schrieb Roman Gelfand:
I am not sure I understand. I am sending out email from postfix.
Postfix looks up the target domain mx record. Are you saying the
domain the target domain's dns server varies response based on query
source ip address?
the dns root ( which is the
Am 05.12.2013 15:45, schrieb li...@rhsoft.net:
nobody said that anywhere
if they receive mails from other senders that senders
are *not* using DNS and ignore the MX
yep i agree in this, but as long deliver is related at resolv public dns
whith such mx , produce an error looks fine to me.
Hi, I have a problem with address rewriting.
The mail originates from a broken, cannot be changed, mail system that sends
out mails to the wrong receiver:
Ex:
Mail send to: firstname_lastn...@domain.dk
Should have been send to:
firstname.lastn...@domain.com
I have solved this with a canonical
On Thu, Dec 05, 2013 at 08:23:18AM +0100, Matteo Cazzador wrote:
hostname ... server refused to talk to me: 550 Denied by policy
http://www.postfix.org/postconf.5.html#smtp_skip_5xx_greeting
Note, some time ago there were systems (perhaps Microsoft Exchange)
that returned 5xx codes in the
On Thu, Dec 05, 2013 at 11:01:06AM +0100, Matteo Cazzador wrote:
Hi, is it possible to act on it using
delay_warning_time and or
I would recommend setting this to a value in the 2-4 hour range on
outbound MTAs. If you have separate inbound MTAs I would leave this
unset (default is 0h, which
Hi, thanks a lot i will follow your suggest!
Best regards.
Il 05/12/2013 17:08, Viktor Dukhovni ha scritto:
On Thu, Dec 05, 2013 at 11:01:06AM +0100, Matteo Cazzador wrote:
Hi, is it possible to act on it using
delay_warning_time and or
I would recommend setting this to a value in the 2-4
On Thu, Dec 05, 2013 at 04:45:48PM +0100, Troels Hansen wrote:
canonical_maps = regexp:/etc/postfix/recipientmap
and recipientmap contains the following:
/^(.*)_(.*)@domain\.dk$/ ${1}.${2}@domain.com
This works, however it should only be done from mails originating
from the broken
Hello,
not tested ... and as far as I remember
1/ use a mix of smtpd_client_restrictions and FILTER to redirect trafic from
10.11.12.13 to a local smtpd/port (for smtpd/27)
10.11.12.13 FILTER smtp:[127.0.0.1]:27
2/ define a new local cleanup service on smtpd/27
something like that:
Thank you for the reply.
On 05-12-2013 15:26, Charles Marcus wrote:
On 2013-12-05 7:50 AM, Andreas Kasenides andr...@cymail.eu wrote:
smtpd_client_restrictions =
permit_mynetworks
permit_sasl_authenticated
reject_unknown_client
permit
Obviously this rejects any requests where
18 matches
Mail list logo
