Re: Postfix for bulk email and TLS
On 01/04/17 09:03, Xinhuan Zheng wrote: > Does anyone in postfix mailing list have experience using Postifx > software for sending bulk emails with TLS encryption? Can you share your > experience with me? It works just fine. > The amount of bulk email is quite large, normally > for marketing purpose. In the past we have been using sendmail bundled > with CentOS 6 OS for a few years already. But we need to upgrade our > system and one new requirement is to use TLS. Postfix support for TLS goes way back. > So I’m planning on using > recent CentOS 7 operating system. But as I look at its repository, > postfix and openssl appear to be old versions. Please see the Red Hat backports policy at: https://access.redhat.com/security/updates/backporting/ OpenSSL in CentOS 7 is fine, I would not change or mess with it as it's an integral part of the distribution. Postfix is fine as well and there is no lack of TLS support in the Postfix 2.10.1. That said, you can get a newer postfix for CentOS 7 from GhettoForge: http://ghettoforge.org/index.php/postfix3 ...please note that as of this writing the latest version is in gf-testing Peter
Re: problem with protection.outlook.com released spam getting bounced
On 3/31/2017 3:50 PM, John Stoffel wrote: > So I created the following entry in my header_checks file: > > /^Delivered-To:/ WARN Found email with Delivered-To: header already in it! > > And while it did correctly warn on a bogus email that matched with > looping, it also matched on a bunch of other emails, which didn't get > rejected for looping. Postfix bounces mail when the Delivered-To address is the same as the current recipient. > > So I'm wondering if the problem is that I'm not accepting email for my > legacy "foo.com" domain properly, while I am accepting email for my > "foo.bar.com" domain that we're now supposed to be using for all > email. > The easiest explanation is that you are accepting mail for the old domain, then forwarding it through outlook back to the new domain. Or something similar. > I'm glad I just did a warning match at first, instead of holding all > these emails, because it would have been a disaster for a bit until I > figured it out. Is there anyway, besides the hold queue to just log > all the headers of these messages so I can try to understand the issue > in more detail? To log all headers, use a header_check like: /./ info NOTE: postfix only allows one header_check rule per header, so this will disable any header_checks below it. Usually people put a log-all rule like this at the end of header_checks file. > I suspect that part of the problem is that we use > this server for outgoing emails, but all incoming from the internet > arrives through *.outbound.protection.outlook.com, so maybe they do > something to the headers? Test; don't speculate. As a bystander, my job it to speculate: I don't think outlook is adding the offending headers. -- Noel Jones > > My logs show the following: > > Mar 31 09:34:10 mailhost postfix/smtpd[28317]: connect from > mail-sn1nam01lp0113.outbound.protection. > outlook.com[207.46.163.113] > Mar 31 09:34:10 mailhost postfix/smtpd[28317]: 7B6D1A05FE: > client=mail-sn1nam01lp0113.outbound.prote > ction.outlook.com[207.46.163.113] > Mar 31 09:34:10 mailhost postfix/cleanup[28211]: 7B6D1A05FE: warning: > header Delivered-To: j...@foo.com from > mail-sn1nam01lp0113.outbound.protection.outlook.com[207.46.163.113]; > from=to= proto=ESMTP > helo=: Found email with > Delivered-To: header already in it! > Mar 31 09:34:10 mailhost postfix/cleanup[28211]: 7B6D1A05FE: > message-id= > Mar 31 09:34:10 mailhost postfix/qmgr[27314]: 7B6D1A05FE: > from= , size=62180, nrcpt=1 (queue active) > Mar 31 09:34:10 mailhost postfix/local[28017]: 7B6D1A05FE: > to= , relay=local, delay=0.33, delays=0.28/0/0/0.05, dsn=5.4.6, > status=bounced (mail forwarding loop for j...@foo.com) > Mar 31 09:34:10 mailhost postfix/bounce[28363]: 7B6D1A05FE: sender > non-delivery notification: CCEC5A074E > Mar 31 09:34:10 mailhost postfix/qmgr[27314]: 7B6D1A05FE: removed > > > So I'm matching things... but I'm also matching on alot of other emails which > the logs look like this: > > > Mar 31 09:36:21 mailhost postfix/smtpd[28317]: connect from > hdqmta.foo.com[192.168.172.13] > Mar 31 09:36:21 mailhost postfix/smtpd[28317]: E08F2A07A4: > client=hdqmta.foo.com[192.168.172.13] > Mar 31 09:36:21 mailhost postfix/cleanup[28191]: E08F2A07A4: warning: > header Delivered-To: foo...@foo.bar.com from hdqmta.foo.com[192.168.172.13]; > from= to= proto=ESMTP > helo=: Found email with Delivered-To: header already in > it! > Mar 31 09:36:21 mailhost postfix/cleanup[28191]: E08F2A07A4: > message-id=<201703311636.v2vgahrb028...@fovm0026.iss.bar.co.jp> > Mar 31 09:36:21 mailhost postfix/qmgr[27314]: E08F2A07A4: > from= , size=7014, nrcpt=1 (queue active) > Mar 31 09:36:21 mailhost postfix/smtpd[28317]: disconnect from > hdqmta.foo.com[192.168.172.13] > Mar 31 09:36:22 mailhost postfix/smtp[28312]: E08F2A07A4: > to= , relay=smtp.na.bar.local[192.168.64.152]:25, > delay=0.19, delays=0.01/0/0/0.18, dsn=2.6.0, status=sent (250 2.6.0 > <201703311636.v2vgahrb028...@fovm0026.iss.bar.co.jp> > [InternalId=91027536871548, Hostname=NA-EXMB-P20.NA.BAR.LOCAL] Queued mail > for delivery) > Mar 31 09:36:22 mailhost postfix/qmgr[27314]: E08F2A07A4: removed >
Re: Postfix for bulk email and TLS
> On Mar 31, 2017, at 4:03 PM, Xinhuan Zhengwrote: > > Does anyone in postfix mailing list have experience using Postifx software > for sending bulk emails with TLS encryption? Can you share your experience > with me? TLS does not materially affect the performance of bulk-email delivery except when a high-volume destination's MX host set includes some hosts that are down. When one of the MX hosts is down and you don't use TLS, connection re-use will shift more of the load to the hosts that are up. With TLS there is no connection re-use, and so connection latency may rise if the remote destination is partly down. This is rare in practice for high-volume destinations. > So I’m planning on using recent CentOS 7 operating system. But as I look at > its repository, postfix and openssl appear to be old versions. Postfix TLS support is reasonably mature by Postfix 2.8, but older versions should also be fine. Just set: smtp_tls_protocols = !SSLv2, !SSLv3 smtp_tls_ciphers = medium smtp_tls_security_level = may smtp_tls_loglevel = 1 smtpd_tls_protocols = !SSLv2, !SSLv3 smtpd_tls_ciphers = medium smtpd_tls_security_level = may smtpd_tls_loglevel = 1 smtpd_tls_cert_file = ... your cert file location ... smtpd_tls_key_file = ... your key file location if different from cert file ... if these are not already the defaults for your Postfix version. -- Viktor.
Re: problem with protection.outlook.com released spam getting bounced
> "John" == John Stoffelwrites: > "Noel" == Noel Jones writes: Noel> On 3/30/2017 9:26 AM, John Stoffel wrote: >>> >>> Hi all, >>> >>> We're running postfix-2.6.6-6.el6_5.x86_64 on RHEL 6.6 and running >>> into a problem where emails that have been released from our outside >>> spam protection company, *.protection.outlook.com, are getting >>> rejected with messages like this: >>> >>> Mar 26 06:00:56 mailhost postfix/smtpd[2270]: connect from >>> mail-sn1nam01lp0113.outbound.protection.outlook.com[207.46.163.113] >>> Mar 26 06:00:56 mailhost postfix/smtpd[2270]: 51235A07D1: >>> client=mail-sn1nam01lp0113.outbound.protection.outlook.com[207.46.163.113] >>> Mar 26 06:00:56 mailhost postfix/cleanup[2279]: 51235A07D1: >>> message-id=<1490445496218.20153408.25880761.5137938...@backend.ttktravelinsider.com> >>> Mar 26 06:00:56 mailhost postfix/qmgr[27442]: 51235A07D1: >>> from= , size=40439, nrcpt=1 (queue >>> active) >>> Mar 26 06:00:56 mailhost postfix/local[2278]: 51235A07D1: >>> to= , relay=local, delay=0.29, delays=0.28/0/0/0.01, >>> dsn=5.4.6, status=bounced (mail forwarding loop for saba.shar...@sub.com) >>> Mar 26 06:00:56 mailhost postfix/bounce[2273]: 51235A07D1: sender >>> non-delivery notification: 97DF2A080B >>> Mar 26 06:00:56 mailhost postfix/qmgr[27442]: 51235A07D1: removed >>> >>> These emails are released by the end user and should be delivered, but are >>> getting bounced back. >>> >>> How would I go about figuring out if it's really a bogus "Delivered-To: " >>> header that's causing this rejection? >>> Noel> Some things you can do... Noel> - search your logs for the message-id recorded above to see if this Noel> message has been here before. Maybe this mail arrived before, was Noel> forwarded off-site, then came back; don't do that. John> So I looked back through my logs until early February and I didn't see John> it. So it's not that sort of loop as far as I can tell. Noel> - You can use the HOLD action to freeze an incoming message in the Noel> queue before the local delivery agent has a chance to bounce it. Noel> Then you can examine the message. To HOLD the message, you can use Noel> a check_recipient_access map, or a check_client_access map, or a Noel> header_checks rule. John> Ok, thanks for the hints! I'll have to read up on how to do a John> header_checks rule and implement it so that I can see what's going on John> here. Noel> (NOTE: don't be tempted to use header_checks IGNORE to remove a Noel> bogus Delivered-To header! The internet will thank you.) John> I know, but ... I might be forced to, since my users are bitching John> about losing email they release from spam. But! I can also take this John> to the vendor as proof they are doing something wrong as well. But John> first I need to get some messages and headers to look at first. So I created the following entry in my header_checks file: /^Delivered-To:/ WARN Found email with Delivered-To: header already in it! And while it did correctly warn on a bogus email that matched with looping, it also matched on a bunch of other emails, which didn't get rejected for looping. So I'm wondering if the problem is that I'm not accepting email for my legacy "foo.com" domain properly, while I am accepting email for my "foo.bar.com" domain that we're now supposed to be using for all email. I'm glad I just did a warning match at first, instead of holding all these emails, because it would have been a disaster for a bit until I figured it out. Is there anyway, besides the hold queue to just log all the headers of these messages so I can try to understand the issue in more detail? I suspect that part of the problem is that we use this server for outgoing emails, but all incoming from the internet arrives through *.outbound.protection.outlook.com, so maybe they do something to the headers? My logs show the following: Mar 31 09:34:10 mailhost postfix/smtpd[28317]: connect from mail-sn1nam01lp0113.outbound.protection. outlook.com[207.46.163.113] Mar 31 09:34:10 mailhost postfix/smtpd[28317]: 7B6D1A05FE: client=mail-sn1nam01lp0113.outbound.prote ction.outlook.com[207.46.163.113] Mar 31 09:34:10 mailhost postfix/cleanup[28211]: 7B6D1A05FE: warning: header Delivered-To: j...@foo.com from mail-sn1nam01lp0113.outbound.protection.outlook.com[207.46.163.113]; from= to= proto=ESMTP helo=: Found email with Delivered-To: header already in it! Mar 31 09:34:10 mailhost postfix/cleanup[28211]: 7B6D1A05FE: message-id= Mar 31 09:34:10 mailhost postfix/qmgr[27314]: 7B6D1A05FE: from= , size=62180, nrcpt=1 (queue active) Mar 31 09:34:10 mailhost postfix/local[28017]: 7B6D1A05FE: to= , relay=local, delay=0.33, delays=0.28/0/0/0.05, dsn=5.4.6, status=bounced (mail
Postfix for bulk email and TLS
Hello, Does anyone in postfix mailing list have experience using Postifx software for sending bulk emails with TLS encryption? Can you share your experience with me? The amount of bulk email is quite large, normally for marketing purpose. In the past we have been using sendmail bundled with CentOS 6 OS for a few years already. But we need to upgrade our system and one new requirement is to use TLS. So I’m planning on using recent CentOS 7 operating system. But as I look at its repository, postfix and openssl appear to be old versions. Thanks, - xinhuan
Re: how to remove string "[MASSMAIL]" from the subject ?
I`m comming to You with this big bottle of virtual beer :)) http://craftbeernation.org/blog/wp-content/uploads/2014/05/very-big-beer.jpg Thanks a lot my friend und viele Gruesse aus Nuernberg! On Fri, Mar 31, 2017 at 1:56 PM, Ralf Hildebrandtwrote: > * Ralf Hildebrandt : > > * Zalezny Niezalezny : > > > As I see here header_checks can do it. There is only one problem. This > rule > > > searching for a subject with string [MASSMAIL] and replacing complete > > > subject line with word "test". > > > > > > /^Subject:.*[MASSMAIL].*/ REPLACE Subject: test > > > > /^Subject:(.*)[MASSMAIL](.*)/ REPLACE Subject: $1$2 > > Sorry: > > /^Subject:(.*)\[MASSMAIL\](.*)/ REPLACE Subject: $1$2 > > -- > [*] sys4 AG > > http://sys4.de, +49 (89) 30 90 46 64 > Schleißheimer Straße 26/MG, 80333 München > > Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 > Vorstand: Patrick Ben Koetter, Marc Schiffbauer > Aufsichtsratsvorsitzender: Florian Kirstein >
Re: postfix uses A record for MX less domains
* Mario Theodoridis: > Hi everyone, > > i'm having a curious issue with our postfix instance. > > It seems it is sending emails to a domain's A record when no MX is found. > > Is that standard? Yes. > If so, can i disable this somewhere? No. > connect to bikinibottom.com[208.73.211.70]:25: Connection refused > to= , relay=none, delay=407, > delays=407/0.01/0.15/0, dsn=4.4.1, status=deferred (connect to > bikinibottom.com[208.73.211.70]:25: Connection refused) transport_maps: bikinibottom.com error:This domain does not accept mail -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG, 80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
postfix uses A record for MX less domains
Hi everyone, i'm having a curious issue with our postfix instance. It seems it is sending emails to a domain's A record when no MX is found. Is that standard? If so, can i disable this somewhere? connect to bikinibottom.com[208.73.211.70]:25: Connection refused to=, relay=none, delay=407, delays=407/0.01/0.15/0, dsn=4.4.1, status=deferred (connect to bikinibottom.com[208.73.211.70]:25: Connection refused) # dig mx bikinibottom.com ;bikinibottom.com. IN MX # dig a bikinibottom.com bikinibottom.com. 300 IN A 208.73.211.70 It's a temporary failure on top of that, left to linger in the queue til Clue sticks would be appreciated. -- Mit Freundlichen Grüßen / Regards Mario Theodoridis regify GmbH Römerstrasse 39 | D-78183 Hüfingen Amtsgericht Freiburg HRB 709343 Telefon: +49 771 8978 4238
Re: how to remove string "[MASSMAIL]" from the subject ?
* Ralf Hildebrandt: > * Zalezny Niezalezny : > > As I see here header_checks can do it. There is only one problem. This rule > > searching for a subject with string [MASSMAIL] and replacing complete > > subject line with word "test". > > > > /^Subject:.*[MASSMAIL].*/ REPLACE Subject: test > > /^Subject:(.*)[MASSMAIL](.*)/ REPLACE Subject: $1$2 Sorry: /^Subject:(.*)\[MASSMAIL\](.*)/ REPLACE Subject: $1$2 -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG, 80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
Re: how to remove string "[MASSMAIL]" from the subject ?
* Zalezny Niezalezny: > As I see here header_checks can do it. There is only one problem. This rule > searching for a subject with string [MASSMAIL] and replacing complete > subject line with word "test". > > /^Subject:.*[MASSMAIL].*/ REPLACE Subject: test /^Subject:(.*)[MASSMAIL](.*)/ REPLACE Subject: $1$2 -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG, 80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
Re: how to remove string "[MASSMAIL]" from the subject ?
As I see here header_checks can do it. There is only one problem. This rule searching for a subject with string [MASSMAIL] and replacing complete subject line with word "test". /^Subject:.*[MASSMAIL].*/ REPLACE Subject: test How to replace only single string [MAILMAN] without interrupting the rest of the subject ? Subject: [MASSMAIL] test message blablabla /^Subject:.*[MASSMAIL].*/ REPLACE Subject: test Its replacing to Subject: test How to replace that string to: Subject: test message blablabla Maybe some one knows ? Cheers Zalezny On Fri, Mar 31, 2017 at 1:29 PM, Zalezny Niezalezny < zalezny.niezale...@gmail.com> wrote: > This list (postfix-users) is so configured that when I`m clicking Reply on > Your answer, system sending message to directly to you instead of the list. > On mobile device some times its difficult. It was not my intention to write > an E-mail directly to You... I prefer list. > > Mailman is connected as usual with Postfix. So its forwarding messages > directly to Postfix and Postfix sending it to another relay. > Its quite diffucult for me because on that host I have 180 mailing lists > with ~5mln users. [MAILMAN] prefix is only on few of them and i`m searching > for some fast solution. > > Thats why I`m here... On Postfix-users list. I also opened Topic on > mailman list. > > Maybe somebody else knows how to monipulate Subject with Postfix ? > > > Thanks in advance for any help. > > > Cheers > > Zalezny > > > > > > > > > On Fri, Mar 31, 2017 at 1:11 PM, Larry Stone> wrote: > >> Neither do I as you have provided no information about your Postfix >> configuration or anything else. As it says in the Postfix list welcome >> email you received: >> TO REPORT A PROBLEM see http://www.postfix.org/DEBUG_README.html#mail >> But if you’ve verified Mailman is not adding it as a list prefix tag, >> then you need to tell us what else is handling the email before it makes it >> to your mailbox. >> >> Also, reply on list, not directly to me. Future emails sent directly to >> me will be ignored. >> >> -- >> Larry Stone >> lston...@stonejongleux.com >> >> >> >> >> >> > On Mar 31, 2017, at 6:03 AM, Zalezny Niezalezny < >> zalezny.niezale...@gmail.com> wrote: >> > >> > hi larry, >> > >> > i have removed prefix but for some list system simply adding this >> prefix.i dnt know what to do. >> > >> > Any how it would be great to know how to remove that string with >> postfix. >> > >> > >> > cheers >> > >> > zalezny >> > >> > 31 mar 2017 12:58 "Larry Stone" >> napisał(a): >> > This is a Mailman mailing list you run? That Mailman has the option to >> add a tag in front of the subject (and it’s not the default so you would >> have had to explicitly turn it on). There is a Mailman-users mailing list >> and that would be the appropriate place for help. >> > >> > But, since it says [MASSMAIL] and MASS implies to me that it’s to >> indicate that it’s being sent to a MASS of recipients, it sounds like it >> might be a mail filter downline of Mailman that, for instance, sees the >> “Precedence: bulk” header and tags the mail. In which case Mailman has >> nothing to do with it. >> > >> > In any event, the [MASSMAIL] tag is a symptom of some other problem >> adding the undesired (to you at least) tag. Fix the problem, not the >> symptom. >> > >> > -- >> > Larry Stone >> > lston...@stonejongleux.com >> > >> > >> > >> > >> > >> > > On Mar 31, 2017, at 5:32 AM, Zalezny Niezalezny < >> zalezny.niezale...@gmail.com> wrote: >> > > >> > > Hi, >> > > >> > > will it be possible to remove string [MASSMAIL] from outgoing E-mails >> ? >> > > >> > > >> > > From: bla!@firma.com >> > > to: *@gmail.com >> > > Subject: [MASSMAIL] text of the messages >> > > >> > > I would like to have some thing like this. >> > > >> > > From: bla!@firma.com >> > > to: *@gmail.com >> > > Subject: text of the messages >> > > >> > > >> > > Unfortunatelly Mailman adding this string to some of my mailing lists >> and I do not know how to change it, maybe it will be possible to rewrite it >> with Postfix ? >> > > >> > > >> > > >> > > Thanks in advance for any support. >> > > >> > > >> > > >> > > Cheeers >> > > >> > > Zalezn >> > >> >> >
Re: how to remove string "[MASSMAIL]" from the subject ?
This list (postfix-users) is so configured that when I`m clicking Reply on Your answer, system sending message to directly to you instead of the list. On mobile device some times its difficult. It was not my intention to write an E-mail directly to You... I prefer list. Mailman is connected as usual with Postfix. So its forwarding messages directly to Postfix and Postfix sending it to another relay. Its quite diffucult for me because on that host I have 180 mailing lists with ~5mln users. [MAILMAN] prefix is only on few of them and i`m searching for some fast solution. Thats why I`m here... On Postfix-users list. I also opened Topic on mailman list. Maybe somebody else knows how to monipulate Subject with Postfix ? Thanks in advance for any help. Cheers Zalezny On Fri, Mar 31, 2017 at 1:11 PM, Larry Stonewrote: > Neither do I as you have provided no information about your Postfix > configuration or anything else. As it says in the Postfix list welcome > email you received: > TO REPORT A PROBLEM see http://www.postfix.org/DEBUG_README.html#mail > But if you’ve verified Mailman is not adding it as a list prefix tag, then > you need to tell us what else is handling the email before it makes it to > your mailbox. > > Also, reply on list, not directly to me. Future emails sent directly to me > will be ignored. > > -- > Larry Stone > lston...@stonejongleux.com > > > > > > > On Mar 31, 2017, at 6:03 AM, Zalezny Niezalezny < > zalezny.niezale...@gmail.com> wrote: > > > > hi larry, > > > > i have removed prefix but for some list system simply adding this > prefix.i dnt know what to do. > > > > Any how it would be great to know how to remove that string with postfix. > > > > > > cheers > > > > zalezny > > > > 31 mar 2017 12:58 "Larry Stone" napisał(a): > > This is a Mailman mailing list you run? That Mailman has the option to > add a tag in front of the subject (and it’s not the default so you would > have had to explicitly turn it on). There is a Mailman-users mailing list > and that would be the appropriate place for help. > > > > But, since it says [MASSMAIL] and MASS implies to me that it’s to > indicate that it’s being sent to a MASS of recipients, it sounds like it > might be a mail filter downline of Mailman that, for instance, sees the > “Precedence: bulk” header and tags the mail. In which case Mailman has > nothing to do with it. > > > > In any event, the [MASSMAIL] tag is a symptom of some other problem > adding the undesired (to you at least) tag. Fix the problem, not the > symptom. > > > > -- > > Larry Stone > > lston...@stonejongleux.com > > > > > > > > > > > > > On Mar 31, 2017, at 5:32 AM, Zalezny Niezalezny < > zalezny.niezale...@gmail.com> wrote: > > > > > > Hi, > > > > > > will it be possible to remove string [MASSMAIL] from outgoing E-mails ? > > > > > > > > > From: bla!@firma.com > > > to: *@gmail.com > > > Subject: [MASSMAIL] text of the messages > > > > > > I would like to have some thing like this. > > > > > > From: bla!@firma.com > > > to: *@gmail.com > > > Subject: text of the messages > > > > > > > > > Unfortunatelly Mailman adding this string to some of my mailing lists > and I do not know how to change it, maybe it will be possible to rewrite it > with Postfix ? > > > > > > > > > > > > Thanks in advance for any support. > > > > > > > > > > > > Cheeers > > > > > > Zalezn > > > >
Re: how to remove string "[MASSMAIL]" from the subject ?
Neither do I as you have provided no information about your Postfix configuration or anything else. As it says in the Postfix list welcome email you received: TO REPORT A PROBLEM see http://www.postfix.org/DEBUG_README.html#mail But if you’ve verified Mailman is not adding it as a list prefix tag, then you need to tell us what else is handling the email before it makes it to your mailbox. Also, reply on list, not directly to me. Future emails sent directly to me will be ignored. -- Larry Stone lston...@stonejongleux.com > On Mar 31, 2017, at 6:03 AM, Zalezny Niezalezny >wrote: > > hi larry, > > i have removed prefix but for some list system simply adding this prefix.i > dnt know what to do. > > Any how it would be great to know how to remove that string with postfix. > > > cheers > > zalezny > > 31 mar 2017 12:58 "Larry Stone" napisał(a): > This is a Mailman mailing list you run? That Mailman has the option to add a > tag in front of the subject (and it’s not the default so you would have had > to explicitly turn it on). There is a Mailman-users mailing list and that > would be the appropriate place for help. > > But, since it says [MASSMAIL] and MASS implies to me that it’s to indicate > that it’s being sent to a MASS of recipients, it sounds like it might be a > mail filter downline of Mailman that, for instance, sees the “Precedence: > bulk” header and tags the mail. In which case Mailman has nothing to do with > it. > > In any event, the [MASSMAIL] tag is a symptom of some other problem adding > the undesired (to you at least) tag. Fix the problem, not the symptom. > > -- > Larry Stone > lston...@stonejongleux.com > > > > > > > On Mar 31, 2017, at 5:32 AM, Zalezny Niezalezny > > wrote: > > > > Hi, > > > > will it be possible to remove string [MASSMAIL] from outgoing E-mails ? > > > > > > From: bla!@firma.com > > to: *@gmail.com > > Subject: [MASSMAIL] text of the messages > > > > I would like to have some thing like this. > > > > From: bla!@firma.com > > to: *@gmail.com > > Subject: text of the messages > > > > > > Unfortunatelly Mailman adding this string to some of my mailing lists and I > > do not know how to change it, maybe it will be possible to rewrite it with > > Postfix ? > > > > > > > > Thanks in advance for any support. > > > > > > > > Cheeers > > > > Zalezn >
Re: how to remove string "[MASSMAIL]" from the subject ?
This is a Mailman mailing list you run? That Mailman has the option to add a tag in front of the subject (and it’s not the default so you would have had to explicitly turn it on). There is a Mailman-users mailing list and that would be the appropriate place for help. But, since it says [MASSMAIL] and MASS implies to me that it’s to indicate that it’s being sent to a MASS of recipients, it sounds like it might be a mail filter downline of Mailman that, for instance, sees the “Precedence: bulk” header and tags the mail. In which case Mailman has nothing to do with it. In any event, the [MASSMAIL] tag is a symptom of some other problem adding the undesired (to you at least) tag. Fix the problem, not the symptom. -- Larry Stone lston...@stonejongleux.com > On Mar 31, 2017, at 5:32 AM, Zalezny Niezalezny >wrote: > > Hi, > > will it be possible to remove string [MASSMAIL] from outgoing E-mails ? > > > From: bla!@firma.com > to: *@gmail.com > Subject: [MASSMAIL] text of the messages > > I would like to have some thing like this. > > From: bla!@firma.com > to: *@gmail.com > Subject: text of the messages > > > Unfortunatelly Mailman adding this string to some of my mailing lists and I > do not know how to change it, maybe it will be possible to rewrite it with > Postfix ? > > > > Thanks in advance for any support. > > > > Cheeers > > Zalezn
how to remove string "[MASSMAIL]" from the subject ?
Hi, will it be possible to remove string [MASSMAIL] from outgoing E-mails ? From: bla!@firma.com to: *@gmail.com Subject: [MASSMAIL] text of the messages I would like to have some thing like this. From: bla!@firma.com to: *@gmail.com Subject: text of the messages Unfortunatelly Mailman adding this string to some of my mailing lists and I do not know how to change it, maybe it will be possible to rewrite it with Postfix ? Thanks in advance for any support. Cheeers Zalezn
Re: No milters have been used at around midnight
Hi, > Am 30.03.2017 um 17:25 schrieb Viktor Dukhovni: > > >> On Mar 30, 2017, at 11:15 AM, Christian Rößner >> wrote: >> >> It is a VM, but the host uses ECC-RAM. No errors were reported to the kernel >> message buffer. > > Is it possible that some log messages were lost when the log > socket got re-created as part of log-rotation? Unfortunately not. There was no load on the system. It is standard rsyslog. > Do your milters always add headers? Or only for spammy messages? Yes and they also always log to syslog on connect/discconect and processing mails. > Also, you have default_action=accept, perhaps your milters were too > busy at the time. When did milter logging cease? When did it resume? > What was the message delivery rate during the "gap"... There have been very few mails at that time. That is what makes me wonder. No load could have caused this issue. I personally wonder how many people make use of that new feature smtpd_milters_maps and maybe nobody else discovered this issue though. Maybe I need to figure out how to do a test on sending mail from my relay server, while simultaneously sending mail from remote and watching. I think that should trigger the problem again, if I am right. Let's see what I can do here. Christian -- Erlenwiese 14, 36304 Alsfeld T: +49 6631 78823400, F: +49 6631 78823409, M: +49 171 9905345 smime.p7s Description: S/MIME cryptographic signature