Re: Newb question - simple script
Thanks for the reply. I'm aware it's not a good design, which is why I also asked for suggestions for better ways to accomplish my purpose :) I'm going to try the subethasmtp java smtp server. From: Victor Duchovni victor.ducho...@morganstanley.com To: postfix-users@postfix.org Sent: Mon, October 11, 2010 3:26:13 PM Subject: Re: Newb question - simple script On Mon, Oct 11, 2010 at 02:07:20PM -0700, jimmy zoto wrote: I'm trying to copy all incoming mail to a local FIFO file for special purpose processing by a Java program. I don't know the best way to do this. This sounds like a bad design. It is unlikely that your FIFO has any way to indicate success or failure. You probably can't indicate the end of the message to the FIFO listener. Your FIFO probably can't support parallel delivery. There are likely many more issues. Even if you solve your apparent problem, your real problem (bad design) will not be solved. -- Viktor.
search message body
Morning list. Apologies for the post. I have alot of queued mail and would like to know if it is possible to serach for a string in the body of mails which are queued? i.e, i would like to find the message-id's of all queued mail with "reply if we can work together" in the message body. Thanks once again. regards Tom
LDAP, groups and users without local accounts
Hi, perhaps you guys can help me. I'm integrating postfix into our ldap environment. We have groups (posixGroup) with memberUids in them (e.g. lenfers for me). Adding mail info to those groups works and all local users get resolved correctly. But sometimes there are users (e.g. externuser) that need to be in those groups (rights and mail related) but have only an external mail account. I cannot find a setup so that this is resolved accordingly, because postfix tries to deliver the mail to the memberUids (externuser instead of externu...@gmail.com). Relevant config part from my lookup config: | query_filter = ( (|(objectClass=gosaMailAccount)(objectClass=gosaMailAlias)) (|(mail=%s)(gosaMailAlternateAddress=%s))) | result_attribute = gosaMailForwardingAddress, uid, memberUid, aliasDestMail Postfix versions 2.7.0 and 2.5.1 TIA, Jakob
Re: Queue full of double-bounce
Wietse Venema skrev 2010-10-11 23:00: Patric Falinder: then you have found the timer bug that causes Postfix to deliver only one message probe per 300 seconds, and we can start looking for workarounds (such as changing the src/util/events.c module and replacing zero delay requests by 1 millisecond delay requests). Wietse [ Attachment, skipping... ] Cool, I will try that tomorrow when I get to work and feedback the results. I've been meaning to upgrade to Postfix 2.7 too so might as well do that when I'm at it. I should only compile this testprogram and not install it right? Don't replace the installed Postfix. The timer stuff works exactly the same way as your Postfix 2.5.5. I don't write each Postfix release from scratch. Wietse I have now tried that on the VMWare ESX server and I actually got normal completion after 100 iterations as a result, so I guess it doesn't have to do with the timer thing!? I also upgraded to Postfix 2.7, without VDA cause this time because this server wasn't meant to have that patch in the first place, and I've been watching the queue for a couple of minutes and the double-bounce messages seems to go away as they should. I'm gonna keep looking though, to see if it gets filled again but it Looks like the upgrade fixed it. I can report back at the end of the day to see if it's actually fixed. Thanks a lot Wietse for all your help! I'm really grateful. -Patric
hide (do not disclose) reject reason to client but log as usual
Hello, I would like to be able to configure smtpd so that a generic smtp session reject code to be given without explanation (ex. helo command rejected, user unknown, client host rbl, etc) while at the same time detail the reject reason in mail.log as usual. Is this possible? Thank you
Re: adding recipient
On 10/12/2010 1:12 AM, Tom Kinghorn wrote: Good morning List. I just wanted to know if it is possible to add a recipient to a message which is queued? I come from an exim background where we could do so using *exim -Ma*r /message-id/ *new-recipient-address*. Thanks in advance. Tom Postfix has no such mechanism.
Re: adding recipient
On 2010/10/12 01:05 PM, Noel Jones wrote: I come from an exim background where we could do so using *exim -Ma*r /message-id/ *new-recipient-address*. Thanks in advance. Tom Postfix has no such mechanism. Thanks for the response Noel. Regards Tom
best way to send raw email (files)?
I have a legacy application which produces emails as text files (email headers, body). I was wondering, what would be the best way to send mails delivered in such format? Some more background: - application is running on a Windows system, - it writes the files to the Samba share (same server where Postfix is running). I was thinking of the following approach: - check if the /samba/emails/somefile.eml is not opened already (if it is, the application still writes to it), - if it's not opened, do a: cat /samba/emails/somefile.eml | sendmail -t Is it a reasonable approach? I'm a bit worried it's not very scalable (i.e. list the directory, run lsof for each file, spawn cat and sendmail, and that in some kind of loop). Critique is welcome, especially if there are better ways to deal with raw email files. -- Tomasz Chmielewski http://wpkg.org
Re: LDAP, groups and users without local accounts
On Tue, Oct 12, 2010 at 10:05:10AM +0200, Jakob Lenfers wrote: perhaps you guys can help me. I'm integrating postfix into our ldap environment. We have groups (posixGroup) with memberUids in them (e.g. lenfers for me). Adding mail info to those groups works and all local users get resolved correctly. But sometimes there are users (e.g. externuser) that need to be in those groups (rights and mail related) but have only an external mail account. I cannot find a setup so that this is resolved accordingly, because postfix tries to deliver the mail to the memberUids (externuser instead of externu...@gmail.com). If your posixGroup objects have a multi-valued member attribute that is a sequence of strings representing login names, you must use /etc/aliases or .forward files to handle mail for any user accounts that require remote delivery. If the posixGroup lists a sequence of member DNs, you can express queries that directly fetch the primary mail address of the underlying user. I am guessing the memberDN scenario is not what you've got in your schema. -- Viktor.
Re: Queue full of double-bounce
Patric Falinder: as a result, so I guess it doesn't have to do with the timer thing!? No you cannot prove the absence of this bug. Perhaps it triggers when you run lots of instances of my test program in parallel. We have no idea of what all the other virtual machines are doing and we have no idea how VMware tools futzes with the guest system clock. I also upgraded to Postfix 2.7, without VDA cause this time because this server wasn't meant to have that patch in the first place, and I've been watching the queue for a couple of minutes and the double-bounce messages seems to go away as they should. I'm gonna keep looking though, to see if it gets filled again but it Looks like the upgrade fixed it. I can report back at the end of the day to see if it's actually fixed. As I wrote before there are no changes in this part of Postfix since version 2.4. I expect that lost timer bugs will come back again and again. This weekend someone else reported a lost timer interrupt problem in FreeBSD on ESX that caused idle Postfix daemons to hang instead of exiting after $max_idle seconds. Wietse
Re: search message body
On Tue, Oct 12, 2010 at 09:47:44AM +0200, Tom Kinghorn wrote: Morning list. Apologies for the post. I have alot of queued mail and would like to know if it is possible to serach for a string in the body of mails which are queued? i.e, i would like to find the message-id's of all queued mail with reply if we can work together If the message content is not base64 encoded, and this string is not split across multiple message body lines, a simple egrep -l should work. Otherwise, you need to search for either the head or tail of this string, (at least half is likely to be on a whole line). To find it in base64 encoded text, and assuming you have the text case (uppper/lower) exactly right: $ echo reply if we can work together | openssl base64 cmVwbHkgaWYgd2UgY2FuIHdvcmsgdG9nZXRoZXIK $ echo reply if we can work together | openssl base64 IHJlcGx5IGlmIHdlIGNhbiB3b3JrIHRvZ2V0aGVyCg== $ echo reply if we can work together | openssl base64 ICByZXBseSBpZiB3ZSBjYW4gd29yayB0b2dldGhlcgo= then search for any of: cmVwbHkgaWYgd2UgY2 FuIHdvcmsgdG9nZXRo cGx5IGlmIHdlIGNhbi B3b3JrIHRvZ2V0aGVy ZXBseSBpZiB3ZSBjYW 4gd29yayB0b2dldGhl via # egrep -l 'cmVwbHkgaWYgd2UgY2|FuIHdvcmsgdG9nZXRo|cGx5IGlmIHdlIGNhbi|B3b3JrIHRvZ2V0aGVy|ZXBseSBpZiB3ZSBjYW|4gd29yayB0b2dldGhl' queue-files There may be some false positives and false negatives. More reliable results require a full MIME parser, HTML decoder, ... -- Viktor.
Re: best way to send raw email (files)?
Tomasz Chmielewski: cat /samba/emails/somefile.eml | sendmail -t sendmail -t filename assuming that the file does not contain garbage such as Control-Z at the end of the file. Only slightly faster would be to use one of the mini-sendmail programs that read a message on standard input and submit via SMTP. How do you know when the input file is complete? You should not start submission of a file that is still being written to. Wietse
Re: Queue full of double-bounce
Wietse Venema: Patric Falinder: as a result, so I guess it doesn't have to do with the timer thing!? No you cannot prove the absence of this bug. Perhaps it triggers Forget it, according to your other message you are sending mail with Postfix into an MTA that rejects your address probes. Wietse
Re: adding recipient
Tom Kinghorn: I just wanted to know if it is possible to add a recipient to a message which is queued?br By design you cannot add a record when a file is already committed to the queue. The reason for this is that there is no way to undo the change in case of failure (disk full or whatever), so you would end up with a corrupted queue file. Wietse
Re: best way to send raw email (files)?
On 12.10.2010 16:40, Wietse Venema wrote: Tomasz Chmielewski: cat /samba/emails/somefile.eml | sendmail -t sendmail -t filename Thanks for the tip. assuming that the file does not contain garbage such as Control-Z at the end of the file. Only slightly faster would be to use one of the mini-sendmail programs that read a message on standard input and submit via SMTP. How do you know when the input file is complete? You should not start submission of a file that is still being written to. I wanted to check with lsof if it's still opened or not. Another option would be to only look at files which were last modified i.e. a minute/two ago, or older than that. An better way would be to make the client produce a file like somefile.eml.tmp, and when it's fully written, do a mv/rename, which should be atomic - but I'm not sure how the other side is flexible. -- Tomasz Chmielewski http://wpkg.org
exclude sender from aliases
Hello to the community! :) Sorry for bothering the list initially with a technical question. I have setup a mail forwarder, that is getting the aliases (mailing lists) from a MySQL database. How can I avoid, that the sender receives its own mail when he is on the mailing list? I thought about a sender address-variable that i could use in the MySQL query or a configuration variable like allow_recipient_is_sender = off. Neither this nor other solutions I found in the docs or the rest of the www. I'd be really happy if someone could help. Regards! lp smime.p7s Description: S/MIME Cryptographic Signature
Re: Block all but a few from sending mail offsite
Hello, master.cf: smtp inet n - n - - smtpd pickupfifo n - n 1 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 postconf -n: alias_database = hash:/etc/postfix/aliases alias_maps = hash:/etc/postfix/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix html_directory = /usr/share/doc/postfix-2.7.1-documentation/html inet_interfaces = all mail_owner = postfix mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man maximal_backoff_time = 1 minimal_backoff_time = 1 mydomain = XXX.com myhostname = hq-relaytest-01 mynetworks = 127.0.0.0/8 newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix queue_run_delay = 1 readme_directory = /usr/share/doc/postfix-2.7.1-documentation/readme relay_domains = XXX.com sample_directory = /etc/postfix setgid_group = postdrop smtpd_client_connection_count_limit = 100 smtpd_recipient_restrictions = check_recipient_access hash:/etc/postfix/throttle, check_relay_domains unknown_local_recipient_reject_code = 550 I should explain what the throttle file in the smtpd_recipient_restrictions above is. We are attempting to have this server act as a relay. We want all mail from certain domains to go directly to the hold queue so that we can use a separate program to un-hold mails at a specific rate. Contents of the throttle file: XXX.com HOLD As per http://www.postfix.org/RESTRICTION_CLASS_README.html#external, I modified the smtpd_recipient_restrictions to the following: smtpd_recipient_restrictions = check_recipient_access hash:/etc/postfix/throttle, check_sender_access hash:/etc/postfix/restricted_senders, check_relay_domains and added: smtpd_restriction_classes = local_only local_only = check_recipient_access hash:/etc/postfix/local_domains, reject This worked as expected and blocked certain senders from sending mail outside the local domains. Now I am trying to convert this to block everyone except for certain senders to send mail outside the local domains. I have tried modifying restricted_senders to be: b...@xxx.comHOLD @ REJECT I was expecting this: - b...@xxx.com can send to both to outside and inside domains (put in the hold queue). - If anyone else sends to an inside domain, the mail is put in the hold queue (because of the throttle file, and my separate program will send this). - If anyone else sends to an outside domain, the mail is rejected (because of the restricted_senders file above). Am I completely going about this the wrong way? Should I not be thinking of smtpd_recipient_restrictions the way I think of firewall rules? I am looking for some pointers on how to properly do this. Thank you. --- On Mon, 10/11/10, Sahil Tandon sa...@freebsd.org wrote: From: Sahil Tandon sa...@freebsd.org Subject: Re: Block all but a few from sending mail offsite To: postfix-users@postfix.org Date: Monday, October 11, 2010, 5:00 PM On Mon, 2010-10-11 at 16:45:13 -0700, John Swift wrote: For my Postfix web server, I was able to get the example working that was at the bottom of the web page here: http://www.postfix.org/RESTRICTION_CLASS_README.html#external. In that section of the web page, it says It is left as an exercise for the reader to change this into a scheme where only some users have permission to send mail to off-site destinations, and where most users are restricted. I've tried many many different things but have been unable to change
Re: Newb question - simple script
On 10/11/2010 11:07 PM, jimmy zoto wrote: I'm trying to copy all incoming mail to a local FIFO file for special purpose processing by a Java program. I don't know the best way to do this. FIFO certainly isn't it. If you must go this route, use a pipe(8) transport fed by always_bcc so you can at least return the basic OK/REJECT status codes with your script. But as both Victor and Wietse already suggested, SMTP has the full spectrum of status codes available. I can execute this successfully on the command line, but I haven't been able to run it successfully from Postfix. It doesn't matter whether the destination file is a normal file or a FIFO. Nothing shows up in the logs. I have no indication the script is running. I copied the script into the queue_directory and have it entered in master.cf http://master.cf as : pipefilter unix - n n - 1 pipe flags=Rq user=filteruser argv=pipefilter -vvv -- How is that a FIFO ? pipe(8) allows you to keep the session open until it returns, it's certainly not one-way (the exit status is returned to postfix). -- J.
Re: adding recipient
On 10/12/2010 08:12 AM, Tom Kinghorn wrote: Good morning List. I just wanted to know if it is possible to add a recipient to a message which is queued? What could possibly be the reason for this ? You forgot to list a recipient ? so re-send the message. There are ways to re-direct and re-inject queued mail, of course - but altering the queued message is not a normal reason to do so. -- J.
Re: exclude sender from aliases
On 10/12/2010 05:46 PM, Lukas Pirl wrote: Hello! hmmm, sad story ;) If you need this functionality, you can install a mailing list manager. They do take the sender into account. -- J.
Re: reverse the polarity of the neutron flow
On 10/12/2010 09:42 PM, The Doctor wrote: Doctor Who saying in the 1970s. What do I need to reverse. Tried another MTA and got reports that people were not getting e-mail. All right switch back. Forgot that the 'sendmail' was not the correct one. No problem, just use the postfix sendmail. Hmm!! No mail is getting delievered. What did I forget? In my opinion ? A brain. -- J.
Re: hide (do not disclose) reject reason to client but log as usual
Le 12/10/2010 12:09, Costin Gusa a écrit : Hello, I would like to be able to configure smtpd so that a generic smtp session reject code to be given without explanation (ex. helo command rejected, user unknown, client host rbl, etc) while at the same time detail the reject reason in mail.log as usual. Is this possible? Thank you sure: REJECT we reject you (#code) where only you know what #code means. but this is a really bad idea. when I get rejected without a reason I can work on, I simply blocklist the other side. remember: this story is about reputation. if you think you can solve your spam problem using your own measures, don't forget that we too have a problem with spam. and if you take a measure that might work for you but causes problems for us, then we'll consider that you're part of the problem.
Re: Block all but a few from sending mail offsite
Le 12/10/2010 01:45, John Swift a écrit : Hello, For my Postfix web server, I was able to get the example working that was at the bottom of the web page here: http://www.postfix.org/RESTRICTION_CLASS_README.html#external. In that section of the web page, it says It is left as an exercise for the reader to change this into a scheme where only some users have permission to send mail to off-site destinations, and where most users are restricted. I've tried many many different things but have been unable to change the scheme where some users have permission to send mail offsite and most users are restricted. Can I get a little help with this? I'm guessing this is a small config change that I'm completely missing. can you explain your need clearly? with the following: smtpd_sender_restrictions = check_sender_access hash:/etc/postfix/access_sender == access_sender j...@exampleOK j...@example.comOK example.comreject_unauth_destination .example.comreject_unauth_destination joe and jim can send offsite, while other *example.com can only send to managed domains (mydestination, relay domains, virtual mailbox domains, virtual alias domains).
Re: reverse the polarity of the neutron flow
On 10/12/2010 12:42 PM, The Doctor wrote: Doctor Who saying in the 1970s. What do I need to reverse. Tried another MTA and got reports that people were not getting e-mail. All right switch back. Forgot that the 'sendmail' was not the correct one. No problem, just use the postfix sendmail. Hmm!! No mail is getting delievered. What did I forget? Gosh, it could be just about anything. How about some log entries, and postconf output, per the troubleshooting guidelines? Joe
Re: Messages w/ No Subject
Le 12/10/2010 01:41, Carlos Mennens a écrit : I was wondering how mail administrators using Postfix handle messages w/o any subject material? I don't know if this is an RFC guideline that requires email to have a subject but I find it extremely annoying when email doesn't have a subject. I don't know if that's just personal preference or if it's an actual guideline for mail to have 'subject' data. Do you guys reject mail if no 'subject' is present in the message? No. If you mean an empty subject header, then there is no reason to reject it. an empty subject happens enough. if you mean mail without a subject header, then you can reject it, but that almost never happens.
Re: best way to send raw email (files)?
On Tue, Oct 12, 2010 at 04:49:39PM +0200, Tomasz Chmielewski wrote: How do you know when the input file is complete? You should not start submission of a file that is still being written to. I wanted to check with lsof if it's still opened or not. lsof does not know about other NFS clients. The NFS-safe way of creating mail messages is the maildir delivery protocol, which the client system must follow to ensure robust en-queueing of mail. -- Viktor.
Re: reverse the polarity of the neutron flow
On Tue, Oct 12, 2010 at 01:42:25PM -0600, The Doctor wrote: What did I forget? * rm -rf / (Read mail, really fast) * A name * http://www.postfix.org/DEBUG_README.html#mail Bastian -- We fight only when there is no other choice. We prefer the ways of peaceful contact. -- Kirk, Spectre of the Gun, stardate 4385.3
Re: hide (do not disclose) reject reason to client but log as usual
On Wed, Oct 13, 2010 at 00:04, mouss mo...@ml.netoyen.net wrote: Le 12/10/2010 12:09, Costin Gusa a écrit : Hello, I would like to be able to configure smtpd so that a generic smtp session reject code to be given without explanation (ex. helo command rejected, user unknown, client host rbl, etc) while at the same time detail the reject reason in mail.log as usual. Is this possible? Thank you sure: REJECT we reject you (#code) I'm sure there's some detail in the documentation which tells me where exactly do you put that in order to act as a generic reject message, but being unable to find it is the reason I mailed you. My postconf -n looks like this: http://paste.lug.ro/126607 but don't think this is relevant to the answer. `postconf -d|grep reject' options gives me the posibility to change the reject code (which I don't intend). I just want to modify the text, for example: I don't want the text helo command rejected to be prepended to my custom REJECT internal code 123 in a *_helo_restrictions check. if not generic, then at least I'd like to be able to overwrite the reject text for each reject reason, preferably without recompiling from source. where only you know what #code means. rfc821 gives also explanations for second-digit of the reject codes so you don't need the text: The second digit encodes responses in specific categories: x0z Syntax -- These replies refer to syntax errors, syntactically correct commands that don't fit any functional category, and unimplemented or superfluous commands. x1z Information -- These are replies to requests for information, such as status or help. x2z Connections -- These are replies referring to the transmission channel. x3z Unspecified as yet. x4z Unspecified as yet. x5z Mail system -- These replies indicate the status of the receiver mail system vis-a-vis the requested transfer or other mail system action. [...] Each reply text is recommended rather than mandatory, and may even change according to the command with which it is associated. Note the wording in the last phrase, *recommended rather than mandatory*, which means I am complying with rfc821. but this is a really bad idea. when I get rejected without a reason I can work on, I simply blocklist the other side. remember: this story is about good, an eye for an eye, brilliant! so then you're not delivering to m$ sexchange at all, for example? reputation. if you think you can solve your spam problem using your own measures, don't forget that we too have a problem with spam. and if you take a measure that might work for you but causes problems for us, then we'll consider that you're part of the problem. please define causes problems for us and detail a little more. I rarely get complains from users about receiving DSN's with generic reject text and most of the time is because they don't know how to read DSN very well rather than complaining.
Re: hide (do not disclose) reject reason to client but log as usual
see, mouss, that's the reason in my systems this email would have never got a chance for 220 OK, even without any external spam filter in place. On Tue, Oct 12, 2010 at 22:42, The Doctor doc...@doctor.nl2k.ab.ca wrote: Doctor Who saying in the 1970s. What do I need to reverse. Tried another MTA and got reports that people were not getting e-mail. All right switch back. Forgot that the 'sendmail' was not the correct one. No problem, just use the postfix sendmail. Hmm!! No mail is getting delievered. What did I forget? -- Member - Liberal International This is doc...@nl2k.ab.ca Ici doc...@nl2k.ab.ca God, Queen and country! Never Satan President Republic! Beware AntiChrist rising! http://twitter.com/rootnl2k http://www.facebook.com/dyadallee Are you a real human: http://www.cuttingedge.org/news/n1334.cfm ...because of the following header: Received: from localhost (localhost.nl2k.ab.ca [127.0.0.1]) by doctor.nl2k.ab.ca (Postfix) with ESMTP id 2030912CFC90 for postfix-users@postfix.org; Tue, 12 Oct 2010 15:01:47 -0600 (MDT)
Re: reverse the polarity of the neutron flow
Hi! People, I just don't get it, what is the point of comments such as: What did I forget? In my opinion ? A brain. and What did I forget? * rm -rf / (Read mail, really fast) * A name * http://www.postfix.org/DEBUG_README.html#mail Jeroen and Bastian, I think that was too rude, even if the way of asking a question is not correct, we are here to help. At least Bastian gave one URL that he can read (after giving one of many ways of rendering your *NIX system useless), but, come on! don't make fun of the people that still lacks knowledge, we all had to learn at some point. Sincerely, Ildefonso Camargo
Re: hide (do not disclose) reject reason to client but log as usual
On 10/12/2010 5:33 PM, Costin Gusa wrote: On Wed, Oct 13, 2010 at 00:04, moussmo...@ml.netoyen.net wrote: Le 12/10/2010 12:09, Costin Gusa a écrit : Hello, I would like to be able to configure smtpd so that a generic smtp session reject code to be given without explanation (ex. helo command rejected, user unknown, client host rbl, etc) while at the same time detail the reject reason in mail.log as usual. Is this possible? Thank you sure: REJECT we reject you (#code) I'm sure there's some detail in the documentation which tells me where exactly do you put that in order to act as a generic reject message, but being unable to find it is the reason I mailed you. The built-in postfix restrictions (reject_...) have built-in responses. You can't adjust them without patching the code. Access maps (check_..._access restrictions) can specify custom reject messages by including the custom text in the map. man 5 access RBL responses can be customized with default_rbl_reply and rbl_reply_maps. A policy service or a milter can reject mail using their own message. See postfix docs for more about these features. -- Noel Jones
Re: hide (do not disclose) reject reason to client but log as usual
Costin Gusa: for example: I don't want the text helo command rejected to be prepended to my custom REJECT internal code 123 Postfix will reveal both the name and the value of the element (client, helo, sender, recipient) that triggers a reject, because down over here in the real world, Postfix rules will occasionally reject legitimate mail. I doubt that it is worthwhile to complicate Postfix source code with the output equivalent of the smtpd_command_filter feature, but you are welcome to give it a stab. Wietse
