Can anyone who is interested in patching source code please contact me
offlist
We need to make small changes in maillog formats for compliance
requirements of a client
I look with great fright upon the day that the format of that dbase will
change. The mailflow on my private server will be completely undone!
Anyway. No worries, I'll check the code and see what I can come up with.
It's just my silly wish to torture spambots a bit.
On Fri, Nov 2, 2012 at 12:27
On Wed, 2012-10-31 at 09:01:23 -0400, Wietse Venema wrote:
> Ralf Hildebrandt:
> > * Sahil Tandon :
> ...
> > > test -n "`$POSTCONF -c $config_directory -n smtpd_relay_restrictions`"
> > >
> > > With this, the forward compatibility shim would only trigger if
> > > smtpd_relay_restrictions does
Hi,
>> You cannot query the ZEN list via the Google Servers...
Ah, yes, of course.
> He may not be allowed to from his own resolvers either, possibly causing
> this problem. Alex at one time you had a Spamhaus datafeed
> subscription. Some time ago your load had dropped below the daily limit
Michal Kurka:
> Hello.
> I need accept incoming mails with invalid envelope sender address. But
> Postfix reject these mails:
>
> MAIL FROM: <@168.1.150>
> 501 5.1.7 Bad sender address syntax
>
> I used "sender_canonical_maps" with record
> @168.1.150 u...@domain.tld
> but this isn't eno
Noel Jones:
> On 11/1/2012 8:55 AM, Han Boetes wrote:
> > I think you have a point there. Let's see what happens. Maybe later
> > on I will use spamd to annoy the zombies found by postscreen. To
> > keep the logfiles clean and for sadistic reasons. ;-)
> >
> > BTW how can I read this dbase?
> >
On 11/1/2012 8:08 AM, Ralf Hildebrandt wrote:
> You cannot query the ZEN list via the Google Servers...
He may not be allowed to from his own resolvers either, possibly causing
this problem. Alex at one time you had a Spamhaus datafeed
subscription. Some time ago your load had dropped below the
On Thu, Nov 01, 2012 at 07:06:04PM +0100, Michal Kurka wrote:
> Dne 1.11.2012 v 17:57 Reindl Harald napsal(a):
>
> > > But is some solution for Postfix version <2.7 (and >2.1), if
> > > upgrade isn't possible?
> >
> > why should a upgrade not be possible?
>
> If server has older system, then up
On Thu, Nov 01, 2012 at 07:06:04PM +0100, Michal Kurka wrote:
> Dne 1.11.2012 v 16:48 Viktor Dukhovni napsal(a):
>
> > > But is some solution for Postfix version <2.7 (and >2.1), if upgrade
> > > isn't possible?
> >
> > Upgrades are always *possible*. You just need to be sufficiently
> > motiva
Dne 1.11.2012 v 09:37 Claus Assmann napsal(a):
> >address. It always send MAIL FROM: <@168.1.150>
>
> Which also has a command syntax error: space after colon is invalid.
Yes. Fortunately Postfix this tolerates.
Dne 1.11.2012 v 16:48 Viktor Dukhovni napsal(a):
> > But is some solution for Pos
Am 01.11.2012 17:44, schrieb Michal Kurka:
> Dne 1.11.2012 v 15:56 Viktor Dukhovni napsal(a):
>>> I need accept incoming mails with invalid envelope sender address. But
>>> Postfix reject these mails:
>>>
>>> MAIL FROM: <@168.1.150>
>>> 501 5.1.7 Bad sender address syntax
>>
>> http://www.po
Hi,
>> I have a trivial question: I have several smtpd blocks in my
>> master.cf. Most of the time with similar options, but maybe just
>> single options change. Is there some "include" option that I could
>> cut these options and paste them in a separate file and include it
>> where needed?
>
On Thu, Nov 01, 2012 at 05:44:33PM +0100, Michal Kurka wrote:
> > > MAIL FROM: <@168.1.150>
> > > 501 5.1.7 Bad sender address syntax
> >
> > http://www.postfix.org/postconf.5.html#smtpd_command_filter
>
> Yes, nice solution, thanks for a link!
>
> But is some solution for Postfix version <2.7
On Thu, Nov 01, 2012 at 04:46:21PM +0100, Christian Rößner wrote:
> I have a trivial question: I have several smtpd blocks in my
> master.cf. Most of the time with similar options, but maybe just
> single options change. Is there some "include" option that I could
> cut these options and paste t
Dne 1.11.2012 v 15:56 Viktor Dukhovni napsal(a):
> > I need accept incoming mails with invalid envelope sender address. But
> > Postfix reject these mails:
> >
> > MAIL FROM: <@168.1.150>
> > 501 5.1.7 Bad sender address syntax
>
> http://www.postfix.org/postconf.5.html#smtpd_command_filter
>address. It always send MAIL FROM: <@168.1.150>
Which also has a command syntax error: space after colon is invalid.
This is explicitly listed in RFC 5321, pg.20:
Since it has been a common source of errors, it is worth noting that
spaces are not permitted on either side of the colon follo
Michal Kurka skrev den 01-11-2012 16:48:
Unfortunately I cannot set up that mail client which sending this
ugly
address. It always send MAIL FROM: <@168.1.150>
and telnet 168.1.150 25 works ?
have you invented ipv3 for mobilephones ? :)
it should be possible to make it contain valid sender
Am 01.11.2012 16:48, schrieb Michal Kurka:
> Dne 1.11.2012 v 16:18 Benny Pedersen napsal(a):
>
>> Michal Kurka skrev den 01-11-2012 16:05:
>>> Hello.
>>>I need accept incoming mails with invalid envelope sender address. But
>>> Postfix reject these mails:
>>>
>>> MAIL FROM: <@168.1.150>
>>>
On Thu, Nov 01, 2012 at 04:05:18PM +0100, Michal Kurka wrote:
> Hello.
> I need accept incoming mails with invalid envelope sender address. But
> Postfix reject these mails:
>
> MAIL FROM: <@168.1.150>
> 501 5.1.7 Bad sender address syntax
http://www.postfix.org/postconf.5.html#smtpd_comman
On Thu, Nov 01, 2012 at 08:37:43AM +0800, Fred Ho wrote:
> The problem happened intermittently with different senders and
> I found it usually involved multiple recipients and have attachments.
> What I don't understand is Postfix qmgr took over 2 hours later
> to process that stucked mail while
Dne 1.11.2012 v 16:18 Benny Pedersen napsal(a):
> Michal Kurka skrev den 01-11-2012 16:05:
> > Hello.
> >I need accept incoming mails with invalid envelope sender address. But
> > Postfix reject these mails:
> >
> > MAIL FROM: <@168.1.150>
> > 501 5.1.7 Bad sender address syntax
>
> add [] a
Hi,
I have a trivial question: I have several smtpd blocks in my master.cf. Most of
the time with similar options, but maybe just single options change. Is there
some "include" option that I could cut these options and paste them in a
separate file and include it where needed?
Just a sample wi
Michal Kurka skrev den 01-11-2012 16:05:
Hello.
I need accept incoming mails with invalid envelope sender
address. But
Postfix reject these mails:
MAIL FROM: <@168.1.150>
501 5.1.7 Bad sender address syntax
add [] around hostname
sillyexample@[127.0.0.1]
FromName hidded, so roundcube use emailaddr skrev den 01-11-2012 15:57:
thanks from windy and cloudy hamburg
why not change the bot ?
# body.eml
From: "Bot"
To: "innocent recipient"
Subject: bot msg
hi friend :)
# send it with sendmail like this
sendmail -f ran...@example.com ab...@exampl
Hello.
I need accept incoming mails with invalid envelope sender address. But
Postfix reject these mails:
MAIL FROM: <@168.1.150>
501 5.1.7 Bad sender address syntax
I used "sender_canonical_maps" with record
@168.1.150 u...@domain.tld
but this isn't enough.
(In old version Postfix (2.1
On Thu, 01 Nov 2012 10:22:13 +0100
Robert Schetterer wrote:
> Am 01.11.2012 09:14, schrieb Ram:
> >
> > On 11/01/2012 11:49 AM, mancyb...@gmail.com wrote:
> >> Hi All, first post here, nice to meet you :)
> >>
> >> I've been using postfix and dovecot for years but always with few users.
> >>
> >
hello list,
hello everyone.
is it possible to rewrite the From: header on outgoing Mails for only a
few chosen accounts?
thanks from windy and cloudy hamburg
marko
On 11/1/2012 8:55 AM, Han Boetes wrote:
> I think you have a point there. Let's see what happens. Maybe later
> on I will use spamd to annoy the zombies found by postscreen. To
> keep the logfiles clean and for sadistic reasons. ;-)
>
> BTW how can I read this dbase?
>
> ~% postmap -s btree:/var
thorso...@lavabit.com skrev den 31-10-2012 22:48:
Sure. Why did you (why did the author of the guide) choose Cyrus
SASL? If you are using Dovecot IMAP, it makes absolutely no sense
then to use Cyrus SASL. Dovecot SASL is much easier to set up. If
you're using something else for IMAP, Dovecot SASL
I think you have a point there. Let's see what happens. Maybe later on I
will use spamd to annoy the zombies found by postscreen. To keep the
logfiles clean and for sadistic reasons. ;-)
BTW how can I read this dbase?
~% postmap -s btree:/var/spool/postfix/postscreen/db
1.2.3.4 1351857604;13517
/ Alex wrote on Thu 1.Nov'12 at 9:03:00 -0400 /
> Hi,
>
> >> I have a fc15 server with postfix-2.8.10 and have enabled postscreen.
> >> I've enabled it before without any difficulty, so I'm not sure what
> >> I'm doing wrong in this case. For some reason it is printing these
> >> errors periodi
* Alex :
> > cat /etc/resolv.conf
> > postfix check
> >
> > what's the output of those?
>
> It's set up to use the local caching server,
good. Which server is the caching server asking?
> and doesn't otherwise
> have any resolution issues. Even when I try to resolve that host using
> 8.8.4.4,
Hi,
>> I have a fc15 server with postfix-2.8.10 and have enabled postscreen.
>> I've enabled it before without any difficulty, so I'm not sure what
>> I'm doing wrong in this case. For some reason it is printing these
>> errors periodically:
>>
>> Oct 31 23:41:15 portal postfix/dnsblog[1520]: warn
/ Wietse Venema wrote on Thu 1.Nov'12 at 7:48:44 -0400 /
> Han Boetes:
> > After that postscreen gets to deal with whatever comes next. Now incase
> > postscreen decides that the ip is a zombie it's being blacklisted by
> > postscreen. In that case I'd like to hand the ip back to OpenBSD spamd.
Han Boetes:
> After that postscreen gets to deal with whatever comes next. Now incase
> postscreen decides that the ip is a zombie it's being blacklisted by
> postscreen. In that case I'd like to hand the ip back to OpenBSD spamd.
Good luck with that. I would not invest development time for such
a
On 10/31/2012 4:46 PM, thorso...@lavabit.com wrote:
>> The above two settings are sufficient to require encryption on every
>> connection. Note these settings are not appropriate for an
>> internet-facing server.
>
> I don't want to send passwords in clear that's what I'm trying to
> accomplish.
Hi,
I'm using OpenBSD spamd before postscreen. I scripted a log tailing script
which checks any new connection to a few rbls and if it's not on them I
whitelist the ip, bypassing further greyfiltering.
After that postscreen gets to deal with whatever comes next. Now incase
postscreen decides that
Am 01.11.2012 09:14, schrieb Ram:
>
> On 11/01/2012 11:49 AM, mancyb...@gmail.com wrote:
>> Hi All, first post here, nice to meet you :)
>>
>> I've been using postfix and dovecot for years but always with few users.
>>
>> Now i must build a server for 1500 users,
>> they will use various email sof
On 11/01/2012 11:49 AM, mancyb...@gmail.com wrote:
Hi All, first post here, nice to meet you :)
I've been using postfix and dovecot for years but always with few users.
Now i must build a server for 1500 users,
they will use various email software (thunderbird, outlook, ..)
the webmail (i'm no
* Alex :
> Hi,
>
> I have a fc15 server with postfix-2.8.10 and have enabled postscreen.
> I've enabled it before without any difficulty, so I'm not sure what
> I'm doing wrong in this case. For some reason it is printing these
> errors periodically:
>
> Oct 31 23:41:15 portal postfix/dnsblog[152
* thorso...@lavabit.com :
> Hi,
>
> I'm getting the following connections from suspicious IPs.
>
> $ sudo more /var/log/mail.info
>
> postfix/smtpd[PID]: connect from unknown[IP]
> postfix/smtpd[PID]: lost connection after UNKNOWN from
> unknown[IP]
> postfix/smtpd[PID]: disconnect from un
41 matches
Mail list logo
