It is also doing it in my pop3/e-mail client software of outlook and mac mail on my mac. so it is not just web mail.

I have not made any changes to my main.cf sense i built this system, and that was months ago where as this problem just started.

I did reboot my router and it all kicked in with one exception..so my router was causing 95% of it.

now the remaining problem is i can use my pop3/outlook mail program using my ispconfig server smtp server to send to HOTMAIL and i get it. BUT when i use the web mail to send to HOTMAIL hot mail never gets it. (note: aol and others get my web mail but not hotmail)

here is a copy of the mail log after i sent a message in WEBMAIL to my HOTMAIL account (still yet to get the message in hotmail)

Normally i do not use Hotmail, but i wanted to check wat was happening...
I did a test and i discovered that when i send an e-mail to hotmail, it will never reach the mailbox...
I guess we need a little help here.

Okay I found something out...I can get mail in hotmail when i address to multiple people in a field like to or cc but ONLY as long as the hotmail address is not last and here is why.

I found in AOL mail & hotmail looking at the headers of message's sent from my ISPConfig's webmail that it is putting quotes and @domain.com added to the end of the last email address in the address field.

here is an example of one that i got in hotmail because the hotmail address was not the last address:

# The sender_canonical_maps parameter specifies optional address
# mapping lookup tables for envelope and header SENDER addresses.
#
# For example, you want to rewrite the SENDER address user@ugly.domain
# to user@pretty.domain, while still being able to send mail to the
# RECIPIENT address user@ugly.domain.
# See man 5 canonical, /etc/postfix/canonical or
# /etc/postfix/sample-canonical.cf for more details

contents of /etc/postfix/canonical

Code:

# CANONICAL(5) CANONICAL(5)
#
# NAME
# canonical - Postfix canonical table format
#
# SYNOPSIS
# postmap /etc/postfix/canonical
#
# postmap -q "string" /etc/postfix/canonical
#
# postmap -q - /etc/postfix/canonical <inputfile
#
# DESCRIPTION
# full description removed for these forums
#
#
# TABLE FORMAT
# The input format for the postmap(1) command is as follows:
#
# pattern result
# When pattern matches a mail address, replace it by
# the corresponding result.
#
# blank lines and comments
# Empty lines and whitespace-only lines are ignored,
# as are lines whose first non-whitespace character
# is a `#'.
#
# multi-line text
# A logical line starts with non-whitespace text. A
# line that starts with whitespace continues a logi-
# cal line.
#
# TABLE SEARCH ORDER
# With lookups from indexed files such as DB or DBM, or from
# networked tables such as NIS, LDAP or SQL, patterns are
# tried in the order as listed below:
#
# user@domain address
# Replace user@domain by address. This form has the
# highest precedence.
#
# This is useful to clean up addresses produced by
# legacy mail systems. It can also be used to pro-
# duce Firstname.Lastname style addresses, but see
# below for a simpler solution.
#
# user address
# Replace user@site by address when site is equal to
# $myorigin, when site is listed in $mydestination,
# or when it is listed in $inet_interfaces or
# $proxy_interfaces.
#
# This form is useful for replacing login names by
# Firstname.Lastname.
#
# @domain address
# Replace other addresses in domain by address. This
# form has the lowest precedence.
#
# RESULT ADDRESS REWRITING
# The lookup result is subject to address rewriting:
#
# o When the result has the form @otherdomain, the
# result becomes the same user in otherdomain.
#
# o When "append_at_myorigin=yes", append "@$myorigin"
# to addresses without "@domain".
#
# o When "append_dot_mydomain=yes", append ".$mydomain"
# to addresses without ".domain".
#
# ADDRESS EXTENSION
# When a mail address localpart contains the optional recip-
# ient delimiter (e.g., user+foo@domain), the lookup order
# becomes: user+foo@domain, user@domain, user+foo, user, and
# @domain.
#
# The propagate_unmatched_extensions parameter controls
# whether an unmatched address extension (+foo) is propa-
# gated to the result of table lookup.
#
# REGULAR EXPRESSION TABLES
# This section describes how the table lookups change when
# the table is given in the form of regular expressions. For
# a description of regular expression lookup table syntax,
# see regexp_table(5) or pcre_table(5).
#
# Each pattern is a regular expression that is applied to
# the entire address being looked up. Thus, user@domain mail
# addresses are not broken up into their user and @domain
# constituent parts, nor is user+foo broken up into user and
# foo.
#
# Patterns are applied in the order as specified in the ta-
# ble, until a pattern is found that matches the search
# string.
#
# Results are the same as with indexed file lookups, with
# the additional feature that parenthesized substrings from
# the pattern can be interpolated as $1, $2 and so on.
#
# TCP-BASED TABLES
# This section describes how the table lookups change when
# lookups are directed to a TCP-based server. For a descrip-
# tion of the TCP client/server lookup protocol, see tcp_ta-
# ble(5). This feature is not available up to and including
# Postfix version 2.2.
#
# Each lookup operation uses the entire address once. Thus,
# user@domain mail addresses are not broken up into their
# user and @domain constituent parts, nor is user+foo broken
# up into user and foo.
#
# Results are the same as with indexed file lookups.
#
# BUGS
# The table format does not understand quoting conventions.
#
# CONFIGURATION PARAMETERS
# The following main.cf parameters are especially relevant.
# The text below provides only a parameter summary. See
# postconf(5) for more details including examples.
#
# canonical_classes
# What addresses are subject to canonical address
# mapping.
#
# canonical_maps
# List of canonical mapping tables.
#
# recipient_canonical_maps
# Address mapping lookup table for envelope and
# header recipient addresses.
#
# sender_canonical_maps
# Address mapping lookup table for envelope and
# header sender addresses.
#
# propagate_unmatched_extensions
# A list of address rewriting or forwarding mecha-
# nisms that propagate an address extension from the
# original address to the result. Specify zero or
# more of canonical, virtual, alias, forward,
# include, or generic.
#
# Other parameters of interest:
#
# inet_interfaces
# The network interface addresses that this system
# receives mail on. You need to stop and start Post-
# fix when this parameter changes.
#
# local_header_rewrite_clients
# Rewrite message header addresses in mail from these
# clients and update incomplete addresses with the
# domain name in $myorigin or $mydomain; either don't
# rewrite message headers from other clients at all,
# or rewrite message headers and update incomplete
# addresses with the domain specified in the
# remote_header_rewrite_domain parameter.
#
# proxy_interfaces
# Other interfaces that this machine receives mail on
# by way of a proxy agent or network address transla-
# tor.
#
# masquerade_classes
# List of address classes subject to masquerading:
# zero or more of envelope_sender, envelope_recipi-
# ent, header_sender, header_recipient.
#
# masquerade_domains
# List of domains that hide their subdomain struc-
# ture.
#
# masquerade_exceptions
# List of user names that are not subject to address
# masquerading.
#
# mydestination
# List of domains that this mail system considers
# local.
#
# myorigin
# The domain that is appended to locally-posted mail.
#
# owner_request_special
# Give special treatment to owner-xxx and xxx-request
# addresses.
#
# remote_header_rewrite_domain
# Don't rewrite message headers from remote clients
# at all when this parameter is empty; otherwise, re-
# write message headers and append the specified
# domain name to incomplete addresses.
#
# SEE ALSO
# cleanup(8), canonicalize and enqueue mail
# postmap(1), Postfix lookup table manager
# postconf(5), configuration parameters
# virtual(5), virtual aliasing
#
# README FILES
# Use "postconf readme_directory" or "postconf html_direc-
# tory" to locate this information.
# DATABASE_README, Postfix lookup table overview
# ADDRESS_REWRITING_README, address rewriting guide
#
# LICENSE
# The Secure Mailer license must be distributed with this
# software.
#
# AUTHOR(S)
# Wietse Venema
# IBM T.J. Watson Research
# P.O. Box 704
# Yorktown Heights, NY 10598, USA
#
# CANONICAL(5)

THanks edge, but my problem with hotmail is the extra domain info being tagged at the end of the last email address addressed to.

IE: TO: *****@hotmail.com, "*****@aim.com"@on****cs.com

above shows a message address format that will go to HOTMAIL because the hotmail address is ok. but if the hotmail address was the only address or the last address my server is adding the extra domain.com to the end of a vaild email address causing it not to get to hotmail.

Falko,
I did those commands and then went into webmail sent a message TO: my aim and CC: my hotmail. THe message went to my hotmail just fine then!!! so then i tried a second message just to my hotmail and NOTHING.

so now it looks like it is no longer putting the @domain.com at the end of the last email address in a field so that is fixed but my webmail is still not going through 100% to hotmail. but all my POP/OUTLOOK mail sending to hotmail using my ISPConfig smtp server DO go through.

Here is a copy of my mail log unedited...this log first shows a message sent UN-SUCCESSFULLY to my hotmail then it shows a 2nd message TO: my AIM and HOTMAIL. My AIM got it great but still nothing in my hotmial.

(I leave you these 3 code sets in hopes you see something causing this...i compared the last two and they looked idential to me but only one delievered) THANKS!