Bernardo Pons:
> On these days where theft of credentials of legitimate e-mail server users
> in order to send spam checking the MAIL FROM: using
> smtpd_reject_unlisted_sender would be a helping Postfix feature.
>
> Perhaps it is a misunderstanding from my side about the actual meaning of
> param
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20-12-13 20:54, Bernardo Pons wrote:
> On these days where theft of credentials of legitimate e-mail
> server users in order to send spam checking the MAIL FROM: using
> smtpd_reject_unlisted_sender would be a helping Postfix feature.
>
> Perhap
On these days where theft of credentials of legitimate e-mail server users
in order to send spam checking the MAIL FROM: using
smtpd_reject_unlisted_sender would be a helping Postfix feature.
Perhaps it is a misunderstanding from my side about the actual meaning of
parameter smtpd_reject_unlisted_
On Fri, Dec 20, 2013 at 04:54:02PM +0400, Vladimir Kozlov wrote:
> 18.12.2013 15:03, Vladimir Kozlov wrote:
> >I've tryig to use after-queue content filter as described in
> >FILTER_README.
I'd recommend that you take a look at amavisd-new.
> >How could I pass the authentication information (i.e
18.12.2013 15:03, Vladimir Kozlov wrote:
I've tryig to use after-queue content filter as described in FILTER_README.
How could I pass the authentication information (i.e. was initial
message sent by authenticated user or not) when re-injecting message
using sendmail? The problem is that further
Muzaffer Tolga Ozses:
> Hi,
>
> I've been getting the below messages for quite some time now, and I
> also get them on postqueue -p. What can I do about it?
>
> When I look at postqueue -p, the ID is 44C5E220E91 and when I do a grep, I get
...
> The google search and the above link says it's on g
Hi,
> [...] The user you are trying to contact is receiving mail at a rate
> that prevents additional messages from being delivered. [...]
I do not see what's so unclear about that?
Google thinks that the recipient receives an unusual amount of mail.
It's either the recipient's or Google's fault
Hi,
I've been getting the below messages for quite some time now, and I
also get them on postqueue -p. What can I do about it?
When I look at postqueue -p, the ID is 44C5E220E91 and when I do a grep, I get
44C5E220E91: to=,
relay=alt1.gmail-smtp-in.l.google.com[173.194.70.27]:25, delay=96931,
de