-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/04/2014 04:38 AM, M. Rodrigo Monteiro wrote:
> The port bind seems to be a IPv6 issue. Is there some way to
> prevent that?
>
> inet_protocols = ipv4
>
Thank you. That has allowed Postfix to start.
- --
James Moe
moe dot james at sohnen-mo
On 6/4/2014 11:27 AM, Hirayama, Pat wrote:
> Greetings,
>
> So, occasionally, I receive messages where the sender address gets mangled
> and what I get in my e-mail client is a combination of the sender's address
> AND the hostname of my MX server. This is annoying (primarily because it
> tend
Maarten Vanraes:
> hi,
>
> I'm using pipe for some delivery transport. the logs tell me something like:
>
> status=sent (delivered by )
>
> now my transport stores some parts in a database and possibly sends it back
> into postfix... so for audit purposes, it would be nice if the pipe transport
Greetings,
So, occasionally, I receive messages where the sender address gets mangled and
what I get in my e-mail client is a combination of the sender's address AND the
hostname of my MX server. This is annoying (primarily because it tends to be
spam, and my spam rules usually white list my d
On Wed, Jun 04, 2014 at 04:04:36PM +0200, Maarten Vanraes wrote:
> I'm using pipe for some delivery transport. the logs tell me something like:
>
> status=sent (delivered by )
>
> now my transport stores some parts in a database and possibly sends it back
> into postfix... so for audit purposes
hi,
I'm using pipe for some delivery transport. the logs tell me something like:
status=sent (delivered by )
now my transport stores some parts in a database and possibly sends it back
into postfix... so for audit purposes, it would be nice if the pipe transport
would get the first output line
James Moe:
> Jun 03 23:20:10 sma-server3 postfix[10741]: name_mask: all
> Jun 03 23:20:10 sma-server3 postfix[10741]: inet_addr_local:
> configured 2 IPv4 addresses
> Jun 03 23:20:10 sma-server3 postfix[10741]: inet_addr_local:
> configured 2 IPv6 addresses
Are they running Postfix with verbose mo
2014-06-04 3:44 GMT-03:00 James Moe :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> Port 126 is defined since port 25 is used by the main MTA. I am
> using postfix as a local transport.
> The port bind seems to be a IPv6 issue. Is there some way to prevent
> that?
>
>
inet_protocols
Am 03.06.2014 22:50, schrieb Peter Bittner:
Hi,
I'm trying to find out which is the correct way to configure alias
domains on postfix.
For example, I have 3 different domains (example.com, example.info,
example.net), and when I send an e-mail to a user on any of the three
domains it's always se
On 04/06/2014 11:01, Luigi Cirillo wrote:
Hi there,
I am trying to configure postfix on Debian 7 to manage virtual
domains. I tried to send an email from a test user, using
squirrelmail.
The system send the email as user.virtualdomain@hostname.fqdn.com.
How should I configure to send emails a
Hi there,
I am trying to configure postfix on Debian 7 to manage virtual
domains. I tried to send an email from a test user, using
squirrelmail.
The system send the email as user.virtualdomain@hostname.fqdn.com.
How should I configure to send emails as u...@virtualdomain.com?
This is my main.cf
11 matches
Mail list logo