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_a
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
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)
>
>
&
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 post
On 28 May 2013 20:35, Viktor Dukhovni wrote:
> 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 29 May 2013 20:05, Jeroen Geilman wrote:
> On 05/29/2013 11:26 AM, Simon B wrote:
>>
>> On 28 May 2013 20:35, Viktor Dukhovni wrote:
>>>
>>> On Tue, May 28, 2013 at 08:22:56PM +0200, Simon B wrote:
>>>
>>>> On 28 May 2013 19:34, "Vik
On 30 May 2013 22:44, Wietse Venema wrote:
> Simon B:
>> That's what I thought. I did your suggestion and postfix did not
>> complain. Not doing postfix stop/start or even /etc/init.d/postfix
>> start/stop..
>>
>> So, now I'm stumped. There are other
On 31 May 2013 21:07, "Viktor Dukhovni" wrote:
>
> On Fri, May 31, 2013 at 06:46:50PM +0200, Simon B wrote:
>
> > smtp inet n - - - - smtpd -v
> >-o receive_override_options=
> > cleanup unix n -
On 14 June 2013 17:44, c cc wrote:
>
> Hi,
>
> For the last few days, I noticed that our postfix server had crawl to a halt
> due to some kind of email attack. As you can see below, there were a lot of
> smtp connections. I was wondering if there is a way to stop this from
> Postfix? Thanks!
>
>
On 25 Jun 2013 15:04, "Fabrizio Monti" wrote:
>
> @Jerry
>
> >Please don't use HTML format to send email. Plain ASCII is preferred.
> Sorry, correct it immediately.
>
>
> postconf -n
>
> alias_database = hash:/etc/aliases
> broken_sasl_auth_clients = yes
> command_directory = /usr/sbin
> config_di
On 19 Jul 2013 23:28, "Sam Flint" wrote:
>
> my postfix will not accept remote connections, but it will accept local.
>
> postconf -n:
> broken_sasl_auth_clients = yes
> config_directory = /etc/postfix
> home_mailbox = Maildir/
> inet_interfaces = all
> inet_protocols = ipv4, ipv6
> message_size_l
On 19 Jul 2013 23:39, "Sam Flint" wrote:
>
> I see, but it does nothing.
>
Don't top-post please.
Rob explained this perfectly in the archives..
http://postfix.1071664.n5.nabble.com/smtpd-recipient-restrictions-Best-Practices-td10171.html
> Sam
>
>
> On F
On 29 Jul 2013 18:38, "motty cruz" wrote:
>
> Hello, users in my domain are getting lots of spam emails from facebook
such as this update+zj4o40c2_...@facebookmail.com
>
> here is the header:
> Return-Path:
> X-Original-To: u...@domain.com
> Delivered-To: user@domain
> Received: from spamfilter.d
On 22 Aug 2013 13:52, "Charles Marcus" wrote:
>
> Hi all,
>
> This isn't about spam, this is about blocking obvious attempts to
hack/connect to my submission port.
>
> I know and understand the argument against just blanket blocking hosts
based on the country of origin, but I've recently been seei
On 8 Oct 2013 01:54, "Voytek" wrote:
>
> It seems one of my users has been hacked, my postfix server is spewing
spam from many.na...@adomain.tld, how best to prevent any outbound mails
from adomain.tld till I can look at this?
>
Postfix stop
Then post your postconf -n and a log snippet of an out
On 25 Oct 2013 09:51, "Mark Goodge" wrote:
>
> On 24/10/2013 23:50, Tim Legg wrote:
>>
>> Hello,
>> I'm not tring to do virtual domains. Just trying to get it to work with
>> just one domain. This time, I used this guide:
>> https://help.ubuntu.com/12.04/serverguide/postfix.html
>> I can telnet
On 25 Oct 2013 18:54, "Charles Marcus" wrote:
>
> Hello,
>
> I'm really hoping this is either a hoax or I'm seriously misunderstanding
something...
>
> If it is true, how can they legally do this? And more importantly, how
can SASL_AUTH attempts be blocked? Maybe block all SASL attempts from
Linke
On 11 Dec 2013 11:22, "Mark Jamsek" wrote:
>
> On 11/12/2013 9:03 PM, Viktor Dukhovni wrote:
>>
>> On Wed, Dec 11, 2013 at 08:42:29PM +1100, Mark Jamsek wrote:
>>
> And, the glaringly obvious absence of SMTP auth mechanisms:
>
> 220 mail.bsdbox.co ESMTP Postfix
> ehlo bsdbox.co
>>>
On 6 Jan 2014 17:41, wrote:
>
> On 1/6/2014 5:32 PM, Mike McGinn wrote:
>>
>> On Monday, January 06, 2014 10:12:38 Roland Plüss wrote:
>>>
>>> A couple of days ago my mail server got attacked by a spammer. As it
>>> looks like he managed to compromise the password of one of the users on
>>> the sy
Hallo,
For as long as I can I remember, I have blocked connections purporting
to be my own domain/IP address using a postmapped file called
helo_checks.
This is checked AFTER permit_sasl_authenticated.
smtpd_recipient_restrictions =
reject_non_fqdn_sender,
reject_non_fqdn_recipient,
permit_sasl_
On Fri, 10 Jan 2020 at 13:39, Matus UHLAR - fantomas wrote:
>
> On 10.01.20 12:42, Simon B wrote:
> >For as long as I can I remember, I have blocked connections purporting
> >to be my own domain/IP address using a postmapped file called
> >helo_checks.
>
On Fri, 10 Jan 2020 at 15:53, Matus UHLAR - fantomas wrote:
>
> >> On 10.01.20 12:42, Simon B wrote:
> >> >For as long as I can I remember, I have blocked connections purporting
> >> >to be my own domain/IP address using a postmapped file called
> >&g
On Fri, 10 Jan 2020 at 18:22, Simon B wrote:
>
> On Fri, 10 Jan 2020 at 15:53, Matus UHLAR - fantomas
> wrote:
> >
> > >> On 10.01.20 12:42, Simon B wrote:
> > >> >For as long as I can I remember, I have blocked connections purporting
> > >&
On Mon, 13 Jan 2020 at 18:44, Viktor Dukhovni
wrote:
>
> On Mon, Jan 13, 2020 at 06:25:27PM +0100, Simon B wrote:
>
> > > > >> >Since upgrading to 2.11 yesterday (yes, I am on a path to move up
> > > > >> >through debian versions), all mail c
On Wed, 15 Jan 2020 at 13:40, Matus UHLAR - fantomas wrote:
>
> >> On Mon, Jan 13, 2020 at 06:25:27PM +0100, Simon B wrote:
> >> > > > >> >Since upgrading to 2.11 yesterday (yes, I am on a path to move up
> >> > > > >> >thro
On Wed, 15 Jan 2020 at 15:57, Dominic Raferd wrote:
>
>
>
> On Wed, 15 Jan 2020 at 13:36, Simon B wrote:
>>
>> On Wed, 15 Jan 2020 at 13:40, Matus UHLAR - fantomas
>> wrote:
>> >
>> > >> On Mon, Jan 13, 2020 at 06:25:27PM +0100, Si
Hi
Currently the smtpd for receiving mails from amavis is set up like:
119 #The amavis reciever
120 127.0.0.1:10025 inet n - - - - smtpd
Consequently it listens only IPv4
~# netstat -tulpn | grep 10025
tcp0 0 127.0.0.1:10025 0.0.0.0:*
LISTEN 4849/master
Amavis is list
On Wed, 15 Jan 2020 at 17:43, Jaroslaw Rafa wrote:
>
> Dnia 15.01.2020 o godz. 17:26:48 Simon B pisze:
> >
> > Amavis listens on 10024, and postfix listens on 10025
> >
> > That means mail comes in on 587, it goes to amavis on 10024 and comes
> > back on 100
On Wed, 15 Jan 2020 at 18:03, Wietse Venema wrote:
>
> Simon B:
> > Hi
> >
> > Currently the smtpd for receiving mails from amavis is set up like:
> >
> > 119 #The amavis reciever
> > 120 127.0.0.1:10025 inet n - - - - smtpd
> >
> > Conse
On Wed, 15 Jan 2020 at 18:00, Dominic Raferd wrote:
>
>
> On Wed, 15 Jan 2020 at 16:50, Simon B wrote:
>>
>> On Wed, 15 Jan 2020 at 17:43, Jaroslaw Rafa wrote:
>> >
>> > Dnia 15.01.2020 o godz. 17:26:48 Simon B pisze:
>> > >
>>
30 matches
Mail list logo
