Re: Postfix MX selection
On 12/29/2011 01:00 PM, Stan Hoeppner wrote: On 12/29/2011 5:23 AM, Thomas Bange wrote: Hi, I have a mail stuck in my mail queue. The Mail should be delivered to some.u...@some-domain.de. Looking up MX records for the domain gives me: # host -t mx some-domain.de some-domain.de mail is handled by 100 relay2.netnames.net. some-domain.de mail is handled by 10 relay1.netnames.net. Postfix is always attempting to deliver the mail through relay2.netnames.net, which gives the following error: host relay2.netnames.net[212.53.64.44] said: 451 lowest numbered MX record points to local host (in reply to RCPT TO command) The server seems to have a config problem, but why does Postfix tries to deliver the mail through relay2.netnames.net instead of relay1.netnames.net? This is not a Postfix problem. You know how to use Google yes? Given there is definitely a DNS configuration problem on the remote end, do not assume Postfix is doing something incorrect by attempting delivery to the priority 10 MX host. If it's not a resolver cache issue you need to contact the administrator(s) of the remote systems(s) and inform them of the problem. The valid Postfix related question is why it doesn't try to use relay1.netnames.net for delivery when relay2.netnames.net keeps returning 451s. $ telnet relay1.netnames.net 25 Trying 62.128.158.226... telnet: Unable to connect to remote host: Connection refused Answer: relay1 is not available, which should be logged by postfix too, but the OP missed it somehow. -- Tom
Re: post-install, IPv6-only: could not find any active network interfaces (again)
Sahil Tandon wrote: I do not believe Mark should have to jump through extra hoops, or that you should revert the change. This is a FreeBSD port-specific problem created by me that I will address as soon as I can. Wietse Venema wrote: Considering the short time left before the next stable release I am considering the following schedule: - Revert to Postfix 2.8 behavior, and complete the 2.9 release cycle. - In the 2.10 development cycle, make Postfix build on hosts that have no network interfaces. That would eliminate problems like Mark's hosts without IPv4, FreeBSD port builds on hosts with dysfunctional IPv6, and other weird environments. - In the 2.10 development cycle, (re)start the first phase of the IPv6-on-by-default transition, and do this early enough that there is time to make sure that all maintainers are on board. That would be sad news, considering how long it takes for distributions to jump on each new major version. As long as main.cf gets adjusted if necessary during install to maintain backward compatibility, the builtin default does not matter, as long as the package can be build and installed. Mark
Postfix MX selection
Hi, I have a mail stuck in my mail queue. The Mail should be delivered to some.u...@some-domain.de. Looking up MX records for the domain gives me: # host -t mx some-domain.de some-domain.de mail is handled by 100 relay2.netnames.net. some-domain.de mail is handled by 10 relay1.netnames.net. Postfix is always attempting to deliver the mail through relay2.netnames.net, which gives the following error: host relay2.netnames.net[212.53.64.44] said: 451 lowest numbered MX record points to local host (in reply to RCPT TO command) The server seems to have a config problem, but why does Postfix tries to deliver the mail through relay2.netnames.net instead of relay1.netnames.net? Regards, Thomas
Re: hotmail rate limit
* DN Singh dnsingh@gmail.com: So Ralf, with a score of 99 with ReturnPath, what is the maximum delivery that you have got to hotmail in a single day? on mail.python.org for the last week: 2554 28th 3764 27th 3445 26th 3011 25th 2263 24th 3557 23rd 4279 22nd -- 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: Postfix MX selection
Am 29.12.2011 12:23, schrieb Thomas Bange: Hi, I have a mail stuck in my mail queue. The Mail should be delivered to some.u...@some-domain.de. Looking up MX records for the domain gives me: # host -t mx some-domain.de some-domain.de mail is handled by 100 relay2.netnames.net. some-domain.de mail is handled by 10 relay1.netnames.net. Postfix is always attempting to deliver the mail through relay2.netnames.net, which gives the following error: host relay2.netnames.net[212.53.64.44] said: 451 lowest numbered MX record points to local host (in reply to RCPT TO command) The server seems to have a config problem, but why does Postfix tries to deliver the mail through relay2.netnames.net instead of relay1.netnames.net? Regards, Thomas look at your logs it was first tried on low mx then fallback to higher one unless you havent configured another mailrouting by transport etc -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria
Re: Postfix MX selection
On 12/29/2011 5:23 AM, Thomas Bange wrote: Hi, I have a mail stuck in my mail queue. The Mail should be delivered to some.u...@some-domain.de. Looking up MX records for the domain gives me: # host -t mx some-domain.de some-domain.de mail is handled by 100 relay2.netnames.net. some-domain.de mail is handled by 10 relay1.netnames.net. Postfix is always attempting to deliver the mail through relay2.netnames.net, which gives the following error: host relay2.netnames.net[212.53.64.44] said: 451 lowest numbered MX record points to local host (in reply to RCPT TO command) The server seems to have a config problem, but why does Postfix tries to deliver the mail through relay2.netnames.net instead of relay1.netnames.net? This is not a Postfix problem. You know how to use Google yes? http://www.symantec.com/business/support/index?page=contentid=TECH94141 http://www.linuxspy.info/tag/delivery-error-451-lowest-numbered-mx-record-points-to-local-host/ http://www.zimbra.com/forums/administrators/28113-problem-send-emaill-3.html Note the specific mention of netnames.net showing this problem in April 2009, in the 3rd article above. Given there is definitely a DNS configuration problem on the remote end, do not assume Postfix is doing something incorrect by attempting delivery to the priority 10 MX host. Have you tried flushing your local resolver cache? You do have a local resolver running on your Postfix MTA host do you not? If you do not, it may be a good time to install one to give your increased flexibility, and performance. If it's not a resolver cache issue you need to contact the administrator(s) of the remote systems(s) and inform them of the problem. -- Stan
Postfix-Amavisd quarantined mail inspection
Hello, I am using postfix, amavisd-new, spam assassin, clamav on a gateway system. A short question (I know it's a bit off-topic but I know that people here run similar systems): I've read how to release and/or forward quarantined mail. But can I read the quarantined mails in situ (i.e. in the quarantine directory)? Can I use some utility to display it in human-readable form and examine details (headers, subject, etc.) so I can decide whether it should be released or not? Thanks, Nick
Re: Postfix-Amavisd quarantined mail inspection
On Thursday 29 December 2011 08:15:40 Nikolaos Milas wrote: I am using postfix, amavisd-new, spam assassin, clamav on a gateway system. A short question (I know it's a bit off-topic but I know that people here run similar systems): I've read how to release and/or forward quarantined mail. But can I read the quarantined mails in situ (i.e. in the quarantine directory)? Can I use some utility to display it in human- readable form and examine details (headers, subject, etc.) so I can decide whether it should be released or not? What did you try? If the quarantine is a maildir, each message is in a separate file. Any pager or viewer or editor can view it. I like mc(1), which has file management bundled with a viewer and editor. If you need more than the plaintext payload, such as MIME decoding and/or HTML rendering (the latter might not be a good idea with spam and virus suspects), you can open the maildir in any MUA which can read a maildir. (You might want to open the maildir in a read-only mode, so as to avoid moving the messages and possibly upsetting the amavisd-new quarantine mechanism.) And of course the amavisd-new list would be a better place to follow up. -- http://rob0.nodns4.us/ -- system administration and consulting Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
Re: Postfix-Amavisd quarantined mail inspection
Ask, not all.. On Dec 29, 2011 9:28 AM, Simon Brereton simon.brere...@buongiorno.com wrote: On Dec 29, 2011 9:15 AM, Nikolaos Milas nmi...@noa.gr wrote: Hello, I am using postfix, amavisd-new, spam assassin, clamav on a gateway system. A short question (I know it's a bit off-topic but I know that people here run similar systems): I've read how to release and/or forward quarantined mail. But can I read the quarantined mails in situ (i.e. in the quarantine directory)? Can I use some utility to display it in human-readable form and examine details (headers, subject, etc.) so I can decide whether it should be released or not? Cat works for me - but all on the amavis list. I believe there's a command for it. Simon
AW: Postfix MX selection
But that does not explain why there was no delivery attempt made on the low MX. After disabling my transport rule for that domain and stopping/starting postfix it now tries to deliver the mail to both MX. Now only the guys at netnames.net need to fix their servers... Regards, Thomas
Re: Upgrade ...
On Thu, 29 Dec 2011, Barbara M. wrote: My plan is to update Postfix (and dovecot, procmail), in the old box to the release in the new box and when tested, move user/data to the new box (new box is 64 bit while old box is 32 bit, but hope this isn't a problem). Copying the old /etc/postfix dir to the new server and restarting the service seems work well (not tested local delivery, procmail, ...). There is some guidolines that I can study/follow to have a painless migration? Funny, I just did a server migration. =) Caveat: I don't run CentOS (which is Red Hat based), I run Debian. I wound up doing a dist-upgrade for my old server to bring it up to current Stable (Squeeze), to make sure that everything was on par with what's current in the latest version of Postfix, and then pretty much ported over my requisite files - straight copy of /etc/postfix aliases, and hand alteration of the existing main.cf. I didn't port over master.cf because the new one contained features than what I already had in place. (Much of my configuration was current back in '03, when that server first came up under Mandrake. Those were the days) This said, if it's possible, I'd highly recommend doing an in-place version upgrade for the distribution you're using - but to avoid killing the server, make sure you can downgrade, that it's not going to break, or that you have a fallback if necessary. I have no idea what CentOS will do if you do such a thing, so check with their support channels before you go that route and find out what to do in order to avoid blowing up that server. -Dennis
Re: post-install, IPv6-only: could not find any active network interfaces (again)
Mark Martinec: Sahil Tandon wrote: I do not believe Mark should have to jump through extra hoops, or that you should revert the change. This is a FreeBSD port-specific problem created by me that I will address as soon as I can. Wietse Venema wrote: Considering the short time left before the next stable release I am considering the following schedule: - Revert to Postfix 2.8 behavior, and complete the 2.9 release cycle. - In the 2.10 development cycle, make Postfix build on hosts that have no network interfaces. That would eliminate problems like Mark's hosts without IPv4, FreeBSD port builds on hosts with dysfunctional IPv6, and other weird environments. - In the 2.10 development cycle, (re)start the first phase of the IPv6-on-by-default transition, and do this early enough that there is time to make sure that all maintainers are on board. That would be sad news, considering how long it takes for distributions to jump on each new major version. This problem has an excellent solution. Change the built-in default now for long-term future compatibility, and edit main.cf at install time now for short-term historical compatibility. As long as main.cf gets adjusted if necessary during install to maintain backward compatibility, the builtin default does not matter, as long as the package can be build and installed. The built-in default matters big time for the majority of sites that use Postfix on IPv4-only networks. They will see an unexpected drop in performance as Postfix makes useless DNS lookups and useless IPv6 connection attempts. This is why I must require that both parts of the above solution are implemented, or none at all. There is not much time left for me to work on the 2.9 stable release, and I don't want to be distracted by open problems with ports maintainers. Wietse
AW: Postfix MX selection
look at your logs I did that (before posting). it was first tried on low mx There was no delivery attempt made on the low MX. then fallback to higher one All attempts where made against the high MX. unless you havent configured another mailrouting by transport etc Now I configured a transport rule to route mail to the domain explicitly through relay1.netnames.net. relay1.netnames.net is reachable, but fails with the same error (lowest numbered MX record points to local host (in reply to RCPT TO command)). So both MX for that domain seem to be broken. But that does not explain why there was no delivery attempt made on the low MX. I also queried different DNS servers for MX records on the domain, they all returned the same results as in my first post (and yes, I do have local resolvers running). So I guess this is not a DNS issue (at least not on my end). Regards, Thomas
Re: Postfix-Amavisd quarantined mail inspection
On 12/29/11 3:15 PM, Nikolaos Milas wrote: Hello, I am using postfix, amavisd-new, spam assassin, clamav on a gateway system. A short question (I know it's a bit off-topic but I know that people here run similar systems): I've read how to release and/or forward quarantined mail. But can I read the quarantined mails in situ (i.e. in the quarantine directory)? Can I use some utility to display it in human-readable form and examine details (headers, subject, etc.) so I can decide whether it should be released or not? please use the amavisd-new mailing list for this topic: List-Subscribe: http://lists.amavis.org/cgi-bin/mailman/listinfo/amavis-users, mailto:amavis-users-requ...@amavis.org?subject=subscribe /rolf
Re: Postfix-Amavisd quarantined mail inspection
On Dec 29, 2011 9:15 AM, Nikolaos Milas nmi...@noa.gr wrote: Hello, I am using postfix, amavisd-new, spam assassin, clamav on a gateway system. A short question (I know it's a bit off-topic but I know that people here run similar systems): I've read how to release and/or forward quarantined mail. But can I read the quarantined mails in situ (i.e. in the quarantine directory)? Can I use some utility to display it in human-readable form and examine details (headers, subject, etc.) so I can decide whether it should be released or not? Cat works for me - but all on the amavis list. I believe there's a command for it. Simon
Upgrade ...
I read the already suggested:
http://stevejenkins.com/blog/2011/01/building-postfix-2-8-on-rhel5-centos-5-
from-source/
My current situation is:
- Old server CentOS 4.x based (Postfix 2.2)
I want to migrate to a new CentOS 6.x (Postfix 2.6)
My plan is to update Postfix (and dovecot, procmail), in the old box to
the release in the new box and when tested, move user/data to the new box
(new box is 64 bit while old box is 32 bit, but hope this isn't a
problem).
Copying the old /etc/postfix dir to the new server and restarting the
service seems work well (not tested local delivery, procmail, ...).
There is some guidolines that I can study/follow to have a painless
migration?
Thanks, B.
Attached my old postconf (if useful)
-
2bounce_notice_recipient = postmaster
access_map_reject_code = 554
address_verify_default_transport = $default_transport
address_verify_local_transport = $local_transport
address_verify_map =
address_verify_negative_cache = yes
address_verify_negative_expire_time = 3d
address_verify_negative_refresh_time = 3h
address_verify_poll_count = 3
address_verify_poll_delay = 3s
address_verify_positive_expire_time = 31d
address_verify_positive_refresh_time = 7d
address_verify_relay_transport = $relay_transport
address_verify_relayhost = $relayhost
address_verify_sender = postmaster
address_verify_service_name = verify
address_verify_transport_maps = $transport_maps
address_verify_virtual_transport = $virtual_transport
alias_database = hash:/etc/postfix/aliases
alias_maps = hash:/etc/postfix/aliases
allow_mail_to_commands = alias, forward
allow_mail_to_files = alias, forward
allow_min_user = no
allow_percent_hack = yes
allow_untrusted_routing = no
alternate_config_directories =
always_bcc =
anvil_rate_time_unit = 60s
anvil_status_update_time = 600s
append_at_myorigin = yes
append_dot_mydomain = yes
application_event_drain_time = 100s
authorized_flush_users = static:anyone
authorized_mailq_users = static:anyone
authorized_submit_users = static:anyone
backwards_bounce_logfile_compatibility = yes
berkeley_db_create_buffer_size = 16777216
berkeley_db_read_buffer_size = 131072
best_mx_transport =
biff = yes
body_checks =
body_checks_size_limit = 51200
bounce_notice_recipient = postmaster
bounce_queue_lifetime = 3d
bounce_service_name = bounce
bounce_size_limit = 5
broken_sasl_auth_clients = no
canonical_classes = envelope_sender, envelope_recipient, header_sender,
header_recipient
canonical_maps =
cleanup_service_name = cleanup
command_directory = /usr/sbin
command_execution_directory =
command_expansion_filter =
1234567890!@%-_=+:,./abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ
command_time_limit = 3000
config_directory = /etc/postfix
connection_cache_service = scache
connection_cache_status_update_time = 600s
connection_cache_ttl_limit = 2s
content_filter =
daemon_directory = /usr/libexec/postfix
daemon_timeout = 18000s
debug_peer_level = 2
debug_peer_list =
default_database_type = hash
default_delivery_slot_cost = 5
default_delivery_slot_discount = 50
default_delivery_slot_loan = 3
default_destination_concurrency_limit = 20
default_destination_recipient_limit = 50
default_extra_recipient_limit = 1000
default_minimum_delivery_slots = 3
default_privs = nobody
default_process_limit = 100
default_rbl_reply = $rbl_code Service unavailable; $rbl_class [$rbl_what]
blocked using $rbl_domain${rbl_reason?; $rbl_reason}
default_recipient_limit = 1
default_transport = smtp
default_verp_delimiters = -=
defer_code = 450
defer_service_name = defer
defer_transports =
delay_notice_recipient = postmaster
delay_warning_time = 0h
deliver_lock_attempts = 20
deliver_lock_delay = 1s
disable_dns_lookups = no
disable_mime_input_processing = no
disable_mime_output_conversion = no
disable_verp_bounces = no
disable_vrfy_command = no
dont_remove = 0
double_bounce_sender = double-bounce
duplicate_filter_limit = 1000
empty_address_recipient = MAILER-DAEMON
enable_original_recipient = yes
error_notice_recipient = postmaster
error_service_name = error
execution_directory_expansion_filter =
1234567890!@%-_=+:,./abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ
expand_owner_alias = no
export_environment = TZ MAIL_CONFIG
fallback_relay =
fallback_transport =
fast_flush_domains = $relay_domains
fast_flush_purge_time = 7d
fast_flush_refresh_time = 12h
fault_injection_code = 0
flush_service_name = flush
fork_attempts = 5
fork_delay = 1s
forward_expansion_filter =
1234567890!@%-_=+:,./abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ
forward_path = $home/.forward${recipient_delimiter}${extension},
$home/.forward
hash_queue_depth = 1
hash_queue_names = deferred, defer
header_address_token_limit = 10240
header_checks =
header_size_limit = 102400
helpful_warnings = yes
home_mailbox = Mailbox
hopcount_limit = 50
html_directory = no
ignore_mx_lookup_error = no
import_environment = MAIL_CONFIG MAIL_DEBUG MAIL_LOGTAG TZ XAUTHORITY
DISPLAY
Re: hotmail rate limit
I am implementing SPF one some domains that were without. Already looking at DKIM, making some tests and will implement soon… And getting to the next steps… Ralf, those numbers are per hour ? Or Per day ? At this moment i can send around 2k emails to hotmail per hour with a score of 65 in return path... On Dec 29, 2011, at 7:10 PM, Ralf Hildebrandt wrote: * DN Singh dnsingh@gmail.com: So Ralf, with a score of 99 with ReturnPath, what is the maximum delivery that you have got to hotmail in a single day? on mail.python.org for the last week: 2554 28th 3764 27th 3445 26th 3011 25th 2263 24th 3557 23rd 4279 22nd -- 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: hotmail rate limit
On 12/29/2011 7:12 PM, Helder Oliveira wrote: Ralf, those numbers are per hour ? Or Per day ? It's pretty clear they are per day. Note the question asked in a single day. Then see Ralf's answer contains dates/days: 22nd - 28th On Dec 29, 2011, at 7:10 PM, Ralf Hildebrandt wrote: So Ralf, with a score of 99 with ReturnPath, what is the maximum delivery that you have got to hotmail in a single day? on mail.python.org for the last week: 2554 28th 3764 27th 3445 26th 3011 25th 2263 24th 3557 23rd 4279 22nd -- Stan
alias map size limit
Dear List, Is there any performance related or other concerns if I try to send mail to a group containing thousands of users (say 8000) using the alias map? In case we want to use alias map for this, then which type of db we should use? With regards, Goutam
Re: Upgrade ...
On Thu, 29 Dec 2011, Barbara M. wrote: I read the already suggested: http://stevejenkins.com/blog/2011/01/building-postfix-2-8-on-rhel5-centos-5- from-source/ My current situation is: - Old server CentOS 4.x based (Postfix 2.2) I want to migrate to a new CentOS 6.x (Postfix 2.6) My plan is to update Postfix (and dovecot, procmail), in the old box to the release in the new box and when tested, move user/data to the new box (new box is 64 bit while old box is 32 bit, but hope this isn't a problem). Copying the old /etc/postfix dir to the new server and restarting the service seems work well (not tested local delivery, procmail, ...). There is some guidolines that I can study/follow to have a painless migration? Thanks, B. At least, I would recommend you to read all the release notes of all version from yours to the past from here: http://www.postfix.org/announcements.html You could maybe find there something usefull... Tomas
