virtual_alias_maps no longer working

Hello everybody I had a perfectly working Postfix configuration, but after a server restart something went weird. Postfix claims several users are unknown. It turns out that these are aliases from my virtual_alias_maps file. I have the following in main.cf: virtual_alias_maps = dbm:/etc/postfi

Re: virtual_alias_maps no longer working

Juerg Reimann schrieb: >Does anybody have an idea what could be wrong? Just a wild guess... Is your Postfix chroot'ed, and if so, have the listed files been copied there? Enabling debugging, what do the logs tell you about the mapping process? Cheers, Nik

smtp_connection_cache_on_demand question

Hello, I've stumbled across one of our older systems and noticed a minor problem in its mail delivery system. Nov 20 07:13:55 n2rhps87 postfix/smtp[10528]: 5BB06440329: to=, relay=mailrelay.cms1[10.254.254.18]:25, delay=300, delays=0.07/0/0.01/300, dsn=5.5.0, status=bounced (Protocol error:

Do not send mails to addresses with more than 3 dots in username part

Hello, I run a Drupal 7 website on a CentOS 6.4 server with postfix-2.6.6-2.2.el6_1.x86_64. In the last few months the amount of fake users trying to register at my website has increased dramatically - I get 2 or 3 of such registrations per minute. Mostly they have fake mail adresses with many d

Re: smtp_connection_cache_on_demand question

On Fri, Nov 22, 2013 at 10:02:33AM +0100, Pavel Urban wrote: > Nov 20 07:13:55 n2rhps87 postfix/smtp[10528]: 5BB06440329: > to=, relay=mailrelay.cms1[10.254.254.18]:25, > delay=300, delays=0.07/0/0.01/300, dsn=5.5.0, status=bounced > (Protocol error: host mailrelay.cms1[10.254.254.18] said: >

Re: Do not send mails to addresses with more than 3 dots in username part

Should I use smtp_header_checks here? I have also asked the question at http://serverfault.com/questions/556723/silently-drop-outgoing-mails-to-us-er-n-a-megmail-com-more-than-3-dots-in-user (And I apologize for my mail being not in plain text - I use Gmail and they have changed their interface a

Re: Do not send mails to addresses with more than 3 dots in username part

Am 22.11.2013 10:12, schrieb Alexander Farber: > I run a Drupal 7 website on a CentOS 6.4 server with > postfix-2.6.6-2.2.el6_1.x86_64. > > In the last few months the amount of fake users trying to register at my > website has increased dramatically - I get > 2 or 3 of such registrations per m

Re: Do not send mails to addresses with more than 3 dots in username part

On Fri, Nov 22, 2013 at 10:45 AM, li...@rhsoft.net wrote: > > problems needs to be solved on the root cause not worked around somewhere > else > No, at the moment I am looking for the Postfix workaround. I'd like my postfix to drop OUTGOING mail silently if addressed to us.er.n.a...@gmail.com

Re: Do not send mails to addresses with more than 3 dots in username part

I think I'd like to use smtp_header_checks with DISCARD action - but http://postfix.org/header_checks.5.html says such a combination is not supported?

Re: Do not send mails to addresses with more than 3 dots in username part

Am 22.11.2013 10:48, schrieb Alexander Farber: > On Fri, Nov 22, 2013 at 10:45 AM, li...@rhsoft.net > > wrote: > > > problems needs to be solved on the root cause not worked around > somewhere else > > > > No, at the moment I am loo

Re: Do not send mails to addresses with more than 3 dots in username part

Hello, I know regexes well - but can't figure out, where to applly them in Postfix, since smtp_header_checks with DISCARD action seems not to be supported with OUTGOING mail? On Fri, Nov 22, 2013 at 11:22 AM, Robert Schetterer wrote: > > > Am 22.11.2013 10:48, schrieb Alexander Farber: > > > I'

Re: Do not send mails to addresses with more than 3 dots in username part

Alexander Farber: > Hello, I know regexes well - but can't figure out, where to applly them in > Postfix, since smtp_header_checks with DISCARD action seems not to be > supported with OUTGOING mail? Attack the problem at the point where mail ENTERS Postfix. Wietse

Re: Do not send mails to addresses with more than 3 dots in username part

Am 22.11.2013 12:11, schrieb Alexander Farber: > Hello, I know regexes well - but can't figure out, where to applly them > in Postfix, since smtp_header_checks with DISCARD action seems not to be > supported with OUTGOING mail? perhaps try restriction classes in combination with regex sender res

Re: Do not send mails to addresses with more than 3 dots in username part

Thanks, I agree with all general advices... But for now I just want to stop the flood (and also Drupal is difficult to modify for me + I don't want to add CAPTCHA to my already overloaded reg. form, etc., etc.). So the following seems to work for me for now - /etc/postfix/header_checks: /^To: \S

Re: Do not send mails to addresses with more than 3 dots in username part

Am 22.11.2013 12:38, schrieb Alexander Farber: > Thanks, I agree with all general advices... > But for now I just want to stop the flood > (and also Drupal is difficult to modify for me + > I don't want to add CAPTCHA to my > already overloaded reg. form, etc., etc.) zero understanding to refuse

Re: Do not send mails to addresses with more than 3 dots in username part

I admin this website for 3 years already and despite it being just a small obscure card game - there haven't been a month without a challenge, where I had to go and change something manually. This postfix workaround is pretty perfect for now, I enjoy looking at maillog right now and see the Nov 2

Re: incoming mail errors

* Dave Johnsom : It's either this: > check_policy_service inet:127.0.0.1:, or this: > check_policy_service inet:127.0.0.1:10031, Find out what's listening on port and 10031: % sudo netstat -tulpen |egrep ":(|10031)" (which are both listed TWICE in your config!) -- [*] sys4 AG

Re: Do not send mails to addresses with more than 3 dots in username part

my last post in this thread because we are going off-topic discard messages on a MTA is the *last resort* if nothing else happens but not the solution for a broken web-app because it is the wrong layer hence even if you insist in "more than 3 dots in username part" this belong to the *web applica

Re: Do not send mails to addresses with more than 3 dots in username part

Yes, Reindl, thanks again for all these _obvious_ advices, while I was just asking a specific Postfix-related one. On Fri, Nov 22, 2013 at 1:03 PM, li...@rhsoft.net wrote: > my last post in this thread because we are going off-topic > > discard messages on a MTA is the *last resort* if nothing

Re: virtual_alias_maps no longer working

On Fri, Nov 22, 2013 at 09:00:01AM +0100, Juerg Reimann wrote: > I had a perfectly working Postfix configuration, but after a > server restart something went weird. Postfix claims several > users are unknown. It turns out that these are aliases from my > virtual_alias_maps file. I have the followin

Re: Do not send mails to addresses with more than 3 dots in username part

A CAPTCHA isn't going to solve your problem either, my forums have always had a rather hard-to-solve CAPTCHA enabled, and I too get hundreds of these registrations per day with many dots @gmail.com That said, I agree it'd be better to stop registrations from this format in the first place, but thi

Re: Do not send mails to addresses with more than 3 dots in username part

On 11/22/2013 04:12 AM, Alexander Farber wrote: > Hello, > > I run a Drupal 7 website on a CentOS 6.4 server > with postfix-2.6.6-2.2.el6_1.x86_64. > > In the last few months the amount of fake users trying to register at my > website has increased dramatically - I get 2 or 3 of such registration

Binding virtual ip

I have created a virtual ip on the loopback interface. How do I make postfix listen on that interface? ifconfig -- eth0 Link encap:Ethernet HWaddr 00:0c:29:89:ed:18 inet addr:192.168.0.244 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST

Re: Do not send mails to addresses with more than 3 dots in username part

I've spent last 2 hours with Drupal CAPTCHA module - the default image and math captchas didn't stop any spam user at all - I could see fake users still registering - every few seconds (scary!). I have uploaded a russian font then and configured the CAPTCHA to use russian letters only (since my si

Re: Binding virtual ip

sorry for the bother. it's inet_interfaces. On Fri, Nov 22, 2013 at 9:23 AM, Roman Gelfand wrote: > I have created a virtual ip on the loopback interface. How do I make > postfix listen on that interface? > > ifconfig > -- > > eth0 Link encap:Ethernet HWaddr 00:0c:29:89:ed:18 >

Re: Do not send mails to addresses with more than 3 dots in username part

Am 22.11.2013 15:31, schrieb Alexander Farber: > I've spent last 2 hours with Drupal CAPTCHA module - > the default image and math captchas didn't stop > any spam user at all - I could see fake users > still registering - every few seconds (scary!). > > I have uploaded a russian font then and con

Re: Do not send mails to addresses with more than 3 dots in username part

Yes, ok - it's my fault. Next time I will ask a Postfix question here, I shouldn't forget to add a disclaimer "and please no CMS or web admin advice needed" ;-)

Re: Do not send mails to addresses with more than 3 dots in username part

On 22 Nov 2013, at 07:42 , li...@rhsoft.net wrote: > that's why i did not name captcha only besdies that your > "3 dots in username part" should happen on the webserver With gmail at least, periods in the username field are non-significant. All of these email addresses are identical to google: t

Re: Do not send mails to addresses with more than 3 dots in username part

On 11/23/2013 12:38 AM, Alexander Farber wrote: > So the following seems to work for me for now - > > /etc/postfix/header_checks: > > /^To: \S+\.\S+\.\S+\.\s...@gmail.com $/i DISCARD > > /etc/postfix/main.cf : > > header_checks = pcre:/etc/postfix/header_c

Re: Binding virtual ip

Roman Gelfand skrev den 2013-11-22 15:23: I have created a virtual ip on the loopback interface. How do I make postfix listen on that interface? tcp0 0 127.0.0.1:250.0.0.0:* LISTEN tcp0 0 192.168.0.244:250.0.0.0:* LIST

Re: can someone explain this SPF fail to me

jeffrey j donovan skrev den 2013-11-21 18:40: : host mail.ncem-pa.org[204.186.202.37] said: 554 5.7.1 : Recipient address rejected: Failed SPF check; beth.k12.pa.us, Redundant applicable 'v=spf1' sender policies found (in reply to RCPT TO command) Reporting-MTA: dns; smtp5.beth.k12.p

Re: can someone explain this SPF fail to me

LunarZone skrev den 2013-11-21 21:20: Why do you even have this record? "v=spf1 include:_spf.google.com ~all" Did you get it from here? https://support.google.com/a/answer/178723 You already have what you need for Google site verification, google site verification is a valid spf record ? se