Michael Munger:
> Bill:
>
> Thank you for both items. I shall pour over them.
And I have made a note to log the sender when rejecting the (MAIL
FROM) SIZE parameter.
Wietse
On 12/01/2016 09:37 AM, Wietse Venema wrote:
And I have made a note to log the sender when rejecting the (MAIL
FROM) SIZE parameter.
Wow. Wasn't expecting that! Thank you, sir.
> On Thu, Nov 17, 2016 at 10:18:01PM +0100, Walter Doekes wrote:
>> That looks like I have my DNS recursor to blame for the problem. It's a
>> powerdns recursor, version 4.0.0~alpha2 if I'm not mistaken.
>>
>> I'll be forwarding the issue with the appropriate evidence there if it
>> hasn't been fix
On 11/28/2016 at 4:56 PM, "Bill Cole"
wrote:
>
>On 28 Nov 2016, at 17:29, rich.gre...@hushmail.com wrote:
>
>> I changed it. When I compose and send to an outside domain now,
>I get
>> an error that hints towards port 25 being strongly preferred
>over 587.
>>
>> Sending of the message faile
I've been getting a lot of these errors for mail sent to Yahoo all of a
sudden:
421 4.7.0 [TSS04] Messages from 24.105.170.68 temporarily deferred due to user
complaints - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html
(in reply to MAIL FROM command))
The included link s
On Thu, Dec 01, 2016 at 03:35:40PM -0500, Fongaboo wrote:
> However we do have virtual aliases on hosted domains that ultimately point
> to yahoo.com addresses. Undoubtedly, I can reference instances of spam
> received to the virtual and then forwarded on to Yahoo's mailserver from
> there.
>
> B
Hi, I throttle my traffic to AOL and HOTMAIL, maybe you need to do the same for
Yahoo.
I had to lookup each ISP's limits to configure it in Postfix to help with all
the mail to them getting deferred.
I must say it has been years since users complained about mail not getting
delivered to those d
Fongaboo:
[forwarding spam to Yahoo and getting blocked]
> But can they really blame the middleman (us) for mail that is just passing
> through our hands? I mean, I understand it's possible for them to do
Absolutely. Yahoo is not the only one who does this, by the way.
Wietse
This sounds like a great idea. Where do you actually specify AOL's mail
servers for this rule?
On Thu, 1 Dec 2016, Fazzina, Angelo wrote:
Hi, I throttle my traffic to AOL and HOTMAIL, maybe you need to do the same for
Yahoo.
I had to lookup each ISP's limits to configure it in Postfix to h
Here, for my config anyway.
You can read the docs on how transport file works.
Good luck.
-ALF
/etc/postfix/maps/transport
# Slow transport for AOL
# 'slowaol' are configured in master.cf and main.cf
aol.com slowaol:aol.com
-Angelo Fazzina
Operating Systems Program
Okay, I'm made some exciting progress and I am grateful for the help. I will
show to people how I got this working
At first thought, I figured that it would simply be the IMAP password used by
Dovecot to access my mailbox. Not exactly true... I did some digging in some
blogs and the document
On 11/27/16 2:15 PM, li...@lazygranch.com wrote:
is there any situation where an unauthorized user needs to connect to port 587?
Not that I can think of.
The IPFW block is working fine. I also added blocking for 143 of course.
Original Message
From: @lbutlr
Sent: Thursday, December 1, 2016 4:42 PM
To: postfix-users@postfix.org
Subject: Re: Port 587 users question
On 11/27/16 2:15 PM, li...@lazygranch.com wrote:
> is there any situation wher
On 30 Nov 2016, at 22:18, Stefan Monnier wrote:
Don't chroot the Postfix smtp delivery agent. It will then notice
changes in /etc/resolv.conf, rather than using a stale copy in
the chroot jail. Better don't use chroot at all, unless it is
very carefully and robustly built.
Ha!
# find /v
On 1 Dec 2016, at 13:47, rich.gre...@hushmail.com wrote:
On 11/28/2016 at 4:56 PM, "Bill Cole"
wrote:
[...]
I made modifications to the master.cf file.
To get one, you need an entry similar to this in
your
master.cf file:
submission inet n - n - - smtpd
-
> Beyond Viktor's recommendation to NOT chroot Postfix, another option is to
> run Postfix on demand, since you appear to only be running it
> in a client-only mode. I'm not sure how you'd do that on Debian, but the
> general idea is to run 'master -e 60' whenever a file appears in the
> maildrop q
On 11/30/16 2:35 PM, Michael Munger wrote:
I am writing a log parser so that when users complain "so and so sent me
an email and I didn't get it" I can query the logs and find this with
ease. Ultimately, I want ot make this self service through a web page.
I went a different way. Users can chose
On 12/1/16 1:35 PM, Fongaboo wrote:
But can they really blame the middleman (us) for mail that is just
passing through our hands?
Yes they can, and they do. Unlike Google, which seems able to mostly
usally eventually figure this out, Yahoo mail has *always* been a source
of frustration because
18 matches
Mail list logo
