sent mail to the mail list which contains myself
Hi there, When I send mails to the mail list that contains myself, I will received the mail. Is there any way to discard there mails sent back to the original sender in the mail list? Thanks, Bu Xiaobing
Re: sent mail to the mail list which contains myself
On Tue, 28 May 2013 16:04:09 +0800 Bu Xiaobing wrote: > When I send mails to the mail list that contains myself, I will > received the mail. > > Is there any way to discard there mails sent back to the original > sender in the mail list? > This not related to postfix. But if you're using Mailman to manage mail list, there are option to change this behavior.. look at "Receive your own posts to the list?" and set it to "No".
Re: Huge mail queue
On Tue, May 28, 2013 at 02:30:29PM +0800, Ramesh wrote: > Our mail server configured Postfix version 2.4.5 with mailmarshal 2.4.5 is very old. Is the rest of the system this old? Have you kept up with all your OS distributor's security updates? Likewise, have you kept up-to-date on any software you might have installed outside the OS's packaging system? > as content filter, recently mail server not responding because of > huge mail queue, content filter cpu usage is 100%, my investigation > found more than 18k mails are in que, sender email address is > m...@zbavitu.net > > I have manually deleted mails in content filter queue and deferred > mails in mail server, now mail server functioning normally. Did you save a spample (sample of the spams)? > I wanted to investigate weather our mail server compromised or > content filter (windows machine) infected. Generally I would not suspect Postfix of compromise, but there are numerous attack vectors which are being probed every day on every Internet-connected machine. Does the Postfix machine also run a web server? A name server? An [in]secure shell server? There have been numerous known exploits of those services over the years since Postfix 2.4.5 (2007-07-31, nearly six years ago.) > Please suggest methods to investigate so that will take precautions > in future the same will not repeat. Specific suggestions would depend on knowing what happened. You would need to share logs which show the *origin* of at least one of the spams. An exploit on the Postfix machine itself would show logs from "postfix/pickup" from the compromised account. Of course, privilege escalation is a possibility as well, and you must rule that out. If you do not, logs (and everything!) are of dubious value. Given the age of the Postfix, and the fact that 2.4.5 itself was 11 patchlevels behind the final update of Postfix 2.4 in 2011, I think the best advice is to reinstall a recent release of your OS of choice. > I would like to know how to load balancing mail server, due to > above issue mail server was down for 24 hours, we have secondary mx > which queues mails when primary mx is down, Is there any method > where users can send or receive mails from secondary mx when > primary is down. That is not trivial, and is a matter outside the purview of Postfix. What you'd need is load balancing on your mail store, not your MTA. When Postfix delivers a message, it is done with it. Postfix offers the administrator the postsuper(1) and postcat(1) tools for dealing with the queue and viewing queued mail, but these tools are not suitable for end users (and I would absolutely not recommend trying to work around that with a web frontend!) Generally the best answer for people asking this is to improve the security and reliability of the primary MX host, and do away with your secondary MX spam magnet. -- http://rob0.nodns4.us/ -- system administration and consulting Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
Re: sent mail to the mail list which contains myself
On Tue, May 28, 2013 at 04:04:09PM +0800, Bu Xiaobing wrote: > When I send mails to the mail list that contains myself, I will > received the mail. > > Is there any way to discard there mails sent back to the original > sender in the mail list? If you mean THIS mailing list, no, it does not offer that feature. You'll have to find a way in your MDA or your MUA. -- http://rob0.nodns4.us/ -- system administration and consulting Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
Re: Problem sending emails to virtual users
On 5/27/2013 9:27 PM, SONNY LASKAR wrote: > > *My problem is with sending emails to virtual users. It always says > "unknown user".* > Please assist > Welcome to postfix. For assistance please see: http://www.postfix.org/DEBUG_README.html#mail When posting to this list, use plain text only, no html. Do not top-post.
Virtual User Aliases
Hi A few days ago there was an issue with one of our mail servers - and I had to disable perl related filters (dkim and amavisd). And since then it's not processing virtual_user_aliases. in postconf -n postconf -n | grep virtual_user_aliases virtual_alias_maps = hash:/etc/postfix/virtual_user_aliases, proxy:mysql:/etc/postfix/Mail-Alias.cf And if I use postalias, I get the correct result: postalias -q p...@example.co.uk /etc/postfix/virtual_user_aliases p...@example.com but in the logs: May 27 23:30:15 mail postfix/smtpd[16493]: Anonymous TLS connection established from c62.cesmail.net[216.154.195.54]: TLSv1 with cipher RC4-SHA (128/128 bits) May 27 23:30:16 mail policyd-spf[16496]: None; identity=helo; client-ip=216.154.195.54; helo=c62.cesmail.net; envelope-from=si...@example.net; receiver=p...@example.co.uk May 27 23:30:16 mail policyd-spf[16496]: Pass; identity=mailfrom; client-ip=216.154.195.54; helo=c62.cesmail.net; envelope-from=si...@example.net; receiver=p...@example.co .uk May 27 23:30:16 mail postfix-policyd: rcpt=764, greylist=update, host=216.154.195.54 (c62.cesmail.net), from=si...@example.net, to=p...@example.co.uk, size=717 May 27 23:30:16 mail postfix-policyd: rcpt=764, throttle=update(a), host=216.154.195.54, from=si...@example.net, to=p...@example.co.uk, size=717/1024, quota=1432/25000 , count=2/512(3), rcpt=2/3600(3), threshold=0%|0%|0% May 27 23:30:16 mail postfix-policyd: rcpt=764, throttle_rcpt=update(a), host=216.154.195.54, from=si...@example.net, to=p...@example.co.uk, count=2/128(1293), threshold=0 % May 27 23:30:16 mail postfix/smtpd[16493]: 57FF6C8C033: client=c62.cesmail.net[216.154.195.54] May 27 23:30:17 mail postfix/cleanup[16712]: 57FF6C8C033: message-id=<20130528013014.tc0sl3txwo4gwc88-ylqv...@webmail.cesmail.net> May 27 23:30:17 mail postfix/qmgr[16323]: 57FF6C8C033: from=, size=1209, nrcpt=1 (queue active) May 27 23:30:17 mail dovecot: deliver(p...@example.co.uk): msgid=<20130528013014.tc0sl3txwo4gwc88-ylqv...@webmail.cesmail.net>: si...@example.net: saved mail to INBOX May 27 23:30:17 mail postfix/pipe[16721]: 57FF6C8C033: to=, relay=dovecot, delay=2, delays=2/0/0/0.05, dsn=2.0.0, status=sent (delivered via dovecot se rvice) May 27 23:30:17 mail postfix/qmgr[16323]: 57FF6C8C033: removed normally that delivered line would mention p...@example.com and that's where Dovecot would deliver it. How can I diagnose this? Thanks. Simon
Re: Virtual User Aliases
On Tue, May 28, 2013 at 05:33:46PM +0200, Simon B wrote: > Hi > > A few days ago there was an issue with one of our mail servers - and I > had to disable perl related filters (dkim and amavisd). And since > then it's not processing virtual_user_aliases. http://www.postfix.org/postconf.5.html#receive_override_options -- Viktor.
Re: Virtual User Aliases
Simon B skrev den 2013-05-28 17:33: May 27 23:30:17 mail postfix/pipe[16721]: 57FF6C8C033: to=, relay=dovecot, delay=2, delays=2/0/0/0.05, dsn=2.0.0, status=sent (delivered via dovecot se rvice) normally that delivered line would mention p...@example.com and that's where Dovecot would deliver it. and i see dovecot delivered it, if you have 2 mailboxes, and only wnat one, check postfix virtual_alias maps -- senders that put my email into body content will deliver it to my own trashcan, so if you like to get reply, dont do it
Relay attempts from bot filling mail queue and getting my server blacklisted: how's it happening?
Hello, I am experiencing something very similar to, or exactly the same as, what is described at http://www.tolaris.com/2009/07/15/stopping-spam-botnets-with-fail2ban/ . Basically, someone/something has been attempting to relay mail through my server (at least I believe that to be what's happening). I'm confused because this server should *not* be configured as an open relay, yet it seems that Postfix attempts to deliver this outgoing mail to its final destination (thousands of @hotmail.com users, in this case). At a minimum, Postfix is connecting to the recipient's mail server to the end result that both Hotmail and Yahoo have black-listed my server because of these messages. I had over 106,000 deferred messages in my Postfix queue this morning. It seems that some of these messages are rejected with "Relay access denied" (correctly so): postfix/smtpd[27811]: NOQUEUE: reject: RCPT from unknown[189.84.21.206]: 554 5.7.1 : Relay access denied; from= to=< (where example.com is a *Web* domain on my server, but there is no email service configured for it, and the local part, "gpusv", is invalid/fake/random). It bears mention that the sender local part and domain change periodically, but all of the domains are legitimate and have DNS records that point to this server (some Web, some email, etc.). Yet, at the same time, I see log entries that make it seem as though this bot is actually able to push-through outgoing mail (I apologize for the wrapping; see link at end of message for better formatting): May 28 06:30:01 example2 amavis[21173]: (21173-12-9) ESMTP::10024 /var/lib/amavis/tmp/amavis-20130528T062825-21173: -> , SIZE=1348 Received: from example2.com ([127.0.0.1]) by localhost (example2.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP; Tue, 28 May 2013 06:30:01 -0700 (PDT) May 28 06:30:01 example2 amavis[21173]: (21173-12-9) Checking: AodNAbQyfJVE [189.84.21.206] -> , May 28 06:30:01 example2 amavis[21173]: (21173-12-9) Open relay? Nonlocal recips but not originating: filipe-s-carva...@hotmail.com, linoguz...@hotmail.com May 28 06:30:01 example2 amavis[21173]: (21173-12-9) cached bb4750473febfc3a2c5e49a67135b953 from (0,1) May 28 06:30:01 example2 amavis[21173]: (21173-12-9) p001 1 Content-Type: text/plain, size: 912 B, name: May 28 06:30:01 example2 postfix/smtpd[12536]: A163122A43E6: client=localhost.localdomain[127.0.0.1] May 28 06:30:01 example2 postfix/cleanup[21166]: A163122A43E6: message-id=<20130528133001.a163122a4...@example2.com> May 28 06:30:01 example2 postfix/qmgr[32248]: A163122A43E6: from=, size=1741, nrcpt=2 (queue active) May 28 06:30:01 example2 amavis[21173]: (21173-12-9) FWD via SMTP: -> ,, 250 2.0.0 Ok, id=21173-12-9, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as A163122A43E6 May 28 06:30:01 example2 amavis[21173]: (21173-12-9) Passed CLEAN, [189.84.21.206] [189.84.21.206] -> ,, mail_id: AodNAbQyfJVE, Hits: 21.996, size: 1348, queued_as: A163122A43E6, 124 ms May 28 06:30:01 example2 postfix/smtp[21338]: 84D7022A43E9: to=, relay=127.0.0.1[127.0.0.1]:10024, conn_use=9, delay=9.7, delays=1.9/7.7/0/0.13, dsn=2.0.0, status=sent (250 2.0.0 Ok, id=21173-12-9, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as A163122A43E6) May 28 06:30:01 example2 postfix/smtp[21338]: 84D7022A43E9: to=, relay=127.0.0.1[127.0.0.1]:10024, conn_use=9, delay=9.7, delays=1.9/7.7/0/0.13, dsn=2.0.0, status=sent (250 2.0.0 Ok, id=21173-12-9, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as A163122A43E6) May 28 06:30:01 example2 postfix/qmgr[32248]: 84D7022A43E9: removed May 28 06:30:01 example2 postfix/error[21283]: A163122A43E6: to=, relay=none, delay=0.04, delays=0.03/0.01/0/0, dsn=4.4.2, status=deferred (delivery temporarily suspended: lost connection with mx3.hotmail.com[65.54.188.94] while sending RCPT TO) May 28 06:30:01 example2 amavis[21173]: (21173-12-9) TIMING [total 130 ms] - lookup_sql: 4 (3%)3, lookup_sql: 3 (2%)5, SMTP pre-DATA-flush: 1 (1%)6, SMTP DATA: 32 (25%)30, check_init: 1 (1%)31, digest_hdr: 1 (1%)32, digest_body_dkim: 1 (0%)33, gen_mail_id: 1 (1%)34, mime_decode: 11 (8%)42, get-file-type1: 20 (15%)57, parts_decode: 0 (0%)57, check_header: 2 (1%)59, spam-wb-list: 3 (3%)61, update_cache: 1 (1%)62, decide_mail_destiny: 2 (1%)63, fwd-connect: 4 (3%)66, fwd-mail-pip: 14 (10%)77, fwd-rcpt-pip: 1 (1%)78, fwd-data-chkpnt: 3 (3%)80, write-header: 1 (1%)81, fwd-data-contents: 0 (0%)81, fwd-end-chkpnt: 10 (7%)89, prepare-dsn: 1 (1%)89, main_log_entry: 9 (7%)97, update_snmp: 2 (2%)99, SMTP pre-response: 0 (0%)99, SMTP response: 1 (0%)99, unlink-1-files: 0 (0%)99, rundown: 1 (1%)100 Has anyone seen this before? Is this a misconfiguration on my part? Or has one of my user's accounts been compromised? Log excerpts and relevant configuration details can be found in my post here: http://www.howtoforge.com/forums/showpost.php?p=297832&postcount=5 I really appreciate any help. Thank you!
Re: Relay attempts from bot filling mail queue and getting my server blacklisted: how's it happening?
Ben Johnson: > Hello, > > I am experiencing something very similar to, or exactly the same as, > what is described at > http://www.tolaris.com/2009/07/15/stopping-spam-botnets-with-fail2ban/ . You need to show Postfix logs of the unwanted mail as it arrives **from the internet**, not as it comes out of the Amavis filter. Also, you need to follow instructions as per the mailing list welcome message. Do not post "revelant fragments" of main.cf. TO REPORT A PROBLEM see http://www.postfix.org/DEBUG_README.html#mail TO (UN)SUBSCRIBE see http://www.postfix.org/lists.html Thank you for using Postfix.
Re: How can I restrict some specific users from sending email to external domains?
On Mon, 27 May 2013 23:27:40 +0200 Patrick Ben Koetter wrote > * Benny Pedersen : > > Bogdan Enache skrev den 2013-05-27 21:38: > > > > >How should I define the restrictions so other users will not be > > >affected by this restriction, and where should I put them in the > > >config? > > You need to catch the sender address and route it into a dedicated filter > ruleset. Here's how you do it: > > The check_sender_access restriction below triggers the lookup to catch the > sender: > > smtpd_recipient_restrictions = > ... > check_sender_access hash:/etc/postfix/internal_senders > permit_mynetworks > reject_unauth_destination > ... > > In the map you list the senders that should be re-routed to the dedicated > filter ruleset: > > # /etc/postfix/internal_senders > restric...@example.com internal_only > > The rule above says to route restric...@example.com to a ruleset called > "internal_only". You need to define it, before you can add rules to it: > > smtpd_restriction_classes = > internal_only > > Now you can create the restriction class "internal_only" and add rules. They > are executed top to bottom - first match wins: > > internal_only = > check_recipient_access hash:/etc/postfix/internal_domains > reject > > In the map /etc/postfix/internal_domains you list all recipient domains the > sender should be permitted to send to. When you say "OK" you tell Postfix to > permit the senders request (send a message): > > # /etc/postfix/internal_domains > example.com OK > example.org OK > > If the recipient domain is not in /etc/postfix/internal_domains Postfix will > look for the next rule. In "internal_only" I wrote "reject". This is a static > action, which always is true if Postfix tests it. It gives you what you want. > Either the recipient domain is on /etc/postfix/internal_domains or the > request action (send a message) will be rejected. > > > this is solved with postfwd, but its possible to learn more with > > postfix :) > > Less tools rulez. ;) > > p@rick > This is an interesting issue. Would it be possible to implement the setting in conjuction with a REDIRECT action? In a way that would be transparent for the user: if the message is directed to a local domain -> OK, if it isn't then -> REDIRECT Chris
Re: Virtual User Aliases
On 28 May 2013 18:03, Viktor Dukhovni wrote: > On Tue, May 28, 2013 at 05:33:46PM +0200, Simon B wrote: >> Hi >> >> A few days ago there was an issue with one of our mail servers - and I >> had to disable perl related filters (dkim and amavisd). And since >> then it's not processing virtual_user_aliases. > > http://www.postfix.org/postconf.5.html#receive_override_options Good hint Victor. The only place this is set is in master.cf under the submission port (and these emails are not coming in on that port). It's also in the (now disabled) dkim port, but that's about it. Is there something I'm missing? :) Simon
Re: Relay attempts from bot filling mail queue and getting my server blacklisted: how's it happening?
Wietse Venema: > Ben Johnson: > > Hello, > > > > I am experiencing something very similar to, or exactly the same as, > > what is described at > > http://www.tolaris.com/2009/07/15/stopping-spam-botnets-with-fail2ban/ . I strongly suggest that you swap the order of the following two rules in main.cf: check_recipient_access mysql:/etc/postfix/mysql-virtual_recipient.cf, reject_unauth_destination, This should be: reject_unauth_destination, check_recipient_access mysql:/etc/postfix/mysql-virtual_recipient.cf, Many open relay problems are caused by having an access table before reject_unauth_destination. Wietse > You need to show Postfix logs of the unwanted mail as it arrives > **from the internet**, not as it comes out of the Amavis filter. > > Also, you need to follow instructions as per the mailing list > welcome message. Do not post "revelant fragments" of main.cf. > > TO REPORT A PROBLEM see http://www.postfix.org/DEBUG_README.html#mail > > TO (UN)SUBSCRIBE see http://www.postfix.org/lists.html > > Thank you for using Postfix. >
Re: How can I restrict some specific users from sending email to external domains?
On Tue, May 28, 2013 at 07:09:43PM +0200, Chris wrote: > > The check_sender_access restriction below triggers the lookup to catch the > > sender: > > > > smtpd_recipient_restrictions = > > ... > > check_sender_access hash:/etc/postfix/internal_senders > > permit_mynetworks > > reject_unauth_destination > > ... Sender checks before "reject_unauth_destination" in recipient restrictions are risky. Too easy to become an open relay. Better to use sender restrictions. smtpd_sender_restrictions = permit_auth_destination, check_sender_access hash:/etc/postfix/internal_senders The internal_senders will be listed with a "REJECT" action. Another variant is a white-list: smtpd_sender_restrictions = check_sender_access hash:/etc/postfix/external_senders, reject_unauth_destination Here you list senders allowed to send out with an "OK" action. -- Viktor.
Re: Relay attempts from bot filling mail queue and getting my server blacklisted: how's it happening?
On Tue, May 28, 2013 at 01:18:25PM -0400, Wietse Venema wrote: > I strongly suggest that you swap the order of the following > two rules in main.cf: > > check_recipient_access mysql:/etc/postfix/mysql-virtual_recipient.cf, > reject_unauth_destination, > > This should be: > > reject_unauth_destination, > check_recipient_access mysql:/etc/postfix/mysql-virtual_recipient.cf, > > Many open relay problems are caused by having an access table > before reject_unauth_destination. Indeed the second form is safer, and equivalent provided all the recipients are in a domain that is not rejected by reject_unauth_destination. Though in this case it is a *recipient* check, so problems are unlikely, unless the table includes unintended remote addresses. Unlike sender addresses, recipient addresses are not subject to "forgery". -- Viktor.
Re: Virtual User Aliases
On 28 May 2013 18:33, Benny Pedersen wrote: > Simon B skrev den 2013-05-28 17:33: > >> May 27 23:30:17 mail postfix/pipe[16721]: 57FF6C8C033: >> to=, relay=dovecot, delay=2, delays=2/0/0/0.05, >> dsn=2.0.0, status=sent (delivered via dovecot se >> rvice) > > >> normally that delivered line would mention p...@example.com and that's >> where Dovecot would deliver it. > > > and i see dovecot delivered it, if you have 2 mailboxes, and only wnat one, > check postfix virtual_alias maps Yes, I'm not losing the mail - it's just not being delivered to the right mailbox.. Simon
Re: Problem sending emails to virtual users
I had enabled debug for all queries on mysql but only the following relevant lines were seen: 130528 10:24:07 1924 Connect postfix@localhost on postfix 1924 Query SELECT goto FROM alias WHERE address='supp...@example.com' AND active = '1' 1924 Query SELECT goto FROM alias WHERE address='supp...@example.com' AND active = '1' 130528 10:24:13 1924 Query SELECT goto FROM alias WHERE address='example.com' AND active = '1' 1925 Connect postfix@localhost on postfix 1925 Query SELECT domain FROM domain WHERE domain='example.com' AND backupmx = '0' AND active = '1' 1924 Query SELECT goto FROM alias WHERE address='tic...@example.com' AND active = '1' 1924 Query SELECT goto FROM alias WHERE address='example.com' AND active = '1' 1925 Query SELECT domain FROM domain WHERE domain='example.com' AND backupmx = '0' AND active = '1' 130528 10:24:24 1923 Query SET GLOBAL general_log = 0 I am not able to figure out why it says unknown user
Re: Virtual User Aliases
On Tue, May 28, 2013 at 07:25:02PM +0200, Simon B wrote: > On 28 May 2013 18:33, Benny Pedersen wrote: > > Simon B skrev den 2013-05-28 17:33: > > > >> May 27 23:30:17 mail postfix/pipe[16721]: 57FF6C8C033: > >> to=, relay=dovecot, delay=2, delays=2/0/0/0.05, > >> dsn=2.0.0, status=sent (delivered via dovecot se > >> rvice) Virtual alias rewriting is performed by cleanup(8) per the override flags passed from smtpd. Since this address was not rewritten, and what changed recently is a newly disabled filter. Despite reports to the contrary the problem is receive_override_options or last resort a cleanup service with master.cf overrides for virtual_alias_maps, ... -- Viktor.
Re: Relay attempts from bot filling mail queue and getting my server blacklisted: how's it happening?
Viktor Dukhovni: > On Tue, May 28, 2013 at 01:18:25PM -0400, Wietse Venema wrote: > > > I strongly suggest that you swap the order of the following > > two rules in main.cf: > > > > check_recipient_access mysql:/etc/postfix/mysql-virtual_recipient.cf, > > reject_unauth_destination, > > > > This should be: > > > > reject_unauth_destination, > > check_recipient_access mysql:/etc/postfix/mysql-virtual_recipient.cf, > > > > Many open relay problems are caused by having an access table > > before reject_unauth_destination. > > Indeed the second form is safer, and equivalent provided all the > recipients are in a domain that is not rejected by > reject_unauth_destination. > > Though in this case it is a *recipient* check, so problems are unlikely, > unless the table includes unintended remote addresses. Unlike sender > addresses, recipient addresses are not subject to "forgery". There is no need to forge "u...@yahoo.com" if a spammer really wants to send mail there :-) Wietse
Re: Virtual User Aliases
On 28 May 2013 19:34, "Viktor Dukhovni" wrote: > > On Tue, May 28, 2013 at 07:25:02PM +0200, Simon B wrote: > > > On 28 May 2013 18:33, Benny Pedersen wrote: > > > Simon B skrev den 2013-05-28 17:33: > > > > > >> May 27 23:30:17 mail postfix/pipe[16721]: 57FF6C8C033: > > >> to=, relay=dovecot, delay=2, delays=2/0/0/0.05, > > >> dsn=2.0.0, status=sent (delivered via dovecot se > > >> rvice) > > Virtual alias rewriting is performed by cleanup(8) per the override > flags passed from smtpd. Since this address was not rewritten, > and what changed recently is a newly disabled filter. Despite > reports to the contrary the problem is receive_override_options or > last resort a cleanup service with master.cf overrides for > virtual_alias_maps, ... I know you're right. I just can't find it and I'd rather not rip things out in trial and error. I'll keep digging.. Simon
Re: Virtual User Aliases
On Tue, May 28, 2013 at 08:22:56PM +0200, Simon B wrote: > On 28 May 2013 19:34, "Viktor Dukhovni" wrote: > > > > On Tue, May 28, 2013 at 07:25:02PM +0200, Simon B wrote: > > > > > On 28 May 2013 18:33, Benny Pedersen wrote: > > > > Simon B skrev den 2013-05-28 17:33: > > > > > > > >> May 27 23:30:17 mail postfix/pipe[16721]: 57FF6C8C033: > > > >> to=, relay=dovecot, delay=2, delays=2/0/0/0.05, > > > >> dsn=2.0.0, status=sent (delivered via dovecot se > > > >> rvice) > > > > Virtual alias rewriting is performed by cleanup(8) per the override > > flags passed from smtpd. Since this address was not rewritten, > > and what changed recently is a newly disabled filter. Despite > > reports to the contrary the problem is receive_override_options or > > last resort a cleanup service with master.cf overrides for > > virtual_alias_maps, ... > > I know you're right. I just can't find it and I'd rather not rip things out > in trial and error. > > I'll keep digging.. At the very least run "postfix reload", or even "stop/start" perhaps master.cf does not match run-time reality. You can also briefly run "cleanup -v" to see what cleanup is doing with rewriting and what flags it receives from smtpd. -- Viktor.
Re: sent mail to the mail list which contains myself
On 2013-5-28 16:12, li...@kurawa.fidonet.or.id wrote: On Tue, 28 May 2013 16:04:09 +0800 Bu Xiaobing wrote: When I send mails to the mail list that contains myself, I will received the mail. Is there any way to discard there mails sent back to the original sender in the mail list? This not related to postfix. But if you're using Mailman to manage mail list, there are option to change this behavior.. look at "Receive your own posts to the list?" and set it to "No". The mail lists built for internal use only, the lists/members are maintained by LDAP, so I think the Mailman can't help.
Re: sent mail to the mail list which contains myself
On 5/28/2013 9:11 PM, Bu Xiaobing wrote: > On 2013-5-28 16:12, li...@kurawa.fidonet.or.id wrote: >> On Tue, 28 May 2013 16:04:09 +0800 >> Bu Xiaobing wrote: >> >>> When I send mails to the mail list that contains myself, I will >>> received the mail. >>> >>> Is there any way to discard there mails sent back to the original >>> sender in the mail list? >>> >> >> This not related to postfix. But if you're using Mailman to manage mail >> list, there are option to change this behavior.. look at "Receive your >> own posts to the list?" and set it to "No". >> > > The mail lists built for internal use only, the lists/members are > maintained by LDAP, so I think the Mailman can't help. What you have is called a "distribution list". As others mentioned, if you want the feature you describe, you will need to use mailing list manager software for everyone in the list to have this option. If you want this only for yourself, again as mentioned, create a rule/filter in your MUA to discard such messages. -- Stan
