d.h...@yournetplus.com wrote:
> Quoting mouss :
>
>> Russell Jones wrote:
>>> Actually that's all the logs show when sending to a non-existent address
>>> that resides on the same physical server, but I got it figured it.
>>>
>>> Believe it or not, it was actually my AVG antivirus. It turns out th
Quoting mouss :
Russell Jones wrote:
Actually that's all the logs show when sending to a non-existent address
that resides on the same physical server, but I got it figured it.
Believe it or not, it was actually my AVG antivirus. It turns out that
when scanning outgoing mail, by default AVG wi
Russell Jones wrote:
> Actually that's all the logs show when sending to a non-existent address
> that resides on the same physical server, but I got it figured it.
>
> Believe it or not, it was actually my AVG antivirus. It turns out that
> when scanning outgoing mail, by default AVG will use its
Charles Marcus wrote:
> On 9/28/2009 7:19 AM, Noel Jones wrote:
>>> For some reason, if a local user sends mail to another local user who
>
>> If your client doesn't notify you that the mail can't be delivered, it's
>> a client configuration problem.
>
> It sounds to me like this postfix instance
On 9/28/2009 9:40 AM, Russell Jones wrote:
Actually that's all the logs show when sending to a non-existent address
that resides on the same physical server, but I got it figured it.
Believe it or not, it was actually my AVG antivirus. It turns out that
when scanning outgoing mail, by default AV
Actually that's all the logs show when sending to a non-existent address
that resides on the same physical server, but I got it figured it.
Believe it or not, it was actually my AVG antivirus. It turns out that
when scanning outgoing mail, by default AVG will use its own "Auto SMTP
server". Fo
On 9/28/2009 7:19 AM, Noel Jones wrote:
>> For some reason, if a local user sends mail to another local user who
> If your client doesn't notify you that the mail can't be delivered, it's
> a client configuration problem.
It sounds to me like this postfix instance *is* the client... or, it is
the
On 27-Sep-2009, at 23:41, Russell Jones wrote:
Sep 28 00:29:58 server2 postfix/smtpd[3447]: NOQUEUE: reject: RCPT
from c-98-197-128-40.hsd1.tx.comcast.net[98.197.128.40]: 550 5.1.1 >: Recipient address rejected: User unknown in virtual alias table;
from=
"550 5.1.1 : Recipient address reject
Russell Jones:
> For some reason, if a local user sends mail to another local user who
> doesn't exist, my Postfix installation doesn't seem to notify the sender
> of the error, nor deliver a bounce message to the sender.
...
> Sep 28 00:29:58 server2 postfix/smtpd[3447]: NOQUEUE: reject: RCPT fr
On 9/28/2009 12:41 AM, Russell Jones wrote:
For some reason, if a local user sends mail to another local user who
doesn't exist, my Postfix installation doesn't seem to notify the sender
of the error, nor deliver a bounce message to the sender.
Log snippet of what I am talking about:
Sep 28 00:
On 9/28/2009, Russell Jones (rjo...@eggycrew.com) wrote:
> On my older, production Exim server, ths popup occurs immediately.
Per the welcome message you received when you joined the list:
TO REPORT A PROBLEM see:
http://www.postfix.org/DEBUG_README.html#mail
At a minimum, postfix version and ou
For some reason, if a local user sends mail to another local user who
doesn't exist, my Postfix installation doesn't seem to notify the sender
of the error, nor deliver a bounce message to the sender.
Log snippet of what I am talking about:
Sep 28 00:29:48 server2 dovecot: imap-login: Login:
12 matches
Mail list logo
