[pfx] Postfix + mysql connection lost after RCPT

Hi there, We're using Postfix + Mysql and we're getting this mysql connection lost issue very often. Nov 22 14:38:28 smtp2 postfix/submission/smtpd[16064]: disconnect from unknown[177.128.116.180] ehlo=2 starttls=1 auth=1 mail=1 rcpt=1 data=1 quit=1 commands=8 Nov 22 14:38:28 smtp2

Re: Outgoing content-filter

Nevermind, got it working after changing default_destination_recipient_limit=1. Em seg., 27 de fev. de 2023 às 17:30, Rafael Azevedo escreveu: > Wietse, > Also I've noticed that when the filter is applied it kinds of groups the > pipe process per domain. > > For example, I c

Re: Outgoing content-filter

nd because of that the filter is being applied once for all messages within same domain. Does this makes sense?? Thanks Em seg., 27 de fev. de 2023 às 15:44, Rafael Azevedo escreveu: > Thanks for the reply Wietse. > > This is my scenario: > > mail in > postfix policy_check ->

Re: Outgoing content-filter

" will only process > > messages that arrive via SMTP port 25? > > Rafael Azevedo: > > Hi Wietse, thanks for the reply. > > > > Yes I am. And this message is being sent through port 25. > > Just to be clear, I was talking about **receiving*** the

Re: Outgoing content-filter

Hi Wietse, thanks for the reply. Yes I am. And this message is being sent through port 25. There's one thing I have doubt about: will it process as the after-queue content-filter? Thanks once again. Regards. Em seg., 27 de fev. de 2023 às 12:32, Wietse Venema escreveu: > Rafael Azev

Re: Outgoing content-filter

Even running this as the filter-script it just doesn't work: #!/bin/bash # Localize these. echo Message content rejected; exit 75; The message goes to final recipient instead of being rejected. Thanks Em seg., 27 de fev. de 2023 às 11:33, Rafael Azevedo escreveu: > Thats

Re: Outgoing content-filter

t >in.$$ || { echo Cannot save mail to file; exit $EX_TEMPFAIL; } > > /usr/bin/altermime --input=in.$$ \ >--disclaimer=/home/filter/stopka.txt \ >--disclaimer-html=/home/filter/stopka.html \ > > $SENDMAIL "$@" > exit $? > &

Outgoing content-filter

Hi there, I was doing a research about how to implement an outgoing email filter. For every sent message we want to add a footer with a counter. I've tried to add the "content_filter" tag as shown: smtp inet n - n - 50 smtpd -o content_filter=footer

Re: Postfix spawn

Thank you so much for your time and help. You guys are the best! Thanks Em seg., 8 de nov. de 2021 às 16:16, escreveu: > > Its a PHP simple script: > > > > #!/usr/bin/php > > > print_r("action=PERMIT\n\n"); > > ?> > > > As Wietse stated, the policy server is designed to be recycled to avoid

Re: Postfix spawn

Thanks a lot Wietse, the problem was the PHP script not being reused. Problem fixed. Huge thanks to everyone here, you guys are awesome! Thanks!!! Em seg., 8 de nov. de 2021 às 14:55, Wietse Venema escreveu: > Rafael Azevedo: > > Hi there, > > > > We're testing a custom

Re: Postfix spawn

Its a PHP simple script: #!/usr/bin/php I have other scripts running on Gentoo doing much "harder" work and it performs in less than 0.1 second... Sample output: 08/11/2021 15:25:15 - Message 2 sent to mya...@test.com in 1023 ms. 08/11/2021 15:25:16 - Message 3 sent to mya...@test.com in 1022

Postfix spawn

Hi there, We're testing a custom filter for PHP using spawn services. During our tests, we noticed that every time that we invoke the check_policy_service through docker container it takes about 1 second to run the filter script. I first thought it was the local spawn that would be taking too

Re: Postfix-fg and maillog_file to stdout

Yes I can, but only if you send me the config files you want the results for. It will be a pleasure. Em sáb., 6 de nov. de 2021 às 12:28, Viktor Dukhovni < postfix-us...@dukhovni.org> escreveu: > > On 5 Nov 2021, at 5:14 pm, Rafael Azevedo wrote: > > > > POSTFIX logs u

Re: Postfix-fg and maillog_file to stdout

Let me know if you need any help. []s Em sáb., 6 de nov. de 2021 às 10:31, Curtis Maurand escreveu: > > Perfect. That was the other solution I had been looking at. > > ==C >

Re: delete from hold queue

Where did Viktor come from... Definitely not from this Earth. This is the kind of knowledge that comes from Mars... For more humans like you here... cheers! Em sex., 5 de nov. de 2021 às 22:04, Viktor Dukhovni < postfix-us...@dukhovni.org> escreveu: > On Sat, Nov 06, 2021 at 12:32:14AM +0100,

Re: delete from hold queue

There are times when you get temporary blocked and the message has to be delivery. For those cases, hold is a great tool. I do use HOLD for yahoo deliveries very often. BR, R Em qui., 28 de out. de 2021 às 06:12, Bastian Blank escreveu: > On Thu, Oct 28, 2021 at 10:39:52AM +0200, richard

Re: Postfix-fg and maillog_file to stdout

t be possible? > > > > My systems use rsyslog. The timestamp format is configurable. > > > Thanks > > Em sex., 5 de nov. de 2021 às 13:10, Rafael Azevedo > escreveu: > > Thanks Wietse, > > After disabling chroot, everything worked just as expected. > &g

Re: Postfix-fg and maillog_file to stdout

t_delimiter = + smtpd_banner = $myhostname ESMTP $mail_name smtpd_relay_restrictions = permit_mynetworks \ permit_sasl_authenticated \ defer_unauth_destination BR, Rafael Em sex., 5 de nov. de 2021 às 17:59, Rafael Azevedo escreveu: > Viktor, > > I was able to use ISO-DATE format through S

Re: Postfix-fg and maillog_file to stdout

Em sex., 5 de nov. de 2021 às 17:37, Rafael Azevedo escreveu: > Hi Viktor, > Thanks for the reply! > > SELinux is off, but AppArmor on. > > Any further suggestions? > > Thanks > > Em sex., 5 de nov. de 2021 às 17:20, Viktor Dukhovni < > postfix-us...@dukhovni

Re: Postfix-fg and maillog_file to stdout

Hi Viktor, Thanks for the reply! SELinux is off, but AppArmor on. Any further suggestions? Thanks Em sex., 5 de nov. de 2021 às 17:20, Viktor Dukhovni < postfix-us...@dukhovni.org> escreveu: > On Fri, Nov 05, 2021 at 12:00:56PM -0400, Wietse Venema wrote: > > Rafael Azeve

Re: Postfix-fg and maillog_file to stdout

this meta_sequenceId field came from, but I made the day with it. As they say "done is better than perfect". Huge thanks once again here. R Em sex., 5 de nov. de 2021 às 14:46, Wietse Venema escreveu: > Rafael Azevedo: > > Linux docker-1 4.15.0-161-generic #169-Ubuntu S

Re: Postfix-fg and maillog_file to stdout

Linux docker-1 4.15.0-161-generic #169-Ubuntu SMP Fri Oct 15 13:41:54 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Em sex., 5 de nov. de 2021 às 14:09, Wietse Venema escreveu: > Rafael Azevedo: > > One last thing, is it possible to change the date format of the output? > > >

Re: Postfix-fg and maillog_file to stdout

, Rafael Azevedo escreveu: > Thanks Wietse, > > After disabling chroot, everything worked just as expected. > > Thanks a lot guys. > > BR, > R > > Em sex., 5 de nov. de 2021 às 13:01, Wietse Venema > escreveu: > >> Rafael Azevedo: >> > After disabl

Re: Postfix-fg and maillog_file to stdout

Thanks Wietse, After disabling chroot, everything worked just as expected. Thanks a lot guys. BR, R Em sex., 5 de nov. de 2021 às 13:01, Wietse Venema escreveu: > Rafael Azevedo: > > After disabling chroot, it worked! > > LINUX bites, if chroot breaks relative pathnames

Re: Postfix-fg and maillog_file to stdout

After disabling chroot, it worked! Any clue about how can I have milliseconds in this output? Huge thanks. Em sex., 5 de nov. de 2021 às 12:34, Rafael Azevedo escreveu: > This is the maillog_file=/dev/stdout output: > > Nov 05 11:07:15 smtp21 postfix/qmgr[421]: 8A78016204F: fro

Re: Postfix-fg and maillog_file to stdout

/qmgr[421]: 3A280162053: removed Nov 05 11:07:20 smtp21 postfix/qmgr[421]: DA1A6162052: removed Em sex., 5 de nov. de 2021 às 12:32, Rafael Azevedo escreveu: > Sorry about that, I was testing the timestamp withing mail.log. > > root@smtp21:/# postconf -nf > alias_database = hash:

Re: Postfix-fg and maillog_file to stdout

omain datagram socket pathnames. > > > qmgr unix n - n 300 1 qmgr > > smtp unix - - y - - smtp > > relay unix - - y - - smtp > > Wietse > > Rafael Azevedo: &

Re: Postfix-fg and maillog_file to stdout

]: reload -- version 3.4.13, configuration /etc/postfix Where there is "11:06:20.00" it should be something like "11:06:20.123456". Thanks a lot. Em sex., 5 de nov. de 2021 às 12:09, Rafael Azevedo escreveu: > Config follows: > > root@smtp21:/# postconf -nf

Re: Postfix-fg and maillog_file to stdout

Yes I did. Thanks a lot for the help here. As you can see, this is exactly the subject of this message: postfix-fg and stdout. :) But the output shows only qmgr logs. All others are suppressed. Any ideas? Thanks Em sex., 5 de nov. de 2021 às 11:39, escreveu: > > I've set the maillog_file to

Re: Postfix-fg and maillog_file to stdout

Thanks for the reply. I've set the maillog_file to stdout but I don't get other logs (mainly the delivery log comming from smtp process). It just shows qmgr logs in the output. Thanks Em sex., 5 de nov. de 2021 às 11:28, escreveu: > > I'm running postfix on containers and have set logging to

Postfix-fg and maillog_file to stdout

Hi there, I'm running postfix on containers and have set logging to stdout. I notice that just the qmgr logs are sent to stdout, smtp logs are ignored. I don't have syslog installed on this container... Any idea how to fix this? Also, is it possible to use milliseconds in the stdout logging?

Re: [External] SPAM attack from bounce techniques

16, Wietse Venema escreveu: > Rafael Azevedo: > > Hi Kevin, > > I think this might be related to a customized content filter after queue > > that we have. > > How should the content filter answer in case we don't want to accept the > > message neither for bounce

Re: SPAM attack from bounce techniques

:37, Rafael Azevedo escreveu: > Hi there, > > I've noticed that one of our servers is receiving a huge amount of > unauthorized requests. > > User connects to our server and tries to send an email to any destination. > Our servers denies the message because user

Re: [External] SPAM attack from bounce techniques

escreveu: > On 12/29/2020 7:37 AM, Rafael Azevedo wrote: > > Hi there, > > > > I've noticed that one of our servers is receiving a huge amount of > > unauthorized requests. > > > > User connects to our server and tries to send an email to any > > destination

Re: SPAM attack from bounce techniques

t; Ludi > > > > *Von:* owner-postfix-us...@postfix.org *Im > Auftrag von *Rafael Azevedo > *Gesendet:* Dienstag, 29. Dezember 2020 13:38 > *An:* Postfix users > *Betreff:* SPAM attack from bounce techniques > > > > Hi there, > > > > I've notic

SPAM attack from bounce techniques

Hi there, I've noticed that one of our servers is receiving a huge amount of unauthorized requests. User connects to our server and tries to send an email to any destination. Our servers denies the message because user is not authenticated. Then, a bounce is generated to the source address,

Re: Receiving emails from my own address

Huge thanks!! Em sex., 6 de nov. de 2020 às 13:15, Patrick Laimbock escreveu: > On 06-11-2020 13:48, Rafael Azevedo wrote: > > Hi there, > > > > This is an old issue and I believe it has already focused on older > > discussions. > > > > I'm receiving SPA

Re: Receiving emails from my own address

It didn't work. :( Em sex., 6 de nov. de 2020 às 11:30, Matus UHLAR - fantomas < uh...@fantomas.sk> escreveu: > On 06.11.20 11:10, Rafael Azevedo wrote: > >How can smtpd_sender_login_maps fix this issue? > >As far as I know, this is only a shortcut for authentication. &g

Re: Receiving emails from my own address

e nov. de 2020 às 10:42, Matus UHLAR - fantomas < uh...@fantomas.sk> escreveu: > On 06.11.20 09:48, Rafael Azevedo wrote: > >This is an old issue and I believe it has already focused on older > >discussions. > > > >I'm receiving SPAM from my own address. &g

Receiving emails from my own address

Hi there, This is an old issue and I believe it has already focused on older discussions. I'm receiving SPAM from my own address. Checking server logs, user is not authenticating and the only way this spammer can play a trick is by sending an email to its own address (ie: from

Re: Reject Chinese mail

I've blocked the entire ASIA netblocks in my ASN. We don't exchange any information with that part of the world, neither any of our customers. All we get from that part of the world is DDoS attacks, brute force attacks and spam. Sorry for those who don't agree with me, its ok, but I got tired of

Re: Postfix audit

Thank you Viktor, We already have that log, but they're asking for additional confirmation. Thanks in advance. Em qua, 12 de jun de 2019 às 16:11, Viktor Dukhovni escreveu: > > On Wed, Jun 12, 2019 at 03:52:10PM -0300, Rafael Azevedo wrote: > > > Its the communication betw

Re: Postfix audit

> RESULT (ACCEPTED OR REJECTED)[final destination's server] They need to have the confirmation of the acceptance of the message by the final destination's provider. Em qua, 12 de jun de 2019 às 15:19, Viktor Dukhovni escreveu: > > On Wed, Jun 12, 2019 at 09:51:45AM -0300, Rafael Aze

Re: Postfix audit

What we need is a complete conversation between the servers. We're being requested to give the detailed messages between the servers to validate the message delivery. This would be an example of the log needs: 2019-06-12 12:44:47 SERVER -> CLIENT: 220 indus.server.net ESMTP Postfix 2019-06-12

Re: Postfix audit

Hi Wietse, Could you please give me more details about option 2 (SMTP-level splitter) ? Thanks in advance. BR, Em ter, 11 de jun de 2019 às 12:37, Wietse Venema escreveu: > > Rafael Azevedo: > > I need the full SMTP transaction, commands such as EHLO, MAIL FROM:, > >

Re: Postfix audit

I need the full SMTP transaction, commands such as EHLO, MAIL FROM:, RCPT TO:, and DATA... Em ter, 11 de jun de 2019 às 11:50, @lbutlr escreveu: > > On Jun 11, 2019, at 8:30 AM, @lbutlr wrote: > > Maybe 'relay=.*\]:25’? > > Looking at my logs it looks like > > '\]:25:’ is enough. > > -- >

Postfix audit

Hi guys, We're in an audit process here and this is giving us a headech. Is there anyway to log the MTA to MTA transactions one per file? For example, client requests to send a message, the MTA says OK, sends the message and keep a log of the MTA to MTA transaction. Thanks in advance. BR,

Re: Blacklist honeypot senders

Hi there, I've done that by building a policy filter that bans those IPs using iptables whenever those trap accounts get reached. It wasn't that easy, but its beautiful how it's working. Chain SPAMBLOCK (X references) pkts bytes target prot opt in out source destination 0 0

Re: Release from HOLD

nf -n | grep -i transport > > > > -ANGELO FAZZINA > > ang...@uconn.edu > University of Connecticut, ITS, SSG, Server Systems > 860-486-9075 > > -Original Message- > From: owner-postfix-us...@postfix.org On > Behalf Of Rafael Azevedo > Sent: Thursday,

Release from HOLD

Hi guys, I had a failure in one of our postfix routines that sent all messages to HOLD. Now, I'm trying to release from HOLD using 'postsuper -H ALL'. The thing is that all messages are being deferred (mail transport unavailable). So, is there a way to check current message transport and maybe

Re: Content filter - reijnect message back into queue

> it can be any port, but it has to be configured not to send mail back > to the filter not to create a loop. this is what I'm trying to figure out: how to re-inject. I'm reading The Book of Postfix as Viktor suggested. Hope to find some answers soon. Thanks!

Re: Content filter - reijnect message back into queue

Can the reinjection port be other than 10025 ?

Re: Content filter - reijnect message back into queue

> No you did not. By default "MAIL_CONFIG=/etc/postfix" with no trailing "/". > Perhaps you're starting Postfix via: > > postfix -c /etc/postfix/ start this is how we start postfix intances since this server has multiple testing configurations. > don't do that. why? and why shall I

Re: Content filter - reijnect message back into queue

> Well, I don't recall any mention of multiple Postfix configurations > until now. For "sendmail" to work in a non-default Postfix instance > the associated configuration directory must be listed in the default > instance's main.cf file's "alternate_config_directories" parameter. Ok, got it back

Re: Content filter - reijnect message back into queue

2019 às 21:33, Viktor Dukhovni escreveu: > > > > > On Jan 4, 2019, at 6:18 PM, Rafael Azevedo wrote: > > > > # postmulti -l > > - - y /etc/postfix > > > > # postfix status > > postfix: Postfix is running with bac

Re: Content filter - reijnect message back into queue

fifo -u -o syslog_name=xx.net MAIL_CONFIG=/etc/mailservers/xx.net/host.xx.net/ MAIL_LOGTAG=postfix LANG=C GENERATION=15302 Em sex, 4 de jan de 2019 às 20:43, Viktor Dukhovni escreveu: > > > On Jan 4, 2019, at 5:13 PM, Rafael Azevedo wrote: > > > > They don't. But there

Re: Content filter - reijnect message back into queue

They don't. But there might be some variable with undesired default value. # cd /etc/postfix/ lab postfix # grep 'config_directory' main.cf master.cf lab postfix # Em sex, 4 de jan de 2019 às 20:11, Viktor Dukhovni escreveu: > > > > > On Jan 4, 2019, at 4:59 PM, Rafael

Re: Content filter - reijnect message back into queue

> THAT IS POLICY DELEGATION PROTOCOL NOT CONTENT FILTER. What are the differences?

Re: Content filter - reijnect message back into queue

In fact I didn't. There's no config_directory set in my main.cf file. Em sex, 4 de jan de 2019 às 18:46, Viktor Dukhovni escreveu: > > > On Jan 4, 2019, at 3:37 PM, Rafael Azevedo wrote: > > > > Jan 4 17:41:54 lab postfix/pipe[2027085]: EE5D013E179F: > > to=, rela

Re: Content filter - reijnect message back into queue

into Postfix. > > On 04.01.19 16:47, Rafael Azevedo wrote: > >Would you please tell me how to send it back to POSTFIX ? > > call sendmail and pass te message to it, or sent it to postfix via > SMTP/LMTP, apparently on different port where content_filter is turned off, > so postfix do

Re: Content filter - reijnect message back into queue

> FILTER_README has examples for doing that with /usr/sbin/sendmail > and with SMTP. Has anybody ever made that example work? There's no way. post_queue_content_filterunix- n n - - pipe flags=Rq user=myuser null_sender=

Re: Content filter - reijnect message back into queue

in Postfix 2.0 and later. What am I missing here? Thanks! BR, Rafael Em sex, 4 de jan de 2019 às 16:57, Rafael Azevedo escreveu: > > Digging on FILTER_README, I've noticed that: > > The content_filter setting has lower precedence than a FILTER > action that is specified

Re: Content filter - reijnect message back into queue

Digging on FILTER_README, I've noticed that: The content_filter setting has lower precedence than a FILTER action that is specified in an access(5), header_checks(5) or body_checks(5) table. Even using OK, PREPEND, the message could not go back into queue. JIT: ACCEPT ACTIONS OK

Re: Content filter - reijnect message back into queue

Hi Wietse, Thanks for your help. > You forgot to send it back into Postfix. Would you please tell me how to send it back to POSTFIX ? > BTW what is that "action=PERMIT" stuff? There is no such feature > with Postfix filters. Are you confusing SMTPD_POLICY_README and > FILTER_README? Yes, I

Re: Content filter - reijnect message back into queue

ivered via post_queue_content_filter service) BR, Rafael Em sex, 4 de jan de 2019 às 15:28, Viktor Dukhovni < postfix-us...@dukhovni.org> escreveu: > > > > On Jan 4, 2019, at 11:54 AM, Rafael Azevedo wrote: > > > > So I kindly ask you guys how can I re-inject message bac

Re: Content filter - reijnect message back into queue

org> escreveu: > > > > On Jan 4, 2019, at 11:54 AM, Rafael Azevedo wrote: > > > > So I kindly ask you guys how can I re-inject message back into queue. > > http://www.postfix.org/FILTER_README.html > > -- > Viktor. > >

Content filter - reijnect message back into queue

Hi there, I'm trying to build my own content filter so I can actually filter outgoing messages and take appropriated actions upon spam messages. After some time I was able to make postfix send messages to the content filter. The documentation says that content_filter expects a "transport:maps"

Re: Postfix 2.10.0 to be released soon

Nice Wietse! Have you published a what has changed list already? Thanks and congrats. Cheers Rafael Em 04/02/2013, às 23:30, Wietse Venema wie...@porcupine.org escreveu: postfix-2.10.0-RC1 gives a preview of what the upcoming stable release will look like. I'll make one more pass over the

Re: Balancing destination concurrency + rate delay

I read that warning, but wasn't sure I understood it properly. I know that setting destination recipient limit to anything above one defines a destination as a domain, so by setting it to 2 we're saying wait 1s between every delivery to a Yahoo domain, right? And if every message sent is

Re: smtp_fallback_relay and greylists

It says use the same host. It does not say use the same myhostname setting. Thanks once again Wietse! Your help is very appreciated. I'll try to work on this. BR, - Rafael

Messages stucked in maildrop folder

Hi Guys, I noticed that a specific SMTP has lots of files on maildrop folder, and I dont know why postfix is not sending theses messages neither to its destination or back to sender. I tried reading this document (http://www.postfix.org/MAILDROP_README.html) but could not understand how to

Re: Messages stucked in maildrop folder

Just to share with everyone (in case somebody see this problem in the future), it seems to be fixed after I added this to main.cf: mailbox_command = /usr/bin/maildrop -d ${USER} After that all messages went through. BR - Rafael - Mensagem original - De: Rafael Azevedo raf

Re: smtp_fallback_relay and greylists

It says use the same host. It does not say use the same myhostname setting. Wietse, Could you please tell me the difference of same host and myhostname? What I understood from the document is that its suggested to use the same host/ip to re-send the message in cases of greylists. In my case,

Re: smtp_fallback_relay and greylists

A host is a computer (or virtual machine). myhostname is a Postfix parameter. Now plug these into the context of Wietse's statement to you and you should understand. Thanks Stan! But if I point it to another host (different than myhostname) it will send through another IP right? I'm not

Re: smtp_fallback_relay and greylists

smtp_bind_address sets the SOURCE IP address. Yes, but I cant have 2 servers with same smtp_bind_address - Rafael

Mail sending failures when destination has multiple MX servers

Hi Guys, I noticed lots of errors like this on my log files: Client host rejected: Please try primary mx first (in reply to RCPT TO command)) So I checked the domain and it has multiple mx servers, with different priority each one. Then I ask: why is postfix using secondary mx server

Re: Mail sending failures when destination has multiple MX servers'

Why do you believe the error messageas from random mail servers? Because for some reason the secondary mail server is telling me to send to primary first, very simple. If it were sending to primary, then we should not get this error, right? But maybe the DNS is giving me wrong information

Re: Mail sending failures when destination has multiple MX servers'

Thanks to Robert and Wietse, it was very clearful. -- Rafael

smtp_fallback_relay and greylists

Hello guys! I was reading the smtp_fallback_relay doc at http://www.postfix.org/postconf.5.html#smtp_fallback_relay and couldn't be able to make it work. It says: smtp_fallback_relay (default: $fallback_relay) […] With bulk email deliveries, it can be beneficial to run the

Re: Question about SMTP Relay per destination

. Thanks in advance. -- Rafael Em 12/01/2013, às 20:57, Wietse Venema wie...@porcupine.org escreveu: Rafael Azevedo - IAGENTE: We're having problems to deliver to specific destination because of too many opened connections from the same domain (its spread over lots of SMTP servers connection

Re: Question about SMTP Relay per destination

Wietse Venema wie...@porcupine.org wrote: - If you mean something else, please stop wasting my time. Thank you for your time. - Rafael

Question about SMTP Relay per destination

Hi Guys, We have lots of SMTPs running on different IPs sending to many different destinations. So what I need to do is, if any of this SMTP receives an email to specific destination, the mail must be relayed to a specific SMTP. We work with named transports for this specific domains, so I

Re: Relay

Hi Ramesh, I had a similar problem, but not using Amazon services. I'd suggest you to check your DKIM configuration since its little bit tricky. This is my suggestion: 1) Check your trusted-hosts file and make sure your sending server's IP is on that list 2) Check your key list and make sure

Re: Relay

Also, as far as I know postfix won't add any SPF header to your sending messages. I think it will check for SPF for incoming mail only, so check your domain and see if your DNS has any TXT valid SPF record. -- Rafael Em 12/01/2013, às 07:50, Ramesh itsrames...@yahoo.co.in escreveu: Hi

Re: destination_rate_delay and connection_reuse_time_limit

Em 08/01/2013, às 17:16, Wietse Venema wie...@porcupine.org escreveu: Reindl Harald: Big deal. Now I can block all mail for gmail.com by getting 100 email messages into your queue how comes? how do you get gmail.com answer to any delivery from you with 4xx? He wants to temporarily

Re: destination_rate_delay and connection_reuse_time_limit

Barring a clean slow down signal, and a stable feedback mechanism, the only strategy is manually tuned rate delays, and spreading the load over multiple sending IPs (Postfix instances don't help if they share a single IP). I have multiple instances of Postfix running on multiple IPs. The

Re: destination_rate_delay and connection_reuse_time_limit

I agree with Reindl, I guess Witsie is now better understanding the problem here. I'd see this as a additional feature, not default configuration. It would be even better if that could be parametrized on named transport basis. - Rafael Em 08/01/2013, às 19:02, Reindl Harald

Re: destination_rate_delay and connection_reuse_time_limit

When faced with a destination that imposes tight rate limits you must pre-configure your MTA to always stay under the limits. Nothing good happens when the Postfix output rate under load exceeds the remote limit whether you throttle the queue repeatedly or not. But many times we just don't

Re: destination_rate_delay and connection_reuse_time_limit

That's not what happens when a destination is throttled, all mail there is deferred, and is retried some indefinite time later that is at least 5 minutes but perhaps a lot longer, and at great I/O cost, with expontial backoff for each message based on time in the queue, … I totally disagree

Re: destination_rate_delay and connection_reuse_time_limit

I was watching my log files now looking for deferred errors, and for my surprise, we got temporary blocked by Yahoo on some SMTPs (ips), as shown: Jan 9 13:20:52 mxcluster yahoo/smtp[8593]: 6731A13A2D956: host mta5.am0.yahoodns.net[98.136.216.25] refused to talk to me: 421 4.7.0 [TS02]

Re: destination_rate_delay and connection_reuse_time_limit

There's gotta be a solution for this. There is - you need to register your mailserver(s) with yahoo You mean Yahoo's Feedback Program (feedbackloop.yahoo.net) ? - Rafael

Re: destination_rate_delay and connection_reuse_time_limit

...@johnpeach.com escreveu: On Wed, 9 Jan 2013 13:37:00 -0200 Rafael Azevedo - IAGENTE raf...@iagente.com.br wrote: There's gotta be a solution for this. There is - you need to register your mailserver(s) with yahoo You mean Yahoo's Feedback Program (feedbackloop.yahoo.net) ? I forget exactly what

Re: destination_rate_delay and connection_reuse_time_limit

I was watching my log files now looking for deferred errors, and for my surprise, we got temporary blocked by Yahoo on some SMTPs (ips), as shown: Jan 9 13:20:52 mxcluster yahoo/smtp[8593]: 6731A13A2D956: host mta5.am0.yahoodns.net[98.136.216.25] refused to talk to me: 421 4.7.0 [TS02]

Re: destination_rate_delay and connection_reuse_time_limit

Rafael Azevedo - IAGENTE: I was watching my log files now looking for deferred errors, and for my surprise, we got temporary blocked by Yahoo on some SMTPs (ips), as shown: Jan 9 13:20:52 mxcluster yahoo/smtp[8593]: 6731A13A2D956: host mta5.am0.yahoodns.net[98.136.216.25] refused to talk

Re: destination_rate_delay and connection_reuse_time_limit

Now Yahoo is giving another response: said: 451 Message temporarily deferred - [160] (in reply to end of DATA command) See, this is very hard to solve. I'm really truing to better understand the problem in order to find out the best solution. I'd like to thank in advance for the help, its

Re: destination_rate_delay and connection_reuse_time_limit

hosted on this provider that are being blocked. Any help would be very appreciated. Thanks in advance. Att. -- Rafael Azevedo | IAGENTE Fone: 51 3086.0262 MSN: raf...@hotmail.com Visite: www.iagente.com.br Em 07/01/2013, às 15:57, Viktor Dukhovni postfix-us...@dukhovni.org escreveu

Re: destination_rate_delay and connection_reuse_time_limit

terms. Anyway, thanks for your time and all the help. It was for sure very appreciated. Any help here would also be appreciated. Thanks in advance. Att. -- Rafael Azevedo | IAGENTE Fone: 51 3086.0262 MSN: raf...@hotmail.com Visite: www.iagente.com.br Em 08/01/2013, às 12:09, Wietse Venema wie

Re: destination_rate_delay and connection_reuse_time_limit

stop trying at least for a while. Att. -- Rafael Azevedo | IAGENTE Fone: 51 3086.0262 MSN: raf...@hotmail.com Visite: www.iagente.com.br Em 08/01/2013, às 13:34, Wietse Venema wie...@porcupine.org escreveu: Rafael Azevedo - IAGENTE: I truly believe that postfix is the best MTA ever, but you

Re: destination_rate_delay and connection_reuse_time_limit

Em 08/01/2013, às 14:21, Wietse Venema wie...@porcupine.org escreveu: Rafael Azevedo - IAGENTE: Why keep trying when we have a clear signal of a temporary error? As Victor noted Postfix does not keep trying the SAME delivery. Yes you're right and I know that. But it keeps trying for another

Re: destination_rate_delay and connection_reuse_time_limit

Att. -- Rafael Azevedo | IAGENTE Fone: 51 3086.0262 MSN: raf...@hotmail.com Visite: www.iagente.com.br Em 08/01/2013, às 14:07, Viktor Dukhovni postfix-us...@dukhovni.org escreveu: On Tue, Jan 08, 2013 at 01:59:14PM -0200, Rafael Azevedo - IAGENTE wrote: But Witse, would you agree with me

  1   2   >