Re: Problems with postfix while sending emails
Steve Jenkins put forth on 3/15/2011 10:16 PM: On Tue, Mar 15, 2011 at 8:54 PM, Stan Hoeppner s...@hardwarefreak.com wrote: Steve Jenkins put forth on 3/15/2011 1:34 PM: and anyone not signing should consider it. Anyone not using seat belts and turn signals should consider it. I can see a clear advantage to the latter, but not the former. Can you briefly explain why you believe everyone should sign mail? Of course, we both know there's no magic bullet. But signing can help receivers verify the true provenance of the sender's message. Does it guarantee that the message isn't SPAM? Of course not. Every SPAM I've received from a GMail account has been signed. :) The bot spam problem has been largely solved on the receiving end. DKIM only protects against forged mail. Bot spam is where most of the forging takes place. Snowshoe spammers don't forge sender domains. They purchase cheap throw away domains by the millions. If all legit senders implemented DKIM tomorrow it would change nothing, unless all receivers REQUIRED DKIM sigs. If that were to happen, snowshoe spammers would simply start signing, eliminating any minute benefit it currently has. And then there's still the phishing and 419 problem with hacked freemail accounts, where DKIM is totally useless. But can signing help identify and/or deter some spammers? Sure. And Identify and deter spammers? Louisiana farm land for sale? ;) with optional ADSP extension to DKIM, it's even better. I see no downside to signing, and therefore ANY potential upside is a good thing. The resource overhead of DKIM signing and verifying is very low, so what good reason is there to NOT sign? One downside is that one must install a milter, policy daemon, and/or content filter to send, or verify a DKIM sig and then score the message. Frankly, I don't know how to answer your 20% question. Maybe on your system, 20% is as good as it's gonna get! But based on what I know That's probably because it was a rhetorical question. DKIM can't do anything to help block that 20% because it *is* signed. about you, I get the sense you're someone who primarily deals with lots of incoming mail. And it always seems that where one stands Yes, 99% of my mail flow is inbound. depends on where one sits. :) I'm sitting on the other side. We process very little incoming mail, but send millions of legitimate emails to our customers every week. DKIM signing them has undeniably increased our inbox deliverability rates, and inbound processors can know that if a mail claims to come from us but isn't signed, it's bogus. As I mentioned above, the forged mail problem is almost entirely bot spam, solved by all other means before DKIM. The only reason your deliverability increased is because those receivers *require* DKIM for bulk senders. If you recall DKIM's genesis was at Yahoo, one of the largest receivers on the planet. Funny how it's only good for gorillas, and does nothing for the vast majority of other MXen on the planet. Again, with no downside and little-to-no cost, even a small potential upside is a good thing. Not in this case. There is no DKIM upside for most receivers, esp those not using scoring filters. And I'm guessing those already using scoring content filters (SA) and/or policy daemons have more than enough scoring criteria already to block most spam, and that adding a score for DKIM pass would do nothing to catch the few that get through. -- Stan
Re: Problems with postfix while sending emails
Stan Hoeppner: The bot spam problem has been largely solved on the receiving end. DKIM only protects against forged mail. Bot spam is where most of the forging takes place. Snowshoe spammers don't forge sender domains. Stan, He uses DKIM as part of a whitelisting agreement with mail receivers. No, it does not remove the bad guys from the spam sending pool. We know that, and there is no need to hammer on that. As long as RSA isn't broken, Steve can use DKIM to get preferred treatment for his email: less filtering means fewer false positives. Wietse
Re: Problems with postfix while sending emails
Hi Guys! I'm having a hard time with postfix while I try to send emails using my PF-SERVER. Postfix is running perfectly, the problem is that I get some delay when sending the emails depending on the sender's domain address. In this case, the problematic domain name is zoom4u.com.br. I've checked the MX records for this domain and this is what I get: # host -t mx zoom4u.com.br zoom4u.com.br mail is handled by 30 ASPMX4.GOOGLEMAIL.COMhttp://aspmx4.googlemail.com/ . zoom4u.com.br mail is handled by 30 ASPMX5.GOOGLEMAIL.COMhttp://aspmx5.googlemail.com/ . zoom4u.com.br mail is handled by 10 ALT1.ASPMX.L.GOOGLE.COMhttp://alt1.aspmx.l.google.com/ . zoom4u.com.br mail is handled by 10 mail.zoom4u.com.br. zoom4u.com.br mail is handled by 20 ALT2.ASPMX.L.GOOGLE.COMhttp://alt2.aspmx.l.google.com/ . zoom4u.com.br mail is handled by 20 ASPMX.L.GOOGLE.COMhttp://aspmx.l.google.com/ . zoom4u.com.br mail is handled by 30 ASPMX2.GOOGLEMAIL.COMhttp://aspmx2.googlemail.com/ . zoom4u.com.br mail is handled by 30 ASPMX3.GOOGLEMAIL.COMhttp://aspmx3.googlemail.com/ . For another domain that send extremally fast: # host -t mx iagentemail.com.br iagentemail.com.br mail is handled by 10 mail.iagentemail.com.br. When I use any domain different than zoom4u.com.br, postfix accepts the messages very very fast, up to 40 messages per second. When I change the sender to zoom4u.com.br it sends up to 2 messages per second. I had to publish my POSTCONF -d at http://187.1.133.20/postconf.txt because postfix-users mailing list blocks messages with more than 40.000 chars. Anybody has any idea about how to fix this? Thanks in advance. Rafeal
Re: Problems with postfix while sending emails
Rafael Azevedo: I had to publish my POSTCONF -d at Send postconf -n not postconf -d. Which blog gives this false information?
Re: Problems with postfix while sending emails
Hi Wietse, Thanks for helping me. This is my postconf -n: bounce_queue_lifetime = 1h broken_sasl_auth_clients = yes command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/lib/postfix data_directory = /var/lib/mailservers/mxcluster.iagentemail.com.br debug_peer_level = 5 default_destination_concurrency_limit = 5 html_directory = /usr/share/doc/postfix-2.2.10/html inet_interfaces = $myhostname initial_destination_concurrency = 5 mail_owner = postfix mail_spool_directory = /var/spool/mail mailq_path = /usr/bin/mailq manpage_directory = /usr/share/man maximal_queue_lifetime = 15m milter_default_action = accept milter_protocol = 2 mydestination = $myhostname, localhost.$mydomain, localhost mydomain = mx01.iagentemail.com.br myhostname = mx01.iagentemail.com.br mynetworks = 168.100.189.0/28, 127.0.0.0/8, 187.1.133.0/24 mynetworks_style = class myorigin = $mydomain newaliases_path = /usr/bin/newaliases non_smtpd_milters = inet:localhost:20209, unix:/var/run/dkim-filter/dkim-filter.sock queue_directory = /var/spool/mailservers/mxcluster.iagentemail.com.br readme_directory = /usr/share/doc/postfix-2.2.10/readme relay_domains = mysql:/etc/postfix/mysql_relay_domains_maps.cf sample_directory = /etc/postfix sendmail_path = /usr/sbin/sendmail setgid_group = postdrop smtp_connection_cache_destinations = terra.com.br bol.com.br zaz.com.br uol.com.br ig.com.br hotmail.com gmail.com weg.net yahoo.com yahoo.com.br smtp_connection_cache_on_demand = yes smtp_connection_cache_time_limit = 60s smtpd_client_connection_count_limit = 100 smtpd_delay_reject = no smtpd_error_sleep_time = 0 smtpd_helo_restrictions = check_helo_access regexp:/etc/postfix/helo-proibidos , reject_invalid_hostname reject_unknown_hostname, reject_non_fqdn_hostname smtpd_milters = inet:localhost:20209, unix:/var/run/dkim-filter/dkim-filter.sock smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, check_relay_domains, reject_non_fqdn_hostname, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_unauth_destination, reject_unauth_pipelining, reject_unverified_recipient, reject_unknown_recipient_domain, reject_invalid_hostname, reject_rbl_client opm.blitzed.org, reject_rbl_client list.dsbl.org, reject_rbl_client bl.spamcop.net, reject_rbl_client sbl-xbl.spamhaus.org smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_security_options = noanonymous smtpd_sender_restrictions = reject_unknown_sender_domain, reject_non_fqdn_sender unknown_local_recipient_reject_code = 550 virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf virtual_gid_maps = static:207 virtual_mailbox_base = /home/vmail virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains_maps.cf virtual_mailbox_limit = 5120 virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf virtual_minimum_uid = 207 virtual_transport = virtual virtual_uid_maps = static:207 On Tue, Mar 15, 2011 at 10:00 AM, Wietse Venema wie...@porcupine.orgwrote: Rafael Azevedo: I had to publish my POSTCONF -d at Send postconf -n not postconf -d. Which blog gives this false information?
Re: Problems with postfix while sending emails
Rafael Azevedo: Hi Guys! I'm having a hard time with postfix while I try to send emails using my PF-SERVER. Postfix is running perfectly, the problem is that I get some delay when sending the emails depending on the sender's domain address. Can you show a good example from the mail LOGFILE? Can you show a bad example from the mail LOGFILE? You can replace the username by XXX. Wietse
Re: Problems with postfix while sending emails
Hi Wietse! Thanks again for helping me! Here is the postfix log: # SLOW DOMAIN Mar 15 10:37:46 mxcluster postfix/smtpd[22804]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:46 mxcluster postfix/smtpd[22804]: 70E82E42D0: client= srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:46 mxcluster postfix/cleanup[21751]: 70E82E42D0: message-id= 8d3ee53c5d281ab3dae9471182931...@iagentemail.com.br Mar 15 10:37:46 mxcluster dkim-filter[4513]: 70E82E42D0 DKIM-Signature header added Mar 15 10:37:47 mxcluster postfix/qmgr[27773]: 70E82E42D0: from= reto...@iagentemail.com.br, size=629, nrcpt=2 (queue active) Mar 15 10:37:47 mxcluster postfix/smtpd[22804]: lost connection after RSET from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:47 mxcluster postfix/smtpd[22804]: disconnect from srv01.iagentemail.com.br[189.38.86.124] # FASTER DOMAIN Mar 15 10:37:47 mxcluster postfix/smtpd[19313]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:47 mxcluster postfix/smtpd[19313]: 45B50E42F5: client= srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:47 mxcluster postfix/cleanup[22025]: 45B50E42F5: message-id= 950c281e36abb9600cdf730baff00...@iagentemail.com.br Mar 15 10:37:47 mxcluster dkim-filter[4513]: 45B50E42F5 DKIM-Signature header added Mar 15 10:37:47 mxcluster postfix/smtp[23002]: 70E82E42D0: host mx2.iagente.com.br[189.38.95.92] said: 450 4.7.1 Client host rejected: cannot find your hostname, [187.1.133.20] (in reply to RCPT TO command) Mar 15 10:37:47 mxcluster postfix/qmgr[27773]: 45B50E42F5: from= reto...@iagentemail.com.br, size=630, nrcpt=2 (queue active) Mar 15 10:37:47 mxcluster postfix/smtpd[19313]: lost connection after RSET from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:47 mxcluster postfix/smtpd[19313]: disconnect from srv01.iagentemail.com.br[189.38.86.124] Thanks in advance. Rafael On Tue, Mar 15, 2011 at 10:14 AM, Wietse Venema wie...@porcupine.orgwrote: Rafael Azevedo: Hi Guys! I'm having a hard time with postfix while I try to send emails using my PF-SERVER. Postfix is running perfectly, the problem is that I get some delay when sending the emails depending on the sender's domain address. Can you show a good example from the mail LOGFILE? Can you show a bad example from the mail LOGFILE? You can replace the username by XXX. Wietse
Re: Problems with postfix while sending emails
Rafael Azevedo: [ Charset ISO-8859-1 unsupported, converting... ] Hi Wietse! Thanks again for helping me! Here is the postfix log: # SLOW DOMAIN Mar 15 10:37:46 mxcluster postfix/smtpd[22804]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:46 mxcluster postfix/smtpd[22804]: 70E82E42D0: client= srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:46 mxcluster postfix/cleanup[21751]: 70E82E42D0: message-id= 8d3ee53c5d281ab3dae9471182931...@iagentemail.com.br Mar 15 10:37:46 mxcluster dkim-filter[4513]: 70E82E42D0 DKIM-Signature header added Mar 15 10:37:47 mxcluster postfix/qmgr[27773]: 70E82E42D0: from= reto...@iagentemail.com.br, size=629, nrcpt=2 (queue active) Mar 15 10:37:47 mxcluster postfix/smtp[23002]: 70E82E42D0: host mx2.iagente.com.br[189.38.95.92] said: 450 4.7.1 Client host rejected: cannot find your hostname, [187.1.133.20] (in reply to RCPT TO command) Mar 15 10:37:47 mxcluster postfix/smtpd[22804]: lost connection after RSET from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:47 mxcluster postfix/smtpd[22804]: disconnect from srv01.iagentemail.com.br[189.38.86.124] The above message is rejected because 187.1.133.20 has no PTR record. You forgot the logfile record with the status=xxx and delay=yyy of message 70E82E42D0. # FASTER DOMAIN Mar 15 10:37:47 mxcluster postfix/smtpd[19313]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:47 mxcluster postfix/smtpd[19313]: 45B50E42F5: client= srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:47 mxcluster postfix/cleanup[22025]: 45B50E42F5: message-id= 950c281e36abb9600cdf730baff00...@iagentemail.com.br Mar 15 10:37:47 mxcluster dkim-filter[4513]: 45B50E42F5 DKIM-Signature header added Mar 15 10:37:47 mxcluster postfix/qmgr[27773]: 45B50E42F5: from= reto...@iagentemail.com.br, size=630, nrcpt=2 (queue active) Mar 15 10:37:47 mxcluster postfix/smtpd[19313]: lost connection after RSET from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:47 mxcluster postfix/smtpd[19313]: disconnect from srv01.iagentemail.com.br[189.38.86.124] You forgot the logfile record with the status=xxx and delay=yyy of message 45B50E42F5. Wietse
Re: Problems with postfix while sending emails
Hi, Actually I believe that there is a DNS problem on that MX server, cause PTR is set properly. The delay is not on the delivery, but when my application connects to the MX SERVER and send the messages. When using ZOOM4U.COM.BR, my application sends only 2 messages per second and there is no limitation in that system. When I change the sender domain, the application almost burns the server with the very fast sending messages. The log file for the google account (the delivery worked cause there is no DNS problems there). Mar 15 11:14:22 mxcluster postfix/smtp[2891]: 8F8C3FAC35: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.159.27]:25, delay=4.3, delays=0.53/0.01/0.52/3.2, dsn=2.0.0, status=sent (250 2.0.0 OK 1300198390 d10si21857046and.121) Again, the delay is when I connect to the SMTP to SEND the email FROM THE APPLICATION. The SMTP is sending messages really fast to other SMTPs. Thanks in advance. Rafael On Tue, Mar 15, 2011 at 11:10 AM, Wietse Venema wie...@porcupine.org wrote: Rafael Azevedo: [ Charset ISO-8859-1 unsupported, converting... ] Hi Wietse! Thanks again for helping me! Here is the postfix log: # SLOW DOMAIN Mar 15 10:37:46 mxcluster postfix/smtpd[22804]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:46 mxcluster postfix/smtpd[22804]: 70E82E42D0: client= srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:46 mxcluster postfix/cleanup[21751]: 70E82E42D0: message-id= 8d3ee53c5d281ab3dae9471182931...@iagentemail.com.br Mar 15 10:37:46 mxcluster dkim-filter[4513]: 70E82E42D0 DKIM-Signature header added Mar 15 10:37:47 mxcluster postfix/qmgr[27773]: 70E82E42D0: from= reto...@iagentemail.com.br, size=629, nrcpt=2 (queue active) Mar 15 10:37:47 mxcluster postfix/smtp[23002]: 70E82E42D0: host mx2.iagente.com.br[189.38.95.92] said: 450 4.7.1 Client host rejected: cannot find your hostname, [187.1.133.20] (in reply to RCPT TO command) Mar 15 10:37:47 mxcluster postfix/smtpd[22804]: lost connection after RSET from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:47 mxcluster postfix/smtpd[22804]: disconnect from srv01.iagentemail.com.br[189.38.86.124] The above message is rejected because 187.1.133.20 has no PTR record. You forgot the logfile record with the status=xxx and delay=yyy of message 70E82E42D0. # FASTER DOMAIN Mar 15 10:37:47 mxcluster postfix/smtpd[19313]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:47 mxcluster postfix/smtpd[19313]: 45B50E42F5: client= srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:47 mxcluster postfix/cleanup[22025]: 45B50E42F5: message-id= 950c281e36abb9600cdf730baff00...@iagentemail.com.br Mar 15 10:37:47 mxcluster dkim-filter[4513]: 45B50E42F5 DKIM-Signature header added Mar 15 10:37:47 mxcluster postfix/qmgr[27773]: 45B50E42F5: from= reto...@iagentemail.com.br, size=630, nrcpt=2 (queue active) Mar 15 10:37:47 mxcluster postfix/smtpd[19313]: lost connection after RSET from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:47 mxcluster postfix/smtpd[19313]: disconnect from srv01.iagentemail.com.br[189.38.86.124] You forgot the logfile record with the status=xxx and delay=yyy of message 45B50E42F5. Wietse
Re: Problems with postfix while sending emails
Looks like POSTFIX is checking something on each delivery try using the SENDER DOMAIN. On Tue, Mar 15, 2011 at 11:17 AM, Rafael Azevedo raf...@gmail.com wrote: Hi, Actually I believe that there is a DNS problem on that MX server, cause PTR is set properly. The delay is not on the delivery, but when my application connects to the MX SERVER and send the messages. When using ZOOM4U.COM.BR, my application sends only 2 messages per second and there is no limitation in that system. When I change the sender domain, the application almost burns the server with the very fast sending messages. The log file for the google account (the delivery worked cause there is no DNS problems there). Mar 15 11:14:22 mxcluster postfix/smtp[2891]: 8F8C3FAC35: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.159.27]:25, delay=4.3, delays=0.53/0.01/0.52/3.2, dsn=2.0.0, status=sent (250 2.0.0 OK 1300198390 d10si21857046and.121) Again, the delay is when I connect to the SMTP to SEND the email FROM THE APPLICATION. The SMTP is sending messages really fast to other SMTPs. Thanks in advance. Rafael On Tue, Mar 15, 2011 at 11:10 AM, Wietse Venema wie...@porcupine.org wrote: Rafael Azevedo: [ Charset ISO-8859-1 unsupported, converting... ] Hi Wietse! Thanks again for helping me! Here is the postfix log: # SLOW DOMAIN Mar 15 10:37:46 mxcluster postfix/smtpd[22804]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:46 mxcluster postfix/smtpd[22804]: 70E82E42D0: client= srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:46 mxcluster postfix/cleanup[21751]: 70E82E42D0: message-id= 8d3ee53c5d281ab3dae9471182931...@iagentemail.com.br Mar 15 10:37:46 mxcluster dkim-filter[4513]: 70E82E42D0 DKIM-Signature header added Mar 15 10:37:47 mxcluster postfix/qmgr[27773]: 70E82E42D0: from= reto...@iagentemail.com.br, size=629, nrcpt=2 (queue active) Mar 15 10:37:47 mxcluster postfix/smtp[23002]: 70E82E42D0: host mx2.iagente.com.br[189.38.95.92] said: 450 4.7.1 Client host rejected: cannot find your hostname, [187.1.133.20] (in reply to RCPT TO command) Mar 15 10:37:47 mxcluster postfix/smtpd[22804]: lost connection after RSET from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:47 mxcluster postfix/smtpd[22804]: disconnect from srv01.iagentemail.com.br[189.38.86.124] The above message is rejected because 187.1.133.20 has no PTR record. You forgot the logfile record with the status=xxx and delay=yyy of message 70E82E42D0. # FASTER DOMAIN Mar 15 10:37:47 mxcluster postfix/smtpd[19313]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:47 mxcluster postfix/smtpd[19313]: 45B50E42F5: client= srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:47 mxcluster postfix/cleanup[22025]: 45B50E42F5: message-id= 950c281e36abb9600cdf730baff00...@iagentemail.com.br Mar 15 10:37:47 mxcluster dkim-filter[4513]: 45B50E42F5 DKIM-Signature header added Mar 15 10:37:47 mxcluster postfix/qmgr[27773]: 45B50E42F5: from= reto...@iagentemail.com.br, size=630, nrcpt=2 (queue active) Mar 15 10:37:47 mxcluster postfix/smtpd[19313]: lost connection after RSET from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:47 mxcluster postfix/smtpd[19313]: disconnect from srv01.iagentemail.com.br[189.38.86.124] You forgot the logfile record with the status=xxx and delay=yyy of message 45B50E42F5. Wietse
Re: Problems with postfix while sending emails
Rafael Azevedo: Hi, Actually I believe that there is a DNS problem on that MX server, cause PTR is set properly. My own PTR lookup fails with NXDOMAIN. Can you show the missing logfiles records that I asked for? If you want me to help, then you must answer my questions. Wietse
Re: Problems with postfix while sending emails
On 15/03/11 15:10, Wietse Venema wrote: Rafael Azevedo: [ Charset ISO-8859-1 unsupported, converting... ] Hi Wietse! Thanks again for helping me! Here is the postfix log: # SLOW DOMAIN Mar 15 10:37:46 mxcluster postfix/smtpd[22804]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:46 mxcluster postfix/smtpd[22804]: 70E82E42D0: client= srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:46 mxcluster postfix/cleanup[21751]: 70E82E42D0: message-id= 8d3ee53c5d281ab3dae9471182931...@iagentemail.com.br Mar 15 10:37:46 mxcluster dkim-filter[4513]: 70E82E42D0 DKIM-Signature header added Mar 15 10:37:47 mxcluster postfix/qmgr[27773]: 70E82E42D0: from= reto...@iagentemail.com.br, size=629, nrcpt=2 (queue active) Mar 15 10:37:47 mxcluster postfix/smtp[23002]: 70E82E42D0: host mx2.iagente.com.br[189.38.95.92] said: 450 4.7.1 Client host rejected: cannot find your hostname, [187.1.133.20] (in reply to RCPT TO command) Mar 15 10:37:47 mxcluster postfix/smtpd[22804]: lost connection after RSET from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:47 mxcluster postfix/smtpd[22804]: disconnect from srv01.iagentemail.com.br[189.38.86.124] The above message is rejected because 187.1.133.20 has no PTR record. There are 2 nameservers listed in DNS that should have PTR records for 133.1.187.in-addr.arpa, both of these have 2 ip-addresses, resulting in 4 DNS servers to check. Two of these return correct data, the other two return no PTR record, and a strange looking SOA, for that matter. $ dig ns 133.1.187.in-addr.arpa ; DiG 9.7.1-P2 ns 133.1.187.in-addr.arpa ;; global options: +cmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 34523 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 4 ;; QUESTION SECTION: ;133.1.187.in-addr.arpa.IN NS ;; ANSWER SECTION: 133.1.187.in-addr.arpa. 5234IN NS ns1.dns2.com.br. 133.1.187.in-addr.arpa. 5234IN NS ns2.dns2.com.br. ;; ADDITIONAL SECTION: ns1.dns2.com.br.84434 IN A 187.1.143.64 ns1.dns2.com.br.84434 IN A 189.38.86.79 ns2.dns2.com.br.84434 IN A 187.1.143.65 ns2.dns2.com.br.84434 IN A 189.38.86.80 $ dig +short -x 187.1.133.20 @189.38.86.79 mxcluster.iagentemail.com.br. = OK $ dig +short -x 187.1.133.20 @187.1.143.64 = No PTR, this is your problem $ dig +short soa 133.1.187.in-addr.arpa @187.1.143.64 cyrus.webpro.com.br. raffus.gmail.com. 1299803423 10800 3600 604800 10800 = Google mailbox as hostmaster address? I think the person maintaining the DNS address space of *your mailserver* made a typo or a config error somewhere. Regards, Tom signature.asc Description: OpenPGP digital signature
Re: Problems with postfix while sending emails
Hi Wietse, Thanks again!! Sorry, I just found a problem in our DNS PTR records that were just fixed. This problem was cause yesterday and we're having the delay for over months.. The logs file you asked is here: # SLOW DOMAIN (ZOOM4U.COM.BR) Mar 15 11:38:16 mxcluster postfix/smtpd[8864]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 11:38:16 mxcluster postfix/smtpd[8864]: 32781115314: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 11:38:16 mxcluster postfix/cleanup[10447]: 32781115314: message-id=b2955c8d96c9a28da7e669619b7f5...@iagentemail.com.br Mar 15 11:38:16 mxcluster dkim-filter[4513]: 32781115314 DKIM-Signature header added Mar 15 11:38:16 mxcluster postfix/qmgr[27773]: 32781115314: from=reto...@iagentemail.com.br, size=630, nrcpt=2 (queue active) Mar 15 11:38:16 mxcluster postfix/smtp[13274]: 32781115314: host mx1.iagente.com.br[189.38.95.91] said: 450 4.7.1 Client host rejected: cannot find your hostname, [187.1.133.20] (in reply to RCPT TO command) Mar 15 11:38:17 mxcluster postfix/smtp[13274]: 32781115314: to=di...@iagente.com.br, relay=mx2.iagente.com.br[189.38.95.92]:25, delay=0.86, delays=0.6/0.02/0.23/0.01, dsn=4.7.1, status=deferred (host mx2.iagente.com.br[189.38.95.92] said: 450 4.7.1 Client host rejected: cannot find your hostname, [187.1.133.20] (in reply to RCPT TO command)) Mar 15 11:38:18 mxcluster postfix/smtpd[8864]: lost connection after RSET from srv01.iagentemail.com.br[189.38.86.124] Mar 15 11:38:18 mxcluster postfix/smtpd[8864]: disconnect from srv01.iagentemail.com.br[189.38.86.124] # FAST DOMAIN (IAGENTEMAIL.COM.BR) Mar 15 11:38:18 mxcluster postfix/smtpd[10043]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 11:38:18 mxcluster postfix/smtpd[10043]: C982F115371: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 11:38:18 mxcluster postfix/cleanup[8869]: C982F115371: message-id=bfd59a612aa359e7af6e9278b8cea...@iagentemail.com.br Mar 15 11:38:18 mxcluster dkim-filter[4513]: C982F115371 DKIM-Signature header added Mar 15 11:38:18 mxcluster postfix/qmgr[27773]: C982F115371: from=reto...@iagentemail.com.br, size=631, nrcpt=2 (queue active) Mar 15 11:38:18 mxcluster postfix/smtpd[10043]: lost connection after RSET from srv01.iagentemail.com.br[189.38.86.124] Mar 15 11:38:18 mxcluster postfix/smtpd[10043]: disconnect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 11:38:19 mxcluster postfix/smtp[13278]: C982F115371: host mx1.iagente.com.br[189.38.95.91] said: 450 4.7.1 Client host rejected: cannot find your hostname, [187.1.133.20] (in reply to RCPT TO command) Mar 15 11:38:19 mxcluster postfix/smtp[13278]: C982F115371: to=di...@iagente.com.br, relay=mx3.iagente.com.br[189.38.95.5]:25, delay=0.38, delays=0.14/0.01/0.22/0, dsn=4.7.1, status=deferred (host mx3.iagente.com.br[189.38.95.5] said: 450 4.7.1 Client host rejected: cannot find your hostname, [187.1.133.20] (in reply to RCPT TO command)) Mar 15 11:38:19 mxcluster postfix/smtp[13273]: 32781115314: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=3.1, delays=0.6/0.02/0.45/2.1, dsn=2.0.0, status=sent (250 2.0.0 OK 1300199826 24si16259995yhl.74) Mar 15 11:38:21 mxcluster postfix/smtp[13274]: C982F115371: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=2.8, delays=0.14/0/0.44/2.2, dsn=2.0.0, status=sent (250 2.0.0 OK 1300199829 y15si21902165ank.154) Thanks in advance. On Tue, Mar 15, 2011 at 11:23 AM, Wietse Venema wie...@porcupine.org wrote: Rafael Azevedo: Hi, Actually I believe that there is a DNS problem on that MX server, cause PTR is set properly. My own PTR lookup fails with NXDOMAIN. Can you show the missing logfiles records that I asked for? If you want me to help, then you must answer my questions. Wietse
Re: Problems with postfix while sending emails
Hi Tom, I've just fixed the DNS problem. I'm still having problem with the connection delay for some domains... Thanks for helping!! Rafael On Tue, Mar 15, 2011 at 11:27 AM, Tom Hendrikx t...@whyscream.net wrote: On 15/03/11 15:10, Wietse Venema wrote: Rafael Azevedo: [ Charset ISO-8859-1 unsupported, converting... ] Hi Wietse! Thanks again for helping me! Here is the postfix log: # SLOW DOMAIN Mar 15 10:37:46 mxcluster postfix/smtpd[22804]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:46 mxcluster postfix/smtpd[22804]: 70E82E42D0: client= srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:46 mxcluster postfix/cleanup[21751]: 70E82E42D0: message-id= 8d3ee53c5d281ab3dae9471182931...@iagentemail.com.br Mar 15 10:37:46 mxcluster dkim-filter[4513]: 70E82E42D0 DKIM-Signature header added Mar 15 10:37:47 mxcluster postfix/qmgr[27773]: 70E82E42D0: from= reto...@iagentemail.com.br, size=629, nrcpt=2 (queue active) Mar 15 10:37:47 mxcluster postfix/smtp[23002]: 70E82E42D0: host mx2.iagente.com.br[189.38.95.92] said: 450 4.7.1 Client host rejected: cannot find your hostname, [187.1.133.20] (in reply to RCPT TO command) Mar 15 10:37:47 mxcluster postfix/smtpd[22804]: lost connection after RSET from srv01.iagentemail.com.br[189.38.86.124] Mar 15 10:37:47 mxcluster postfix/smtpd[22804]: disconnect from srv01.iagentemail.com.br[189.38.86.124] The above message is rejected because 187.1.133.20 has no PTR record. There are 2 nameservers listed in DNS that should have PTR records for 133.1.187.in-addr.arpa, both of these have 2 ip-addresses, resulting in 4 DNS servers to check. Two of these return correct data, the other two return no PTR record, and a strange looking SOA, for that matter. $ dig ns 133.1.187.in-addr.arpa ; DiG 9.7.1-P2 ns 133.1.187.in-addr.arpa ;; global options: +cmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 34523 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 4 ;; QUESTION SECTION: ;133.1.187.in-addr.arpa. IN NS ;; ANSWER SECTION: 133.1.187.in-addr.arpa. 5234 IN NS ns1.dns2.com.br. 133.1.187.in-addr.arpa. 5234 IN NS ns2.dns2.com.br. ;; ADDITIONAL SECTION: ns1.dns2.com.br. 84434 IN A 187.1.143.64 ns1.dns2.com.br. 84434 IN A 189.38.86.79 ns2.dns2.com.br. 84434 IN A 187.1.143.65 ns2.dns2.com.br. 84434 IN A 189.38.86.80 $ dig +short -x 187.1.133.20 @189.38.86.79 mxcluster.iagentemail.com.br. = OK $ dig +short -x 187.1.133.20 @187.1.143.64 = No PTR, this is your problem $ dig +short soa 133.1.187.in-addr.arpa @187.1.143.64 cyrus.webpro.com.br. raffus.gmail.com. 1299803423 10800 3600 604800 10800 = Google mailbox as hostmaster address? I think the person maintaining the DNS address space of *your mailserver* made a typo or a config error somewhere. Regards, Tom
Re: Problems with postfix while sending emails
Rafael Azevedo: Mar 15 11:38:17 mxcluster postfix/smtp[13274]: 32781115314: to=di...@iagente.com.br, relay=mx2.iagente.com.br[189.38.95.92]:25, delay=0.86, delays=0.6/0.02/0.23/0.01, dsn=4.7.1, status=deferred (host mx2.iagente.com.br[189.38.95.92] said: 450 4.7.1 Client host rejected: cannot find your hostname, [187.1.133.20] (in reply to RCPT TO command)) With a 50% chance to get NXDOMAIN for your PTR record, Postfix will have to try to deliver this recipient 2-3 times before the PTR lookup succeeds, so the message will be delayed for 5-10 minutes. Wietse
Re: Problems with postfix while sending emails
Hi Wietse, I thing I havent made myself clear. I have an email app running on BOX A and POSTFIX on BOX B. The BOX A connects to POSTFIX to send the messages. Thats exactly where the delay is. When the application tries to send the messages to POSTFIX, the APP sends about 2 messages per second TO POSTFIX using domain ZOOM4U.COM.BR. If I just change the SENDER DOMAIN TO ANY OTHER NAME, the APP sends about 40 messages per second TO POSTFIX. After that, POSTFIX manages the delivery by itself and there is no issue at all in that part. It really delivery the messages to SMTP's recipients very fast. The bottleneck is when POSTFIX RECEIVES THE CONNECTION from my application when using domain ZOOM4U.COM.BR. I've already fixed the DNS records. It might take a while to propagate. Thanks in advance. Rafael On Tue, Mar 15, 2011 at 11:52 AM, Wietse Venema wie...@porcupine.org wrote: Rafael Azevedo: Mar 15 11:38:17 mxcluster postfix/smtp[13274]: 32781115314: to=di...@iagente.com.br, relay=mx2.iagente.com.br[189.38.95.92]:25, delay=0.86, delays=0.6/0.02/0.23/0.01, dsn=4.7.1, status=deferred (host mx2.iagente.com.br[189.38.95.92] said: 450 4.7.1 Client host rejected: cannot find your hostname, [187.1.133.20] (in reply to RCPT TO command)) With a 50% chance to get NXDOMAIN for your PTR record, Postfix will have to try to deliver this recipient 2-3 times before the PTR lookup succeeds, so the message will be delayed for 5-10 minutes. Wietse
Re: Problems with postfix while sending emails
Rafael Azevedo: Hi Wietse, I thing I havent made myself clear. I have an email app running on BOX A and POSTFIX on BOX B. The BOX A connects to POSTFIX to send the messages. Thats exactly where the delay is. When the application tries to send the messages to POSTFIX, the APP sends about 2 messages per second TO POSTFIX using domain ZOOM4U.COM.BR. The bottleneck is when POSTFIX RECEIVES THE CONNECTION from my application when using domain ZOOM4U.COM.BR. There are no fast or slow domain names in your logging. Therefore, your conclusions are not supported by your evidence. What I do see is that your server can't deliver mail due to DNS lookup error (50% likelihood of NXDOMAIN). Delays while delivering mail will result in delays while Postfix receives mail. This is a built-in defense to prevent the sender from overwhelming the Postfix queue. Therefore, you need to fix the delays with mail delivery (due ti bad DNS or whatever). Then, there will be no delays while Postfix receives mail. Wietse
Re: Problems with postfix while sending emails
Hi Wietse, Thanks so much for your help! I've already fixed the DNS problem. For testing pourposes, I'm using now another IP C CLASS that has no DNS fails. This is my test output - sending 5 emails per sender domain: # DOMAIN ZOOM4U.COM.BR (about 1 email per second) 12:56:10 - Sending email #1...OK 12:56:10 - Sending email #2...OK 12:56:11 - Sending email #3...OK 12:56:12 - Sending email #4...OK 12:56:13 - Sending email #5...OK # NOW USING IAGENTEMAIL.COM.BR (5 emails per second) 12:56:14 - Sending email #1...OK 12:56:14 - Sending email #2...OK 12:56:14 - Sending email #3...OK 12:56:14 - Sending email #4...OK 12:56:14 - Sending email #5...OK In both cases I'm using the same SMTP that uses another C class. See the difference? Thanks Rafael On Tue, Mar 15, 2011 at 12:26 PM, Wietse Venema wie...@porcupine.org wrote: Rafael Azevedo: Hi Wietse, I thing I havent made myself clear. I have an email app running on BOX A and POSTFIX on BOX B. The BOX A connects to POSTFIX to send the messages. Thats exactly where the delay is. When the application tries to send the messages to POSTFIX, the APP sends about 2 messages per second TO POSTFIX using domain ZOOM4U.COM.BR. The bottleneck is when POSTFIX RECEIVES THE CONNECTION from my application when using domain ZOOM4U.COM.BR. There are no fast or slow domain names in your logging. Therefore, your conclusions are not supported by your evidence. What I do see is that your server can't deliver mail due to DNS lookup error (50% likelihood of NXDOMAIN). Delays while delivering mail will result in delays while Postfix receives mail. This is a built-in defense to prevent the sender from overwhelming the Postfix queue. Therefore, you need to fix the delays with mail delivery (due ti bad DNS or whatever). Then, there will be no delays while Postfix receives mail. Wietse
Re: Problems with postfix while sending emails
* Rafael Azevedo raf...@gmail.com: Hi Wietse, Thanks so much for your help! I've already fixed the DNS problem. For testing pourposes, I'm using now another IP C CLASS that has no DNS fails. This is my test output - sending 5 emails per sender domain: # DOMAIN ZOOM4U.COM.BR (about 1 email per second) 12:56:10 - Sending email #1...OK 12:56:10 - Sending email #2...OK 12:56:11 - Sending email #3...OK 12:56:12 - Sending email #4...OK 12:56:13 - Sending email #5...OK # NOW USING IAGENTEMAIL.COM.BR (5 emails per second) 12:56:14 - Sending email #1...OK 12:56:14 - Sending email #2...OK 12:56:14 - Sending email #3...OK 12:56:14 - Sending email #4...OK 12:56:14 - Sending email #5...OK In both cases I'm using the same SMTP that uses another C class. See the difference? Where are the postfix logs for that? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Problems with postfix while sending emails
Sorry! I forgot the log files.. In order to reduce the logs I've made a test with 2 destinations per domain sender, as follows: # TEST 1: 13:15:14 - Sending email #1...OK 13:15:15 - Sending email #2...OK # TEST 2 13:15:15 - Sending email #1...OK 13:15:15 - Sending email #2...OK POSTFIX LOGS: Mar 15 13:16:23 mxcluster postfix/smtpd[31423]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:23 mxcluster postfix/smtpd[31423]: D40E120EAA8: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:23 mxcluster postfix/cleanup[31427]: D40E120EAA8: message-id=da148727b8e4e2c708f2247e952e3...@iagentemail.com.br Mar 15 13:16:24 mxcluster dkim-filter[4513]: D40E120EAA8 DKIM-Signature header added Mar 15 13:16:24 mxcluster postfix/qmgr[6659]: D40E120EAA8: from=reto...@iagentemail.com.br, size=631, nrcpt=2 (queue active) Mar 15 13:16:24 mxcluster postfix/smtpd[31423]: 5E9C320EAC6: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:24 mxcluster postfix/cleanup[31427]: 5E9C320EAC6: message-id=bbf2745b30c38b261c50af0e222b7...@iagentemail.com.br Mar 15 13:16:24 mxcluster postfix/smtp[31429]: D40E120EAA8: to=di...@iagente.com.br, relay=mx2.iagente.com.br[189.38.95.92]:25, delay=0.67, delays=0.52/0.01/0.02/0.12, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as F1EAF6DFA4E64) Mar 15 13:16:24 mxcluster dkim-filter[4513]: 5E9C320EAC6 DKIM-Signature header added Mar 15 13:16:24 mxcluster postfix/qmgr[6659]: 5E9C320EAC6: from=reto...@iagentemail.com.br, size=631, nrcpt=2 (queue active) Mar 15 13:16:24 mxcluster postfix/smtpd[31423]: lost connection after RSET from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:24 mxcluster postfix/smtpd[31423]: disconnect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:24 mxcluster postfix/smtpd[31423]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:24 mxcluster postfix/smtpd[31423]: EE82220EB26: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:25 mxcluster postfix/cleanup[31427]: EE82220EB26: message-id=49aacc28e1c170356dc8fb54834a8...@iagentemail.com.br Mar 15 13:16:25 mxcluster dkim-filter[4513]: EE82220EB26 DKIM-Signature header added Mar 15 13:16:25 mxcluster postfix/qmgr[6659]: EE82220EB26: from=reto...@iagentemail.com.br, size=632, nrcpt=2 (queue active) Mar 15 13:16:25 mxcluster postfix/smtpd[31423]: 133F620EB53: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:25 mxcluster postfix/cleanup[31427]: 133F620EB53: message-id=dfcd063ee7c7c3843829ad4c45969...@iagentemail.com.br Mar 15 13:16:25 mxcluster dkim-filter[4513]: 133F620EB53 DKIM-Signature header added Mar 15 13:16:25 mxcluster postfix/qmgr[6659]: 133F620EB53: from=reto...@iagentemail.com.br, size=632, nrcpt=2 (queue active) Mar 15 13:16:25 mxcluster postfix/smtpd[31423]: lost connection after RSET from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:25 mxcluster postfix/smtpd[31423]: disconnect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:25 mxcluster postfix/smtp[31438]: EE82220EB26: to=di...@iagente.com.br, relay=mx3.iagente.com.br[189.38.95.5]:25, delay=0.47, delays=0.1/0.02/0.15/0.21, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as DB5861FDE7702) Mar 15 13:16:25 mxcluster postfix/smtp[31440]: 133F620EB53: to=di...@iagente.com.br, relay=mx2.iagente.com.br[189.38.95.92]:25, delay=0.43, delays=0.11/0.01/0.13/0.17, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as EA8BA6DFA521F) Mar 15 13:16:27 mxcluster postfix/smtp[29978]: D40E120EAA8: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=3.1, delays=0.52/0/0.45/2.2, dsn=2.0.0, status=sent (250 2.0.0 OK 1300205714 x34si22095693anx.127) Mar 15 13:16:27 mxcluster postfix/qmgr[6659]: D40E120EAA8: removed Mar 15 13:16:27 mxcluster postfix/smtp[31429]: 5E9C320EAC6: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=3.1, delays=0.58/0/0.45/2.1, dsn=2.0.0, status=sent (250 2.0.0 OK 1300205714 p50si22191243yhi.8) Mar 15 13:16:27 mxcluster postfix/smtp[31437]: EE82220EB26: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=2.7, delays=0.1/0.01/0.45/2.1, dsn=2.0.0, status=sent (250 2.0.0 OK 1300205715 m1si10205166ybn.28) Mar 15 13:16:27 mxcluster postfix/qmgr[6659]: EE82220EB26: removed Mar 15 13:16:27 mxcluster postfix/smtp[31439]: 133F620EB53: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=2.6, delays=0.11/0.01/0.45/2, dsn=2.0.0, status=sent (250 2.0.0 OK 1300205715 o2si378647ybn.42) Mar 15 13:16:27 mxcluster postfix/qmgr[6659]: 133F620EB53: removed Mar 15 13:16:35 mxcluster postfix/smtp[31431]: 5E9C320EAC6: to=di...@iagente.com.br, relay=mx1.iagente.com.br[189.38.95.91]:25, delay=11, delays=0.58/0.01/5.2/5.2, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as CFB4A6DB6AC99) Thanks once again. Rafael On Tue, Mar 15, 2011 at 1:02 PM, Ralf Hildebrandt ralf.hildebra...@charite.de wrote: * Rafael Azevedo raf...@gmail.com: Hi Wietse, Thanks so much for your help! I've already
Re: Problems with postfix while sending emails
* Rafael Azevedo raf...@gmail.com: Sorry! I forgot the log files.. In order to reduce the logs I've made a test with 2 destinations per domain sender, as follows: # TEST 1: 13:15:14 - Sending email #1...OK 13:15:15 - Sending email #2...OK # TEST 2 13:15:15 - Sending email #1...OK 13:15:15 - Sending email #2...OK POSTFIX LOGS: Mar 15 13:16:23 mxcluster postfix/smtpd[31423]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:23 mxcluster postfix/smtpd[31423]: D40E120EAA8: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:23 mxcluster postfix/cleanup[31427]: D40E120EAA8: message-id=da148727b8e4e2c708f2247e952e3...@iagentemail.com.br Mar 15 13:16:24 mxcluster dkim-filter[4513]: D40E120EAA8 DKIM-Signature header added Mar 15 13:16:24 mxcluster postfix/qmgr[6659]: D40E120EAA8: from=reto...@iagentemail.com.br, size=631, nrcpt=2 (queue active) Mar 15 13:16:24 mxcluster postfix/smtp[31429]: D40E120EAA8: to=di...@iagente.com.br, relay=mx2.iagente.com.br[189.38.95.92]:25, delay=0.67, delays=0.52/0.01/0.02/0.12, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as F1EAF6DFA4E64) Mar 15 13:16:27 mxcluster postfix/smtp[29978]: D40E120EAA8: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=3.1, delays=0.52/0/0.45/2.2, dsn=2.0.0, status=sent (250 2.0.0 OK 1300205714 x34si22095693anx.127) Mar 15 13:16:27 mxcluster postfix/qmgr[6659]: D40E120EAA8: removed Mar 15 13:16:24 mxcluster postfix/smtpd[31423]: 5E9C320EAC6: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:24 mxcluster postfix/cleanup[31427]: 5E9C320EAC6: message-id=bbf2745b30c38b261c50af0e222b7...@iagentemail.com.br Mar 15 13:16:24 mxcluster dkim-filter[4513]: 5E9C320EAC6 DKIM-Signature header added Mar 15 13:16:24 mxcluster postfix/qmgr[6659]: 5E9C320EAC6: from=reto...@iagentemail.com.br, size=631, nrcpt=2 (queue active) Mar 15 13:16:27 mxcluster postfix/smtp[31429]: 5E9C320EAC6: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=3.1, delays=0.58/0/0.45/2.1, dsn=2.0.0, status=sent (250 2.0.0 OK 1300205714 p50si22191243yhi.8) Mar 15 13:16:35 mxcluster postfix/smtp[31431]: 5E9C320EAC6: to=di...@iagente.com.br, relay=mx1.iagente.com.br[189.38.95.91]:25, delay=11, delays=0.58/0.01/5.2/5.2, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as CFB4A6DB6AC99) Mar 15 13:16:24 mxcluster postfix/smtpd[31423]: lost connection after RSET from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:24 mxcluster postfix/smtpd[31423]: disconnect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:24 mxcluster postfix/smtpd[31423]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:24 mxcluster postfix/smtpd[31423]: EE82220EB26: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:25 mxcluster postfix/cleanup[31427]: EE82220EB26: message-id=49aacc28e1c170356dc8fb54834a8...@iagentemail.com.br Mar 15 13:16:25 mxcluster dkim-filter[4513]: EE82220EB26 DKIM-Signature header added Mar 15 13:16:25 mxcluster postfix/qmgr[6659]: EE82220EB26: from=reto...@iagentemail.com.br, size=632, nrcpt=2 (queue active) Mar 15 13:16:25 mxcluster postfix/smtp[31438]: EE82220EB26: to=di...@iagente.com.br, relay=mx3.iagente.com.br[189.38.95.5]:25, delay=0.47, delays=0.1/0.02/0.15/0.21, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as DB5861FDE7702) Mar 15 13:16:27 mxcluster postfix/smtp[31437]: EE82220EB26: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=2.7, delays=0.1/0.01/0.45/2.1, dsn=2.0.0, status=sent (250 2.0.0 OK 1300205715 m1si10205166ybn.28) Mar 15 13:16:27 mxcluster postfix/qmgr[6659]: EE82220EB26: removed Mar 15 13:16:25 mxcluster postfix/smtpd[31423]: 133F620EB53: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:25 mxcluster postfix/cleanup[31427]: 133F620EB53: message-id=dfcd063ee7c7c3843829ad4c45969...@iagentemail.com.br Mar 15 13:16:25 mxcluster dkim-filter[4513]: 133F620EB53 DKIM-Signature header added Mar 15 13:16:25 mxcluster postfix/qmgr[6659]: 133F620EB53: from=reto...@iagentemail.com.br, size=632, nrcpt=2 (queue active) Mar 15 13:16:25 mxcluster postfix/smtpd[31423]: lost connection after RSET from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:25 mxcluster postfix/smtpd[31423]: disconnect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:25 mxcluster postfix/smtp[31440]: 133F620EB53: to=di...@iagente.com.br, relay=mx2.iagente.com.br[189.38.95.92]:25, delay=0.43, delays=0.11/0.01/0.13/0.17, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as EA8BA6DFA521F) Mar 15 13:16:27 mxcluster postfix/smtp[31439]: 133F620EB53: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=2.6, delays=0.11/0.01/0.45/2, dsn=2.0.0, status=sent (250 2.0.0 OK 1300205715 o2si378647ybn.42) Mar 15 13:16:27 mxcluster postfix/qmgr[6659]: 133F620EB53: removed You're sending 4 Emails to
Re: Problems with postfix while sending emails
Ralf!! Exactally!!! The major delay is at (c=connection setup time including DNS, HELO and TLS). Thats what is taking too long, but ONLY when I use sender ZOOM4U.COM.BR as the domain name. Any idea?? Thanks a lot! On Tue, Mar 15, 2011 at 1:30 PM, Ralf Hildebrandt ralf.hildebra...@charite.de wrote: * Rafael Azevedo raf...@gmail.com: Sorry! I forgot the log files.. In order to reduce the logs I've made a test with 2 destinations per domain sender, as follows: # TEST 1: 13:15:14 - Sending email #1...OK 13:15:15 - Sending email #2...OK # TEST 2 13:15:15 - Sending email #1...OK 13:15:15 - Sending email #2...OK POSTFIX LOGS: Mar 15 13:16:23 mxcluster postfix/smtpd[31423]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:23 mxcluster postfix/smtpd[31423]: D40E120EAA8: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:23 mxcluster postfix/cleanup[31427]: D40E120EAA8: message-id=da148727b8e4e2c708f2247e952e3...@iagentemail.com.br Mar 15 13:16:24 mxcluster dkim-filter[4513]: D40E120EAA8 DKIM-Signature header added Mar 15 13:16:24 mxcluster postfix/qmgr[6659]: D40E120EAA8: from=reto...@iagentemail.com.br, size=631, nrcpt=2 (queue active) Mar 15 13:16:24 mxcluster postfix/smtp[31429]: D40E120EAA8: to=di...@iagente.com.br, relay=mx2.iagente.com.br[189.38.95.92]:25, delay=0.67, delays=0.52/0.01/0.02/0.12, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as F1EAF6DFA4E64) Mar 15 13:16:27 mxcluster postfix/smtp[29978]: D40E120EAA8: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=3.1, delays=0.52/0/0.45/2.2, dsn=2.0.0, status=sent (250 2.0.0 OK 1300205714 x34si22095693anx.127) Mar 15 13:16:27 mxcluster postfix/qmgr[6659]: D40E120EAA8: removed Mar 15 13:16:24 mxcluster postfix/smtpd[31423]: 5E9C320EAC6: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:24 mxcluster postfix/cleanup[31427]: 5E9C320EAC6: message-id=bbf2745b30c38b261c50af0e222b7...@iagentemail.com.br Mar 15 13:16:24 mxcluster dkim-filter[4513]: 5E9C320EAC6 DKIM-Signature header added Mar 15 13:16:24 mxcluster postfix/qmgr[6659]: 5E9C320EAC6: from=reto...@iagentemail.com.br, size=631, nrcpt=2 (queue active) Mar 15 13:16:27 mxcluster postfix/smtp[31429]: 5E9C320EAC6: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=3.1, delays=0.58/0/0.45/2.1, dsn=2.0.0, status=sent (250 2.0.0 OK 1300205714 p50si22191243yhi.8) Mar 15 13:16:35 mxcluster postfix/smtp[31431]: 5E9C320EAC6: to=di...@iagente.com.br, relay=mx1.iagente.com.br[189.38.95.91]:25, delay=11, delays=0.58/0.01/5.2/5.2, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as CFB4A6DB6AC99) Mar 15 13:16:24 mxcluster postfix/smtpd[31423]: lost connection after RSET from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:24 mxcluster postfix/smtpd[31423]: disconnect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:24 mxcluster postfix/smtpd[31423]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:24 mxcluster postfix/smtpd[31423]: EE82220EB26: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:25 mxcluster postfix/cleanup[31427]: EE82220EB26: message-id=49aacc28e1c170356dc8fb54834a8...@iagentemail.com.br Mar 15 13:16:25 mxcluster dkim-filter[4513]: EE82220EB26 DKIM-Signature header added Mar 15 13:16:25 mxcluster postfix/qmgr[6659]: EE82220EB26: from=reto...@iagentemail.com.br, size=632, nrcpt=2 (queue active) Mar 15 13:16:25 mxcluster postfix/smtp[31438]: EE82220EB26: to=di...@iagente.com.br, relay=mx3.iagente.com.br[189.38.95.5]:25, delay=0.47, delays=0.1/0.02/0.15/0.21, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as DB5861FDE7702) Mar 15 13:16:27 mxcluster postfix/smtp[31437]: EE82220EB26: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=2.7, delays=0.1/0.01/0.45/2.1, dsn=2.0.0, status=sent (250 2.0.0 OK 1300205715 m1si10205166ybn.28) Mar 15 13:16:27 mxcluster postfix/qmgr[6659]: EE82220EB26: removed Mar 15 13:16:25 mxcluster postfix/smtpd[31423]: 133F620EB53: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:25 mxcluster postfix/cleanup[31427]: 133F620EB53: message-id=dfcd063ee7c7c3843829ad4c45969...@iagentemail.com.br Mar 15 13:16:25 mxcluster dkim-filter[4513]: 133F620EB53 DKIM-Signature header added Mar 15 13:16:25 mxcluster postfix/qmgr[6659]: 133F620EB53: from=reto...@iagentemail.com.br, size=632, nrcpt=2 (queue active) Mar 15 13:16:25 mxcluster postfix/smtpd[31423]: lost connection after RSET from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:25 mxcluster postfix/smtpd[31423]: disconnect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:16:25 mxcluster postfix/smtp[31440]: 133F620EB53: to=di...@iagente.com.br, relay=mx2.iagente.com.br[189.38.95.92]:25, delay=0.43, delays=0.11/0.01/0.13/0.17, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as EA8BA6DFA521F) Mar 15 13:16:27 mxcluster
Re: Problems with postfix while sending emails
* Rafael Azevedo raf...@gmail.com: Mar 15 13:21:05 mxcluster postfix/smtpd[32624]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:21:05 mxcluster postfix/smtpd[32624]: 4B5ED20FA17: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:21:05 mxcluster postfix/cleanup[32629]: 4B5ED20FA17: message-id=cfa989796f031bc8b7ce2dcb36bcd...@iagentemail.com.br Mar 15 13:21:05 mxcluster postfix/qmgr[32622]: 4B5ED20FA17: from=reto...@iagentemail.com.br, size=631, nrcpt=2 (queue active) Mar 15 13:21:08 mxcluster postfix/smtp[32630]: 4B5ED20FA17: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=3, delays=0.48/0.01/0.48/2, dsn=2.0.0, status=sent (250 2.0.0 OK 1300205995 v5si10220362ybk.19) Mar 15 13:21:16 mxcluster postfix/smtp[32631]: 4B5ED20FA17: to=di...@iagente.com.br, relay=mx3.iagente.com.br[189.38.95.5]:25, delay=11, delays=0.48/0.02/0.33/10, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as B8DEB1FDFA1D9) Mar 15 13:21:16 mxcluster postfix/qmgr[32622]: 4B5ED20FA17: removed Mar 15 13:21:05 mxcluster postfix/smtpd[32624]: BEADA20FA21: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:21:05 mxcluster postfix/cleanup[32629]: BEADA20FA21: message-id=dbb4e00eee98482ba5a38b204393b...@iagentemail.com.br Mar 15 13:21:06 mxcluster postfix/qmgr[32622]: BEADA20FA21: from=reto...@iagentemail.com.br, size=631, nrcpt=2 (queue active) Mar 15 13:21:08 mxcluster postfix/smtp[32633]: BEADA20FA21: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=3, delays=0.47/0.01/0.47/2, dsn=2.0.0, status=sent (250 2.0.0 OK 1300205996 c4si22142822ana.147) Mar 15 13:21:12 mxcluster postfix/smtp[32634]: BEADA20FA21: to=di...@iagente.com.br, relay=mx2.iagente.com.br[189.38.95.92]:25, delay=7, delays=0.47/0.02/0.32/6.2, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 39BA26DFCFC3D) Mar 15 13:21:12 mxcluster postfix/qmgr[32622]: BEADA20FA21: removed Mar 15 13:21:16 mxcluster postfix/smtpd[32624]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:21:16 mxcluster postfix/smtpd[32624]: 4034320FAC4: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:21:16 mxcluster postfix/cleanup[32629]: 4034320FAC4: message-id=71101a571841567787cf650fdf6dc...@iagentemail.com.br Mar 15 13:21:16 mxcluster postfix/qmgr[32622]: 4034320FAC4: from=reto...@iagentemail.com.br, size=632, nrcpt=2 (queue active) Mar 15 13:21:18 mxcluster postfix/smtp[32630]: 4034320FAC4: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=2.6, delays=0.1/0/0.46/2, dsn=2.0.0, status=sent (250 2.0.0 OK 1300206006 x1si22136093anx.190) Mar 15 13:21:22 mxcluster postfix/smtp[32631]: 4034320FAC4: to=di...@iagente.com.br, relay=mx2.iagente.com.br[189.38.95.92]:25, delay=6.6, delays=0.1/0/0.31/6.2, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 438906DFD1E63) Mar 15 13:21:22 mxcluster postfix/qmgr[32622]: 4034320FAC4: removed Mar 15 13:21:16 mxcluster postfix/smtpd[32624]: 5A4A520FADE: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:21:16 mxcluster postfix/cleanup[32629]: 5A4A520FADE: message-id=b18bac1205dff5edc6f56bd24ccd4...@iagentemail.com.br Mar 15 13:21:16 mxcluster postfix/qmgr[32622]: 5A4A520FADE: from=reto...@iagentemail.com.br, size=632, nrcpt=2 (queue active) Mar 15 13:21:18 mxcluster postfix/smtp[32633]: 5A4A520FADE: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=2.6, delays=0.09/0/0.46/2, dsn=2.0.0, status=sent (250 2.0.0 OK 1300206006 p36si10211256ybk.38) Mar 15 13:21:27 mxcluster postfix/smtp[32634]: 5A4A520FADE: to=di...@iagente.com.br, relay=mx2.iagente.com.br[189.38.95.92]:25, delay=11, delays=0.09/0/0.34/11, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4059C6DFD3439) Mar 15 13:21:27 mxcluster postfix/qmgr[32622]: 5A4A520FADE: removed In this log, delivery to gmail seems to be faster than delivery to iagente.com.br. Again, the difference is in the d value only -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Problems with postfix while sending emails
Wietse, I use this settings: FROM: raf...@zoom4u.com.br SENDER: reto...@iagentemail.com.br REPLY TO = FROM So the email is sent as reto...@iagentemail.com.br but using FROM raf...@zoom4u.com.br because we want to receive every email bounce on reto...@iagentemail.com.br. This is used for every email sent by our system. We only change the FROM and REPLY to addresse, but when using ZOOM4U as FROM it really slows down connection speed. Thanks again. Rafael On Tue, Mar 15, 2011 at 1:32 PM, Wietse Venema wie...@porcupine.org wrote: Rafael Azevedo: Sorry guys! Here is the CLEAN LOG (I added some trash on the other message); # TEST 1 - ZOOM4U.COM.BR 13:19:55 - Sending email #1...OK 13:19:56 - Sending email #2...OK There is no zoom4 in the postfix logging. Your claims are not supported by your evidence. Wietse
Re: Problems with postfix while sending emails
* Rafael Azevedo raf...@gmail.com: Ralf!! Exactally!!! The major delay is at (c=connection setup time including DNS, HELO and TLS). No, in d, not c Thats what is taking too long, but ONLY when I use sender ZOOM4U.COM.BR as the domain name. You're not using the sender ZOOM4U.COM.BR anywhere. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Problems with postfix while sending emails
* Rafael Azevedo raf...@gmail.com: Wietse, I use this settings: FROM: raf...@zoom4u.com.br SENDER: reto...@iagentemail.com.br REPLY TO = FROM Well, postfix doesn't log that. Postfix is only logging the envelope sender (SENDER in your case) So the email is sent as reto...@iagentemail.com.br but using FROM raf...@zoom4u.com.br because we want to receive every email bounce on reto...@iagentemail.com.br. Yes, that's ok We only change the FROM and REPLY to addresse, but when using ZOOM4U as FROM it really slows down connection speed. Please try disabling DKIM :) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Problems with postfix while sending emails
Hi Ralf, I've already tried that. I did disable dkim and the delay time almost didnt change. Thanks On Tue, Mar 15, 2011 at 1:39 PM, Ralf Hildebrandt ralf.hildebra...@charite.de wrote: * Rafael Azevedo raf...@gmail.com: Wietse, I use this settings: FROM: raf...@zoom4u.com.br SENDER: reto...@iagentemail.com.br REPLY TO = FROM Well, postfix doesn't log that. Postfix is only logging the envelope sender (SENDER in your case) So the email is sent as reto...@iagentemail.com.br but using FROM raf...@zoom4u.com.br because we want to receive every email bounce on reto...@iagentemail.com.br. Yes, that's ok We only change the FROM and REPLY to addresse, but when using ZOOM4U as FROM it really slows down connection speed. Please try disabling DKIM :) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Problems with postfix while sending emails
* Rafael Azevedo raf...@gmail.com: Ralf, No it isnt. The delay is on the connection setup, as you can see: Mar 15 13:16:35 mxcluster postfix/smtp[31431]: 5E9C320EAC6: to=di...@iagente.com.br, relay=mx1.iagente.com.br[189.38.95.91]:25, delay=11, delays=0.58/0.01/ 5.2 /5.2, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as CFB4A6DB6AC99) Again, the log below doesn't show that. So it's not consistently slow. That setup connection delay happens when I use ZOOM4U domain as FROM (SENDER) domain. Try disabling DKIM. Maybe the DKIM check on the receiving side is failing in horrible ways (or is slow or or or) Mar 15 13:21:05 mxcluster postfix/smtpd[32624]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:21:05 mxcluster postfix/smtpd[32624]: 4B5ED20FA17: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:21:05 mxcluster postfix/cleanup[32629]: 4B5ED20FA17: message-id=cfa989796f031bc8b7ce2dcb36bcd...@iagentemail.com.br Mar 15 13:21:05 mxcluster postfix/qmgr[32622]: 4B5ED20FA17: from=reto...@iagentemail.com.br, size=631, nrcpt=2 (queue active) Mar 15 13:21:08 mxcluster postfix/smtp[32630]: 4B5ED20FA17: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=3, delays=0.48/0.01/0.48/2, dsn=2.0.0, status=sent (250 2.0.0 OK 1300205995 v5si10220362ybk.19) Mar 15 13:21:16 mxcluster postfix/smtp[32631]: 4B5ED20FA17: to=di...@iagente.com.br, relay=mx3.iagente.com.br[189.38.95.5]:25, delay=11, delays=0.48/0.02/0.33/10, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as B8DEB1FDFA1D9) Mar 15 13:21:16 mxcluster postfix/qmgr[32622]: 4B5ED20FA17: removed Mar 15 13:21:05 mxcluster postfix/smtpd[32624]: BEADA20FA21: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:21:05 mxcluster postfix/cleanup[32629]: BEADA20FA21: message-id=dbb4e00eee98482ba5a38b204393b...@iagentemail.com.br Mar 15 13:21:06 mxcluster postfix/qmgr[32622]: BEADA20FA21: from=reto...@iagentemail.com.br, size=631, nrcpt=2 (queue active) Mar 15 13:21:08 mxcluster postfix/smtp[32633]: BEADA20FA21: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=3, delays=0.47/0.01/0.47/2, dsn=2.0.0, status=sent (250 2.0.0 OK 1300205996 c4si22142822ana.147) Mar 15 13:21:12 mxcluster postfix/smtp[32634]: BEADA20FA21: to=di...@iagente.com.br, relay=mx2.iagente.com.br[189.38.95.92]:25, delay=7, delays=0.47/0.02/0.32/6.2, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 39BA26DFCFC3D) Mar 15 13:21:12 mxcluster postfix/qmgr[32622]: BEADA20FA21: removed Mar 15 13:21:16 mxcluster postfix/smtpd[32624]: connect from srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:21:16 mxcluster postfix/smtpd[32624]: 4034320FAC4: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:21:16 mxcluster postfix/cleanup[32629]: 4034320FAC4: message-id=71101a571841567787cf650fdf6dc...@iagentemail.com.br Mar 15 13:21:16 mxcluster postfix/qmgr[32622]: 4034320FAC4: from=reto...@iagentemail.com.br, size=632, nrcpt=2 (queue active) Mar 15 13:21:18 mxcluster postfix/smtp[32630]: 4034320FAC4: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=2.6, delays=0.1/0/0.46/2, dsn=2.0.0, status=sent (250 2.0.0 OK 1300206006 x1si22136093anx.190) Mar 15 13:21:22 mxcluster postfix/smtp[32631]: 4034320FAC4: to=di...@iagente.com.br, relay=mx2.iagente.com.br[189.38.95.92]:25, delay=6.6, delays=0.1/0/0.31/6.2, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 438906DFD1E63) Mar 15 13:21:22 mxcluster postfix/qmgr[32622]: 4034320FAC4: removed Mar 15 13:21:16 mxcluster postfix/smtpd[32624]: 5A4A520FADE: client=srv01.iagentemail.com.br[189.38.86.124] Mar 15 13:21:16 mxcluster postfix/cleanup[32629]: 5A4A520FADE: message-id=b18bac1205dff5edc6f56bd24ccd4...@iagentemail.com.br Mar 15 13:21:16 mxcluster postfix/qmgr[32622]: 5A4A520FADE: from=reto...@iagentemail.com.br, size=632, nrcpt=2 (queue active) Mar 15 13:21:18 mxcluster postfix/smtp[32633]: 5A4A520FADE: to=raf...@gmail.com, relay=gmail-smtp-in.l.google.com[74.125.67.27]:25, delay=2.6, delays=0.09/0/0.46/2, dsn=2.0.0, status=sent (250 2.0.0 OK 1300206006 p36si10211256ybk.38) Mar 15 13:21:27 mxcluster postfix/smtp[32634]: 5A4A520FADE: to=di...@iagente.com.br, relay=mx2.iagente.com.br[189.38.95.92]:25, delay=11, delays=0.09/0/0.34/11, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4059C6DFD3439) Mar 15 13:21:27 mxcluster postfix/qmgr[32622]: 5A4A520FADE: removed -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Problems with postfix while sending emails
* Rafael Azevedo raf...@gmail.com: Hi Ralf, I've already tried that. I did disable dkim and the delay time almost didnt change. Well, I'm out of ideas, but it's not really a postfix problem when the receiving side is being slow. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Problems with postfix while sending emails
It seems that POSTFIX is checking the DNS for that domain (ZOOM4U) and for some reason its taking too long. On Tue, Mar 15, 2011 at 1:42 PM, Rafael Azevedo raf...@gmail.com wrote: Hi Ralf, I've already tried that. I did disable dkim and the delay time almost didnt change. Thanks On Tue, Mar 15, 2011 at 1:39 PM, Ralf Hildebrandt ralf.hildebra...@charite.de wrote: * Rafael Azevedo raf...@gmail.com: Wietse, I use this settings: FROM: raf...@zoom4u.com.br SENDER: reto...@iagentemail.com.br REPLY TO = FROM Well, postfix doesn't log that. Postfix is only logging the envelope sender (SENDER in your case) So the email is sent as reto...@iagentemail.com.br but using FROM raf...@zoom4u.com.br because we want to receive every email bounce on reto...@iagentemail.com.br. Yes, that's ok We only change the FROM and REPLY to addresse, but when using ZOOM4U as FROM it really slows down connection speed. Please try disabling DKIM :) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Problems with postfix while sending emails
Rafael Azevedo: It seems that POSTFIX is checking the DNS for that domain (ZOOM4U) and for some reason its taking too long. What is the evidence for this? Where are the DNS queries? Do not jump to conclusions that aren't supported by evidence. Wietse
Re: Problems with postfix while sending emails
Ralf, you're the g-e-n-i-o-u-s The problem is with DK-MILTER not DKIM. I disable DK-MILTER from main.cf and its just very very very fast! Thanks a lot you guys for the help!! Now things are back to normal! Rafael On Tue, Mar 15, 2011 at 1:45 PM, Ralf Hildebrandt ralf.hildebra...@charite.de wrote: * Rafael Azevedo raf...@gmail.com: Hi Ralf, I've already tried that. I did disable dkim and the delay time almost didnt change. Well, I'm out of ideas, but it's not really a postfix problem when the receiving side is being slow. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Problems with postfix while sending emails
* Rafael Azevedo raf...@gmail.com: It seems that POSTFIX is checking the DNS for that domain (ZOOM4U) and for some reason its taking too long. Do you have a caching DNS server? Also please note that the delays(c) value consists of 4 different timings: 1) time in connection setup, 2) including DNS, 3) EHLO and 4) STARTTLS so you cannot know if: * the connection setup is slow * DNS (finding and resolving the MX)is slow, * if EHLO (or EHLO checks on the receiving side!) or * STARTTLS are slow (if it's being used at all...) You CAN check the timings using debug_peer_list = ... but not to a sub second resolution(since syslog()) is being used. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Problems with postfix while sending emails
* Rafael Azevedo raf...@gmail.com: Ralf, you're the g-e-n-i-o-u-s The problem is with DK-MILTER not DKIM. Doesn't DK-Milter do DKIM? I disable DK-MILTER from main.cf and its just very very very fast! Thanks a lot you guys for the help!! Now things are back to normal! \o/ -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Problems with postfix while sending emails
I might, but DKIM does not need DK-MILTER. Does it? ;p On Tue, Mar 15, 2011 at 1:55 PM, Ralf Hildebrandt ralf.hildebra...@charite.de wrote: * Rafael Azevedo raf...@gmail.com: Ralf, you're the g-e-n-i-o-u-s The problem is with DK-MILTER not DKIM. Doesn't DK-Milter do DKIM? I disable DK-MILTER from main.cf and its just very very very fast! Thanks a lot you guys for the help!! Now things are back to normal! \o/ -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
RE: Problems with postfix while sending emails
-Original Message- From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] On Behalf Of Ralf Hildebrandt Sent: Tuesday, March 15, 2011 9:55 AM To: postfix-users@postfix.org Subject: Re: Problems with postfix while sending emails * Rafael Azevedo raf...@gmail.com: Ralf, you're the g-e-n-i-o-u-s The problem is with DK-MILTER not DKIM. Doesn't DK-Milter do DKIM? No, it only does DomainKeys, which is historic. And dk-milter has bugs, and is no longer supported. Anybody running it should seriously consider turning it off.
Re: Problems with postfix while sending emails
On Tue, Mar 15, 2011 at 12:23 PM, Murray S. Kucherawy m...@cloudmark.com wrote: -Original Message- From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] On Behalf Of Ralf Hildebrandt Sent: Tuesday, March 15, 2011 9:55 AM To: postfix-users@postfix.org Subject: Re: Problems with postfix while sending emails * Rafael Azevedo raf...@gmail.com: Ralf, you're the g-e-n-i-o-u-s The problem is with DK-MILTER not DKIM. Doesn't DK-Milter do DKIM? No, it only does DomainKeys, which is historic. And dk-milter has bugs, and is no longer supported. Anybody running it should seriously consider turning it off. Allow me to second Murray's statement. There's no need to sign with DomainKeys any more, and anyone running a mail server should consider replacing DK signing with DKIM signing (and anyone not signing should consider it). Multiple packages are listed at http://www.postfix.org/addon.html - but I recommend OpenDKIM (http://opendkim.org/), which is insanely easy to set up as as a milter in Posfix. SteveJ
Re: Problems with postfix while sending emails
Steve Jenkins put forth on 3/15/2011 1:34 PM: and anyone not signing should consider it. Anyone not using seat belts and turn signals should consider it. I can see a clear advantage to the latter, but not the former. Can you briefly explain why you believe everyone should sign mail? Before you do, let me share some meager data with you. Inbox spam from Aug 19, 2010 to Mar 15, 2011 Spam: 368 w/DKIM-Sig: 76 Total: 20% with DKIM signature Spam trap from Jan 23, 2011 to Mar 15, 2011 Spam: 1878 w/DKIM-Sig: 1 Total: 0.005% with DKIM signature About 99% of the trap spam could be blocked instantly by simply removing the addresses from a white list, as most of it is bot spam. Note that most of the Inbox DKIM signed spam comes through mailing lists, ~50% from kernel.org. MLMs account for 99+% of my non spam inbound mail. Thus, as you can see, of the stuff that's difficult or impossible to REJECT, 20% of it is signed. How does that signature help me block this 20% ?? -- Stan
Re: Problems with postfix while sending emails
On Tue, Mar 15, 2011 at 8:54 PM, Stan Hoeppner s...@hardwarefreak.com wrote: Steve Jenkins put forth on 3/15/2011 1:34 PM: and anyone not signing should consider it. Anyone not using seat belts and turn signals should consider it. I can see a clear advantage to the latter, but not the former. Can you briefly explain why you believe everyone should sign mail? Hi, Stan. Of course, we both know there's no magic bullet. But signing can help receivers verify the true provenance of the sender's message. Does it guarantee that the message isn't SPAM? Of course not. Every SPAM I've received from a GMail account has been signed. :) But can signing help identify and/or deter some spammers? Sure. And with optional ADSP extension to DKIM, it's even better. I see no downside to signing, and therefore ANY potential upside is a good thing. The resource overhead of DKIM signing and verifying is very low, so what good reason is there to NOT sign? Frankly, I don't know how to answer your 20% question. Maybe on your system, 20% is as good as it's gonna get! But based on what I know about you, I get the sense you're someone who primarily deals with lots of incoming mail. And it always seems that where one stands depends on where one sits. :) I'm sitting on the other side. We process very little incoming mail, but send millions of legitimate emails to our customers every week. DKIM signing them has undeniably increased our inbox deliverability rates, and inbound processors can know that if a mail claims to come from us but isn't signed, it's bogus. Again, with no downside and little-to-no cost, even a small potential upside is a good thing. Respectfully, SteveJ
