On Tue, 2011-10-04 at 12:25 +0530, Dhanraj Wadhe wrote:
> Hi All,
>
> We are public email provider with postfix at backend. We are facing
> issue with getting black listed again and again.
>
Blacklisted where ? by whom ?
Usually If you get listed in any common blacklist you will get evidence
w
Hi,
Is there a way to limit the number of recipients per message based on
the sender email address ?
Thanks,
With Best Regards,
Janaka
mephistophe...@operamail.com:
> smtpd_tls_ciphers = RSA
As documented, smtpd_tls_ciphers specifies a cipher GRADE
not a cipher NAME.
TLS_README suggests that the grades are export and high.
Wietse
http://www.postfix.org/postconf.5.html#smtpd_tls_ciphers
http://www.postfix.org/TLS_README
The TLS ciphers I use for transport between a number of our servers are
limited to
openssl ciphers -v "RSA:\!MEDIUM:\!LOW:\!EXPORT:\!NULL" -tls1 -ssl3
AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256)
Mac=SHA1
CAMELLIA256-SHA SSLv3 Kx=RSA Au=RSA Enc=Camellia(256)
Ma
On 10/4/2011 5:42 PM, Eric Cunningham wrote:
> On 10/4/2011 4:19 PM, wolfgang wrote:
>> On 2011-10-04 21:36, Eric Cunningham wrote:
postmap -q 'e...@whoi.edu'
pcre:/etc/postfix/access/final_recipient_access
>>>
>>> Great suggestion for this, unfortunately, it returns nothing:
>>>
>>> # po
On 10/4/2011 4:19 PM, wolfgang wrote:
On 2011-10-04 21:36, Eric Cunningham wrote:
postmap -q 'e...@whoi.edu'
pcre:/etc/postfix/access/final_recipient_access
Great suggestion for this, unfortunately, it returns nothing:
# postmap -q 'e...@whoi.edu'
pcre:/etc/postfix/access/final_sender_access
On 2011-10-04 21:36, Eric Cunningham wrote:
> > postmap -q 'e...@whoi.edu'
> > pcre:/etc/postfix/access/final_recipient_access
>
> Great suggestion for this, unfortunately, it returns nothing:
>
> # postmap -q 'e...@whoi.edu'
> pcre:/etc/postfix/access/final_sender_access #
Use
pcre:/etc/postfix/
* wolfgang :
> On 2011-10-04 21:02, Ralf Hildebrandt wrote:
>
> > It could be pcre:/etc/postfix/access/final_recipient_access
> > Given that pcre: is involved, lot's of funky stuff could happen.
>
> Try and run
> postmap -q 'e...@whoi.edu'
> pcre:/etc/postfix/access/final_recipient_access
This
On 10/4/2011 2:36 PM, Eric Cunningham wrote:
>> postmap -q 'e...@whoi.edu'
>> pcre:/etc/postfix/access/final_recipient_access
>
> Great suggestion for this, unfortunately, it returns nothing:
>
> # postmap -q 'e...@whoi.edu'
> pcre:/etc/postfix/access/final_sender_access
> #
>
> -Eric
>
>
wh
postmap -q 'e...@whoi.edu' pcre:/etc/postfix/access/final_recipient_access
Great suggestion for this, unfortunately, it returns nothing:
# postmap -q 'e...@whoi.edu' pcre:/etc/postfix/access/final_sender_access
#
-Eric
Eric Cunningham:
> Oct 4 11:53:53 postal1 postfix/smtpd[19496]: NOQUEUE: reject: RCPT from
> fwall.fidcouns.com[207.109.19.34]: 554 5.7.1 : Recipient
> address rejected: Access denied; from=
> to= proto=ESMTP helo=
This means that the recipient address is blocked by one of your
Postfix check_r
On 2011-10-04 21:02, Ralf Hildebrandt wrote:
> It could be pcre:/etc/postfix/access/final_recipient_access
> Given that pcre: is involved, lot's of funky stuff could happen.
Try and run
postmap -q 'e...@whoi.edu'
pcre:/etc/postfix/access/final_recipient_access
Hope this helps,
wolfgang
* Eric Cunningham :
> Hello,
>
> My postfix installation is having trouble accepting email from a
> particular source to any recipients and I haven't been able to
> ascertain the cause so I can address the problem. Here's a logfile
> extraction:
It honors you that you're trying to find the error
On Tue, Oct 4, 2011 at 2:55 AM, Dhanraj Wadhe wrote:
> We are public email provider with postfix at backend. We are facing issue
> with getting black listed again and again.
>
> Currently we have setup reverse lookup, DKIIM and SPF to avoid getting
> listed into rbl's and dnsbl.
Great. Once your
Hello,
My postfix installation is having trouble accepting email from a
particular source to any recipients and I haven't been able to ascertain
the cause so I can address the problem. Here's a logfile extraction:
Oct 4 11:53:52 postal1 postfix/smtpd[19496]: connect from
fwall.fidcouns.com
On Oct 4, 2011, at 10:31 AM, Noel Jones wrote:
>> That's postgrey. It's running, but bears looking into...
> connection refused suggests it's either not running or not the right
> port.
Postgrey wasn't running -- I misinterpreted ps. I put it in monit to be
restarted if it ever quits again. Th
I am not the one that is calling the 'blame' and 'shooting' and
'overreacting'. Its other persons that are saying that of me.
That is what is rude not asking question honestly!
Okay then, so it is my failing that I am less skilled at this Postfix
than you. Enjoy the money and time I did spend a
On Oct 4, 2011, at 5:48 PM, terryjames9...@mm.st wrote:
>
>
> On Tuesday, October 04, 2011 5:45 PM, "Helder Oliveira"
> wrote:
>> Shooting the messenger is very common, learn and let it go
>
> I do not understand why you accuse of shooting anything. I have not
> made any blame. There is wro
On Tuesday, October 04, 2011 5:45 PM, "Helder Oliveira"
wrote:
> Shooting the messenger is very common, learn and let it go
I do not understand why you accuse of shooting anything. I have not
made any blame. There is wrong reaction to my just asking a first
question.
I see now what many peop
On Oct 4, 2011, at 5:38 PM, terryjames9...@mm.st wrote:
> Hello Duane,
>
> On Tuesday, October 04, 2011 4:33 PM, "Duane Hill"
> wrote:
>> You should look here: http://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP
>
> Thank you for the link. I think I already have tried to follow it to set
> up th
Hello Duane,
On Tuesday, October 04, 2011 4:33 PM, "Duane Hill"
wrote:
> You should look here: http://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP
Thank you for the link. I think I already have tried to follow it to set
up these servers.
May be I have missed then something in Dovecot since I am t
I have not made any blame. I am asking a question to learn. So nothing
needed to accuse.
On Tuesday, October 04, 2011 12:29 PM, "Wietse Venema"
wrote:
> terryjames9...@mm.st:
> > Oct 4 08:26:17 tjserver postfix/lmtp[7150]: 086E9204BE:
> > to=, relay=tjserver.loc[private/dovecot-lmtp],
> > dela
On Tue, Oct 4, 2011 at 4:05 PM, wrote:
> Hello,
>
> I am building a Postfix 2.8.5 server. And I am delivering my mail only
> to the Dovecot IMAP mail store using LMTP.
>
> I am following the Wiki pages at www.postfix.org/VIRTUAL_README.html and
> http://www.postfix.org/lmtp.8.html for guidance i
On 10/4/2011 11:06 AM, Glenn English wrote:
>
> On Oct 4, 2011, at 9:05 AM, Noel Jones wrote:
>
>> Look in the log for more information.
>> http://www.postfix.org/DEBUG_README.html#logging
>
> Thanks, Noel. There were about 99 million:
>
>> server postfix/smtpd[17681]: warning: problem talking
On Oct 4, 2011, at 9:05 AM, Noel Jones wrote:
> Look in the log for more information.
> http://www.postfix.org/DEBUG_README.html#logging
Thanks, Noel. There were about 99 million:
> server postfix/smtpd[17681]: warning: problem talking to server
> 127.0.0.1:6: Connection refused
entries.
terryjames9...@mm.st:
> Oct 4 08:26:17 tjserver postfix/lmtp[7150]: 086E9204BE:
> to=, relay=tjserver.loc[private/dovecot-lmtp],
> delay=0.13, delays=0.11/0.02/0/0, dsn=4.3.0, status=deferred (host
> tjserver.loc[private/dovecot-lmtp] said: 451 4.3.0
> Temporary internal error (in reply to end of
Do not quote the entire message with verbose logs unless required! :)
> DO NOT post verbose logging unless required!
DO NOT post verbose logging unless required!
Am 04.10.2011 18:05, schrieb terryjames9...@mm.st:
> Hello,
>
> I am building a Postfix 2.8.5 server. And I am delivering my mail only
> to the Dovecot IMAP mail store using LMTP.
>
> I am following the Wiki pages at www.postfix.org/VIRTUAL_README.html
Hello,
I am building a Postfix 2.8.5 server. And I am delivering my mail only
to the Dovecot IMAP mail store using LMTP.
I am following the Wiki pages at www.postfix.org/VIRTUAL_README.html and
http://www.postfix.org/lmtp.8.html for guidance in these things.
In the testing of LMTP delivery I am
Hello Wietse.
Thank you for the help.
I found the problem to be in my dovecot config file.
Now it is working as expected.
Thanks.
Markus
On 09/19/2011 11:35 PM, Wietse Venema wrote:
Markus Bajones:
Hello Wietse,
thank you for your reply.
I tried to do this, but failed to get any result.
On 10/4/2011 9:54 AM, Glenn English wrote:
> I'm getting a huge amount of Server configuration problem rejects. But not
> all -- I receive from my own nets and some lists. postfix check says I'm OK
> (I don't know if it checks the configuration(s)), and postfix restarts
> without complaint.
>
>
On 10/4/2011 10:54 AM, Glenn English wrote:
I'm getting a huge amount of Server configuration problem rejects. But not all
-- I receive from my own nets and some lists. postfix check says I'm OK (I
don't know if it checks the configuration(s)), and postfix restarts without
complaint.
root@se
I'm getting a huge amount of Server configuration problem rejects. But not all
-- I receive from my own nets and some lists. postfix check says I'm OK (I
don't know if it checks the configuration(s)), and postfix restarts without
complaint.
> root@server:/etc/postfix# postconf -n
> address_veri
Dhanraj Wadhe:
> Hi All,
>
> We are public email provider with postfix at backend. We are facing issue
> with getting black listed again and again.
There are many reasons why this can happen:
- Users forward all their email, and therefore they also forward spam.
- Users are phished and spammers
On 2011-10-04 2:55 AM, Dhanraj Wadhe wrote:
We are public email provider with postfix at backend. We are facing
issue with getting black listed again and again.
Evidence?
Currently we have setup reverse lookup, DKIIM and SPF to avoid getting
listed into rbl's and dnsbl.
Per the welcome mes
Zitat von Dhanraj Wadhe :
Hi All,
We are public email provider with postfix at backend. We are facing issue
with getting black listed again and again.
Currently we have setup reverse lookup, DKIIM and SPF to avoid getting
listed into rbl's and dnsbl.
In most cases the issue arises because yo
Am 04.10.2011 08:55, schrieb Dhanraj Wadhe:
> Hi All,
>
> We are public email provider with postfix at backend. We are facing
> issue with getting black listed again and again.
>
> Currently we have setup reverse lookup, DKIIM and SPF to avoid getting
> listed into rbl's and dnsbl.
that has no r
37 matches
Mail list logo
