I have a long running postfix setup dual stacked IPv4 and IPv6. I've
specified the outbound bind addresses for smtp.
smtp unix - - - - - smtp
-o smtp_bind_address=[...]
-o smtp_bind_address6=[...]
I use the host to receive mail to my domain as well as send
On Wed, Mar 05, 2014 at 04:19:16PM -0500, Wietse Venema wrote:
> Jay G. Scott:
> > overlook a "too many hops" notice.
> >
> > I've seen these at my site before, they've been going on for years,
> > but they're still rare. Maybe 4-6/year. I checked all the "offending"
> > addresses and they came
What has worked for me.
Develop a policy where user must have 8 char min password that is not
dictionary based. Linux Pam for example helps with this.
Then obtain and run fail2ban against your smtp/pop/imap logs. Most passwords
are guessed using dictionary attacks, which fail2ban you can blacklis
On Wednesday 05/03/2014 at 9:25 am, Blake Hudson wrote:
Homer Wilson Smith wrote the following on 3/4/2014 4:38 PM:
Dear Gentle Folk,
What is the state of the art in dealing with users whose SASL
password
has been compromised?
Running CentOS, and latest postfix.
Jay G. Scott:
> overlook a "too many hops" notice.
>
> I've seen these at my site before, they've been going on for years,
> but they're still rare. Maybe 4-6/year. I checked all the "offending"
> addresses and they came back as deliverable. So I believe these
> are transient effects due to occ
>
>
> I'm constantly facing the same problem (passwords comprimised, accounts
> abused). May you be so gentle to share your policyd configuration? It would
> be really helpful. Thank you in advanced.
>
I sent you an email with our configuration/notes. If anyone else is
interested, let me know.
ch
On Mon, Mar 03, 2014 at 05:08:08PM -0600, Noel Jones wrote:
> On 3/3/2014 4:45 PM, Jay G. Scott wrote:
> >
> > I have one user telling me that he has a long mailing list
> > (on the order of 34 -- hardly long) and some of the recipients
> > bounce. If he mails them one at a time the mail works --
Thank you Wietse,
You spurred me to look at the logs and take a closer look. The problem was an
old whitelist entry from when we were in the ISP business. Removing the entry
solved my problem.
Mike
On Tuesday, March 04, 2014 12:34:50 Wietse Venema wrote:
> Mike McGinn:
> > I ma getting some bac
Homer Wilson Smith wrote the following on 3/4/2014 4:38 PM:
Dear Gentle Folk,
What is the state of the art in dealing with users whose SASL password
has been compromised?
Running CentOS, and latest postfix.
When a password gets compromised, spam starts to pour out of the
server f
Am 04.03.2014 23:38, schrieb Homer Wilson Smith:
Change their password?
from my experience the only thing that really stops the spam
Maybe it's anoying for the account owner but it works most reliable.
Counting IPs might help also but what if the spammer uses the same src
ip for its garbage?
tejas sarade:
> Hello,
>
> My understanding is that 'size' field in the Postfix logs shows the size of
> mail including headers and body.
> Can someone tell me if it is correct.
The message content length including Postfix record boundaries
(typically two bytes per record).
The message content l
11 matches
Mail list logo