Re: Receiving bounce messages back to local-host
CT wrote: Noel Jones wrote: On 4/18/2010 4:40 PM, groups wrote: Noel Jones wrote, On 04/18/2010 04:20 PM: On 4/18/2010 4:16 PM, groups wrote: Postfix logs help you know what happened to a particular message. Look in your logs for bounces (sender=<>) arriving from your relayhost, and see what postfix does with it. No need to wonder where they went. -- Noel Jones A lot of the send only hosts have only an IP (not in DNS) Look in the logs for the IP to find associated QUEUEIDs. Apr 18 16:01:24 mailhost postfix/qmgr[3283]: 5BE9956799: from=<>, size=89424, nrcpt=1 (queue active) Look in the logs for other entries with that same QUEUEID 5BE9956799 to see other information associated with that transaction. only 1 entry per transaction ID.. notthing in /var/spool/postfix ... ok.. and found something interesting.. Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 04C2A56799: from=<>, size=83199, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 2B54756799: from=<>, size=83614, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 4D99856799: from=<>, size=84029, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 7B1F756799: from=<>, size=8, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 9BD4456799: from=<>, size=84859, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: BF6DC56799: from=<>, size=85274, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: E147056799: from=<>, size=85689, nrcpt=1 (queue active) All have the same invalid recipient.. These show the sender and number of recipients = 1; the recipient address is listed in a different log line. That seems like an awful lot of bounces in a short period of time. Sending lots of mail to undeliverable addresses is a red flag that something is wrong -- such as a badly outdated mail list, or a compromised machine spewing spam. One of your tasks is to investigate why there are so many bounces, and find a way to reduce them. Sending large amounts of undeliverable mail will have a bad effect on your server's reputation and may eventually lead to blacklisting. Almost looks like it is "ping-ponging" back and forth between the *master-relay* and my relay.. Messages with the null sender "<>" are never bounced, they must be delivered or discarded. Bounces are always sent with the null sender. This prevents bounces from ever looping (except in rare cases of stupid user tricks such as a .forward that rewrites <> to something else -- don't do that). Further information about those messages can be found in the logs. I have seen this invalid recipient on the old Sendmail box.. and it ended up in my queue then expires.. (the sender host has been out of the office when I tried to contact them) so it looks like I have something not right.. there is nothing in mailq.. Charles You need to examine the log further. If there's a problem, postfix will likely tell you what it is, or at least give you a better idea of where to look. Postfix generates several log lines for each message. You need to look at *all* the lines with the same QUEUEID to see what happened to a message. Logs for a single message look something like this below (with my comments). Because postfix can process many messages in parallel, logs for a single message may be separated by a considerable number of unrelated log entries. There may be more or fewer entries depending on what happens with a transaction, but this is fairly typical. Apr 18 00:00:20 mgate2 postfix/smtpd[91955]: connect from private.webmail.example.org[192.168.70.47] to smtpd (client connected; the hostname and IP are logged) Apr 18 00:00:20 mgate2 postfix/smtpd[91955]: 1A2C779788F: client=private.webmail.example.org[192.168.70.47] (the QUEUEID "1A2C779788F" is assigned. That means there was at least one recipient accepted and a queue file was created. Future lines pertaining to this specific message will include this same QUEUEID) Apr 18 00:00:20 mgate2 postfix/cleanup[92028]: 1A2C779788F: message-id=<1100418.aa11...@example.org> (the Message-id: header is logged. This is a helpful unique message identifier when searching the logs for a specific message.) Apr 18 00:00:20 mgate2 postfix/qmgr[95868]: 1A2C779788F: from=<>, size=382, nrcpt=1 (queue active) (envelope sender, size, number of recipients, which queue it's assigned to) Apr 18 00:00:20 mgate2 postfix/smtpd[91955]: disconnect from private.webmail.vbhcs.org[192.168.70.47] (postfix has disconnected from the client. This line can be related to the "connect" line above by the smtpd process id, in this case "91955") Apr 18 00:00:20 mgate2 postfix/local[94393]: 1A2C779788F: to=, relay=local, delay=0.11, delays=0.05 /0.03/0/0.02, dsn=2.0.0, status=sent (delivered to maildir) (the mail was delivered to a local user) Apr 18 00:00:20 mgate2 postfix/qmgr[95868]: 1A2C779788F: removed (postfix co
Re: Receiving bounce messages back to local-host
Noel Jones wrote: On 4/18/2010 4:40 PM, groups wrote: Noel Jones wrote, On 04/18/2010 04:20 PM: On 4/18/2010 4:16 PM, groups wrote: Postfix logs help you know what happened to a particular message. Look in your logs for bounces (sender=<>) arriving from your relayhost, and see what postfix does with it. No need to wonder where they went. -- Noel Jones A lot of the send only hosts have only an IP (not in DNS) Look in the logs for the IP to find associated QUEUEIDs. Apr 18 16:01:24 mailhost postfix/qmgr[3283]: 5BE9956799: from=<>, size=89424, nrcpt=1 (queue active) Look in the logs for other entries with that same QUEUEID 5BE9956799 to see other information associated with that transaction. only 1 entry per transaction ID.. notthing in /var/spool/postfix ... ok.. and found something interesting.. Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 04C2A56799: from=<>, size=83199, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 2B54756799: from=<>, size=83614, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 4D99856799: from=<>, size=84029, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 7B1F756799: from=<>, size=8, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 9BD4456799: from=<>, size=84859, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: BF6DC56799: from=<>, size=85274, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: E147056799: from=<>, size=85689, nrcpt=1 (queue active) All have the same invalid recipient.. These show the sender and number of recipients = 1; the recipient address is listed in a different log line. That seems like an awful lot of bounces in a short period of time. Sending lots of mail to undeliverable addresses is a red flag that something is wrong -- such as a badly outdated mail list, or a compromised machine spewing spam. One of your tasks is to investigate why there are so many bounces, and find a way to reduce them. Sending large amounts of undeliverable mail will have a bad effect on your server's reputation and may eventually lead to blacklisting. Almost looks like it is "ping-ponging" back and forth between the *master-relay* and my relay.. Messages with the null sender "<>" are never bounced, they must be delivered or discarded. Bounces are always sent with the null sender. This prevents bounces from ever looping (except in rare cases of stupid user tricks such as a .forward that rewrites <> to something else -- don't do that). Further information about those messages can be found in the logs. I have seen this invalid recipient on the old Sendmail box.. and it ended up in my queue then expires.. (the sender host has been out of the office when I tried to contact them) so it looks like I have something not right.. there is nothing in mailq.. Charles You need to examine the log further. If there's a problem, postfix will likely tell you what it is, or at least give you a better idea of where to look. Postfix generates several log lines for each message. You need to look at *all* the lines with the same QUEUEID to see what happened to a message. Logs for a single message look something like this below (with my comments). Because postfix can process many messages in parallel, logs for a single message may be separated by a considerable number of unrelated log entries. There may be more or fewer entries depending on what happens with a transaction, but this is fairly typical. Apr 18 00:00:20 mgate2 postfix/smtpd[91955]: connect from private.webmail.example.org[192.168.70.47] to smtpd (client connected; the hostname and IP are logged) Apr 18 00:00:20 mgate2 postfix/smtpd[91955]: 1A2C779788F: client=private.webmail.example.org[192.168.70.47] (the QUEUEID "1A2C779788F" is assigned. That means there was at least one recipient accepted and a queue file was created. Future lines pertaining to this specific message will include this same QUEUEID) Apr 18 00:00:20 mgate2 postfix/cleanup[92028]: 1A2C779788F: message-id=<1100418.aa11...@example.org> (the Message-id: header is logged. This is a helpful unique message identifier when searching the logs for a specific message.) Apr 18 00:00:20 mgate2 postfix/qmgr[95868]: 1A2C779788F: from=<>, size=382, nrcpt=1 (queue active) (envelope sender, size, number of recipients, which queue it's assigned to) Apr 18 00:00:20 mgate2 postfix/smtpd[91955]: disconnect from private.webmail.vbhcs.org[192.168.70.47] (postfix has disconnected from the client. This line can be related to the "connect" line above by the smtpd process id, in this case "91955") Apr 18 00:00:20 mgate2 postfix/local[94393]: 1A2C779788F: to=, relay=local, delay=0.11, delays=0.05 /0.03/0/0.02, dsn=2.0.0, status=sent (delivered to maildir) (the mail was delivered to a local user) Apr 18 00:00:20 mgate2 postfix/qmgr[95868]: 1A2C779788F: removed (postfix completed this
Re: Receiving bounce messages back to local-host
On 4/18/2010 4:40 PM, groups wrote: Noel Jones wrote, On 04/18/2010 04:20 PM: On 4/18/2010 4:16 PM, groups wrote: Postfix logs help you know what happened to a particular message. Look in your logs for bounces (sender=<>) arriving from your relayhost, and see what postfix does with it. No need to wonder where they went. -- Noel Jones A lot of the send only hosts have only an IP (not in DNS) Look in the logs for the IP to find associated QUEUEIDs. Apr 18 16:01:24 mailhost postfix/qmgr[3283]: 5BE9956799: from=<>, size=89424, nrcpt=1 (queue active) Look in the logs for other entries with that same QUEUEID 5BE9956799 to see other information associated with that transaction. only 1 entry per transaction ID.. notthing in /var/spool/postfix ... ok.. and found something interesting.. Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 04C2A56799: from=<>, size=83199, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 2B54756799: from=<>, size=83614, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 4D99856799: from=<>, size=84029, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 7B1F756799: from=<>, size=8, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 9BD4456799: from=<>, size=84859, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: BF6DC56799: from=<>, size=85274, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: E147056799: from=<>, size=85689, nrcpt=1 (queue active) All have the same invalid recipient.. These show the sender and number of recipients = 1; the recipient address is listed in a different log line. That seems like an awful lot of bounces in a short period of time. Sending lots of mail to undeliverable addresses is a red flag that something is wrong -- such as a badly outdated mail list, or a compromised machine spewing spam. One of your tasks is to investigate why there are so many bounces, and find a way to reduce them. Sending large amounts of undeliverable mail will have a bad effect on your server's reputation and may eventually lead to blacklisting. Almost looks like it is "ping-ponging" back and forth between the *master-relay* and my relay.. Messages with the null sender "<>" are never bounced, they must be delivered or discarded. Bounces are always sent with the null sender. This prevents bounces from ever looping (except in rare cases of stupid user tricks such as a .forward that rewrites <> to something else -- don't do that). Further information about those messages can be found in the logs. I have seen this invalid recipient on the old Sendmail box.. and it ended up in my queue then expires.. (the sender host has been out of the office when I tried to contact them) so it looks like I have something not right.. there is nothing in mailq.. Charles You need to examine the log further. If there's a problem, postfix will likely tell you what it is, or at least give you a better idea of where to look. Postfix generates several log lines for each message. You need to look at *all* the lines with the same QUEUEID to see what happened to a message. Logs for a single message look something like this below (with my comments). Because postfix can process many messages in parallel, logs for a single message may be separated by a considerable number of unrelated log entries. There may be more or fewer entries depending on what happens with a transaction, but this is fairly typical. Apr 18 00:00:20 mgate2 postfix/smtpd[91955]: connect from private.webmail.example.org[192.168.70.47] to smtpd (client connected; the hostname and IP are logged) Apr 18 00:00:20 mgate2 postfix/smtpd[91955]: 1A2C779788F: client=private.webmail.example.org[192.168.70.47] (the QUEUEID "1A2C779788F" is assigned. That means there was at least one recipient accepted and a queue file was created. Future lines pertaining to this specific message will include this same QUEUEID) Apr 18 00:00:20 mgate2 postfix/cleanup[92028]: 1A2C779788F: message-id=<1100418.aa11...@example.org> (the Message-id: header is logged. This is a helpful unique message identifier when searching the logs for a specific message.) Apr 18 00:00:20 mgate2 postfix/qmgr[95868]: 1A2C779788F: from=<>, size=382, nrcpt=1 (queue active) (envelope sender, size, number of recipients, which queue it's assigned to) Apr 18 00:00:20 mgate2 postfix/smtpd[91955]: disconnect from private.webmail.vbhcs.org[192.168.70.47] (postfix has disconnected from the client. This line can be related to the "connect" line above by the smtpd process id, in this case "91955") Apr 18 00:00:20 mgate2 postfix/local[94393]: 1A2C779788F: to=, relay=local, delay=0.11, delays=0.05 /0.03/0/0.02, dsn=2.0.0, status=sent (delivered to maildir) (the mail was delivered to a local user) Apr 18 00:00:20 mgate2 postfix/qmgr[95868]: 1A2C779788F: removed (postfix completed this message, and remov
Re: Receiving bounce messages back to local-host
Noel Jones wrote, On 04/18/2010 04:20 PM: On 4/18/2010 4:16 PM, groups wrote: Postfix logs help you know what happened to a particular message. Look in your logs for bounces (sender=<>) arriving from your relayhost, and see what postfix does with it. No need to wonder where they went. -- Noel Jones A lot of the send only hosts have only an IP (not in DNS) Look in the logs for the IP to find associated QUEUEIDs. Apr 18 16:01:24 mailhost postfix/qmgr[3283]: 5BE9956799: from=<>, size=89424, nrcpt=1 (queue active) Look in the logs for other entries with that same QUEUEID 5BE9956799 to see other information associated with that transaction. only 1 entry per transaction ID.. notthing in /var/spool/postfix ... ok.. and found something interesting.. Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 04C2A56799: from=<>, size=83199, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 2B54756799: from=<>, size=83614, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 4D99856799: from=<>, size=84029, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 7B1F756799: from=<>, size=8, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: 9BD4456799: from=<>, size=84859, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: BF6DC56799: from=<>, size=85274, nrcpt=1 (queue active) Apr 18 16:01:22 mailhost postfix/qmgr[3283]: E147056799: from=<>, size=85689, nrcpt=1 (queue active) All have the same invalid recipient.. Almost looks like it is "ping-ponging" back and forth between the *master-relay* and my relay.. I have seen this invalid recipient on the old Sendmail box.. and it ended up in my queue then expires.. (the sender host has been out of the office when I tried to contact them) so it looks like I have something not right.. there is nothing in mailq.. Charles
Re: Receiving bounce messages back to local-host
On 4/18/2010 4:16 PM, groups wrote: Postfix logs help you know what happened to a particular message. Look in your logs for bounces (sender=<>) arriving from your relayhost, and see what postfix does with it. No need to wonder where they went. -- Noel Jones A lot of the send only hosts have only an IP (not in DNS) Look in the logs for the IP to find associated QUEUEIDs. Apr 18 16:01:24 mailhost postfix/qmgr[3283]: 5BE9956799: from=<>, size=89424, nrcpt=1 (queue active) Look in the logs for other entries with that same QUEUEID 5BE9956799 to see other information associated with that transaction.
Re: Receiving bounce messages back to local-host
Following the firewall/smtp relay page http://www.postfix.org/STANDARD_CONFIGURATION_README.html#firewall Process - internal servers *send* through *my-relay* - *my-relay* forwards to *master-relay* - valid email is passing through for all the clients as expected. - *master-relay* kicks back any undeliverable emails to *my-relay* I want the undeliverable email to be sent and received on *my-relay* and not my work account. - I work with end users to "fix" their undeliverable issue. -- Bounce messages are *not* being received back from the *master-relay* to *my-relay*. Sorry, your question isn't entirely clear to me. Bounces are always sent to the envelope sender. If a downstream relay isn't returning bounces to the envelope sender, you need to take that up with the operators of the downstream relay. If you need to control which user receives the bounce, adjust the envelope sender on OUTGOING mail. If this doesn't cover your question, please try to rephrase or show logs of what occurs vs. what you expect to happen. -- Noel Jones Noel, Thanks for the reply.. I *guess* I was wanting to know that the configuration I *do* have is configured correctly to receive an invalid message sent *through* my relay.. This relay is replacing the old Sendmail relay .. Some clarification. [send only host] => [*my-relay*] => [*master-relay*] => Final-Recipient in the case that the Final-Recipient is invalid for whatever reason.. the *master-relay* returns the message back to *my-relay* .. since the send only host can't receive "their invalid" message it ends up in my queue and then times out.. This worked without incident on the old Sendmail relay.. so I am sure that the (downstream relay) configuration is correct... and the issue is with my new relay.. btw (I will be talking to the downstream relay admin tomorrow to see if they can give me any ideas) I am thinking that I might just need to remove this line local_transport = error:local mail delivery is disabled If the envelope sender (bounce recipient) domain is listed in $mydestination, then yes, you should remove this line OR arrange for that recipient to be delivered elsewhere OR use a different envelope sender that is deliverable. Hope this clarifies the issue.. Postfix logs help you know what happened to a particular message. Look in your logs for bounces (sender=<>) arriving from your relayhost, and see what postfix does with it. No need to wonder where they went. -- Noel Jones A lot of the send only hosts have only an IP (not in DNS) Apr 18 16:01:24 mailhost postfix/qmgr[3283]: 5BE9956799: from=<>, size=89424, nrcpt=1 (queue active) but nothing is in the active queue.. Will keep looking.. Thx again.. Charles But there is nothing in /var/
Re: Receiving bounce messages back to local-host
On 4/18/2010 3:38 PM, Charles wrote: Following the firewall/smtp relay page http://www.postfix.org/STANDARD_CONFIGURATION_README.html#firewall Process - internal servers *send* through *my-relay* - *my-relay* forwards to *master-relay* - valid email is passing through for all the clients as expected. - *master-relay* kicks back any undeliverable emails to *my-relay* I want the undeliverable email to be sent and received on *my-relay* and not my work account. - I work with end users to "fix" their undeliverable issue. -- Bounce messages are *not* being received back from the *master-relay* to *my-relay*. Sorry, your question isn't entirely clear to me. Bounces are always sent to the envelope sender. If a downstream relay isn't returning bounces to the envelope sender, you need to take that up with the operators of the downstream relay. If you need to control which user receives the bounce, adjust the envelope sender on OUTGOING mail. If this doesn't cover your question, please try to rephrase or show logs of what occurs vs. what you expect to happen. -- Noel Jones Noel, Thanks for the reply.. I *guess* I was wanting to know that the configuration I *do* have is configured correctly to receive an invalid message sent *through* my relay.. This relay is replacing the old Sendmail relay .. Some clarification. [send only host] => [*my-relay*] => [*master-relay*] => Final-Recipient in the case that the Final-Recipient is invalid for whatever reason.. the *master-relay* returns the message back to *my-relay* .. since the send only host can't receive "their invalid" message it ends up in my queue and then times out.. This worked without incident on the old Sendmail relay.. so I am sure that the (downstream relay) configuration is correct... and the issue is with my new relay.. btw (I will be talking to the downstream relay admin tomorrow to see if they can give me any ideas) I am thinking that I might just need to remove this line local_transport = error:local mail delivery is disabled If the envelope sender (bounce recipient) domain is listed in $mydestination, then yes, you should remove this line OR arrange for that recipient to be delivered elsewhere OR use a different envelope sender that is deliverable. Hope this clarifies the issue.. Postfix logs help you know what happened to a particular message. Look in your logs for bounces (sender=<>) arriving from your relayhost, and see what postfix does with it. No need to wonder where they went. -- Noel Jones
Re: Receiving bounce messages back to local-host
Following the firewall/smtp relay page http://www.postfix.org/STANDARD_CONFIGURATION_README.html#firewall Process - internal servers *send* through *my-relay* - *my-relay* forwards to *master-relay* - valid email is passing through for all the clients as expected. - *master-relay* kicks back any undeliverable emails to *my-relay* I want the undeliverable email to be sent and received on *my-relay* and not my work account. - I work with end users to "fix" their undeliverable issue. -- Bounce messages are *not* being received back from the *master-relay* to *my-relay*. Sorry, your question isn't entirely clear to me. Bounces are always sent to the envelope sender. If a downstream relay isn't returning bounces to the envelope sender, you need to take that up with the operators of the downstream relay. If you need to control which user receives the bounce, adjust the envelope sender on OUTGOING mail. If this doesn't cover your question, please try to rephrase or show logs of what occurs vs. what you expect to happen. -- Noel Jones Noel, Thanks for the reply.. I *guess* I was wanting to know that the configuration I *do* have is configured correctly to receive an invalid message sent *through* my relay.. This relay is replacing the old Sendmail relay .. Some clarification. [send only host] => [*my-relay*] => [*master-relay*] => Final-Recipient in the case that the Final-Recipient is invalid for whatever reason.. the *master-relay* returns the message back to *my-relay* .. since the send only host can't receive "their invalid" message it ends up in my queue and then times out.. This worked without incident on the old Sendmail relay.. so I am sure that the (downstream relay) configuration is correct... and the issue is with my new relay.. btw (I will be talking to the downstream relay admin tomorrow to see if they can give me any ideas) I am thinking that I might just need to remove this line local_transport = error:local mail delivery is disabled Hope this clarifies the issue.. I really think I am missing something very basic.. and just can't see it.. Thx Charles
Re: Receiving bounce messages back to local-host
On 4/18/2010 11:21 AM, CT wrote: Following the firewall/smtp relay page http://www.postfix.org/STANDARD_CONFIGURATION_README.html#firewall Process - internal servers *send* through *my-relay* - *my-relay* forwards to *master-relay* - valid email is passing through for all the clients as expected. - *master-relay* kicks back any undeliverable emails to *my-relay* I want the undeliverable email to be sent and received on *my-relay* and not my work account. - I work with end users to "fix" their undeliverable issue. -- Bounce messages are *not* being received back from the *master-relay* to *my-relay*. Sorry, your question isn't entirely clear to me. Bounces are always sent to the envelope sender. If a downstream relay isn't returning bounces to the envelope sender, you need to take that up with the operators of the downstream relay. If you need to control which user receives the bounce, adjust the envelope sender on OUTGOING mail. If this doesn't cover your question, please try to rephrase or show logs of what occurs vs. what you expect to happen. -- Noel Jones Particulars -- OS: CentOS 5.4 -- my-dom.TLD = my domain -- SUB-DOM = my sub domain Postfinger --System Parameters-- mail_version = 2.5.1 hostname = mailhost.SUB-DOM.my-dom.TLD uname = Linux mailhost.SUB-DOM.my-dom.TLD 2.6.18-164.15.1.el5 #1 SMP Wed Mar 17 11:37:14 EDT 2010 i686 i686 i386 GNU/Linux --Packaging information-- looks like this postfix comes from RPM package: postfix-2.5.1-1.rhel5 --main.cf non-default parameters-- alias_database = hash:/etc/postfix/aliases alias_maps = hash:/etc/postfix/aliases html_directory = /usr/share/doc/postfix-2.5.1-documentation/html local_transport = error:local mail delivery is disabled mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man mime_header_checks = regexp:/etc/postfix/mime_header_checks.regexp mydestination = mynetworks = ppp.pp.0.0/16, DDD.dd.0.0/16 newaliases_path = /usr/bin/newaliases.postfix readme_directory = /usr/share/doc/postfix-2.5.1-documentation/readme relay_domains = SUB-DOM.my-dom.TLD, my-dom.TLD relayhost = *master-relay*.my-dom.TLD sendmail_path = /usr/sbin/sendmail.postfix smtpd_data_restrictions = reject_unauth_pipelining,permit_mynetworks transport_maps = hash:/etc/postfix/transport unknown_local_recipient_reject_code = 450 virtual_alias_maps = hash:/etc/postfix/virtual --master.cf-- smtp inet n - n - - smtpd pickup fifo n - n 60 1 pickup cleanup unix n - n - 0 cleanup qmgr fifo n - n 300 1 qmgr tlsmgr unix - - n 1000? 1 tlsmgr rewrite unix - - n - - trivial-rewrite bounce unix - - n - 0 bounce defer unix - - n - 0 bounce trace unix - - n - 0 bounce verify unix - - n - 1 verify flush unix n - n 1000? 0 flush proxymap unix - - n - - proxymap proxywrite unix - - n - 1 proxymap smtp unix - - n - - smtp relay unix - - n - - smtp -o smtp_fallback_relay= showq unix n - n - - showq error unix - - n - - error retry unix - - n - - error discard unix - - n - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - n - - lmtp anvil unix - - n - 1 anvil scache unix - - n - 1 scache -- end of postfinger output -- -- /etc/postfix/virtual root r...@mailhost.sub-dom.my-dom.tld me m...@mailhost.sub-dom.my-dom.tld -- /etc/postfix/aliases #root: m...@my-domain.tld root: m...@localhost Thx CT
Re: Receiving bounce messages back to local-host
Following the firewall/smtp relay page http://www.postfix.org/STANDARD_CONFIGURATION_README.html#firewall Process - internal servers *send* through *my-relay* - *my-relay* forwards to *master-relay* - valid email is passing through for all the clients as expected. - *master-relay* kicks back any undeliverable emails to *my-relay* I want the undeliverable email to be sent and received on *my-relay* and not my work account. - I work with end users to "fix" their undeliverable issue. -- Bounce messages are *not* being received back from the *master-relay* to *my-relay*. Particulars -- OS: CentOS 5.4 -- my-dom.TLD = my domain -- SUB-DOM= my sub domain Postfinger --System Parameters-- mail_version = 2.5.1 hostname = mailhost.SUB-DOM.my-dom.TLD uname = Linux mailhost.SUB-DOM.my-dom.TLD 2.6.18-164.15.1.el5 #1 SMP Wed Mar 17 11:37:14 EDT 2010 i686 i686 i386 GNU/Linux --Packaging information-- looks like this postfix comes from RPM package: postfix-2.5.1-1.rhel5 --main.cf non-default parameters-- alias_database = hash:/etc/postfix/aliases alias_maps = hash:/etc/postfix/aliases html_directory = /usr/share/doc/postfix-2.5.1-documentation/html local_transport = error:local mail delivery is disabled mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man mime_header_checks = regexp:/etc/postfix/mime_header_checks.regexp mydestination = mynetworks = ppp.pp.0.0/16, DDD.dd.0.0/16 newaliases_path = /usr/bin/newaliases.postfix readme_directory = /usr/share/doc/postfix-2.5.1-documentation/readme relay_domains = SUB-DOM.my-dom.TLD, my-dom.TLD relayhost = *master-relay*.my-dom.TLD sendmail_path = /usr/sbin/sendmail.postfix smtpd_data_restrictions = reject_unauth_pipelining,permit_mynetworks transport_maps = hash:/etc/postfix/transport unknown_local_recipient_reject_code = 450 virtual_alias_maps = hash:/etc/postfix/virtual --master.cf-- smtp inet n - n - - smtpd pickupfifo n - n 60 1 pickup cleanup unix n - n - 0 cleanup qmgr fifo n - n 300 1 qmgr tlsmgrunix - - n 1000? 1 tlsmgr rewrite unix - - n - - trivial-rewrite bounceunix - - n - 0 bounce defer unix - - n - 0 bounce trace unix - - n - 0 bounce verifyunix - - n - 1 verify flush unix n - n 1000? 0 flush proxymap unix - - n - - proxymap proxywrite unix - - n - 1 proxymap smtp unix - - n - - smtp relay unix - - n - - smtp -o smtp_fallback_relay= showq unix n - n - - showq error unix - - n - - error retry unix - - n - - error discard unix - - n - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - n - - lmtp anvil unix - - n - 1 anvil scacheunix - - n - 1 scache -- end of postfinger output -- -- /etc/postfix/virtual rootr...@mailhost.sub-dom.my-dom.tld mem...@mailhost.sub-dom.my-dom.tld -- /etc/postfix/aliases #root:m...@my-domain.tld root:m...@localhost Thx CT I had asked this about 2 weeks ago but could not test it until it was in place.. I did try the mydestination = $myhostname and mydestination = $my-SUB-DOMAIN.. Thx Ct
Receiving bounce messages back to local-host
Following the firewall/smtp relay page http://www.postfix.org/STANDARD_CONFIGURATION_README.html#firewall Process - internal servers *send* through *my-relay* - *my-relay* forwards to *master-relay* - valid email is passing through for all the clients as expected. - *master-relay* kicks back any undeliverable emails to *my-relay* I want the undeliverable email to be sent and received on *my-relay* and not my work account. - I work with end users to "fix" their undeliverable issue. -- Bounce messages are *not* being received back from the *master-relay* to *my-relay*. Particulars -- OS: CentOS 5.4 -- my-dom.TLD = my domain -- SUB-DOM= my sub domain Postfinger --System Parameters-- mail_version = 2.5.1 hostname = mailhost.SUB-DOM.my-dom.TLD uname = Linux mailhost.SUB-DOM.my-dom.TLD 2.6.18-164.15.1.el5 #1 SMP Wed Mar 17 11:37:14 EDT 2010 i686 i686 i386 GNU/Linux --Packaging information-- looks like this postfix comes from RPM package: postfix-2.5.1-1.rhel5 --main.cf non-default parameters-- alias_database = hash:/etc/postfix/aliases alias_maps = hash:/etc/postfix/aliases html_directory = /usr/share/doc/postfix-2.5.1-documentation/html local_transport = error:local mail delivery is disabled mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man mime_header_checks = regexp:/etc/postfix/mime_header_checks.regexp mydestination = mynetworks = ppp.pp.0.0/16, DDD.dd.0.0/16 newaliases_path = /usr/bin/newaliases.postfix readme_directory = /usr/share/doc/postfix-2.5.1-documentation/readme relay_domains = SUB-DOM.my-dom.TLD, my-dom.TLD relayhost = *master-relay*.my-dom.TLD sendmail_path = /usr/sbin/sendmail.postfix smtpd_data_restrictions = reject_unauth_pipelining,permit_mynetworks transport_maps = hash:/etc/postfix/transport unknown_local_recipient_reject_code = 450 virtual_alias_maps = hash:/etc/postfix/virtual --master.cf-- smtp inet n - n - - smtpd pickupfifo n - n 60 1 pickup cleanup unix n - n - 0 cleanup qmgr fifo n - n 300 1 qmgr tlsmgrunix - - n 1000? 1 tlsmgr rewrite unix - - n - - trivial-rewrite bounceunix - - n - 0 bounce defer unix - - n - 0 bounce trace unix - - n - 0 bounce verifyunix - - n - 1 verify flush unix n - n 1000? 0 flush proxymap unix - - n - - proxymap proxywrite unix - - n - 1 proxymap smtp unix - - n - - smtp relay unix - - n - - smtp -o smtp_fallback_relay= showq unix n - n - - showq error unix - - n - - error retry unix - - n - - error discard unix - - n - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - n - - lmtp anvil unix - - n - 1 anvil scacheunix - - n - 1 scache -- end of postfinger output -- -- /etc/postfix/virtual rootr...@mailhost.sub-dom.my-dom.tld mem...@mailhost.sub-dom.my-dom.tld -- /etc/postfix/aliases #root:m...@my-domain.tld root:m...@localhost Thx CT
