using alias_maps and virtual_alias_maps hand-in-hand
Hi!
I thought I could combine (chain together) my alias_{database,maps}
tables with my virtual_alias_maps table.
I figured that if I specify in my aliases table:
root: daniell
and in my virtual table:
daniell daniell@email_address
then mails for root from localhost would end up in the specified
daniell@email_address mailbox (on another machine, using relayhost).
Unfortunatelly sending mail to root ends up in the local mailbox of the
daniell user, altough sending mail to the daniell user ends up in the
daniell@email_address mailbox.
Now I know that I could simply change the alias table to forward mails
for root to the daniell@email_address address, but I can't help but to
remain curious about how could I make the above chaining work.
# postconf -n
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
inet_interfaces = loopback-only
inet_protocols = ipv4
mailbox_size_limit = 0
mydestination = hostname, localhost.localdomain, localhost
myhostname = hostname
mynetworks = 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
readme_directory = no
recipient_delimiter = +
relayhost = [relayhost]
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtpd_use_tls = yes
virtual_alias_maps = hash:/etc/postfix/virtual
Thanks,
Daniel
--
LÉVAI Dániel
PGP key ID = 0x83B63A8F
Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
Re: Ubuntu Upgrade broke my TLS
On 13/12/12 06:26, Stan Hoeppner wrote: On 12/12/2012 6:05 PM, Tony Nelson wrote: I think it's in my best interest to get TLS operational again. So, you encrypt the transmission from the internal corporate groupware server to the gateway server via a private network that you completely control. But then you relay the same message over the public internet in plain text. TLS encrypts the whole connection including the authentication - maybe the OP is more concerned about passwords being sent in plain text than the contents of the actual email. There seems to be a flaw in your logic, in your threat assessment. Your stated posture makes it seem you are more worried about malicious packet sniffing inside your perimeter than outside.
Postfix stable release 2.9.5 and legacy releases 2.8.13, 2.7.12, 2.6.18
[An on-line version of this announcement will be available at
http://www.postfix.org/announcements/postfix-2.9.5.html]
Postfix stable release 2.9.5, and legacy releases 2.8.13, 2.7.12,
2.6.18 are available. They contain fixes and workarounds that are
also part of Postfix 2.10.
Postfix 2.9 only:
* False error (missing ] character) when a reject_{rhs,dns}bl_*
or permit_{rhs,dns}wl_* reply pattern started with [. Reported
by Martijn Brinkers.
Postfix 2.8 and later:
* The postscreen_access_list feature failed to ignore case in the
first character of a command (e.g., permit, reject, etc.).
Reported by Francis Picabia. (This fix is incorrectly listed
in the HISTORY files of earlier releases, and will be removed
with a future patch.)
All supported releases:
* Strip the datalink suffix (e.g., %eth0) from IPv6 addresses
returned by the system getaddrinfo() routine. Such suffixes
break the default mynetworks value, the Postfix SMTP server's
reverse/forward DNS name/address mapping check, and possibly
more.
* To eliminate the possibility of collisions with connection cache
lookup keys, the Postfix LDAP client now computes those lookup
keys by joining the number-valued connection properties with
ASCII null, just like it already did with the string-valued
connection properties.
* There was a memory leak during one-time TLS library initialization
(introduced with Postfix 2.5). Reported by Coverity.
* There was a memory leak in the unused oqmgr(8) program (introduced
with Postfix 2.3). Reported by Coverity.
You can find the updated Postfix source code at the mirrors listed
at http://www.postfix.org/.
Wietse
Re: Postfix stable release 2.9.5 and legacy releases 2.8.13, 2.7.12, 2.6.18
Wietse,
The requested URL /announcements/postfix-2.9.5.html was not found on
this server.
,-(
marko
Am 2012-12-13 14:08, schrieb Wietse Venema:
[An on-line version of this announcement will be available at
http://www.postfix.org/announcements/postfix-2.9.5.html]
Postfix stable release 2.9.5, and legacy releases 2.8.13, 2.7.12,
2.6.18 are available. They contain fixes and workarounds that are
also part of Postfix 2.10.
Postfix 2.9 only:
* False error (missing ] character) when a reject_{rhs,dns}bl_*
or permit_{rhs,dns}wl_* reply pattern started with [. Reported
by Martijn Brinkers.
Postfix 2.8 and later:
* The postscreen_access_list feature failed to ignore case in the
first character of a command (e.g., permit, reject, etc.).
Reported by Francis Picabia. (This fix is incorrectly listed
in the HISTORY files of earlier releases, and will be removed
with a future patch.)
All supported releases:
* Strip the datalink suffix (e.g., %eth0) from IPv6 addresses
returned by the system getaddrinfo() routine. Such suffixes
break the default mynetworks value, the Postfix SMTP server's
reverse/forward DNS name/address mapping check, and possibly
more.
* To eliminate the possibility of collisions with connection cache
lookup keys, the Postfix LDAP client now computes those lookup
keys by joining the number-valued connection properties with
ASCII null, just like it already did with the string-valued
connection properties.
* There was a memory leak during one-time TLS library
initialization
(introduced with Postfix 2.5). Reported by Coverity.
* There was a memory leak in the unused oqmgr(8) program
(introduced
with Postfix 2.3). Reported by Coverity.
You can find the updated Postfix source code at the mirrors listed
at http://www.postfix.org/.
Wietse
Re: Ubuntu Upgrade broke my TLS
On 12/13/2012 1:51 AM, Reindl Harald wrote: Am 13.12.2012 07:26, schrieb Stan Hoeppner: On 12/12/2012 6:05 PM, Tony Nelson wrote: I think it's in my best interest to get TLS operational again. So, you encrypt the transmission from the internal corporate groupware server to the gateway server via a private network that you completely control. But then you relay the same message over the public internet in plain text. There seems to be a flaw in your logic, in your threat assessment. Your stated posture makes it seem you are more worried about malicious packet sniffing inside your perimeter than outside which is reality in the real life there is MUCH more danger that someone connects to your LAN than somebody is able to do the same at ISP level In order to sniff the SMTP traffic from the Exchange server to the Postfix server, someone on the LAN, as you put it, would first need to gain admin access to one of the switches or segment routers, then clone one of the two ports, then sniff the traffic. Or clone the traffic on an ISL, assuming the two servers are not on the same switch. In a well managed network with strong authentication on network devices, I find this scenario extremely unlikely. However, this is a tangential argument. The point of my post is that if one isn't doing TLS (opportunistic or full time) between the gateway and remote MX hosts, then using TLS between the Exchange sever and gateway is irrelevant and unnecessary. -- Stan
Re: Ubuntu Upgrade broke my TLS
On 12/13/2012 5:01 AM, Ned Slider wrote: On 13/12/12 06:26, Stan Hoeppner wrote: On 12/12/2012 6:05 PM, Tony Nelson wrote: I think it's in my best interest to get TLS operational again. So, you encrypt the transmission from the internal corporate groupware server to the gateway server via a private network that you completely control. But then you relay the same message over the public internet in plain text. TLS encrypts the whole connection including the authentication - maybe the OP is more concerned about passwords being sent in plain text than the contents of the actual email. Interesting. How many passwords would potentially be exposed in this scenario Ned? -- Stan
transportmap ignores A record?
Hi, #currently investigating a masive mailbounce I'm running postfix 2.9.4 on freebsd boxen. Is it intentional that a transportmap reading in the form domain etrn-only:hostname intentionally ignores the A record of hostname? In dns, hostname is like domainname has address A domainname has IPv6 address -1 domainname has IPv6 address -2 domainname mail is handled by 10 blah-1 domainname mail is handled by 10 blah-2 It keeps trying both addresses in a loadballanced manner I intented, but blatantly ignores a usabable A host. Am I missing some point here, or overlook a snippet of doc. Regards, Robert
Re: Ubuntu Upgrade broke my TLS
Tony Nelson skrev den 13-12-2012 02:04: It appears that my upgrade didn't go so well. After running apt-get update/upgrade I ended up upgrading some 250+ packages, including Postfix. I now have 2.9.3-2~12.04.4 as you suggested and TLS has started working again. thanks for using opensource that are precompiled :=) with freebsd/gentoo this problem would not exists
Re: Ubuntu Upgrade broke my TLS
Actually I have TLS working both internally and externally. The only problem I was experiencing that I could adequately describe to the list was internally to my exchange servers. It was 100% repeatable. My theory was that if I resolved the internal problem any other similar related problems would be fixed as well. Thank you again to everyone who helped me resolve my issue. Everything seems fine today. -Tony On Dec 13, 2012, at 1:27 AM, Stan Hoeppner s...@hardwarefreak.com wrote: On 12/12/2012 6:05 PM, Tony Nelson wrote: I think it's in my best interest to get TLS operational again. So, you encrypt the transmission from the internal corporate groupware server to the gateway server via a private network that you completely control. But then you relay the same message over the public internet in plain text. There seems to be a flaw in your logic, in your threat assessment. Your stated posture makes it seem you are more worried about malicious packet sniffing inside your perimeter than outside. -- Stan Since 1982, Starpoint Solutions has been a trusted source of human capital and solutions. We are committed to our clients, employees, environment, community and social concerns. We foster an inclusive culture based on trust, respect, honesty and solid performance. Learn more about Starpoint and our social responsibility at http://www.starpoint.com/social_responsibility This email message from Starpoint Solutions LLC is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Opinions, conclusions and other information in this message that do not relate to the official business of Starpoint Solutions shall be understood as neither given nor endorsed by it.
Re: Ubuntu Upgrade broke my TLS
On Thursday, December 13, 2012 03:05:12 PM Benny Pedersen wrote: Tony Nelson skrev den 13-12-2012 02:04: It appears that my upgrade didn't go so well. After running apt-get update/upgrade I ended up upgrading some 250+ packages, including Postfix. I now have 2.9.3-2~12.04.4 as you suggested and TLS has started working again. thanks for using opensource that are precompiled :=) with freebsd/gentoo this problem would not exists Thanks for spread FUD about other FOSS projects. If the OP had left his system in the default configuration and installed all available updates, the problem would not have existed. Being on FreeBSD or Gentoo wouldn't help if the system isn't kept up to date. Scott K
Re: SASL auth and (local) relaying through telnet
On Sun, 09 Dec 2012 16:37:12 +0100 mouss mo...@ml.netoyen.net wrote: humour mew :) you like cats too? or is it the pipe that you like? $ sudo grep /var/log/mail.log saves a few keystorkes For some odd reason I kindda do. Maybe it's the concept of a data-pipe itself, but I imagine I from now on is to lacy to use it together with grep :) /humour If at all possible, I would like the system not to accept the mail. why not? because you sent it using the telnet client program? there is no fundamental difference between mail sent using a standard MUA (thunderbird, outlook, ...) or a program such as telnet, netcat, ... or a script using perl, python, php, ... and no, spammers do not use the telnet program. that would be too slow! they (generally) use spam bots, which can send masse mails in a short time. trying to detect such bots is teh subject of anti-spam measures such as postcreen, greylisting, spam filters (that look for specific headers or other). I see. It makes plenty of sense, and yes, off course this could be scriptet as well, I just thought the example with telnet was easy to illustrate. It might just be me and my wicked way of thinking that made me ask this question, but I'm glad I did even though the premises was wrong, since I leaned some new things. Thanks for all the replies. Cheers
Re: transportmap ignores A record?
On 12/13/2012 7:53 AM, Robert Joosten wrote: Hi, #currently investigating a masive mailbounce I'm running postfix 2.9.4 on freebsd boxen. Is it intentional that a transportmap reading in the form domain etrn-only:hostname intentionally ignores the A record of hostname? Some possibly related doc snippets; http://www.postfix.org/transport.5.html ... In the case of SMTP, specify a service on a non-default port as host:service, and disable MX (mail exchanger) DNS lookups with [host] or [host]:port http://www.postfix.org/postconf.5.html#smtp_address_preference ... The setting smtp_address_preference = ipv6 is unsafe. It can fail to deliver mail when there is an outage that affects IPv6, while the destination is still reachable over IPv4. Sorry for the generic help, but that kind of goes along with the generic problem report. If you need more help, please see http://www.postfix.org/DEBUG_README.html#mail -- Noel Jones
Mail Encoding
I am not sure where the fault in this lies. When using my iPhone and emailing through postfix to an Exchange server and Outlook client, a simple message like Please call me comes up in Outlook as 2+\��pz(!��)h���θ���v��jy2��y�ڜ I then resend the same message from the same iPhone via a different Exchange server (rather that my postfix server) to the same recipient scenario and the message is received correctly. I am not sure where to go. Suggestions on what to look for or how to track this down? Thanks Steffan
Re: Ubuntu Upgrade broke my TLS
On Thu, 13 Dec 2012 09:40:50 -0500 Scott Kitterman articulated: Being on FreeBSD or Gentoo wouldn't help if the system isn't kept up to date. +1 -- Jerry ✌ postfix-u...@seibercom.net _ TO REPORT A PROBLEM see http://www.postfix.org/DEBUG_README.html#mail TO (UN)SUBSCRIBE see http://www.postfix.org/lists.html
Re: Ubuntu Upgrade broke my TLS
Scott Kitterman skrev den 13-12-2012 15:40: Being on FreeBSD or Gentoo wouldn't help if the system isn't kept up to date. same problem goes with windows :) i miss DS in junc.org thanks to org tld i can not secure dkim :(
Re: Mail Encoding
Steffan A. Cline skrev den 13-12-2012 16:19: Suggestions on what to look for or how to track this down? we cant help with exchange servers without knowing output config from either postfinger or postconf -n thanks for using postfix
Re: Ubuntu Upgrade broke my TLS
Jerry skrev den 13-12-2012 17:24: Being on FreeBSD or Gentoo wouldn't help if the system isn't kept up to date. +1 +2, point is the problem is less on the above 2
Re: Mail Encoding
On Thu, Dec 13, 2012 at 08:19:35AM -0700, Steffan A. Cline wrote: I am not sure where the fault in this lies. When using my iPhone and emailing through postfix to an Exchange server and Outlook client, a simple message like Please call me comes up in Outlook as 2+\??pz(!???)h???v??jy2??y?? I then resend the same message from the same iPhone via a different Exchange server (rather that my postfix server) to the same recipient scenario and the message is received correctly. I am not sure where to go. Suggestions on what to look for or how to track this down? You need to capture a copy of the message as it passes through Postfix, use sender_bcc_maps with a suitably uncommon sender address to avoid capturing unrelated traffic. Direct messages for the bcc recipient to a dedicated mbox or maildir. Once the message is received, post a copy here. We need to see the MIME encoding of the iPhone's original message. Exchange re-encodes MIME messages into MAPI in an irreversible way so not much useful can be learned by looking at the Exchange mailbox alone. If you can configure an IMAP client (say mutt) to talk to Exchange's IMAP server, also post the rfc822 message source as seen by mutt (e.g. save the message to an mbox file). -- Viktor.
Re: using alias_maps and virtual_alias_maps hand-in-hand
On Thu, Dec 13, 2012 at 10:55:35AM +0100, LEVAI Daniel wrote:
I thought I could combine (chain together) my alias_{database,maps}
tables with my virtual_alias_maps table.
I figured that if I specify in my aliases table:
root: daniell
and in my virtual table:
daniell daniell@email_address
then mails for root from localhost would end up in the specified
daniell@email_address mailbox (on another machine, using relayhost).
The local(8) delivery agent does not recurse into virtual(5) alias
expansion when expanding local aliases(5). If an address on the
right side of an alias resolves to a domain in $mydestination (after
append_at_myorigin or append_to_mydomain as required) it is delivered
in by the same delivery agent after additional aliases(5) expansion,
and is not reprocessed as a new message via cleanup(8).
This is for compatibility with legacy Sendmail behaviour with
respect to loop-detection, ...
My approach is to handle all mail forwarding in virtual_alias_maps,
and to ensure that the domain behind $myorigin is NOT listed in
$mydestination. Rather mydestination = localhost.$mydomain or
perhaps even mydestination = localhost.invalid, and mail only
ends up in the local mailer's clutches when explicitly forced there
via a rewrite:
mailbox@domain local-mailbox@localhost.invalid
When local-mailbox is expanded via aliases(5), the only addresses
on the right side of aliases that end up in mailboxes rather than
forwarded back into the queue for reprocessing are those that
explicitly resolve to the local domain:
local-mailbox: foo, bar@localhost.invalid
The foo@$myorigin recipient will be forwarded back into the
queue for processing via cleanup(8), (thus virtual(5), ...),
while bar@localhost.invalid will be delivered directly.
The local(8) delivery agent is legacy Sendmail compatibility, use
it sparingly. Its most useful feature is :include: support for
integration with mailing-list managers.
Very few people still read email out of mbox files in /var/spool/mail,
an MTA typically delivers email into a mail-store (Dovecot, Cyrus, ...)
and the legacy support in local(8) should be used exclusively for any
pipe targets that can't easily be supported by other means and for
:include: lists. Don't use aliases(5) for mail forwarding to rfc822
addresses, that's what virtual(5) is for.
--
Viktor.
How to change modified cf files to postconf commands
In the totorial: http://www.campworld.net/thewiki/pmwiki.php/LinuxServersCentOS/Cent6VirtMailServer There are modified postfix .cf files. I don't want to just use a modified postfix file, I want to user postconf to do the modifications. And I am not experienced using things like diff to work out what changes were made from the base install files. Can anyone lend some expertise in identifying the mods so I can work this up as postconf commands? I will be working on this over the next few days. I hope.
Tool to read queued messages?
Hi all, was wondering if anyone has a handy tool, cat -v and pipe to something, perl class, etc. for outputting a queued message file to stdout but have the line breaks display rather than the control characters? It's difficult to troubleshoot where deferred messages from mailer-daemon originally came from when looking at the raw files because all the headers, postfix control info and message body are displayed together as two long lines. Thanks, David
Re: How to change modified cf files to postconf commands
On 12/13/2012 4:17 PM, Robert Moskowitz wrote: In the totorial: http://www.campworld.net/thewiki/pmwiki.php/LinuxServersCentOS/Cent6VirtMailServer There are modified postfix .cf files. I don't want to just use a modified postfix file, I want to user postconf to do the modifications. And I am not experienced using things like diff to work out what changes were made from the base install files. Can anyone lend some expertise in identifying the mods so I can work this up as postconf commands? Why? If you're just going to paste in changes it doesn't matter too much if you paste in a pre-made .cf file or if you run a bunch of postconf commands. Better to learn why each line is there, and why. And most important, if *you* need it. http://www.postfix.org/documentation.html http://www.postfix.org/STANDARD_CONFIGURATION_README.html http://www.postfix.org/VIRTUAL_README.html main.cf parameters and their defaults are documented here: http://www.postfix.org/postconf.5.html Generally, only parameters that differ from their default should be included in your main.cf. -- Noel Jones
Re: Tool to read queued messages?
On 12/13/2012 4:42 PM, David Hubbard wrote: Hi all, was wondering if anyone has a handy tool, cat -v and pipe to something, perl class, etc. for outputting a queued message file to stdout but have the line breaks display rather than the control characters? It's difficult to troubleshoot where deferred messages from mailer-daemon originally came from when looking at the raw files because all the headers, postfix control info and message body are displayed together as two long lines. Thanks, David http://www.postfix.org/postcat.1.html -- Noel Jones
Re: Tool to read queued messages?
Am 13.12.2012 23:42, schrieb David Hubbard: Hi all, was wondering if anyone has a handy tool, cat -v and pipe to something, perl class, etc. for outputting a queued message file to stdout but have the line breaks display rather than the control characters? postcat signature.asc Description: OpenPGP digital signature
Re: Tool to read queued messages?
Le 2012-12-13 23:42, David Hubbard a écrit : Hi all, was wondering if anyone has a handy tool, cat -v and pipe to something, perl class, etc. for outputting a queued message file to stdout but have the line breaks display rather than the control characters? It's difficult to troubleshoot where deferred messages from mailer-daemon originally came from when looking at the raw files because all the headers, postfix control info and message body are displayed together as two long lines. Thanks, David pfqueue should help
RE: Tool to read queued messages?
Thanks everyone for the postcat tip; obviously I'm new to postfix. Finally had to get off qmail after years of resisting. -Original Message- From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] On Behalf Of David Hubbard Sent: Thursday, December 13, 2012 5:43 PM To: postfix-users@postfix.org Subject: Tool to read queued messages? Hi all, was wondering if anyone has a handy tool, cat -v and pipe to something, perl class, etc. for outputting a queued message file to stdout but have the line breaks display rather than the control characters? It's difficult to troubleshoot where deferred messages from mailer-daemon originally came from when looking at the raw files because all the headers, postfix control info and message body are displayed together as two long lines. Thanks, David
Re: How to change modified cf files to postconf commands
On 12/13/2012 05:47 PM, Noel Jones wrote: On 12/13/2012 4:17 PM, Robert Moskowitz wrote: In the totorial: http://www.campworld.net/thewiki/pmwiki.php/LinuxServersCentOS/Cent6VirtMailServer There are modified postfix .cf files. I don't want to just use a modified postfix file, I want to user postconf to do the modifications. And I am not experienced using things like diff to work out what changes were made from the base install files. Can anyone lend some expertise in identifying the mods so I can work this up as postconf commands? Why? If you're just going to paste in changes it doesn't matter too much if you paste in a pre-made .cf file or if you run a bunch of postconf commands. For the past 3 years I have been running with a setup based on: http://www.howtoforge.com/virtual-users-and-domains-with-postfix-courier-mysql-and-squirrelmail-fedora-14-x86_64 Here the postfix changes are done via postconf, so I CAN tell what changes are made and understand what is going on. Better to learn why each line is there, and why. And most important, if *you* need it. Kind of my point. What changes is the author of the tutorial really making so I can understand why. http://www.postfix.org/documentation.html http://www.postfix.org/STANDARD_CONFIGURATION_README.html http://www.postfix.org/VIRTUAL_README.html main.cf parameters and their defaults are documented here: http://www.postfix.org/postconf.5.html Generally, only parameters that differ from their default should be included in your main.cf. Again, what I want to get to. Understand what changes the author made to the defaults. Looks like I will first have to learn how to understand the output of diff.
Postfix used as End to End and relaying to external SMTP server based on FROM address (possible?)
Hi I have never used Postfix, i am a network specialist and understand the methods of SMTP (i deploy Exchange server regularly), I have a Zimbra ZCS v8 server (testing it), i understand it uses postfix, however its not in the default location (its loaded its own one in the zimbra folder). Whats the best software to GUI admin this (Postfix admin?) By default this will only receive and send mail end to end (i have not enabled any relay to another SMTP server inside Zimbra). What i need to do as set the MTA to look at the from address (when sending email from this MTA) then use a relay SMTP server based on the from address (sometimes with or without username / password). However all other addresses not listed needs to send end to end (from the MTA directly, not through a relay). I was going to try and use: relayhost = sender_dependent_relayhost_maps = relayhost file smtp_sasl_password_maps = password file relayhost_file m...@gmail.com [smtp.gmail.com] m...@aol.com [smtp.aol.com] m...@aol.com [smtp.aol.com] m...@domaina.com [smtp.domaina.com] password_file m...@gmail.com username:password m...@aol.com username:password m...@aol.com username:password My understanding is the password file can be specific about the user needing authentication as i will have more than one FROM in the same domain meaning different username and passwords for the same relay domain name (the above shows aol.com) domaina.com also doesnt need a username / password to relay mail (it uses the FROM address) However i need anything else that postfix is trying to send if its not listed in relayhost_file then it should attempt to send this directly (end to end) and not use any relay. Is this possible? I have access to main.cf, however its in a zimbra specific location so i assume they have hybrid most of the postfix system. Many Thanks Ashley -- View this message in context: http://postfix.1071664.n5.nabble.com/Postfix-used-as-End-to-End-and-relaying-to-external-SMTP-server-based-on-FROM-address-possible-tp53191.html Sent from the Postfix Users mailing list archive at Nabble.com.
Re: Tool to read queued messages?
On Thu, Dec 13, 2012 at 05:42:53PM -0500, David Hubbard wrote: Hi all, was wondering if anyone has a handy tool, cat -v and pipe to something, perl class, etc. for outputting a queued message file to stdout but have the line breaks display rather than the control characters? It's difficult to troubleshoot where deferred messages from mailer-daemon originally Bounces? Why are you sending bounces? This is usually a symptom of bigger problems. came from when looking at the raw files because all the headers, postfix control info and message body are displayed together as two long lines. In addition to postcat(1) as mentioned upthread, you can trace the queue ID in your logs. That will probably also reveal the reasons behind the bounces. -- http://rob0.nodns4.us/ -- system administration and consulting Offlist GMX mail is seen only if /dev/rob0 is in the Subject:
Directive mynetwork and mynetwork_style
i am confuse about the utilization of directives: mynetwork and mynetwork_style is mynetwork directive completely dependent on mynetwork_style. can i use only mynetwork for relaying messages or i always have to use mynetwork_style along with mynetwork to allow relaying to particular host or subnet. thanks in advance.
