Pegasus Mail snapin for NWAdmin can cause delivery failure

bryroller

posted Oct 18 '07 at 8:50 pm

Not sure if this is more Mercury/32 or Pegasus Mail related. Please locate in the most logical or beneficial thread.

This snapin is great - it has made our

administration much easier. In using the snapin along with Mercury/32 v4.52(modules

S,P,E,D,X,I) in NDS mode, I have found a couple things that need to be changed

or added in the documentation (I am using v1.10b).

1. The syntax to ignore sorting and

place no spaces in front of the address reads Myforcefirst=N in the

documentation. What actually works (as found by turning on Mydebug) is

Forcefirst=N. I needed to get the "compute" function to remove the space

that gets added to the LDAP address by default.

2. The reason I found this error in

the documentation is that when using Mercury/32 + LDAP addresses + Pegasus Mail

(currently using v4.31), messages being sent to any yahoo address (US or Korea,

at least) are rejected because a space exists in the addresses. To get the

messages to deliver (to yahoo.com and some other domains), the leading space

must not be present in the address.

The MercuryE error that I've

commonly seen when trying to deliver messages where the sender LDAP address has

a leading space is “Connection error during handshake” or a 550 “…does not

conform…” .

Snapin can be found here:

http://prope.insa-lyon.fr/~ppollet/netware/smtpsnp/index.ssi

Not sure if this is more Mercury/32 or Pegasus Mail related. Please locate in the most logical or beneficial thread. This snapin is great - it has made our administration much easier. In using the snapin along with Mercury/32 v4.52(modules S,P,E,D,X,I) in NDS mode, I have found a couple things that need to be changed or added in the documentation (I am using v1.10b).<o:p> </o:p> 1. The syntax to ignore sorting and place no spaces in front of the address reads Myforcefirst=N in the documentation. What actually works (as found by turning on Mydebug) is Forcefirst=N. I needed to get the "compute" function to remove the space that gets added to the LDAP address by default.<o:p> </o:p> 2. The reason I found this error in the documentation is that when using Mercury/32 + LDAP addresses + Pegasus Mail (currently using v4.31), messages being sent to any yahoo address (US or Korea, at least) are rejected because a space exists in the addresses. To get the messages to deliver (to yahoo.com and some other domains), the leading space must not be present in the address.<o:p> </o:p> The MercuryE error that I've commonly seen when trying to deliver messages where the sender LDAP address has a leading space is “Connection error during handshake” or a 550 “…does not conform…” .<o:p></o:p> <o:p></o:p>Snapin can be found here:<o:p> </o:p> <a href="http://prope.insa-lyon.fr/%7Eppollet/netware/smtpsnp/index.ssi" title="http://prope.insa-lyon.fr/~ppollet/netware/smtpsnp/index.ssi" target="_blank" mce_href="http://prope.insa-lyon.fr/~ppollet/netware/smtpsnp/index.ssi">http://prope.insa-lyon.fr/~ppollet/netware/smtpsnp/index.ssi</a>

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history