The telnet works, here is the output:
Also, I checked to see if my user/pass work:
Using above perl command, I got a hash something like this:
***7QWERTYasdYWFk**
I tested that to make sure I get authenticated against the same relay server:
I guess it has to be Postfix. It's just not bringing up SASL to authenticate. Is there a way to debug that?
We have a redhat linux el4 and used as a mail server.We configured postfix.all r working fine.we got a problem for a particular user when he tries to open his mailbox and the error is mentioned below:
ERROR: Could not complete request.
Query: SELECT "INBOX"
Reason Given: Internal error... (3 Replies)
hi all.
Am using smtpd_recipient_restrictions & check_recipient_access in postfix.
The hash file looks like this:
emailaddress1 HOLD
emailaddress2 HOLD
The aim is to place email from these recipients in the hold directory,check them then reinject them back in postfix on some... (0 Replies)
Hi I have a Postfix mail server in a Debian Linux network and used to be able to connect to it on port 25 via telnet. I also have working DNS on the server.
I added this MX record to the DNS zone file:
@ IN MX 10 server.c4.sysinst.ida.liu.se.
It worked fine after that also but then... (3 Replies)
Hi guys
One of our clients have a problem with sending email to a certain domain. No matter what we try, the mails just dont get delivered.
What I did then, is created a new connector on their Exchange server, pointing all mail sent to their client at "domain1" to relay to our Postfix mail... (0 Replies)
Hi,
I did setup one E-mail Server with postfix/dovecot/squirrelmail on CentOS 5.x and is working fine.
I did configure SMTP authentication (without TSL/SSL) so that users from outside can send emails via our email server with SMTP auth. One weird issue i'm getting is that it's working from... (1 Reply)
Hi All!
I have a very annoying problem. I have an openSuSE box, running postfix on it. It is configured, to use gmail to send mails. It is working fine, I accept the messages, but the sender is my gmail account, not the linux box. How can I (if I can) configure postfix to send the mails with... (0 Replies)
hello all,
If i send mails using postfix,the mails stored in queue,not delivered to required recipient...can anyone please tell me the solution for this problem... (4 Replies)
Hello
I have a shell script, which should send email, if any error occurred. This script is running in Red Hat Linux 4.6, and want to configure postfix so it can relay to an Exchange Server.
The Authorization method of Exchange server, I guess is: 250-AUTH NTLM. So I have:
Server A ( Red... (1 Reply)
hi guys
i have a problem with postfix
i can't send any mail to yahoo clients but i cant receive email from yahoo clients
Feb 20 11:46:35 cp postfix/qmgr: 83F658003B: from=<ZZZ@XXX.org>, size=508, nrcpt=1 (queue active)
Feb 20 11:46:35 cp postfix/smtp: 83F658003B: to=<ZZZ@yahoo.com>,... (1 Reply)
Hello,
I have a problem remotely connecting to the postfix. It sais "Connection refused".
# telnet 104.200.16.232 25
Trying 104.200.16.232...
telnet: connect to address 104.200.16.232: Connection refused
But the postfix is started and running.
# telnet 127.0.0.1 25
Trying... (3 Replies)
Discussion started by: galford
3 Replies
LEARN ABOUT X11R4
dmxgetwindowattributes
DMXGetWindowAttributes(3X)DMXGetWindowAttributes(3X)NAME
DMXGetWindowAttributes - determine back-end window attributes
SYNOPSIS
#include <X11/extensions/dmxext.h>
Bool DMXGetWindowAttributes(Display *dpy,
Window window,
int *screen_count,
int available_count,
DMXWindowAttributes *attr);
DESCRIPTION
When calling DMXGetWindowAttributes(), window specifies the window ID of a window on the Xdmx(1) server and available_count specifies the
length of attr.
The number of screens for which information is available will be returned in screen_count and information about those screen will be
returned in attr. If screen_count is less than available_count, then information for all of the screens will be returned. Otherwise,
information for the first available_count screens will be returned.
The DMXWindowAttributes structure is:
typedef struct {
int screen;
Window window;
XRectangle pos, vis;
} DMXWindowAttributes;
For each back-end X server that displays a portion of window, this structure contains the physical screen containing that portion, the win-
dow ID on the back-end X server of the window containing that portion, the position and dimensions of the window on the back-end (pos, in
screen coordinates), and the visible area of the window on the back-end (vis, in window-relative coordinates -- all zeros if the window is
not visible on the backend).
To obtain more information about the physical screen use the DMXGetScreenAttributes(3X) call.
Note that DMX allows multiple back-end windows to overlap in their view of the DMX logical window. Further, a logical window does not have
to be completely covered by back-end windows -- there may be gaps.
As an example, consider a 500x500 window that spans the top two 1024x768 back-end displays (A and B) of a 2048x1536 DMX display composed of
4 1024x768 back-end displays arranged in a cube:
A B
C D
In this case, the DMXGetWindowAttributes call would return the following information for the 500x500 window:
display A: 500x500 window at 1024-250,0 (relative to back end)
with 250x500 visible at 0,0 (relative to window origin)
display B: 500x500 window at -250,0 (relative to back end)
with 250x500 visible at 250,0 (relative to window origin)
display C: 500x500 window at 1024-250,-768 with 0x0 visible at 0,0
display D: 500x500 window at -250,-768 with 0x0 visible at 0,0
RETURN VALUE
DMXGetWindowAttributes() returns True unless there is a protocol error.
DMXGetWindowAttributes() can generate BadWindow and BadAlloc errors.
NOTES
Because this call transports a great deal of information over the wire, please call DMXGetScreenCount(3X) first, and make sure attr is suf-
ficiently large.
On a particular back-end server, it is possible that the associated window has not yet been mapped because the XMapWindow(3X) call that
will eventually map the window had been buffered by Xlib's normal buffering system. To avoid this race condition, please call DMXSync(3X)
before communicating directly with the back-end X server.
SEE ALSO DMXGetScreenCount(3X), DMXSync(3X), DMXGetScreenAttributes(3X), DMX(3X), Xdmx(1)X Version 11 libdmx 1.0.2 DMXGetWindowAttributes(3X)