Hi,
I have a mail receiving server setup , I use Postfix as my mail receiving
server and use the 'sid-milter' (http://sourceforge.net/projects/sid-milter/)
as provided by postfix add-on Software(http://www.postfix.org/addon.html) page
to verify incoming mail's sender-ID and SPF.
Here I am gett
Hi All,
I wanted to differentiate the incoming emails depending on whether they are
generated by same server postfix (e.g. NDR) or being delivered to it by
some smtp client. Is there a easy way to relay all mails generated through
postfix to a different custom transport rule while saving the gener
On 06/17/2013 11:56 AM, Ashay Chitnis wrote:
Hi All,
I wanted to differentiate the incoming emails depending on whether
they are generated by same server postfix
Mail can be submitted locally in several ways; smtp is usually not the
most prevalent way.
sendmail(1) submission is not subject t
On 6/16/2013 12:59 PM, Viktor Dukhovni wrote:
> On Sun, Jun 16, 2013 at 07:55:28AM -0500, Stan Hoeppner wrote:
>
>>> Looks more like a botnet, so the connections may not in fact recur.
>>
>> Quite right, it is a botnet attack. And without further logging, I'd
>> guess this is a DOS attack on TCP
Sharma, Ashish:
> Hi,
>
> I have a mail receiving server setup , I use Postfix as my mail receiving
>-server and use the 'sid-milter' (http://sourceforge.net/projects/sid-milter/
>-) as provided by postfix add-on Software(http://www.postfix.org/addon.html)
>-page to verify incoming mail's sender
On 6/8/13 9:09 AM, DTNX Postmaster wrote:
On Jun 8, 2013, at 17:16, Asai wrote:
On 6/7/2013 4:26 PM, DTNX Postmaster wrote:
The Mail.app applications on iOS (iPhones or iPads) or OS X will
attempt to autodetect the port to connect to; 25, 465, and 587. It
works just fine over the submission p
It would not surprise me in the least to find out I did something wrong. :-}
I know I did "yum install db4-devel" as part of packages I believed
were prerequisites to installing Postfix.
My recall is that I was missing a /usr/include file when test building
a Postfix and I did a "yum provides" t
Robert Lopez:
> It would not surprise me in the least to find out I did something wrong. :-}
>
> I know I did "yum install db4-devel" as part of packages I believed
> were prerequisites to installing Postfix.
> My recall is that I was missing a /usr/include file when test building
> a Postfix an
Asai:
> After investigating this issue further, it looks like there might be
> something I'm missing regarding postscreen. My reasoning for this is
> yesterday a client said she couldn't send email. I looked at her phone
> and the postfix logs and could see that her IP address was being
> rej
On 6/17/13 1:13 PM, Wietse Venema wrote:
Asai:
After investigating this issue further, it looks like there might be
something I'm missing regarding postscreen. My reasoning for this is
yesterday a client said she couldn't send email. I looked at her phone
and the postfix logs and could see tha
On 6/17/13 1:13 PM, Wietse Venema wrote:
Asai:
After investigating this issue further, it looks like there might be
something I'm missing regarding postscreen. My reasoning for this is
yesterday a client said she couldn't send email. I looked at her phone
and the postfix logs and could see tha
On Mon, Jun 17, 2013 at 2:11 PM, Wietse Venema wrote:
> I suggest that you install a compiled version of Postfix, and that
> you use a simpler program to become familiar with the process of
> building your own binaries.
There existed a project goal to install a postfix with postscreen.
The goal
Asai:
> After investigating this issue further, it looks like there might be
> something I'm missing regarding postscreen. My reasoning for this is
> yesterday a client said she couldn't send email. I looked at her phone
> and the postfix logs and could see that her IP address was being
> rejecte
Asai:
After investigating this issue further, it looks like there might be
something I'm missing regarding postscreen. My reasoning for this is
yesterday a client said she couldn't send email. I looked at her phone
and the postfix logs and could see that her IP address was being
rejected by pos
On 06/18/2013 12:15 AM, Asai wrote:
Would it follow then that I should remove the
smtp_sasl_mechanism_filter from main.cf? Would that be causing
clients to try to connect via port 25 even though they're set to
connect to 587?
...what makes you think these things are related in any way ?
I
On 06/18/2013 12:15 AM, Asai wrote:
Would it follow then that I should remove the
smtp_sasl_mechanism_filter from main.cf? Would that be causing
clients to try to connect via port 25 even though they're set to
connect to 587?
...what makes you think these things are related in any way ?
I
Asai:
After investigating this issue further, it looks like there might be
something I'm missing regarding postscreen. My reasoning for this is
yesterday a client said she couldn't send email. I looked at her phone
and the postfix logs and could see that her IP address was being
rejected by pos
Asai:
> Would it follow then that I should remove the smtp_sasl_mechanism_filter
> from main.cf? Would that be causing clients to try to connect via port
No. The CLIENT connects to the WRONG Postfix port.
Wietse
On Jun 17, 2013, at 17:27, Asai wrote:
>> On 06/18/2013 12:15 AM, Asai wrote:
>>> Would it follow then that I should remove the smtp_sasl_mechanism_filter
>>> from main.cf? Would that be causing clients to try to connect via port 25
>>> even though they're set to connect to 587?
>>
>> ...what
So, it's the iPhone which is self-assertively trying to connect to port 25
regardless of what it's explicitly set to?
Works fine for me. I very much doubt your iPhone in question is actually set to
use 587 only. IIRC, that is not the default.
-- Larry Stone
Sent from my iPhone
OK, so perha
On Jun 17, 2013, at 19:03, Asai wrote:
>>> So, it's the iPhone which is self-assertively trying to connect to port 25
>>> regardless of what it's explicitly set to?
>> Works fine for me. I very much doubt your iPhone in question is actually set
>> to use 587 only. IIRC, that is not the default.
21 matches
Mail list logo
